For years, legacy school ERPs took the simplest jobs — telling a parent their child is absent — and wrapped them in modules, logins, licences and lock-in. So schools pay. Heavily. Let's add it up.
Move the slider. Tick the modules a vendor "kindly" sold you.
Illustrative estimates only, not data: the model assumes a ₹250/student/year base licence, module prices as shown, an 18% annual maintenance contract, setup amortised over 3 years, and staff time at ₹250/hour × 44 weeks. The "used daily" share is our editorial estimate of how much of a typical ERP a school touches every day. Your vendor's quote may be lower — or a lot higher. No figure here describes any specific company. The point isn't the exact rupee; it's how much of it buys complexity you never asked for. New to Clasa? Start with what Clasa is and what a school ERP actually covers.
None of this is an accident. It's a business model. The same five moves, in every legacy school ERP pitch:
Attendance, fees, messages, report cards — things that are one job — get split into separate paid products, so the price has no ceiling.
A message costs nothing to send. Charging ₹100–500 per child per year turns your enrolment into their revenue line. Grow the school, grow the bill.
"Onboarding" and "training" fees exist because the software is too complex to use without a course. Simplicity needs no training.
A separate login nobody remembers, that works on one browser, that holds your data hostage so switching feels impossible.
Annual maintenance contracts charge you to not break what already works. The meter never stops.
Strip away the modules, the portal, the per-student meter, the AMC. The thing a school needs every single day is simple: reach parents, record attendance, send a reminder. So that's what we built — as one simple messenger a parent already knows how to use. No login they'll forget. No training. No invoice. Communication should be simple.
To be fair: some schools genuinely need records software — admissions, payroll, exam processing. That's a real category, and Clasa doesn't pretend to replace it. We wrote an honest guide to when a school needs an ERP and when it needs a communication layer first. Clasa is the communication layer.
The communication your school does every day should not cost more than the school bus. With Clasa, it costs nothing.