Part of the School Management Software Guide
Schools Updated June 2026 12 min read

School Software Costs UK: Stack vs Bespoke (2026)

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 with its own licence, its own renewal and its own per-pupil rate, and the real cost is the whole stack added up and projected across the years a school will keep paying it. This guide sets out what a UK school actually spends across the full software stack, why per-pupil pricing compounds, the costs that never appear on an invoice, and how the recurring subscription model compares with owning a system outright.

Speak to us about your school system · +44 7494 618 651 · Mon to Fri, 9am to 6pm

The Unit That Matters Is the Stack, Not the Product

A functioning school is a statutory reporting body, an employer of hundreds, a finance operation with audited accounts, and a safeguarding organisation, and each of those needs software. In practice that means a separate product for the MIS, for safeguarding, for finance, for HR, for parent communication, for timetabling, for assessment tracking, and for cashless catering, among others. Each is bought, licensed and renewed on its own. Comparing two MIS products tells a school which MIS is cheaper; it says nothing about the figure that actually leaves the budget each year, which is all of these together.

What a Secondary School Pays Across the Stack

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, while Bromcom charges a base plus roughly £7 to £11 per pupil, so a large secondary pays more. The big number is never one product; it is the accumulation of a separate paid subscription for safeguarding, finance, parent communication, catering, timetabling, assessment and HR sitting on top of the MIS, each renewed every year. The ranges below are for a secondary of around 1,000 pupils running a separate paid product in every category. They are grounded in published rates where vendors publish them, and in market norms where they do not; most quoting is bespoke to the school, so still check each line against your own contracts. Not every school buys all of these separately, which is part of the point: the stack is as fragmented as the budget that funds 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 spread 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. With a flat-rate cloud MIS at around £1,500, a smaller safeguarding tier and fewer of the specialist tools a secondary needs, a typical primary stack runs roughly £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 runs the other way: it multiplies the per-school stack across every school and adds central finance and trust reporting, which is why trust economics are a category of their own, covered in the multi-academy trust software guide.

Why the Bill Rises as the School Grows

Not every line is priced the same way, and the difference matters. Arbor charges a flat fee, but Bromcom, CPOMS, most assessment tools and others price per pupil, while the payment and catering platforms charge per transaction. Wherever pricing is per pupil or per transaction, the bill rises whenever the roll grows, even though the school is running 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.

Rent that rises, ownership that never arrives. A secondary paying £20,000 a year across its stack spends £100,000 over five years and owns nothing at the end of it. Where lines are priced per pupil, that figure grows as the school grows, with no point at which the spending converts into an asset.

The Costs That Never Reach an Invoice

The headline subscriptions understate the real cost of a fragmented stack, because three significant costs sit outside them.

  • Integration. Separate systems do not share data natively. Connecting them means custom integration work at additional cost, or accepting that data is transferred manually. Either way it is a cost the per-product price tag hides.
  • Staff time reconciling data. When attendance lives in one system, safeguarding in another and payments in a third, staff spend hours moving and cross-checking data between them. That time is a real cost that never appears on any software invoice.
  • The cost of change. Adding a function, growing the roll, or switching a platform when a vendor changes direction all trigger new fees or a migration project. The SIMS migration is the current example: schools that built their operation around one product now face the cost of moving regardless, covered in the SIMS alternatives guide.

The Bespoke Comparison

A bespoke system from ESRE changes the shape of the cost, and not only from rental to ownership. It is built on the engage.re graph, where new functions are added as data rather than rebuilt in code, so the expensive part of conventional software, changing it, is cheap for the life of the system. The school pays once for a system it owns outright, hosted on UK servers it controls, with no per-pupil fee that rises as the roll grows and no renewal that scales with the number of functions switched on, and then evolves it for a fraction of what a change costs anywhere else. 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 running a £20,000-a-year stack spends £100,000 over five years; a full bespoke system, owned outright from the point it is built, typically passes that cumulative spend within three to four years, and then keeps running, and evolving cheaply, while the subscriptions would have kept being paid and rising. For a multi-academy trust, where the stack is multiplied across schools, the case is stronger still. For a single primary on a £1,500 cloud MIS and a lean stack, the cost lines are small, so a bespoke build is not chosen to undercut them; it is chosen for capability, ownership and the ability to evolve, which is a different question from pure saving and one we put plainly below. Either way, the owned system is not the same system in year five that it was in year one: it absorbs every DfE change and every new workflow as data along the way, at a fraction of subscription-stack cost, while a rented stack stays within whatever limits its vendors set.

