The questions to ask a school ERP vendor before you sign questions

A principal sits in a slick vendor demo. The screens are gorgeous, the salesperson is charming, and every click lands exactly where it should. She nods along — and then realises she has no idea what to actually ask. The demo answers questions she didn't have and quietly skips the ones she'll regret not asking: where will our students' data live, what happens if we leave in two years, and what is the real bill once the SMS, gateway and renewal charges arrive? She signs on feeling good. The doubts come later — usually around the first AMC invoice.

Here is the thesis of this guide: the right questions to ask a school ERP vendor are not about features — they are about ownership, exit, compliance and the all-in price. A demo is engineered to show strengths and hide gaps. A short, sharp list of questions does the opposite: it surfaces exactly the risks a demo is designed to bury. Ask these of every vendor on your shortlist, including Inkwelly, and let the answers — not the animation — decide.

Why most school ERP demos mislead

A demo is a sales tool, not a contract. It runs on a clean dummy database, on the vendor's fastest server, narrated by their best presenter. None of that survives contact with 1,200 real students, a Monday-morning fee rush, and a teacher on a 2G phone in a Tier-3 town. The questions to ask a school ERP vendor exist to test what the demo can't show — the boring, binding, expensive parts. Here is what a polished walkthrough routinely hides:

The India bar: what separates a real vendor from a slide deck

India adds a layer of questions that generic ERP checklists ignore. The DPDP Act, 2023 and its DPDP Rules, 2025 now require verifiable parental consent before processing a child's data — and almost every student in your school is a minor under 18. SMS in India is blocked unless it rides a TRAI-registered DLT header with pre-approved templates. From the 2026–27 session, every enrolled student from Class 1 to 12 must have an APAAR ID, and the UDISE+ portal won't open new entries until last year's Student Progression is locked. A vendor that can't speak to these isn't compliant for India — it is a foreign product with an Indian price tag.

The 20 questions to ask a school ERP vendor before you sign

Work through these on every shortlisted vendor. Each is written so a non-technical owner or principal can ask it out loud in a meeting — and each carries the reason it matters, so you know why a vague answer is a red flag.

Data ownership and exit

1. Do we own our data, and can we export all of it the day we leave? — If the answer isn't an unconditional yes, you don't own it; the vendor does. Get it in writing.

2. In what format, and at what cost, is a full export? — A usable export means standard CSV/Excel for every module — students, fees, attendance, marks — at no extra charge. 'We'll provide a PDF' or 'migration assistance is billed separately' is a lock-in in disguise.

3. If we cancel, how long do we keep access to download our records? — You want a defined window (e.g. 30–90 days) to pull everything, not an account that's switched off the day the contract ends.

DPDP and data residency

4. Is our data stored in India? — Under the DPDP Act, student data of minors deserves an India region. Ask where the servers and backups physically sit, not just where the company is registered.

5. How do you handle verifiable parental consent and a parent's right to erase data? — The DPDP Rules, 2025 require real consent for children's data and the ability to withdraw it. The system must support this, not just the contract.

6. Do you sell, share or use our data to train anything? — The answer you want is no. Student data is not a growth asset for your vendor.

WhatsApp and SMS compliance

7. Is your WhatsApp messaging on the official Business API? — The official WhatsApp Business API is governed by Meta's policy and has no separate DLT step; unofficial 'WhatsApp panels' risk numbers getting banned and break the moment you scale.

8. For SMS, is it sent on a DLT-registered header with approved templates? — In India, SMS that isn't on a registered DLT header with an approved template is blocked by telecom operators 100% of the time. Ask who registers the templates — you or them.

CBSE, UDISE+ and APAAR exports

9. Can you export data ready for UDISE+ and APAAR? — From 2026–27, APAAR is mandatory for every student Class 1–12. A one-click, correctly-formatted export saves your office weeks each year versus re-typing into the portal.

10. Does it generate board-format report cards and the Student Progression data UDISE+ needs? — UDISE+ won't accept new entries until promotions, marks and attendance from the prior year are finalised. The ERP should produce this cleanly.

Pricing and hidden fees

11. What is the all-in price per student, per year — everything included? — Indian school ERP typically runs ₹10–₹60 per student per month. Make the vendor write the total, not the headline rate.

