Most schools buy management software once and live with the decision for years — switching later means a second painful data migration and retraining every teacher and parent. That makes the buying decision worth slowing down for. Here is a practical checklist, built around the six areas that actually separate a good fit from an expensive mistake.
1. Where does your data actually live?
Ask any vendor this directly: is our school's data in its own database, or pooled with every other school the vendor serves? A shared, multi-tenant database is cheaper for the vendor to run, but it means your student records, attendance, and fee data sit in the same tables as hundreds of other schools' — a single query mistake or breach has a much larger blast radius. Also ask where the servers physically are. Data hosted outside India adds a layer of cross-border legal complexity under the DPDP Act that most school administrators don't have the bandwidth to manage themselves.
- Is our school's database isolated from every other school's, or shared?
- Is the data physically hosted in India?
- What does the vendor's DPDP Act compliance actually look like in practice — not just a checkbox in a sales deck?
2. What does it actually cost — including the parts nobody mentions upfront
The advertised per-student price is rarely the full number. Two costs are easy to miss until the first invoice: a percentage cut on every online fee payment collected through the platform, and metered SMS packs for parent notifications that get consumed faster than expected. Over a school year, both can add up to more than the base subscription itself. Ask for the full cost breakdown, not just the headline per-student rate, and specifically ask whether fee collection carries any transaction cut and whether parent messaging is unlimited or metered.
3. Can you turn off what you don't need — and pay less for it?
A school with 200 students doesn't need the same feature set as one with 2,000, and paying for unused modules is a quiet, recurring waste. Look for per-student, per-year pricing where modules can be switched on or off as your school's needs change, rather than a single bundled price or opaque per-module upsells added after the contract is signed.
4. Will parents and teachers actually use it?
The best feature list is worthless if the parent app is clunky enough that families give up and call the office instead. Two things predict real adoption: how parents log in (a phone-number login that doesn't require remembering a separate username/password beats email-based logins for most Indian families), and whether the teacher-facing app is fast enough for a teacher to mark attendance in the 30 seconds they actually have between periods, not just fast enough for a sales demo.
- Ask to actually use the parent app on a phone, not just watch a screen-share.
- Ask a teacher who already uses it (not the vendor) how long attendance really takes.
5. How long does switching actually take?
Migrating years of student, fee, and academic history is the single biggest reason schools delay switching software even when they're unhappy with what they have. Ask specifically: who does the migration work — your staff, or the vendor's team — and what is the realistic timeline, in writing, not "it depends." A vendor that quotes a specific number of days and commits to doing the migration themselves is signaling they've done this many times before.
6. What happens when something breaks at 8am on exam day?
Support quality is invisible until the one day you need it. Ask what support actually looks like day-to-day — is it a ticket queue with a multi-day SLA, or a real person who picks up. This matters more for a school than almost any other business, because the failure mode isn't a delayed invoice, it's a locked-out teacher on the morning attendance needs to go out.
The short version
- Isolated, India-hosted data — not a shared database, not hosted abroad.
- The REAL total cost — ask about fee-collection cuts and SMS metering explicitly.
- Modular pricing — pay for what you use, not a fixed bundle.
- Apps parents and teachers will actually open — test them yourself, on a phone.
- A committed migration timeline, done by the vendor's team, not yours.
- Support that answers fast when it actually matters.
Edunia was built around this exact checklist: a private, India-hosted database per school, zero cut on fee collection, unlimited in-app push instead of metered SMS, modular per-student pricing, a phone-login parent app, and a migration the Edunia team handles for you — most schools are live within a week. If you're evaluating options, book a demo and bring this checklist with you.