What It Means for a Real Budget

The five-year comparison is easier to see as cumulative spend. Take a secondary on a £20,000-a-year stack and a Full bespoke build at £45,000, with UK hosting the school controls at around £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
The lines cross in year three. After that the rented stack keeps taking £20,000 or more a year for the same software, while the owned system runs on for the cost of hosting. By year five the school has kept around £47,000; by year ten, around £140,000. Held flat here, the rented figure actually rises as the roll grows, so the real gap is wider. From year four that is close to £20,000 a year back in the budget, about the cost of a full-time teaching assistant.

For a multi-academy trust the arithmetic compounds. A five-school trust spending £15,000 to £20,000 a year on each school's stack carries an £80,000 to £100,000 annual software bill, so an owned trust system at £65,000 to £100,000 costs about one year of it, and then ends the per-pupil renewal that scales every time the trust takes on another school.

Where the cost case is strongest. On price alone, bespoke wins over five years for large secondaries and, especially, multi-academy trusts, where the per-pupil stack is large and multiplied across schools. For a small primary, cloud software is cheap, so the case for building is value and ownership, not a lower bill. Be honest about which of the two you are buying.

When Each Model Makes Sense

  • Subscriptions make sense for a school, often a primary, that wants cheap, supported cloud software quickly and is content within the limits its vendors set. Cloud MIS in particular is inexpensive, and for many smaller schools the whole stack is modest; bespoke is not about saving them money.
  • Bespoke makes sense on cost for large secondaries and multi-academy trusts, where the per-pupil stack is large and, for trusts, multiplied across schools. And it makes sense on value for any school that wants one system it owns and can keep evolving, with new functions added as data in days, an automatic audit trail, and the ability to see whether its interventions actually work, rather than a rented stack whose limits a vendor sets.

There is no single right answer, only the arithmetic and the value weighed against a particular school's size, growth and ambitions. To put real numbers against your own stack, the School Management Software hub sets out exactly what a bespoke build covers and how it is costed, and you can talk it through directly.

Frequently Asked Questions

How much does school software cost in the UK?

The MIS is usually cheap: Arbor publishes a flat £1,500 a year for a primary and £2,000 for a secondary, and Bromcom charges a base plus roughly £7 to £11 per pupil. The bigger figure is the whole stack. A typical primary runs roughly £4,000 to £12,000 a year across all its software; a 1,000-pupil secondary running a separate paid product in every category runs roughly £10,500 to £39,000. A multi-academy trust multiplies the per-school figure.

Why is per-pupil pricing a problem as a school grows?

Much of it is priced per pupil or per transaction. Arbor's MIS is a flat fee, but Bromcom, CPOMS, most assessment tools and the payment platforms scale with pupil numbers or transactions, so those lines rise whenever the roll grows. Adding a form of entry, or a trust taking on a school, scales the cost automatically, and none of that recurring spend builds an owned asset.

Is bespoke school software cheaper than subscriptions?

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. Either way, built on the engage.re graph, the owned system evolves cheaply because new functions are added as data, and it brings an automatic audit trail and the ability to see whether interventions work, which subscriptions do not.

What hidden costs do school software comparisons miss?

Integration between systems that do not share data natively, staff time spent reconciling data between systems, and the cost of change when adding a function, growing the roll or switching a platform. The sticker price of each product understates the cost of running a fragmented stack.

Speak to us about your school system · +44 7494 618 651 · Mon to Fri, 9am to 6pm

Sources and further reading