Education
A school can have perfect records and still not reach its parents. Everything hard about school software lives in that gap.
What’s actually hard here
The constraints that decide the architecture.
Not the sector’s challenges in general. The specific things that make software for it hard, and that anyone proposing to build it should already know.
The register is not a contact list
A school holds a student. A message has to reach a household — which may be a mother on one number, a father on another, and a guardian who is the one who actually answers. The record was designed for enrolment, not for delivery, and the moment you use it for delivery its gaps become visible: the number that was right two years ago, the parent who changed network, the household with one phone between four children. Most school systems treat this as a data-quality problem to nag about. It is a design problem, and it is the whole job.
Delivery is not confirmation
A gateway accepting a message is not a parent receiving it. The receipt comes back later, asynchronously, sometimes never, and a system that renders 'no receipt' as success is telling a head teacher something false about whether a closure notice landed. Schools operate on that answer.
The households you most need to reach are the ones text misses
SMS is the cheap default, and the parents it fails to reach are disproportionately the ones a school most needs to reach — poor signal, shared handsets, a parent who does not read English comfortably. A text-only system does not fail loudly; it just quietly excludes the same families every term. Voice, in the household's own language, costs more and is the only thing that closes that gap.
Fees, attendance, and results are the same record or they are lies
The fee reminder that goes to a parent who paid last week destroys more trust than the reminder recovered. That is not a messaging bug — it is what happens when the finance system and the communication system hold separate copies of the same household, and the reconciliation between them is a person.
How we engineer for it
The practices this sector actually needs.
Relevant platforms
We already built this.
Because we kept meeting the problem. It is not the only thing we can do for this sector — it is the part we had solved enough times to engineer properly.
Tell us what cannot go wrong.
If the constraints above look like your constraints, that is the conversation we want. You will speak to an engineer.