The Microsoft Partner for Schools and Multi-Academy Trusts. One Connected Trust, Not Thirty Systems.
Your schools already run on Microsoft. We build the layer that connects everything around it: apps, automation and AI agents that do the re-keying, chasing and report-building your central team currently does by hand. Everything runs inside your own Microsoft 365 tenant, and a person approves an agent's work before anything goes out.
The challenge
The Gaps Between Your Systems Are Where the Time Goes.
MIS, finance, HR, safeguarding, assessment. Most trusts run on decent systems that were never designed to talk to each other. People fill the gaps: re-keying data, chasing colleagues and rebuilding the same numbers every month.
The Same Data, Typed Into Four Places
Census returns, DfE submissions and board packs are assembled by hand from each school's MIS, the finance ledger and a folder of spreadsheets. The numbers rarely reconcile first time, so your central team spends days each cycle finding out why. The work is invisible until someone leaves and nobody else knows how the spreadsheet works.
Statutory returns built by hand from systems that do not reconcileNobody Has One Number for the Trust
Ask a simple trust-wide question, like attendance this term against last, or spend against budget by school, and the answer takes a week of chasing. Leaders end up making decisions from spreadsheets that were already stale when they were sent. The data exists. It just lives in five places under five different definitions.
Trust-wide questions answered by chasing, not by lookingEvery New School Adds Another System
Growth is the plan, but each school that joins brings its own MIS configuration, its own finance codes and its own way of recording everything. Central teams are expected to absorb the extra aggregation work with the same headcount. The manual workaround that coped with eight schools breaks at fifteen.
Consolidation keeps growing: over 1,100 trusts and counting (DfE, 2025)How we deliver
From Scope to Go-Live. Four Phases, No Surprises.
Phase 1
Discovery & Design
1–2 weeksPhase 2
Configure & Build
2–8 weeksPhase 3
Test & Train
1–2 weeksPhase 4
Go Live
OngoingBuilt for your DPO as much as your COO
Pupil Data Stays in Your Tenant. Full Stop.
AI in a school lives or dies in information governance review, and it should. Everything we build runs inside your trust's own Microsoft 365 tenant, under the security, residency and retention controls you already operate. Agents act with named permissions, every action is logged, and a person approves anything that leaves the building. We support your DPIA from day one rather than treating it as an obstacle.
What you can verify today
- ✓Microsoft Solutions Partner, verifiable in Microsoft's partner directory
- ✓Everything runs in your own Microsoft 365 tenant, nothing hosted by us
- ✓A person approves every agent action that goes outside the trust
- ✓The licences each solution needs, listed in writing before you commit
The AI and Application Audit
We audit the applications your schools run today and show you, honestly, where AI and automation would genuinely help and where they would not. You keep the written report. No pitch at the end, and no follow-up unless you ask for one.
- A map of every application your schools run and where they do and do not connect
- The re-keying list: where central and school staff time actually goes
- Where AI and automation would pay for themselves first, and where to leave well alone
- What your existing Microsoft licences cover, and a written report within 5 working days