A SCOPE THAT MAKES SENSE FOR YOU
Compare the work, before comparing the price.
Use these adoption patterns to compare responsibilities, change effort, and dependencies. Take an agreed requirements list into the quotation process.
Compare the connected work, implementation needs and ownership in each approach.
CHOOSE A STARTING POINT
What should your first scope look like?
These are planning patterns, not fixed packages or contractual entitlements.
ONE COHERENT FIRST PHASE
Focused start
For an institution beginning with a small group of connected workflows and clear process owners.
An admissions-to-enrolment pilot, or a shared student record with attendance and family updates.
- Define one learner population and the first participating teams.
- Connect the essential record, access rules, and two or three workflows.
- Validate a sample migration before the initial launch.
- Agree a review point before expanding the scope.
Put the dependencies side by side.
| Consideration | Focused start | Whole institution | Education group |
|---|---|---|---|
| Starting population | Selected cohort or team | Institution-wide roles | Multiple institutions or campuses |
| Process coverage | A connected first workflow | Cross-department operations | Group standards and campus variations |
| Data preparation | Essential active records | Shared records and relevant history | Cross-campus mapping and reconciliation |
| Decision ownership | Named pilot owner | Institutional steering team | Group governance and campus leads |
| Reporting | First-phase measures | Institution-wide definitions | Consolidated and campus-level views |
| Rollout planning | Pilot, review, expand | Phases aligned to dependencies | Wave plan with campus readiness gates |
| Commercial scope | Confirm capabilities, onboarding, and support | Confirm migration, integrations, and training | Confirm group governance and service requirements |
Account for the whole change.
Platform scope
Learner and staff populations, institutions, capabilities, role access, and any agreed usage assumptions.
Implementation work
Configuration, data preparation and reconciliation, integrations, training, and launch support.
Ongoing responsibilities
Support routes, administrative ownership, update communication, and how later requirements are reviewed.
Compare your scopeFocused adoption → Education groupSEE HOW THE WORK CONNECTS
Compare complete operating scopes
Compare the connected work, implementation needs and ownership in each approach.
- 01
Focused adoption
Compare the connected work, implementation needs and ownership in each approach.
- 02
Whole institution
Compare the connected work, implementation needs and ownership in each approach.
- 03
Education group
Compare the connected work, implementation needs and ownership in each approach.
Illustrative workflow · Shape the details around your institution.
Pricing questions, answered clearly.
Is there a public per-student price?
This website does not publish a fixed tariff. Submit your institution’s scale and priorities to request a scoped quotation; the form does not commit you to a purchase.
Are all 69 capabilities automatically included?
The directory describes the breadth of education workflows to explore. Your proposal must identify the capabilities and service scope included for your institution.
Can we begin with a smaller scope?
Yes—use the focused-start pattern to identify a coherent first phase. Include the shared records and controls that phase depends on, then define a review before expansion.
How can we compare proposals fairly?
Compare the same population, workflows, migration assumptions, integrations, training effort, and support responsibilities. Ask for exclusions and acceptance criteria alongside the price.
TAKE THE NEXT STEP
Turn your priorities into a requirements brief.
Share your scale, preferred timing, and the processes you want to improve first.