Batches and enrolment
Students, batches, subjects and the timetable. One student can sit in more than one batch without being entered twice.
CASE STUDY
Example buildWeb AppCoaching Management Platform
Batches, attendance, online tests and fee payments in one dashboard for students and staff.
- Type
- Web app, staff and parents
- Build time
- 10–14 weeks
- Platforms
- Desktop and mobile browser
- Starts at
- ₹1,00,000*
This is an example build. Tavzuran is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.
The price follows the feature list. The number above buys everything scoped on this page. Take features out and it comes down — the shortest route to a smaller number is a shorter list, and deciding what to drop is what the free call is for.
THE SITUATION
What's actually broken.
A coaching institute runs eleven batches across two centres. Attendance is on paper, fees are tracked in a spreadsheet that one person owns, test scores are on WhatsApp, and parents phone the front desk to ask how their child is doing.
Nothing here is technically difficult. The value is entirely in getting four scattered records into one place, and in the fee reminders going out on their own instead of when someone remembers.
Attendance on paper, fees in one person's spreadsheet
Test scores scattered across WhatsApp groups
Parents phone the front desk for every update
Fee reminders go out when someone remembers
VERSION ONE
What we'd build first.
Every item here earns its place by being something a real user would miss on day one.
Attendance
Marked from a teacher's phone in under a minute per class. Absentees generate a message to the parent the same evening.
Online tests
Objective tests with automatic scoring, a per-student score history and a batch-level view of which topics the class got wrong.
Fees
Instalment schedule per student, an online payment link, an automatic reminder before each due date, and a receipt the parent can keep.
Parent access
Read-only: attendance, test scores, fee status. This one screen removes most of the calls to the front desk.
DELIBERATELY NOT IN V1
What we'd leave out.
Not because these are bad ideas. Because each one is designed better once the first version has told you something.
- Live video classes. Zoom or Meet already does this better than a custom build ever will — link them from the timetable instead.
- A content library and recorded lectures. A big product on its own; worth doing after the operational side is running.
- Subjective and handwritten answer evaluation.
UNDER THE HOOD
How it's put together.
- Web app
- React, used by staff on desktop and parents on phones
- Backend
- Node with Postgres — the data here is deeply relational and a relational database is the honest answer
- Payments
- A gateway with recurring-payment support for instalments
- Messaging
- A transactional SMS or WhatsApp Business provider for reminders
- Hosting
- A single cloud instance; this load does not need anything elaborate
HOW IT RUNS
Week by week.
-
01
Week 1
The data model: what a batch is, what happens when a student switches one, how a part payment is recorded.
-
02
Weeks 2–6
Batches, enrolment, attendance and the staff dashboard.
-
03
Weeks 7–10
Fees, payment links and automated reminders.
-
04
Weeks 11–14
Tests, scoring and the parent view.
THE HARD PART
Attendance a teacher will actually mark
Every build has one problem that decides whether the rest of it matters. This is that problem, written out.
Every feature here is straightforward except this one, and this one decides whether the whole system is worth anything. If attendance is not marked reliably, the parent messages are wrong, the reports are wrong, and staff go back to the register within a fortnight.
The constraint is that a teacher will give this about forty seconds, standing up, at the start of a class, on their own phone, sometimes with no signal in a basement classroom. That rules out a form with a dropdown per student. It means the batch opens pre-marked present, the teacher taps only the absentees, and the whole thing saves locally and syncs later.
It also means being careful about what happens when a class is cancelled, a substitute teaches, or a student attends a different batch that day. Those are the cases that make the data untrustworthy, and the moment the data is untrustworthy nobody uses the system.
BEFORE A PRICE EXISTS
What we'd ask you first.
A quote given without these answers is a guess. These are the questions that actually move the number.
- 01How many batches and centres, and how often do students move between them?
- 02Who owns the fee spreadsheet today, and what happens when they are on leave?
- 03Do the parents you need to reach have smartphones, or is SMS the realistic channel?
- 04What happens to fees when a student joins mid-term or drops out?
- 05Are tests objective, subjective, or both?
AFTERWARDS
How we'd know it worked.
Agreed before the build starts, so there is something to judge it against other than whether it looks nice.
- Attendance is marked for over ninety per cent of classes in the first month, without anyone chasing teachers.
- The gap between a fee falling due and being collected drops.
- Front-desk calls asking about attendance or marks fall noticeably.
- Parents log in more than once — a single visit means the screen did not answer their question.
BEFORE YOU START
Worth knowing.
Every SMS and WhatsApp message costs a few paise, billed by the messaging provider directly to you. At a few thousand messages a month it is small, but it is a running cost and it is not included in the build price.
Websites and apps start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.
KEEP LOOKING
Other example builds.
Web App
Business Automation Dashboard
Replaces daily spreadsheet work with automated reports, alerts and role-based access.
Read the case study Website + CRMReal Estate Listing Portal
Property search, enquiry capture and a lead pipeline a sales team will actually use.
Read the case study Mobile AppDelivery Tracking App
Driver app with live location, proof-of-delivery photos and an owner-side status board.
Read the case studyWant this built for your business?
Tell us what you're thinking. We'll figure out the next step together.
Free 20-min idea call · No obligation