Indian schools do not have a software problem. They have a too-much-software problem. The register gets copied three times, fees get chased family by family, and notices drown in a group chat with two hundred people in it. We fixed it by removing things.
A full demo school inside. Enter as principal, teacher or front desk. No signup.
Everyone starts present. Tap the two who are not here.
None of this is anybody's fault. It is what happens when a school buys three systems that were never introduced to each other, and a diary fills the gaps.
Everyone starts present. The teacher taps the two who are not, on their own phone, from the front of the room. Yesterday can be carried forward. About four seconds.
Before the second period, every absent child's family gets a WhatsApp message in their own language, with the time and the teacher's name. Not at six in the evening.
Registers land as they are submitted, dues reconcile as UPI payments arrive, and a child whose attendance is quietly sliding surfaces in October rather than March.
| Typical school ERP | made.class | |
|---|---|---|
| Parent access | An app to install, an account, a password nobody remembers | WhatsApp. Nothing to install, ever |
| Language | English, usually | Hindi or English per family, chosen by the family |
| Fee payments | Gateway in the middle, convenience charge on the parent | UPI straight to the school account, ₹0 charge |
| Taking attendance | A grid per child, then retyped into a portal | Everyone present by default, tap the exceptions, save once |
| When a parent finds out | Evening, or when the child gets home | Before the second period |
| Compliance returns | A fortnight with a spreadsheet | Compiled from live records, exported |
| What it costs a teacher | A second register, kept on paper because it is faster | One screen, four seconds, no paper backup |
No setup fee, no per-message billing surprises, and no cut of your fee collection. If a term goes badly, you leave with your data.
Two or three sections, running alongside whatever you use now.
Everything, for everyone in the building. Billed once a year, not per module.
More than one campus, or a trust running several schools under one office.
No, and they never will. Everything a family receives arrives on WhatsApp, on the number the school already has. No account, no password, no app store, no forgotten login at the worst possible moment. That is the single design decision the whole product is built around.
Nothing, and no. Payments go by UPI straight into the school's own bank account. We are not a payment gateway and we do not sit in the middle of your money. There are no convenience charges passed to parents, which is the thing families quietly resent most about the current systems.
Most schools do not have a software problem, they have a too-much-software problem. If your teachers still keep a paper register because the software is slower than paper, the software lost. We would rather you run us alongside what you have for one term, on one section, and compare.
Compiled from the records you already keep, rather than retyped in a fortnight of evenings. Attendance, enrolment and staff data already live in one place, so the return becomes a download.
The school does. We hold student data as a processor on your instructions, we do not sell it, and we do not use children's data to train anything. Export everything at any time. Deletion means deletion.
A pilot on two or three sections runs the same week: import a student list as CSV, add guardian numbers, hand teachers a link. A full school usually takes two to three weeks, mostly because cleaning up phone numbers is the real work.
The demo runs a full school: 447 students, live registers, dues and the WhatsApp outbox. Enter as the principal, a teacher, or the front desk.