How it works
A structured engagement, not a software purchase
We start by understanding how your central team and schools actually operate, then build around that.
1. Discovery call
A conversation about your trust structure, current systems, pressures and priorities. No obligation and no product tour.
2. Operations and systems review
We map how work currently flows, which systems hold what, which spreadsheets are load-bearing and where the gaps are.
3. System blueprint
A written proposal: the modules, dashboards, workflows, integrations, AI scope, phasing, assumptions and limitations.
4. Phased implementation
We configure the common platform, then build the trust-specific parts in agreed phases with visible progress.
5. Pilot
A pilot school or central function uses the system for real work so it can be corrected before it spreads.
6. Trust rollout
Rollout school by school with training, role-based access, data checks and support for local variation.
7. Continuous improvement
Regular review of usage, exceptions and priorities, with ongoing configuration, new workflows and new reports.
Management questions workshop
We begin with your questions—not our dashboards.
Before anything is designed, we work with trust leaders to write down the questions the trust actually needs answered.
- What do we need to know every day, week, month and term?
- Which issues currently take too long to identify?
- Which reports require manual spreadsheet work?
- Where do different systems give conflicting answers?
- Which decisions lack sufficient evidence?
- Where do schools repeatedly submit the same information?
- Which trends should trigger professional review?
- How should responsibility pass from central teams to schools?
- How will we measure whether an intervention worked?
- Which AI use cases would create genuine benefit?
The technology is configured around the management questions that matter to the trust.
What we need from you
A successful project depends on
- An executive sponsor with authority to decide
- Access to the people who run the processes
- Agreement on which processes should be consistent
- Named owners for data and for each workflow
- Time from schools during pilot and rollout
What we commit to
How we work
- Plain descriptions of what will and will not be delivered
- Phased delivery with something usable early
- Honest limitations recorded in the blueprint
- Your data remains yours, with agreed export
- Continuous improvement rather than a fixed handover
Timescales and scope depend on the size of the trust, the systems involved and the availability of supplier access. Every engagement is scoped individually.
Book a discovery call
Tell us how your trust currently operates and where the work falls between systems.