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 AppBatches, attendance, online tests and fee payments in one dashboard for students and staff.
This is an example build. HumansOfCoding 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 SITUATION
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.
VERSION ONE
Every item here earns its place by being something a real user would miss on day one.
Students, batches, subjects and the timetable. One student can sit in more than one batch without being entered twice.
Marked from a teacher's phone in under a minute per class. Absentees generate a message to the parent the same evening.
Objective tests with automatic scoring, a per-student score history and a batch-level view of which topics the class got wrong.
Instalment schedule per student, an online payment link, an automatic reminder before each due date, and a receipt the parent can keep.
Read-only: attendance, test scores, fee status. This one screen removes most of the calls to the front desk.
DELIBERATELY NOT IN V1
Not because these are bad ideas. Because each one is designed better once the first version has told you something.
UNDER THE HOOD
HOW IT RUNS
The data model: what a batch is, what happens when a student switches one, how a part payment is recorded.
Batches, enrolment, attendance and the staff dashboard.
Fees, payment links and automated reminders.
Tests, scoring and the parent view.
BEFORE YOU START
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.
MVPs 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
Replaces daily spreadsheet work with automated reports, alerts and role-based access.
Read the case study Website + CRMProperty search, enquiry capture and a lead pipeline a sales team will actually use.
Read the case study Mobile AppDriver app with live location, proof-of-delivery photos and an owner-side status board.
Read the case studyTell us what you're thinking. We'll figure out the next step together.
Free 20-min idea call · No obligation