Most guides to school management software are written with a state school in mind, and the mismatch shows within the first term. A state school buys a management information system largely to satisfy obligations: statutory returns, census data, inspection reporting. If you run a fee-paying school, you need school management software for private schools — software built around a completely different set of pressures: fees to collect, families who chose you and could choose somewhere else, an admissions process that competes for enrolments, and nobody telling you what to buy.
This article is about what changes when the school is fee-paying, and how to evaluate a platform against that reality instead of a generic feature list.
What makes a private school different as a buyer
Fees are a relationship, not a transaction. You are billing the same family for a decade, often for two or three children, while also teaching those children. A collection that damages the relationship costs you a re-enrolment, which is far more expensive than the invoice.
Admissions is competitive. State schools receive allocations. You market, convert enquiries, run open days, and lose applicants to the school down the road. That makes the top of the funnel — enquiries, follow-up, conversion — a real business function rather than an administrative step.
Families expect a service standard. A paying family expects visibility: what their child is doing, what they owe, what happens next. Communication that would be adequate at a state school reads as inattentive when someone is paying.
Retention is the whole business. A student who leaves at the end of Year 5 costs you eight years of fees. Almost nothing in a state-sector MIS is designed around that.
Nobody tells you what to buy. Freedom and burden at once. Without a mandated system, the decision is yours, and so is the mistake.
The criteria that matter
Fee management built for families, not for grants
Sibling discounts, scholarships and bursaries, staggered payment plans, one account covering several children, mid-year joiners and leavers with pro-rata calculation. Look at how a platform's financial tracking and family billing actually renders on a statement, not just how the admin screen looks.
Admissions as a funnel, not a form
Enquiries captured from the website, followed up, converted and measured. If you cannot say what proportion of open-day attendees enrolled, you cannot improve it — an admission process built to track a request from enquiry to enrolment is what closes that gap.
Family-facing quality
What parents actually see — the statement, the report, the announcement — is more visible to your customer than any admin screen, and it is where a paying family forms its judgement. A well-built parent portal is usually the single feature that most affects how a family rates the whole school.
Academic reporting that reflects your curriculum
Private schools frequently run curricula that do not match the national template. Software built around statutory reporting can be rigid here, so check that academic management, attendance and report cards can be configured to your own terms and grading, not just imported from a government template.
Staff permissions that reflect a real structure
Heads of year, subject leads, admissions, bursary, senior leadership. Everyone seeing everything is a data protection problem before it is an operational one.
Retention signals
Attendance drift, unpaid balances, disengaged families. The information that predicts a departure usually sits across three separate modules. That is a different problem from chasing a payment that is already overdue — retention means catching the pattern before the balance becomes a collections case.
The platforms compared
Arbor
UK-focused, cloud MIS built for the maintained and academy-trust sector, with strong analytics, a large installed base, and a school census wizard shaped by statutory reporting.
Strong on: data analysis, workload reduction across multi-academy trusts, and a mature support community.
Consider carefully if: your priorities are fee management and admissions marketing — the product is shaped by what a maintained school reports to government, not by what a fee-paying school has to sell.
Phidias
Used by private and international schools across Latin America and Europe, covering academic, financial and family communication in one system.
Strong on: the private-school model, financial management, and an international-school context.
Consider carefully if: you need behaviour outside its established regions and school types.
Colegium
Latin America-focused, covering academic management, communication, admissions and financial administration for schools across Argentina, Brazil, Chile, Colombia, Mexico and Spain.
Strong on: the Latin American private-school market, admissions and family communication.
Consider carefully if: you operate outside its main regions.
Alexia, Clickedu and Esemtia
Mature Spanish platforms built around the academic year, report cards and family communication, each with a substantial installed base across Spanish private and subsidised schools.
Strong on: the Spanish private and subsidised-school context.
Consider carefully if: you need rolling intakes or operate outside Spain.
KMPUS
Ours, so read it with the scepticism that deserves. Academic management, admissions, financial tracking, CRM and a branded family app in one system, with admissions connected through to the student record and finance without re-entry, plus consolidated reporting across more than one campus — see how it's put together on the K-12 schools solution page.
Strong on: the admissions-to-finance flow, schools running more than one site, and schools that also run non-standard programmes.
Consider carefully if: you want the largest vendor available, or you need deep statutory reporting for a specific national system.
How to evaluate a platform properly
Bring your own scenarios and make each vendor perform them live, rather than trusting a features list:
A family with three children, one on a scholarship, pays in monthly instalments. Show me their statement.
A student joins in February. Calculate the pro-rata fee and enrol them.
Show me every enquiry from last term's open day and what happened to each one.
Show me the families with both an unpaid balance and declining attendance.
Restrict a Head of Year to only their own year group. Show me what they can and cannot see.
Then ask the questions that reveal the most: what is your platform bad at, and what happens to our data if we leave? A vendor with a real answer to both is worth taking seriously; a vendor without one is telling you something too.
Frequently asked questions
Can we use software built for state schools?
You can, and many private schools do. The gap usually shows up in fee management, admissions marketing and the family-facing experience.
How much should we budget?
Compare total three-year cost at your actual student numbers with every module you need, including implementation. The monthly headline figure is rarely the whole picture.
When should we change systems?
Not during your admissions peak. Data cleaning, not configuration, is usually what determines the timeline.
Do we need a separate CRM for admissions?
Ideally not. A separate CRM means enquiry data and student data live apart, which is the re-entry problem in different clothes — check whether the platform's CRM converts an enquiry straight into an enrolled, billed student before you accept two systems as normal.
What about our learning platform?
A different job, and it should stay separate. Look for integration rather than replacement.
If admissions, fees and the family experience are where your time goes, start a free trial of KMPUS — no credit card required.
