Start with the workflows you run, not the features being sold
Vendors will hand you a feature list with 200+ items. Most of them you'll never use. The five workflows that determine whether you'll be happy in 12 months are: how attendance gets marked, how marks get entered and reported, how fees are collected and reconciled, how parents see information, and how transport routes are managed. Test those five end-to-end during demos. Everything else is decoration.
Make a list of your current pain points before any vendor calls. Where does your office staff actually waste time? Whose calls is the principal getting most often? What do parents complain about? An ERP that doesn't fix those specific issues is the wrong ERP — even if it has 200 modules.
Board support: not all vendors handle State Board well
Most school ERP tools default to CBSE patterns and treat State Board, ICSE, IB, and IGCSE as configurable variants. In practice, this means the State Board templates are afterthoughts and won't match what your local board office actually wants on the report card.
Ask the vendor to show you their Tamil Nadu State Board template, their West Bengal Board template, their Maharashtra MSBSHSE template — whichever applies to you. Don't accept 'we can configure it' — ask to see the configured version. If they can't show you a real one, you'll be the customer they configure it for, and the customer who finds the bugs.
Marks improvement analytics — the differentiator no one talks about
Most ERPs report current-term marks. They show you who scored what in the last test. But the question that actually drives academic decisions is: who is improving and who is slipping? Which sections are pulling improvement? Which class teachers are getting results?
An ERP that surfaces marks improvement at the student, section, class, division, and whole-school levels — comparing current vs previous test — gives your academic team something they can act on every term. Most vendors don't have this. Ask specifically.
Mobile apps: included or paid extra?
Parent and Teacher mobile apps are no longer optional. Parents expect push notifications for attendance, fees, and marks. Teachers want to mark attendance and enter marks from their phones during the day, not at a desktop after school.
Some vendors include native iOS and Android apps in the base price. Others charge extra. Some only have web — they'll call it 'mobile-friendly,' which means the website resizes on a phone. Make the distinction explicit before you sign. A native app with push notifications drives 5-10x the parent engagement of a mobile-friendly website.
DPDPA compliance: ask the question, get a written answer
The Digital Personal Data Protection Act (DPDPA) applies to schools handling student data. Consent capture during admissions, audit logs of who accessed what, and the right to erasure all need to be supported. Most vendors will say 'yes, we're compliant' verbally. Get the answer in writing — including specifically which DPDPA requirements they cover and which they don't.
If a vendor can't articulate which sections of DPDPA their product handles, they probably haven't actually thought about it. That's a yellow flag. The market is moving — pick a vendor that's already done this work, not one who'll do it 'soon.'
Pricing models: per-student vs per-module vs flat
Pricing models in this market are inconsistent. Some vendors charge per-student per-month. Others charge per-module bundle. A few charge flat per school. Some charge for setup separately, some bundle it.
Build a 3-year total cost projection before you sign. Include the platform fee, mobile app fees if not included, payment-gateway fees if any, SMS bundles, support tier, and any feature-flag upgrades the vendor mentions casually. The advertised price is rarely the actual price.
- Per-student per-month: most common; predictable
- Per-module: useful if you only need a slice; risky if you grow
- Flat per school: attractive for small schools; can be expensive for large
- Setup fee: ranges from zero to ₹50,000+; ask explicitly
Migration: how does data come over?
Schools have 5-15 years of existing data: student profiles, employee records, marks history per academic year, fee backlogs, salary slips. The right ERP gives you structured Excel/CSV import templates and handles the migration in your initial onboarding — without you paying extra.
Ask: 'show me the import template you'll use for our marks history' before signing. If the vendor stumbles, you'll be in for months of manual data entry once you go live.
Multi-campus and trust-level reporting
If you run a trust with multiple campuses, you need consolidated trust-level reporting alongside per-campus operational independence. Most ERPs handle one or the other — a single school well, or a chain of identical schools well. The combination is rare.
Ask to see the trust-level dashboard. Per-campus admins should see only their campus. Trust admins should see consolidated numbers across all campuses for finance, admissions, and academic performance. If the vendor can't show you a working trust dashboard, build that into the contract as a milestone — or pick someone else.
Per-school database vs multi-tenant
Most cloud school ERPs are multi-tenant — your data sits in shared tables alongside hundreds of other schools. This is fine for cost, but it means backups, restores, exports, and audits are constrained by the vendor's shared architecture.
A few vendors offer per-school database isolation. Each school gets its own database with its own backup and restore. It's slightly more expensive but gives you actual data control. For schools handling sensitive student data, this is increasingly important — and it's what DPDPA compliance officers will start asking about as audits ramp up.
Final checklist before signing
Before you sign anything, run this list:
- Have you seen all five core workflows demonstrated end-to-end with realistic data?
- Have you seen the configured report-card template for your specific board?
- Have you seen the migration import template for your data?
- Have you seen the parent and teacher mobile apps on a real phone?
- Have you tested the parent portal as a parent — not as an admin?
- Have you priced the 3-year total cost including all add-ons?
- Have you confirmed DPDPA compliance in writing?
- Have you talked to two existing customers in your size band and board?