An example use case 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.
Note: this is an example use case illustrating a typical Big Helpers engagement of this shape — not a named client. Real client names and numbers are kept private.
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.
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.
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.
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.
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.
It's an example use case representative of typical Big Helpers school management builds for Indian school groups in tier-2 cities. Specific client names and exact numbers are kept private. The shape, technical choices, and rough economics are accurate to real engagements of this size.
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.
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.
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.
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.
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.
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.