Students, parents and staff each need their own view.
Admission season at a coaching institute: forms on paper and online, fee instalments in a ledger, batch timings in a group chat and parents calling to check whether their child is enrolled. We build software that connects those records while showing each person only their part.
Three audiences, one student record.
What’s next for me
Their timetable, the next class or lesson, material they can open and any assignment or test coming up.
Is everything on track
Fees paid and due, attendance, notices and results where you choose to share them. Usually on a phone, often in a regional language.
Who is where
The admissions pipeline, batch allocation, fee follow-ups and the administrative history behind each student.
From enquiry to first class.
The enquiry becomes an application
A student or parent fills in a form and counsellors can see where each enquiry stands. If following up enquiries is the real bottleneck, our CRM SmartBDM may already cover that part.
Staff check and admit
Documents are reviewed, eligibility confirmed and a seat or batch offered. Waitlists and rejections are recorded too, so nobody is left wondering.
Fees are set and collected
The fee plan, any scholarship or sibling concession and the instalment schedule attach to the student, and receipts come from the same record. More on payments and billing.
Access switches on
The student joins the right course, cohort or timetable. If they transfer or withdraw, access and billing change together under one decision.
Moments that test the system.
A student moves to the evening batch
The timetable, teacher lists and attendance registers all need to follow. If any of them is updated by hand, the student shows absent from a class they no longer attend.
A fee payment is late
The reminder should reach whoever pays, which may not be the student. Whether access pauses is your policy, set once and applied the same way to everyone.
A learner buys a single course
For a paid learning product, access follows the purchase or subscription. Refund rules and when access expires have to be settled before launch.
Marks go out to families
Each parent should see only their own child’s results. A mistake here is public and hard to take back, so these permissions get the most testing.
Agree on these at the outset.
- Whether any users are minors, and how parental consent is captured and stored.
- Who may see marks, attendance and fee status: teachers, coordinators, accounts, parents.
- Your fee structure, including instalments, concessions, late fees and refunds.
- How courses, batches and cohorts are organised, and how often that changes during a year.
- Whether learning content stays in an existing LMS or moves into the new platform.
- Which messages go by SMS, email, WhatsApp or app notification.
Heads of institutes ask us.
Can each course open up different material?
Yes. Access can follow the enrolment, the plan bought or the cohort, and it changes automatically when any of those change.
We’re launching a paid online course. Where should we begin?
With the smallest version that lets real learners pay and learn, then add the rest once you see how they use it. Our notes on planning your first product walk through how to scope it.
Can parents pay fees by UPI?
Yes, through a payment gateway that supports UPI, cards and net banking. Receipts are issued from the student’s record, and the gateway’s own charges apply as usual.
Can teachers mark attendance from a phone?
Yes. A short attendance screen per batch is one of the more useful early pieces, because it feeds parent updates and fee follow-ups without anyone retyping it.
Tell us how a student joins today.
From first enquiry to first class, we’ll find where details get retyped and what to build first.