Private School ERP: Custom Build vs Off-the-Shelf — 2026 Comparison

The verdict in three sentences

For a single-campus private school with standard needs, an off-the-shelf school ERP stays the rational choice: controlled cost, quick start. Once multi-campus, Qualiopi/CPF requirements and specific accounting/payroll integrations appear, SaaS becomes a stack of paid modules and workarounds. A custom build (€70,000–130,000 excl. VAT + ~€14,000/year maintenance) regains the edge when the school wants to own its processes and its parent portal.

Both models, line by line

A SaaS school ERP for 900 pupils runs, modules included, to €30,000–70,000 over 5 years. Custom means €70,000–130,000 excl. VAT upfront, then ~€14,000/year — i.e. €126,000–200,000 over 5 years — but with an owned asset and no per-pupil pricing constraint.

5-year TCO: where the decision tips

The tipping point is not pupil count alone: it is process complexity (Qualiopi, family billing with instalment plans, real-time parent portal) and integration needs. The more specific they are, the more SaaS costs in modules and workarounds, and the more custom pays off.

Mini case study

Sophie runs a private school group in Montpellier, 900 pupils across 2 sites, with continuing-education activity subject to Qualiopi. Her SaaS ERP costs €7 per pupil/year + €9,000/year of modules = €15,300/year, but forces two manual exports and a homemade Qualiopi spreadsheet consuming 0.3 admin FTE.

Moving to a custom ERP at €95,000 excl. VAT + €14,000/year, she automates Qualiopi and family billing, freeing the equivalent of 0.3 FTE (~€14,000/year of payroll). Over 5 years the TCO gap shrinks to ~€30,000, easily offset by recovered admin time and ownership of the tool.

FAQ

How much does a custom school ERP cost in 2026?

Budget €70,000 to 130,000 excl. VAT for development, plus ~€14,000/year maintenance. A SaaS ERP costs €3–7 per pupil/year + modules, i.e. €30,000–70,000 over 5 years for 900 pupils.

When does custom become cost-effective?

Once multi-campus, Qualiopi/CPF requirements and deep accounting/payroll integrations pile up. Process complexity, not headcount alone, tips the calculation.

How do you handle GDPR on minors' data?

Custom lets you choose hosting (EU), minimize collected data and log parental consents. In SaaS you depend on the imposed processor and its location.

Is the parent portal included?

Yes, in a custom build it is part of the scope: grades, absences, invoices, online payments. In SaaS it is often an extra module billed yearly.

Can we start small then expand?

Yes: an initial scope (enrolment, schooling, billing) can ship in 10–14 weeks, then grow. That is the recommended approach to smooth the budget and secure staff buy-in.

Let's scope your project. Tell us your pupil count, number of campuses and Qualiopi/integration constraints and we'll compare SaaS vs custom over 5 years and cost the scope. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.