Enterprise
Practice your whole workforce can do, with the numbers to prove it worked
Your organisation buys sessions. Your admins hand them to teams and people. Every conversation comes back as a score, a transcript and a line on a dashboard your L&D team and your executives can read.
How a rollout works
From one admin account to a practising workforce
Four steps, each done by the person who owns it. Nothing needs Evolve in the loop after onboarding.
What each role sees
Three profiles, one loop
The organisation admin funds and oversees, team admins run their teams, learners practise. Each sees exactly what they need and nothing they should not.
Organisation Admin
Pays for the sessions and answers for the rollout.
- Create teams, appoint team admins and invite people with the role they will hold on acceptance
- Allocate sessions from the organisation pool to each team, and pull unused ones back
- Organisation-wide dashboards: adoption, average score and trend, capability lift, and a team-by-team comparison
- Open any learner's scorecard, coaching notes, feedback and full transcript in the organisation
- Export the organisation report and the sessions table as CSV or JSON, and push every run to your LMS or LRS as xAPI
Team Admin
Builds, assigns and reviews for their own team.
- Build simulations in the no-code builder and practise them on the organisation's sessions
- Assign a simulation to one person or the whole team, with a due date and a session cap
- See who has not started, who is in progress, who is done and who is overdue
- Team dashboard: participation, average score and trend, capability lift, top movers and coaching priorities
- Open each person's runs, feedback and transcript, confirm or amend a score with an audit trail, and export the team report
Learner
Practises what their team admin assigns.
- A clear list of assigned simulations with due dates
- Private, spoken practice with a realistic AI persona, repeated as often as the quota allows
- Rubric-based feedback and a transcript the moment the conversation ends
- Their own results, progress over attempts, and certificates for passes
Reporting that justifies the spend
Numbers your L&D team can take to the board
The organisation is paying for every session. Every session leaves a record it can read, compare and export.
- Team and organisation dashboards. Completion against assignments, average score and trend, capability lift over attempts, and the simulations and criteria people struggle with.
- Team-by-team comparison. Organisation admins see every team side by side. A team of fewer than five learners shows as too small to report, so no individual is ever exposed as an aggregate.
- Drill down to the person. Any learner's runs, grouped by simulation, with each scorecard, the coaching notes, the rubric evidence and the full transcript of the conversation.
- Exports for the people who ask. The organisation and team reports and the filtered sessions table download as CSV or JSON. Nothing needs re-typing.
- xAPI to your LMS or LRS. Every run is recorded as xAPI statements and can be pushed to the learning record store you already report from.
What Enterprise adds
Enterprise, next to the two self-serve tiers
Creator Seats and Learner Passes are bought in the portal in a couple of clicks. Enterprise is the whole organisation on one agreement.
| Feature | Enterprise | Creator Seat | Learner Pass |
|---|---|---|---|
| Who buys the sessions | The organisation, on an annual agreement | The trainer, monthly or annually | The individual, five at a time |
| Organisation, teams and roles | Yes: org admins, team admins, learners | Invite by email, workshop links, embeds and a share link | Not included |
| Assignments with due dates and session caps | Yes, to people or whole teams | Yes, to your clients | Not included |
| Dashboards | Team and organisation, with per-team comparison | Client Results, per person | Own results only |
| Scorecard, feedback and transcript review | Every learner in scope, with an audit trail | Every client run | Own runs only |
| Exports and xAPI | CSV, JSON and xAPI to your LRS | CSV of every client run | Own results |
| Who builds simulations | HR, L&D and team admins | The seat holder | Nobody, practice only |
| SSO, audit log and support | SSO, append-only audit log, named account manager | Priority support | Standard support |
Trust
Built for procurement to say yes to
Single sign-on and role-based access at organisation and team level
Every AI score can be confirmed, amended or voided by a human, with the reason recorded
Training data held and processed in Australia
Bespoke characters and scenarios remain your intellectual property
An append-only audit log of privileged actions your admins can review and export
A published list of every subprocessor and the region it processes data in
Enterprise FAQ
The questions procurement and L&D ask first
- How are sessions bought and allocated?
- Your organisation buys sessions on an annual agreement, invoiced quarterly, at a volume rate. A session is one 10-minute practice conversation; a run that ends inside its first minute is a misfire and is not charged, and anything longer is one whole session. Organisation admins allocate sessions from the pool to teams and can pull unused ones back; team admins assign them to people with a due date and a cap. Learners never buy anything.
- What can an admin see about an individual?
- A team admin sees their team; an organisation admin sees the whole organisation. For each learner in scope: every run grouped by simulation, the scorecard and rubric evidence, the coaching notes, and the full transcript of the conversation. Aggregates across a team are withheld below five learners so a small team never exposes one person.
- How do results reach our LMS or LRS?
- Every run is recorded as xAPI statements, the modern standard that replaces SCORM. Push them to the learning record store you already use, or export the organisation report, the team report or the sessions table as CSV or JSON. We do not offer SCORM or LTI packages.
- What happens at rollout?
- Your account manager sets up the organisation with you: single sign-on if you use it, the first teams and team admins, the session allocation, and any bespoke characters and scenarios, which remain your intellectual property. After that your admins run it. Evolve supplements your facilitated training and debrief; it does not replace them.
- How long is a session, and what counts as one?
- A session is one 10-minute spoken conversation with an AI persona, scored against the rubric the moment it ends. A run that lasts three minutes and a run that lasts the full 10 both count as one session. A run shorter than 1 minute is a misfire: a closed tab, a microphone that never connected, the wrong simulation opened by mistake. It is not charged at all.
Give every employee a safe place to practise
See Evolve in action with a scenario built for your team. No production crew, no scheduling — and it reinforces the facilitator-led training you already run rather than replacing it.