Illustrative blueprint: How a 4-school CBSE group replaced 3 SaaS tools with one custom school management system.
An illustrative planning scenario showing the shape and economics of a typical Big Helpers school management build — one system covering attendance, fees, exams, and a parent app, replacing three disconnected SaaS subscriptions.
Illustrative blueprint: This page is a planning scenario, not a named client engagement or an independently verified result. Names, figures, timelines and outcomes below are assumptions that show how we would scope and reason about a project of this shape.
Modelled starting situation
A CBSE-affiliated school group running 4 campuses in central Maharashtra had grown organically over a decade. Each campus had picked its own digital tools — one used a SaaS school ERP for attendance and fees (₹1.6L/year), one used a different SaaS for exam mark entry (₹70K/year), one used a separate WhatsApp-broadcast tool for parent communication (₹40K/year), and the fourth used a mix of Excel and printed circulars. Group-level visibility was effectively zero — the trustees had to chase 4 principals for fee-collection numbers every month, with each principal pulling data from a different system in a different format. Total annual SaaS spend across the group was about ₹4.2 lakh, with no system talking to any other.
The business problem
Three problems compounded: (1) the trustees had no consolidated dashboard — month-end fee collection rollup took 5-7 working days and was always partially out of date; (2) parents complained about communication chaos — fee reminders came from one app, exam result announcements from another, attendance alerts from a third, and circulars on WhatsApp groups; (3) the SaaS tools didn't talk to each other, so a class teacher had to log into 3 different systems to mark attendance, enter marks, and send a parent communication. The group had tried two unified school ERPs and rejected both — neither matched their CBSE-specific assessment pattern (FA + SA + co-scholastic), and both charged per-student per-year, which would have crossed ₹6L/year at the group's enrolment.
Run a school or school group? Get a free 1-page plan.
Tell us your campus count, total students, and current SaaS spend. We send back a 1-page sketch of what a custom school management system would look like for you, and what it would cost to build.
The system we would design
We built one unified school management system in 11 weeks across the 4 campuses. Single login for class teachers, principals, and trustees with role-based access. Modules included: attendance (biometric + manual), fees (with online payment via Razorpay and offline reconciliation), exam management modelled on the CBSE FA+SA+co-scholastic pattern, library, transport route management, and a parent-facing PWA installable on Android home screen. All notifications consolidated into a single channel — parents got one daily digest at 6 PM (attendance, homework, circulars) plus immediate notifications for fee due, absence, and exam results. Trustees got a group-level dashboard showing fee collection, attendance trends, exam performance, and operational metrics rolled up across all 4 campuses with one-click drill-down per campus. DPDP-compliant: explicit consent capture from parents at admission, separate granular consent for marketing, easy unsubscribe, retention policy aligned with CBSE record-keeping requirements. Hosted on the group's existing AWS account in ap-south-1. Source code in their GitHub from day one.
Features delivered
- Single login + role-based access (teacher / principal / trustee / admin / parent)
- Attendance module — biometric integration + manual entry fallback
- Fees module with Razorpay integration, partial payment, scholarship handling
- CBSE-pattern exam management (FA + SA + co-scholastic, term-wise rollup)
- Parent-facing PWA — installable, no Play Store, works on entry-level Android
- Single daily 6 PM digest to parents (attendance, homework, circulars)
- Real-time alerts for fee due, absence, exam result publication
- Library + book issue / return tracking
- Transport route + bus tracking for parents (where GPS available)
- Group-level trustee dashboard rolling up all 4 campuses
- One-click drill-down from group view to campus to class to individual student
- GST-compliant fee receipt generation with auto-email + WhatsApp delivery
- DPDP-compliant: consent capture, retention policy, parent data export endpoint
- Source code handed over on day-1 of go-live, hosted on group's own AWS account
Expected measurable outcomes
Within 60 days of go-live across all 4 campuses, the trustee group-level dashboard was being checked daily and had replaced the 5-7 day month-end reconciliation entirely. Class teachers reported saving roughly 3 hours per week previously spent juggling 3 systems. Parent app adoption hit 96% inside 60 days — significantly higher than the previous SaaS parent app's lifetime adoption of about 60% — primarily because the PWA had no Play Store install friction (parents tapped a WhatsApp link from the school office and added to home screen). Three SaaS subscriptions totalling about ₹4.2 lakh per year were retired. The build cost ₹4.6 lakh one-time plus about ₹6,000 per month in AWS hosting. Payback achieved inside 14 months, after which the recurring spend dropped from ₹35K/month (old SaaS) to ₹6K/month (own hosting) — a roughly ₹3.5 lakh annual saving going forward.
What we learned
- Schools spend more on per-student SaaS than they realise — the marginal cost looks small per child but multiplies fast across multiple campuses; a custom build crosses break-even surprisingly quickly above 1,500-2,000 students
- CBSE-specific assessment patterns (FA + SA + co-scholastic) and similar boards are exactly where global school SaaS fails — modelling them correctly is the single biggest unlock for principal adoption
- Parent communication consolidation is the most loved feature — parents repeatedly told the school they preferred one app with one daily digest over three apps with random notifications
- PWA over native app was the right call for tier-2 parent base — install friction killed the previous SaaS native app's adoption; the PWA's add-to-home-screen flow doubled adoption
- Trustees use the dashboard far more than predicted — once they had it, they checked it daily, which created healthy operational discipline at campus level (principals knew their numbers were visible)
- DPDP consent capture at admission is easier than retroactive consent — we built it into the admission form from day one, which avoided the painful exercise of re-collecting consent from existing parents later
Frequently asked questions
Is this an actual client?
No. This is an illustrative planning scenario, not a report of one identified client engagement or an independently verified outcome. The workflow, scope, cost ranges and outcome ranges are planning assumptions that show how we would approach a project of this shape.
Will this work for a single-campus school?
Illustrative planning note: Yes — and it's cheaper. Single-campus builds drop to ₹2-3 lakh because we skip the multi-campus rollup layer. Break-even versus per-student SaaS happens at lower enrolment, typically around 600-800 students. Below that, a tuned SaaS may still be the right call.
Can it integrate with our existing biometric attendance hardware?
Illustrative planning note: Yes. We've integrated with eSSL, Mantra, Realtime, and Cosec biometric devices via their standard SDKs and webhook APIs. New biometric integrations add about 1-2 weeks per device family. The system works with manual attendance entry as a fallback if a device is offline.
What about CBSE / state board reporting requirements?
Illustrative planning note: We model the assessment pattern of the boards explicitly — CBSE (FA+SA+co-scholastic), ICSE, and major state boards. Generating the prescribed report card formats and the board's annual data submission templates is included in the standard build. Other boards on request.
How is parent data handled — DPDP?
Illustrative planning note: Explicit consent capture from parents at admission, with separate granular consent for academic communication (essential, no opt-out) and marketing communication (optional, easy opt-out). Retention policy aligned with CBSE record-keeping requirements (typically 5+ years for academic records). Parents can request data export or deletion via a documented endpoint accessible from the parent app. We sign a DPDP-aligned data processing agreement with the school.
What's the maintenance like?
Illustrative planning note: Roughly ₹8,000-15,000 per month for hosting + small fixes during the first year, dropping to ₹6-10K/month after. We hand over source code on day-1 of go-live so any local Laravel/Django developer can extend it. Most school groups keep us on a 6-hour/month retainer for the first academic year then move to ad-hoc.
Related Big Helpers services
Ready to build your school management system?
Talk to a senior engineer in 24 hours — no juniors, no sales reps, no jargon. Just a clear scope, an honest estimate, and a build plan.