Every module, honestly listed.

The enrolment console takes a walk-in from stranger to scheduled in one screen: name, phone and state (mandatory — the state decides the GST split on every future invoice), DPDP consent with its source recorded, the batch, the fee as actually agreed with this student, the registration already collected, and an instalment plan the counsellor shapes row by row. The plan must add up to the rupee before the button unlocks; the server re-checks everything the browser claims. One submit writes the student, the enrolment and the entire schedule atomically — no half-enrolled state can exist.

Around the console: CSV import for existing rosters, a printable admission form and student register, an enquiry-only mode for students who have not picked a batch, and full edit flows whose every change lands in the audit trail.

Every day, on its own schedule, the system chases: each uncancelled instalment with a live balance that is due or past due gets its WhatsApp and email nudge — from your own Interakt number and your own SMTP, with the exact balance and a payment link in the message. A three-day cooldown per instalment per channel keeps it polite; the day something tips overdue, one immediate escalation goes out. Recurring expenses post themselves. Receipts and invoices follow every payment automatically. The full behaviour, rule by rule, is in the reminders guide.

Four roles — owner, finance, admissions, collections — each enforced on the page and on the action behind it: an admissions person cannot open the P&L, a collections person cannot change a fee. Sessions are real objects with an idle timeout and an absolute ceiling, both set by the owner; sign-out actually revokes; a security console shows every live session, each person's last sign-in and password age, and the recent security events — every timestamp in IST. Passwords have a modern policy, resets arrive by email over your own SMTP, and every consequential action lands in an audit trail with who, when and the value before.

Student data is handled for India's DPDP Act as working software: consent recorded with its source, a data-request register, self-service data download in the portal, and erasure by redaction that keeps the financial ledger intact. And leaving is a feature, not a fight: a one-click export of everything, on top of payments and invoices that always lived in your own Razorpay and Zoho Books.