Software for schools, academies and training institutes
Education businesses run on three things: who is enrolled, who has paid, and who turned up. Almost every school we speak to can answer two of those quickly and the third only after an afternoon of work — and it is usually the money one.
What makes this sector different
The constraints that actually shape the software
Every industry claims to be a special case. These are the ones that genuinely change how a system has to be designed.
- 01
The fee cycle is the business model
Revenue is recurring, collection is manual, and a defaulter who quietly stops attending is invisible for weeks. Everything else in an education system is secondary to getting this right.
- 02
Parents are a second user base with different needs
They will not install an app, will not remember a password, and will read a WhatsApp message. Any parent-facing feature that ignores this goes unused, and the front desk keeps taking the calls.
- 03
Sections, not a single class list
A school runs on classes divided into sections, each with its own teacher, room and timetable — and academies run batches that cut across all three. Software that models only a flat class list fights this constantly, and the staff end up maintaining a parallel spreadsheet.
- 04
Grading rules are institution-specific and change
Weightings, grade boundaries and what counts toward an aggregate differ between schools and shift between terms. If they are hard-coded, every change is a support ticket; if they are a spreadsheet formula, they are wrong.
- 05
Multi-campus is more common than vendors assume
A successful school opens a second campus within a couple of years, and discovers their software cannot separate campus data or consolidate reporting across them.
What we build
For education businesses
Not a capability list. These are things we have designed and built, which is why they are specific.
- Student admissions, class and section scheduling, and attendance
- Fee structures with pro-rata, concessions, scholarships and sibling discounts
- Ageing defaulter reports with automated reminders
- Exam entry, weighted grading and report card generation
- Teacher payroll inputs derived from delivered periods
- Parent portals and WhatsApp/SMS notification with delivery tracking
- Multi-campus data isolation with consolidated owner reporting
- Integration with biometric attendance hardware
Relevant systems
Already built, and documented in full
Architecture, roles model and engineering trade-offs are published on each page — not summarised, published.
School Management System
Fee defaulters, attendance and report cards in one place instead of five registers.
One system for admissions, fee cycles, attendance, exams and parent communication — for schools that have outgrown registers and Excel.
Custom CRM
Every lead has one owner and one status, and nobody approves the payment they recorded themselves.
Lead capture by campaign, one owner per lead, and payment proof approved by somebody other than the person who collected it — for services businesses that buy their leads.
How we would engage
FAQ
Education — questions we get asked
We already use a school management system. Is it worth replacing?
Often not. If it handles your fee cycle and your grading rules, keep it — replacing working software is expensive and risky. The cases where a rebuild pays are when the fee model genuinely does not fit, when multi-branch reporting is impossible, or when your team maintains a parallel spreadsheet to compensate for it. That last one is the clearest signal.
Can it handle both a school and a coaching centre model?
Yes, but they are genuinely different shapes and we would want to know which one dominates. Schools are timetable-and-section driven with annual admission and monthly tuition cycles; coaching centres are batch-driven with much higher churn. Our school management system is built school-first and configures down to batches — building for both without deciding which is primary produces something that serves neither well.
How do you handle fee data during migration?
Opening balances are reconciled with you before go-live, not after. We import the outstanding position per student, you check it against your register, and we do not go live until the numbers agree. A system that starts with wrong balances loses the staff's trust in week one and never recovers it.
Tell us how your education operation actually runs.
A 30-minute call, no slide deck. We will tell you whether this is worth building, whether an off-the-shelf product would serve you better, and roughly what it would take.
30 minutes · We reply within one business day.