A school management system is the least glamorous software a school will ever buy and the one that causes the most pain when it is wrong. Registration, marks, reports, fees, attendance and parent communication all run through it, and the cost of changing your mind is a term of disruption.
We have built these for bilingual secondary schools here. This is what we would want a proprietor to know before choosing.
Why most off-the-shelf systems disappoint here
The market is dominated by products designed around a British, American or Indian school year. They are usually competent software. They just make assumptions that do not hold in Cameroon:
- One language. A bilingual school needs report cards and parent notices in English *and* French, often for the same class.
- One curriculum. Anglophone and francophone sub-systems grade, weight and report differently. A system with one hard-coded model forces you to fake it in a spreadsheet.
- Fees paid once. Here fees arrive in instalments, sometimes irregularly, sometimes partly. A system that treats a fee as paid or unpaid cannot describe reality.
- Email as the channel. Parents read WhatsApp and SMS. An emailed report is an unread report.
- Always-on internet. If the system stops working when the connection drops, the bursary stops working with it.
What to insist on
Fees that match how people actually pay
This is where a school gets its money back on the software. The system must handle part payments, instalment plans, arrears carried between terms, discounts for siblings and staff children, and a clear statement per pupil. If the bursar still needs a parallel spreadsheet, the system has failed at its most valuable job.
Mobile Money, and a receipt
Parents paying by MTN MoMo or Orange Money should have the payment land against the pupil's account automatically, with a receipt to the parent's phone. Manual reconciliation of mobile payments is a job nobody should still be doing, and it is where money quietly goes missing.
Marks entry teachers will tolerate
Teachers enter marks for many pupils across several subjects, often on a phone, sometimes on poor connectivity. If entry is slow or loses work when the network drops, they will keep using paper and your data will be permanently late. Ask to see the marks screen on a phone before anything else.
Communication where parents already are
Results published, fees due, school closed tomorrow — these need to reach a parent within minutes. That means SMS or WhatsApp, sent to a group with one action.
It must work when the internet does not
At minimum: registers markable offline and synchronised later, and report cards printable without a connection. A school day cannot pause because a router did.
Buy or build?
Both are defensible. The deciding factor is usually how unusual your school is.
| Buy a product | Build bespoke | |
|---|---|---|
| Upfront cost | Low — usually per pupil per year | 2,000,000 – 8,000,000 XAF |
| Cost over five years | Rises with enrolment | Fixed, plus maintenance |
| Fits your processes | You adapt to it | It adapts to you |
| Time to running | Weeks | 3 – 5 months |
| If the vendor disappears | Serious problem | You hold the code |
| Best when | Your school runs conventionally | Bilingual, multi-campus, or unusual fees |
Our honest guidance: a single-campus school of 300 pupils following one curriculum should buy something and spend the difference on teaching. A bilingual school of 1,200 across two sub-systems, with instalment fee plans and its own reporting format, will spend years fighting a product and should build.
Buy when your school is ordinary. Build when the thing that makes you different is the thing the software must handle.
Questions to ask before you sign
- 1Can I export all my data — pupils, marks, fees — without asking you?
- 2Show me a bilingual report card produced by the system, not a mock-up.
- 3What happens to marks entry when the connection drops mid-session?
- 4How does a part payment against arrears appear on a pupil's statement?
- 5Who can see what? A form teacher should not see the fee ledger.
- 6What is the total cost at 1,200 pupils, not at today's enrolment?
- 7How and when are backups taken, and has a restore ever been tested?
That last one matters more than it sounds. A school's records are irreplaceable, and an untested backup is a belief, not a safeguard.
Whatever you choose, plan the first term
Systems fail on adoption far more often than on features. Load last year's data before you start so staff see something familiar. Train the bursar and the form teachers separately — they need different things. Run paper alongside for one term. And accept that the first term of reports will need checking line by line, because they will.
We have built management systems for schools here, including bilingual reporting and Mobile Money fee collection. Happy to talk through your requirements whether or not you end up building.
Discuss your school's system