I build operations systems for coaching institutes, training academies and schools’ administrative side: admissions and batch management, fee schedules with dues chasing, attendance, parent communication and faculty utilisation.
Why do institutes break at exactly the moment they succeed?
Because forty students are manageable in a register and four hundred across a dozen batches are not — and the transition happens over one good admission season, faster than anyone rebuilds the process.
The symptoms are consistent. Fees arrive part-payment by part-payment, tracked in a book, chased by whoever remembers. Dues live in the owner’s head, which means the dues list is only as good as their week. Batch changes leave attendance orphaned, so a student’s actual record becomes unreliable at exactly the point a parent asks about it. And parents call the front desk with questions the system should have answered by WhatsApp before they thought to ask.
Teaching is the product. The register is the bottleneck — and it does not scale by hiring more people to maintain it, because more hands on the same register produce more versions of the truth.
What does the system cover?
- Admissions and batches. Courses, sections, transfers between batches without orphaning history, and an enquiry pipeline that survives admission season.
- Fee engine. Schedules, instalments, sibling and scholarship discounts, late-fee logic — receipts instant, and a dues list produced by the system rather than by memory.
- Attendance. Daily marking with alerts for students whose attendance is slipping, which is the earliest signal of a student about to drop.
- Parent communication. Fee reminders, schedule changes, results and absence alerts, sent automatically (the messaging layer does the delivery — this is the vertical where it pays back fastest).
- Faculty and room utilisation. Who teaches what, where, when, with the gaps visible.
The two lists that run an institute
The dues list, sorted by age. Not a total — a list, per student, with the last contact recorded. An institute’s cash flow problem is almost never that parents refuse to pay; it is that nobody called at the right moment, and by the time anyone does, three instalments have accumulated into a conversation nobody wants to have. Automated reminders before the due date plus a working list after it changes collection materially, without anyone becoming unpleasant about it.
The attendance-slipping list. A student attending five of the last ten classes is telling you something before they tell their parents. Catching that early is a phone call; catching it at the term’s end is a refund conversation and a lost referral. In a business where word-of-mouth among parents is the entire marketing channel, retention is the growth strategy.
Both lists already exist implicitly in the data every institute collects. The system’s job is to surface them daily and put someone’s name against each one.
Related reading
/products/whatsapp-automation — parent communication engine · /industries/fitness — the same renewal and attendance economics · /industries/therapist — counselling inside institutions, handled with care · /products/company-os — the multi-branch owner view
Where is your dues list right now?
If the answer is “in someone’s head” or “in a book at the front desk”, then the number that determines this month’s cash flow is not being managed. /contact — fees waqt pe, records saaf.
Questions I actually get
Online and offline batches together?
Both, with links and recordings attached to the batch rather than shared ad hoc. A student switching between modes stays one enrolment with one attendance history, which is what keeps the retention numbers honest.
Parents want reports.
Auto-sent summaries — attendance, test performance and dues — on a schedule you set. Front-desk call volume typically falls sharply, because most parent calls are requests for information the system can simply send before it is asked for.
Multi-branch coaching chain?
Per-branch operations with one owner view: enrolments, collections, faculty utilisation and dues per branch, comparable side by side. The comparison is where the management insight lives.
How does the fee engine handle instalments and discounts?
Schedules with instalments, sibling and scholarship discounts, and late-fee logic applied by rule rather than negotiated at the counter. Receipts are instant, and the dues list is a system output rather than someone's recollection.
Can it track faculty and classroom utilisation?
Yes — who teaches what, where, when, with gaps visible. Classrooms and faculty hours are the two fixed costs of an institute, and most run without ever measuring either.
What about admission enquiries that do not convert?
They stay in a pipeline with follow-ups, which matters most in the weeks around admission season. An enquiry that went cold because nobody called back twice is the most expensive kind of loss, because you already paid to generate it.