Twelve modules. One database. No integrations to buy.

The enquiry is where your growth actually happens

A coaching institute lives or dies on how well it follows up. Most lose enquiries in a notebook, a WhatsApp thread and three people's memory.

• Capture an enquiry with its source, so you learn which sources are worth paying for
• Assign an owner and a follow-up date — an enquiry nobody owns is an enquiry nobody calls
• The demo class is a real stage, tracked separately from the enquiry and the admission
• Convert to an admission without retyping a thing
• Conversion by source and by owner, at the end of every month

One form creates the student, the family and the login

Enrolment is where duplicate records get created and then quietly disagree with each other for the next three years.

• Student profile with guardians, contact details and documents
• Batch seat allocated at admission
• The parent's and student's portal access is created at the same moment
• A person has one email address, and it is the address they sign in with — change it in one place and it changes everywhere
• Bulk import when you are moving off spreadsheets

Batches, courses and a timetable that refuses to double-book

Timetable clashes are the kind of mistake that is invisible until a teacher is standing in two rooms at once.

• Courses and batches with the teachers assigned to them
• A dated class calendar — real sessions, not a recurrence rule that drifts from reality
• A teacher cannot be scheduled in two places at once; the database itself refuses the clash
• Reschedule or cancel a single session without disturbing the rest of the term

When we turned this constraint on against our own demo data, it caught fifteen clashes we had not noticed.

Marked in a minute, and the parent knows the same morning

Attendance is only worth collecting if somebody acts on it. The action is usually a message to a parent, and it usually does not get sent.

• Roll-call for a batch from a phone or a laptop
• Absence notifications to parents, sent automatically rather than remembered
• Staff attendance is day-shaped and separate from student sessions — and feeds payroll
• An unmarked day is never silently counted as an absence
• Attendance percentage by batch, by student and by month

The annual price, paid the way families actually pay it

Coaching institutes do not charge by the month. A batch has a price for the year, and the family chooses to pay it in one, two or three parts.

• A batch carries its annual price; the plan is how the family pays it
• Installments with due dates, and a clear view of who is behind
• Cash, UPI, cheque or bank transfer — recorded with the mode and the date
• Printable receipts
• Due reminders that go out without anyone chasing them by hand
• Concessions recorded against the student, with the real price still visible underneath

Marks in, results out — including from an OMR sheet and a phone camera

Checking a hundred OMR sheets by hand on a Sunday evening is a job nobody should still be doing.

• Exams against a batch, with marks entered directly when that is simpler
• Print OMR answer sheets on ordinary A4
• Read the filled sheets from a photograph
• Review anything the scanner was unsure about before anything is committed
• Results land in the student record and appear in the parent portal
• Performance tracked across tests, not just within one

Material reaches the batch, not a WhatsApp group

Study material sent to a group chat is unfindable by the second week and invisible to anyone who joins later.

• Assignments with due dates, shared to a batch
• Notes and study material attached and shared
• Students see what belongs to their batch; parents see what their child was given

Say it once, to exactly the right people

• Institute-wide or batch-specific announcements
• Automatic messages for the things that repeat: absence, fee dues
• A log of what was sent, to whom and when — so 'we were never informed' has an answer

What goes out, recorded as carefully as what comes in

This is the part most coaching software leaves out, and it is the part an owner most needs.

• Every expense by category — salaries, rent, utilities, printing, marketing
• Teacher pay worked out from attendance, with an override that records who changed it and why
• Money in against money out, by month
• Expense breakdown by category, and a profit-and-loss view that is real rather than estimated

The five questions you ask every month

• How much did we collect, and who still owes us
• Which enquiry sources converted
• How is attendance trending, by batch
• How are students performing across tests
• Did the institute make money this month
• Every report exports to CSV and prints

Your receptionist does not need to see salaries

Fixed role lists never survive contact with a real institute. Yours are yours to define.

• Create roles that match how your institute is actually staffed
• Turn individual permissions on and off per role
• Sensible defaults out of the box — Manager, Receptionist, Teacher, Accountant
• Your institute always keeps at least one administrator; the system will not let you lock yourself out

Parents and students, without a seat in your admin

• Parents see attendance, dues, timetable, results and homework — for each of their children
• Students get their own view, separate from their parent's
• Access is by link: no app store, no password to reset every term
• A parent can only ever see their own child's records, enforced by the database and not by the screen