Loading page
Batches instead of classes, monthly or course-wise fees, teacher payouts and attendance — built for coaching centres, institutes and training academies.
An academy runs on batches, not on an academic year. A student joins mid-month for a three-month course, attends four evenings a week, pays monthly or in instalments, and may switch batch when their shift changes. Neither school software nor a spreadsheet handles that gracefully.
The two numbers that decide whether an academy is profitable are collection against enrolled students and teacher cost against batch size. So the system is built to keep both visible every week rather than at month end.
Day, time and room scheduling with capacity, waiting lists and batch transfers mid-course.
Monthly, instalment or full-course fees with pro-rating, discounts and automated dues reminders.
Attendance-pattern warnings so a student who stops attending is called this week, not next month.
Per session, per batch, per student or fixed, with a monthly statement each teacher can verify.
Revenue, teacher cost and margin per batch — the report that decides whether to merge or close one.
Fee status, attendance, test results and schedule for each student and parent.
Everything is organised around the batch: who is in it, who is teaching it, what it costs and who has paid.
An academy's biggest leak is silent drop-off: a student stops attending, nobody notices for three weeks, and by the time anyone calls they have joined a competitor. Attendance-based drop-off alerts flag students whose attendance pattern breaks, while the enquiry pipeline shows how many trials converted.
Those two reports usually matter more than anything else the system produces.
Because payouts can be per session, per student or fixed, profitability varies per batch in ways owners often cannot see. The system reports revenue, teacher cost and margin per batch, which is what tells you whether a small batch should be merged or closed.
Straight answers, including the ones that rule us out.
The pages people read next, and the products that connect to this one.
The systems we build most often, each described by the workflow it manages rather than by a feature list — because the workflow is what decides whether it fits.
Read moreAdmissions, attendance, timetables, exams, results, fees and staff records in one system — with a parent portal so the office stops fielding the same calls.
Read moreFee structures, bulk vouchers, instalments, concessions, fines and reconciliation — with a defaulter list that is current enough to act on.
Read moreAttendance, results, fee status, timetables, notices and documents — online, per student, so the office stops answering the same three questions by phone.
Read moreSchool, college and academy systems, student and parent portals, fee management and admissions — built so the office still uses them in month eight.
Read moreAdmissions enquiry and application forms, honest fee and academic information, notices, galleries and a route into the parent portal.
Read moreSchool software is abandoned more often than replaced, and almost always for the same reason: daily entry is slower than the paper it replaced.
Read moreDescribe your operation and we will come back with a written scope, a fixed price and a delivery date.