Most conversations about school software cost compare one product against another: this MIS against that MIS. That is the wrong unit. A school does not run one piece of software. It runs eight to fifteen. Each one has its own licence, its own renewal and its own per-pupil rate. The real cost is all of them added together, across the years the school keeps paying. This guide covers four things. What a UK school spends across all its software. Why per-pupil pricing grows. The costs that never reach an invoice. How a subscription compares with owning a system outright.
Connect with us about your school system · · Replies within 24 hours
A school is four organisations at once. A statutory reporting body. An employer of hundreds. A finance operation with audited accounts. A safeguarding organisation. Each one needs software. In practice that means a separate product for each job. The MIS, safeguarding, finance, HR, parent communication, timetabling, assessment tracking and cashless catering. There are others. Each is bought, licensed and renewed on its own. Comparing two MIS products tells you which MIS is cheaper. It says nothing about the figure that leaves your budget each year. That figure is all of these together.
Start with the fact that surprises people: the MIS itself is usually cheap now. Arbor publishes a flat £1,500 a year for a primary and £2,000 for a secondary. Bromcom charges a base fee plus about £7 to £11 for each pupil, so a large secondary pays more. The large number is never one product. It is the sum of separate paid subscriptions above the MIS. Safeguarding, finance, parent communication, catering, timetabling, assessment and HR. Each one renews every year. The ranges below are for a secondary of around 1,000 pupils running a separate paid product in every category. They use published rates where a vendor publishes them, and market norms where none exist. Most quotes are specific to a school. Check each line against your own contracts. Not every school buys all of these separately, and that is part of the point. The software is as split as the budget that pays for it.
| System | Typical Annual Cost | How It Is Priced | Common Products |
|---|---|---|---|
| MIS | £2,000 to £12,000 | Flat (Arbor) to per pupil (Bromcom, SIMS) | Arbor, Bromcom, SIMS |
| Safeguarding | £1,000 to £3,000 | Scales with pupil numbers | CPOMS, MyConcern |
| Finance (academy) | £2,000 to £6,000 | Per user or quote | IRIS Financials, PS Financials, iplicit |
| Parent communication | £1,000 to £4,000 | Tier or per transaction | IRIS ParentMail, School Gateway, Weduc |
| Cashless catering & payments | £1,500 to £4,000 | Mostly per transaction | ParentPay, SchoolGrid |
| Timetabling | £1,000 to £4,000 | Annual licence | Edval (Tes), TimeTabler |
| Assessment tracking | £1,000 to £3,000 | Per pupil or tier | FFT Aspire, others |
| HR and staff | £1,000 to £3,000 | Tier | SAMpeople, others |
| Annual total (loaded secondary stack) | £10,500 to £39,000 | ||
| Five-year total | £52,500 to £195,000 |
Two honest qualifications on that table. The range is wide because the products are. A secondary on a flat-rate cloud MIS with lean tools sits near the bottom. One on per-pupil pricing across premium products in every category sits near the top. And most schools do not buy all eight as separate paid subscriptions, because some functions come bundled with the MIS. The figure that bites is the accumulation, not any single line.
A primary school's figures are much lower. A primary usually pays about £1,500 for a flat-rate cloud MIS. It needs a smaller safeguarding tier, and fewer specialist tools than a secondary. Its software then costs about £4,000 to £12,000 a year. The structure is the same, several separate subscriptions renewed annually, but the totals are a fraction of a secondary's. A multi-academy trust works the other way. It multiplies the per-school cost across every school, and adds central finance and trust reporting. Trust economics are therefore their own subject, covered in the multi-academy trust software guide.
Not every line is priced the same way, and the difference matters. Arbor charges a flat fee. Bromcom, CPOMS and most assessment tools charge for each pupil. The payment and catering platforms charge for each transaction. A per-pupil or per-transaction price rises whenever the roll grows. The school runs the same systems, doing the same work. Add a form of entry and those lines all rise at once. For a trust, take on another school and the whole stack scales again. None of that recurring spend accrues to anything the school owns: it is renting, and much of the rent rises with the roll.
The headline subscriptions understate the real cost of a fragmented stack, because three significant costs sit outside them.
A bespoke system from ESRE changes the shape of the cost, and not only from rental to ownership. We build it on the engage.re graph. A new function is added as data, and not rebuilt in code. Changing software is the expensive part of ordinary systems, and here it stays cheap for the life of the system. The school pays once for a system it owns outright, on UK servers it controls. No per-pupil fee rises with the roll. No renewal grows with the number of functions in use. The school then changes the system for a fraction of what a change costs elsewhere. Indicative build costs run roughly as follows, and like any project the real figure depends on scope:
| Scope | Typical One-Off Cost | What It Replaces |
|---|---|---|
| Core: student records, attendance, census output, SEN and behaviour | £15,000 to £28,000 | MIS subscription |
| Full: above plus safeguarding, finance, HR and parent communication | £35,000 to £65,000 | MIS, safeguarding, finance, HR and parent comms |
| MAT: full system plus multi-school dashboards and trust finance | £65,000 to £100,000 | All subscription categories across the trust |
The arithmetic is a five-year comparison, and it lands differently by size. A secondary paying £20,000 a year spends £100,000 over five years. A full system of its own is owned outright from the day it is built. That build usually costs less than the running total within three to four years. It then keeps running, and it keeps changing cheaply. The subscriptions would have continued, and risen. For a multi-academy trust, where the stack is multiplied across schools, the case is stronger still. A single primary on a £1,500 cloud MIS and few tools has small cost lines. A build of its own does not undercut them. It is chosen for what it can do, for ownership, and for the ability to change. That is a different question from saving, and we put it plainly below. The owned system in year five is not the system of year one. It takes every DfE change and every new workflow as data along the way, at a fraction of the subscription cost. A rented set of tools stays inside whatever limits its vendors set.
The five-year comparison is easier to see as cumulative spend. Take a secondary paying £20,000 a year. Compare a full build of its own at £45,000, with UK hosting the school controls at about £1,500 a year. One line climbs every year. The other is paid once and stays close to flat.
| Cumulative spend by | Keep renting (£20,000/yr) | Build and own (£45,000 once + hosting) |
|---|---|---|
| End of year 1 | £20,000 | £46,500 |
| End of year 2 | £40,000 | £48,000 |
| End of year 3 | £60,000 | £49,500 |
| End of year 4 | £80,000 | £51,000 |
| End of year 5 | £100,000 | £52,500 |
| End of year 10 | £200,000 | £60,000 |
For a multi-academy trust the arithmetic compounds. A five-school trust pays £15,000 to £20,000 a year for each school. That is an £80,000 to £100,000 annual software bill. An owned trust system at £65,000 to £100,000 costs about one year of that. It then ends the per-pupil renewal that grows each time the trust takes on a school.
The subscription lines above are the visible cost. One more sits underneath them, and it grows with every product you add.
Each of those eight to fifteen systems holds its own idea of a pupil, a year group and a term. None of them is wrong, and none of them agrees. Somebody in the office joins them, every week.
That is why adding a function costs so much. A new tool does not just cost its licence. It costs a new set of joins to everything you already run.
On engage.re every record type is declared in one shared dictionary. A pupil means one thing across attendance, finance, safeguarding and catering. A new function is a dictionary entry, so it needs no new joins.
We work through this cost in full, including your own staff time, in what does it cost to own and run your own systems. We explain why a rented price rises each year in your software bill goes up every year.
There is no single right answer, only the arithmetic and the value weighed against a particular school's size, growth and ambitions. Put real numbers against your own software. The School Management Software hub sets out what a build covers and how we cost it. You can then talk it through with us.
The MIS is usually cheap. Arbor publishes a flat £1,500 a year for a primary, and £2,000 for a secondary. Bromcom charges a base fee plus about £7 to £11 for each pupil. The bigger figure is the whole stack. A typical primary pays about £4,000 to £12,000 a year for all its software. A 1,000-pupil secondary with a separate paid product in every category pays about £10,500 to £39,000. A multi-academy trust multiplies the per-school figure.
Much of it is priced per pupil or per transaction. The Arbor MIS is a flat fee. Bromcom, CPOMS, most assessment tools and the payment platforms charge by pupil numbers or by transaction. Those lines rise whenever the roll grows. Adding a form of entry raises the cost by itself. So does a trust taking on a school. None of that spending builds an asset you own.
It depends on size. For large secondaries and multi-academy trusts, often yes over five years, because the per-pupil stack is large and, for trusts, multiplied across schools. For a small primary on cheap cloud software, no: bespoke there is chosen for capability and ownership rather than to save money. The owned system sits on the engage.re graph either way. New functions are added as data, so it changes cheaply. It also brings an automatic audit trail, and the ability to see whether your work changes outcomes. Subscriptions bring neither.
Connections between systems that do not share data. Staff time spent matching data between systems. The cost of change when you add a function, grow the roll or move platform. The sticker price of each product understates the cost of running a fragmented stack.
Connect with us about your school system · · Replies within 24 hours