The MAT That Saved £50,000 by Consolidating Systems

Ask a multi-academy trust business manager where the money goes and you will hear about staffing, energy and buildings. Those are the big, visible lines on a budget. What rarely gets the same scrutiny is the quiet accumulation of software subscriptions — the £4 per pupil here, the £900 annual licence there, the module someone added three years ago that nobody has reviewed since. Individually they look trivial. Collectively, across six schools, they can swallow the equivalent of a teaching post.

The trust in this case study is a composite, drawn from patterns we see repeatedly when trusts audit their school admin software for the first time. The numbers are realistic rather than exceptional. If anything, trusts that have never done this exercise tend to be surprised by how conservative a figure like £50,000 turns out to be.

The Hidden Cost of a Patchwork System

Most trusts did not set out to run a dozen platforms. They grew into them. One school adopted a parent messaging app because its previous newsletter system was unreliable. Another bought a standalone EYFS observation tool because the trust-wide MIS could not handle Development Matters properly. A third signed up for an online payments provider after a school trip reconciliation went badly wrong. Each decision was sensible in isolation.

The problem is that overlapping systems do not just duplicate cost — they duplicate work. Pupil data has to be kept current in several places. Staff need training on each interface. Parents end up juggling multiple logins and, inevitably, miss things. And every additional data processor means another data processing agreement, another GDPR review, another supplier to chase when something breaks.

The Audit: Fourteen Systems, Six Schools

The exercise began with a spreadsheet and a simple instruction to every headteacher and office manager: list every piece of software your school pays for, including anything billed to a departmental budget or renewed by direct debit. The trust expected to find seven or eight platforms. It found fourteen.

Four of them did essentially the same job as something else in the stack. Two had not been logged into in over a year but were still being billed annually. Three were being used by a single member of staff each. Only one school could produce an accurate record of what it was paying per pupil.

Roughly two thirds of the saving came from straightforward subscription elimination. The remainder came from lower payment processing fees and from reclaiming administrative time that had been absorbed by maintaining the patchwork. That last category is the one trusts routinely leave off the spreadsheet, and it is often the largest.

What Consolidation Actually Looked Like

Consolidation is not a single switch-flip, and any supplier who tells you otherwise should be treated with suspicion. The trust ran the migration over two terms. It started with the two schools most frustrated by their existing school communication tools, used them as pilots, then rolled out to the remaining four with the pilot heads acting as internal advocates.

Sequencing mattered. Communication and announcements moved first, because that delivered a visible win for parents within days. Observations and assessment followed, timed to the start of a term so that no teacher had to migrate half-finished EYFS records mid-cycle. Payments and clubs booking went last, deliberately scheduled away from trip season.

We thought we were buying a cheaper platform. What we actually bought back was staff time — and that turned out to be worth considerably more than the licence fees we cancelled.

The trust also made a decision that proved important: it resisted the temptation to replicate every quirk of every old system. Where a school had an idiosyncratic process built around a tool's limitations, the process was simplified rather than preserved. Consolidation projects fail when they try to carry forward thirteen years of workarounds.

The Savings Nobody Put on the Spreadsheet

The financial case was what got the project approved. The operational case is what made it stick. Teachers who had been typing observations into one system, uploading photos to another and writing reports from scratch in a third found that accumulated voice notes and photo observations could feed directly into report writing. Pre-meeting preparation for parents' evenings stopped being an evening job.

Office staff saw the sharpest change. Chasing unpaid trip money across two platforms and a paper list became a single filtered view with targeted reminders. Absence reporting moved from the morning phone queue to the app. One business manager estimated the trust had removed around twelve hours of weekly administrative duplication across its central team alone — a meaningful contribution to any serious attempt to reduce teacher workload and support staff pressure.

That last point is the durable one. The trust now requires any new software request to demonstrate that no existing platform covers the need. It is a small governance change that prevents the patchwork from reassembling itself over the next five years.

Parent Engagement Improved as a Side Effect

The unexpected outcome was on the family side. When parents had four apps, engagement was fragmented and uneven — and worst among exactly the families schools most want to reach, including those with English as an additional language and separated families managing two households.

A single platform with push notifications, automatic message translation and family group accounts shifted that. Message open rates rose, parents' evening booking completion improved markedly without office staff making reminder calls, and absence reporting became more timely. Genuine parent engagement is rarely a content problem. More often it is a friction problem.

How to Run the Same Audit in Your Trust

Start with visibility. Ask every school for a complete list of software spend, including anything on a departmental card. Expect the real number to exceed the expected number. Then map each system against the job it does and highlight every overlap.

Next, cost the invisible items: administrative hours spent on duplicate data entry, transaction fees on payments, training time for each interface, and the GDPR overhead of every additional processor. Finally, sequence any migration around the school year rather than the financial year, and pilot before you mandate.

The Bigger Picture for Edtech Beyond 2025

The edtech 2025 conversation has been dominated by artificial intelligence, and reasonably so — AI-assisted lesson planning, report writing and progress analysis are genuinely changing what a teacher's week looks like. But AI only works well on consolidated data. Observations scattered across four systems cannot be analysed as a coherent picture of a child's development.

That is the strategic argument for consolidation that outlives any single budget cycle. The £50,000 is real and welcome. The more valuable outcome is a trust whose data sits in one place, whose staff learn one system, and whose parents have one app — which is the precondition for everything useful that comes next. If you want to see what that looks like in practice, it is worth starting with an honest audit of what you are already paying for.