12. Are SMS, the payment gateway and the mobile app inside that price or extra? — SMS often adds ~₹25 per student per year on top; online collection carries a gateway charge (MDR) of roughly 1.5%. These 'small' line items are where the budget leaks.

13. What is the AMC, and what does it actually cover? — Annual maintenance on licensed software commonly lands at 18–22% of the licence value. Ask exactly what year-two support and upgrades are included for that money.

14. What does training and onboarding cost? — It can range from ~₹30,000 a year for a small school to ₹2.5 lakh for a large one. Confirm whether it's free, capped, or a recurring line item.

Support SLA

15. What is your support response time, and is it guaranteed in writing? — 'We have great support' is not an SLA. Ask for a defined response time for critical issues and whether it survives in the contract.

16. Is support available in our language, by a team that understands Indian schools? — Time-zone-aligned, Hindi-or-regional-language support resolves a fee-day crisis far faster than an overseas ticket queue.

Lock-in and contract

17. What is the contract length, and does it auto-renew? — Watch for multi-year locks and silent auto-renewal with a price hike. A one-year term with a clean exit protects you while you're still proving the fit.

18. What does it cost to leave, and is there an exit or migration fee? — Switching ERPs can carry an effective 'exit tax' of 150–200% of the annual contract value once data migration and retraining are counted. A no-cost data export clause removes most of that risk up front.

Mobile app, migration and training

19. Can I see the real parent and teacher apps and their store ratings? — Don't accept a demo build. Look at the live app, its rating, and the date of the last update — a neglected app is a neglected product.

20. How do you migrate our current data, and who does the work? — Ask for a written migration plan from your registers, Excel or existing ERP, and confirm whether the vendor does it or hands you a template and wishes you luck.

The kinds of vendors you'll be asking

You'll put these questions to a familiar set of names. India's school ERP market includes Teachmint, Vidyalaya, Fedena, Entab, MyClassboard, Campus 365 and Edunext, alongside newer cloud-first products like Inkwelly. Each is strong somewhere and thin somewhere else — one nails fees but charges per SMS, another has a polished app but a punishing exit clause, a third is feature-rich but slow to support a Tier-3 school. The questions above are deliberately vendor-neutral: they're built to expose the gap, whoever is sitting across the table. Use the same list for every demo so you're comparing answers, not personalities.

The cost reality behind the headline price

The number on the brochure is rarely the number you pay. Start with the base of ₹10–₹60 per student per month, then add the parts that are almost always quoted separately: SMS at roughly ₹25 per student per year, a payment-gateway cut near 1.5% of every online collection, training that can run from ₹30,000 to ₹2.5 lakh annually, and an AMC of 18–22% of the licence value if it's a licensed (rather than fully cloud) product. For a 1,000-student school, the difference between 'base price' and 'all-in price' can be a few lakh rupees a year. The vendors who answer question 11 with a single honest total are usually the ones worth shortlisting.

Where Inkwelly fits

We wrote this guide knowing you'll point these questions at us too — and we'd rather you did. Inkwelly is a cloud-first school ERP built for Indian schools, so the India answers are designed in, not bolted on: data hosted in an India region, a full self-service export of your records whenever you want them, the official WhatsApp Business API plus DLT-aware SMS, and exports built for UDISE+ and APAAR. If you're still narrowing your shortlist, our buyer's checklist for choosing a school ERP and our breakdown of what school software actually costs in India go deeper. Ask us question 1 through 20 in your demo. Honest answers should be the easy part.

“A demo shows you what a vendor wants you to see. The right questions show you what you'll be living with two years from now.”

Decide with the answers, not the animation

You don't need a procurement department to choose well — you need this list and the discipline to ask every question of every vendor. Send it ahead of the demo so nobody can improvise. Score the answers, not the slides. The vendor who gives you a single all-in price, an India data region, a no-cost export clause and a written support SLA has already told you more than any feature tour ever will. The one who dodges question 1, 4 or 18 has told you something too.

Bring these 20 questions to your next demo

See how Inkwelly answers every one — data ownership, DPDP, WhatsApp, UDISE+/APAAR and the all-in price. Book a free, no-pressure demo.