CASE STUDY

Example buildWeb App

Coaching Management Platform

Batches, attendance, online tests and fee payments in one dashboard for students and staff.

Type
Web app, staff and parents
Build time
About 8 weeks
Platforms
Desktop and mobile browser
Starts at
₹20,000*

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

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.

Batches and enrolment

Students, batches, subjects and the timetable. One student can sit in more than one batch without being entered twice.

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.

  1. 01

    Week 1

    The data model: what a batch is, what happens when a student switches one, how a part payment is recorded.

  2. 02

    Weeks 2–4

    Batches, enrolment, attendance and the staff dashboard.

  3. 03

    Weeks 5–6

    Fees, payment links and automated reminders.

  4. 04

    Weeks 7–8

    Tests, scoring and the parent view.

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.

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.

Want 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

Book a Free Call