That one question - asked by a principal in Rajkot during a vendor demo - eliminated four of the five ERP vendors on her shortlist in under ten minutes. The remaining four all gave some version of the same answer: "Our system requires stable internet connectivity."

Only one vendor demonstrated an offline mode on the spot. That's who she signed with.

After sitting in on 50+ school ERP demos across Gujarat, Rajasthan, and Madhya Pradesh, we've noticed something: most school leaders ask the wrong questions.

They ask about features. Vendors love feature questions — they've rehearsed those answers. They ask about pricing. Vendors have slides ready for that too.

But there are five questions that cut through the demo theatre and reveal what a system actually does when you need it most. These are the questions vendors hope you skip.

This guide gives you all five - plus the follow-up questions that go even deeper.

Why Most ERP Demos Are Designed to Impress, Not Inform

Before we get to the questions, understand what you're actually watching during a demo.

A school ERP demo is a curated performance. The vendor controls:

  • Which features they show (their best ones)
  • The order they show them (designed to build excitement)
  • The data they use (clean, pre-loaded, looks perfect)
  • The timing (they'll rush past weak spots)

You're seeing the highlight reel, not the match.

The principal from Rajkot understood this. She didn't let the vendor control the narrative. She interrupted their polished presentation with a single practical question - and immediately saw what the system was really made of.

You can do the same. Here's how.

Question 1: "Show Me What Happens When the Internet Goes Down"

Why this question matters:

Internet connectivity is still unreliable across much of India - especially in Tier 2 and Tier 3 cities. Power cuts happen. Router failures happen. Mobile data runs out. And on the exact morning it happens, you still need teachers to mark attendance, parents to receive notifications, and fee transactions to process.

If the answer is "everything stops," you have a problem.

What the vendor's answer reveals:

  • "Our system is fully cloud-based and requires internet" - honest, but it means operational risk for schools in cities with unstable connectivity
  • "We have an offline mode - let me show you" - this is the right answer; demand a live demonstration, not a description
  • "That rarely happens; connectivity has improved" - they're deflecting; this is a red flag

What to look for in the demo:

Ask them to turn off the Wi-Fi on their demo device - right there, in front of you. A system with genuine offline capability should still allow:

  • Attendance marking (syncs when connectivity returns)
  • Homework entries by teachers
  • Viewing previously loaded student data

If they won't switch off the internet during the demo, you already have your answer.

Follow-up question: "How long can your system function offline before data starts to fail? And what happens to data entered offline - does it sync automatically or require manual upload?"

Question 2: "Can You Show Me a Live School Using This System Right Now - Not a Demo Environment?"

Why this question matters:

Demo environments are manicured. They have clean data, no edge cases, no legacy fee structures, no mid-year admission complications. Real schools are messy. A system that looks effortless in a demo can be frustrating in daily use once you encounter:

  • Fee structures with multiple heads and concessions
  • Students mid-year with partial year data
  • Staff who joined with different salary components
  • Parent app users with ten different phone models

What the vendor's answer reveals:

A confident vendor will happily connect you with a live school. A vendor selling vaporware - or a half-built system - will offer to "arrange a reference call" in a few days, or show you a "similar setup."

What to ask:

"I'd like to see your system as it actually looks at a school similar to ours - same student count, same board, preferably in Gujarat. Can we pull up a live dashboard right now?"

If they can, watch for:

  • Is the data current (today's attendance, recent fee payments)?
  • Does it load quickly or lag?
  • Can they navigate naturally, or do they have to think about where things are?

The deeper question: "Can we call the principal of that school right now and ask them what they'd change about your system if they could?"

This is the question vendors never expect. Most will hesitate. A vendor with genuinely happy clients will make the call.

What this reveals about Campus On Click: We have 150+ live schools across Gujarat, Rajasthan, and Madhya Pradesh. We will connect you with any of them - unscripted, unannounced. That confidence comes from actual product quality, not marketing polish.

Question 3: "What Does Your System NOT Do Well?"

Why this question is the one vendors hate most:

Every vendor will tell you what their system does brilliantly. No vendor volunteers its weaknesses. But every software product has gaps - things it handles awkwardly, features that are technically present but practically unusable, integrations that are listed on the brochure but unreliable in practice.

A vendor who can't answer this question honestly is either:

  1. Unaware of their product's limitations (concerning)
  2. Unwilling to tell you (more concerning)

What honest answers look like:

  • "Our timetable module is functional but the interface is less intuitive than our fee module - schools with complex rotating timetables sometimes need more training time"
  • "Our mobile app works well for Android; iOS users occasionally report slower load times on older iPhones"
  • "Our WhatsApp integration works through a business API that requires a separate subscription - it's not built in"

These are honest, specific answers. They tell you the vendor knows their product deeply and respects your intelligence enough to be straight with you.

Red flag answers:

  • "Our system is very comprehensive; we cover everything"
  • "We haven't had any complaints from schools"
  • "Every school has different needs, so it depends"

These non-answers tell you either the vendor is hiding something or they genuinely don't know their product well enough. Neither is good.

Follow-up question: "What's the most common complaint you receive in your support tickets? And how are you addressing it in your roadmap?"

A vendor who can tell you their top support ticket categories - and what they're doing about them - is a vendor who's genuinely invested in improvement. That's who you want a multi-year relationship with.

Question 4: "Walk Me Through What Happens When Something Goes Wrong at 8 AM on a Monday"

Why this question matters:

Fee collection day. Parent app crashing. Attendance module not syncing. These things happen - not often, but they happen. And when they do, they happen at the worst possible time: during the busiest period of the school day, when your staff have zero bandwidth to troubleshoot software.

The question isn't "does your system break?" - everything breaks eventually. The question is: what happens next?

What you're evaluating:

  1. Response time commitment - Is it 2 hours? 24 hours? "Best effort"?
  2. Support channel - Phone? Email only? Chat? Can you call a human being?
  3. Language - For Gujarat schools especially: is there Gujarati-speaking support staff?
  4. Local presence - Is your support team in India, in the same time zone, understanding the Indian school calendar?
  5. Escalation path - If Level 1 support can't solve it, what happens?

What to ask specifically:

"If our fee collection module stops working at 8 AM on the 10th of the month - our biggest fee day - what exactly happens? Who do I call? How quickly will someone respond? And what's your SLA for critical issues?"

Watch the vendor's comfort level with this question. A vendor with mature support infrastructure answers it immediately. A vendor with thin support will hedge.

The follow-up that reveals everything: "Can you show me your support portal right now? I want to see what a logged ticket looks like and your average resolution time."

Most vendors won't expect you to ask to see their support backend. The ones who can show it confidently - with real resolution time data - are the ones worth considering.

What to look for in a support SLA:

  • Critical issues (system down): 2-hour response, 4-hour resolution target
  • Major issues (module failure): 4-hour response, 8-hour resolution
  • Minor issues (UI/display): 24-hour response, 48-hour resolution

Anything slower than this for a school of 500+ students is inadequate.

Question 5: "What Does Data Migration Actually Look Like - And What Happens If We Want to Leave?"

Why this question is the most important long-term question:

Most principals focus entirely on getting into a system. Almost none think about getting out of one.

This is a mistake.

School data is irreplaceable: years of student records, fee histories, exam results, staff information, admission data. If you ever need to switch vendors - because your needs change, because the vendor raises prices dramatically, because support deteriorates - you need to know exactly what data you get back, in what format, and how usable it is.

Data migration in - ask:

"We have 5 years of student data in Excel and Tally. Show me exactly how you migrate that into your system. Who does the migration - your team or ours? How long does it take? What format does our data need to be in? And what happens if there are errors during migration?"

A vendor with a tested migration process will have clear answers: a specific format they accept, a timeline, a team member who handles it, a quality check process.

A vendor who says "just send us your Excel and we'll handle it" - with no further detail - has likely never done a clean migration for a school with complex historical data.

Data migration out - ask:

"If we decide to leave your system after 3 years, what do we get? In what format is our data returned? Can we export it ourselves, or do we depend on you? Is there a charge to get our own data back?"

This question will make some vendors visibly uncomfortable. That discomfort tells you everything.

What acceptable answers look like:

  • "You can export all your data at any time in CSV and Excel format - no charge"
  • "Student records, fee histories, attendance, exam marks - all exportable in standard formats within 48 hours of request"
  • "You own your data completely; we just store it for you"

Red flags:

  • "Data migration out is a separate service we can discuss" (translation: they'll charge you)
  • "Your data is stored in our proprietary format" (translation: it's very difficult to move)
  • "We've never had a school leave us" (deflection - doesn't answer the question)

Why this matters even if you never switch: A vendor who gives you clean data portability rights is a vendor who knows their product is good enough that you won't want to leave. That confidence is exactly what you should look for.

The Vendor Evaluation Scorecard

Use this table during your next demo. Rate each vendor 1-5 on each question.

Question What 5/5 Looks Like What 1/5 Looks Like
Q1: Offline mode Live demo of offline mode with sync explanation "We need internet; so does everyone"
Q2: Live school access Connects you to real school, invites reference call "We can arrange a reference later"
Q3: Honest weaknesses Names specific limitations without prompting "Our system is very comprehensive"
Q4: Support SLA Shows support portal, cites resolution times "We have a dedicated support team"
Q5: Data portability Explains export format, confirms no exit fee "Data migration out is a service"

Scoring:

  • 20-25: Strong candidate - proceed to pilot
  • 14-19: Proceed with caution - ask follow-ups on low-scoring areas
  • Below 14: Walk away

5 Bonus Questions Worth Adding

These aren't in the main list, but experienced school administrators ask them. Consider adding any of these based on your school's specific situation.

For multi-campus schools:
"Show me how the principal of one campus can see data from another campus in real time - without logging out and logging in again."

For CBSE schools:
"When CBSE changes its report card format - as it has done multiple times - how quickly is your system updated? Who bears the cost of that update?"

For Gujarat schools specifically:
"Can your system generate government reports in Gujarati? Show me a sample output."

For fee-sensitive schools:
"Walk me through what happens when a parent disputes a fee. How does your system handle partial payments, reversals, and audit trails?"

For schools considering AI features:
"Any AI features you're advertising - are they live in production right now, or are they on your roadmap? Can I use them today?"

This last question has become increasingly important. Many vendors are advertising "AI-powered" features that are either experimental, not available in India, or require additional subscriptions that aren't mentioned during the demo.

What to Do After the Demo

The Day After: Write Up Your Notes

Don't wait. The day after your demo, write down:

  • What impressed you (and whether it was genuinely useful or just visually slick)
  • What questions they couldn't answer
  • What they promised verbally that wasn't in the written proposal
  • Any numbers they cited (save time by X%, improve collection by Y%) - were these from real data or estimates?

The Reference Check: Do It Yourself

Don't use the references the vendor provides - those are cherry-picked. Instead:

  • Ask the vendor for a list of all schools in your city or district using their system
  • Contact two or three schools from that list yourself
  • Ask them: "What's your biggest frustration with the system?" - not "Are you happy with it?"

The second question gets honest answers. The first gets polite ones.

The Pilot: Non-Negotiable

Before committing to a full-year contract, negotiate a 60-day pilot with one class or department. Any vendor confident in their product will agree to this. A vendor who pushes back against a pilot is a vendor who knows their onboarding experience is rough.

What to test during a pilot:

  • Does attendance sync accurately and on time?
  • Do parents actually open and read notifications?
  • Can teachers figure out the homework module without IT support?
  • Does the fee module handle your school's specific structure?
  • How long does support take to respond when you log a test issue?

Sixty days of real use tells you more than sixty minutes of a polished demo.

Why Campus On Click Publishes This Guide

We know this guide will cost us some leads. Principals who read it carefully will ask us these same questions during our demos - and some of our answers will be less than perfect.

We're okay with that.

Because the schools that work best with us aren't the ones we sold to with a slick presentation. They're the ones who evaluated us rigorously, challenged us honestly, and chose us knowing exactly what they were getting - including our real limitations.

Greenwood Academy in Ahmedabad chose us after asking every question on this list. Their communication transformation story has since been shared with hundreds of schools across India.

When you're ready to ask us these questions, we're ready to answer them.

Book a Demo - We Welcome Hard Questions →

Download: Free Vendor Evaluation Template

We've compiled a printable evaluation template that includes:

  • The 5 questions above (with scoring rubric)
  • 15 additional technical questions for your IT team
  • A feature comparison matrix for 8 common modules
  • A contract review checklist (what to look for before signing)
  • A reference check script

This template has been used by 200+ school principals across India to make more confident ERP decisions.

Download Free: School ERP Vendor Evaluation Template →

What Other School Leaders Are Saying

Rajesh Patel, Principal, CBSE School, Vadodara:
"I used Question 3 in my last demo - 'What does your system NOT do well?' The vendor paused for a full 30 seconds. Then gave me a non-answer. I crossed them off the list immediately. The vendor who answered it clearly and honestly, with specific examples, got our business."

Sunita Mehta, School Owner, Rajkot:
"We'd been burned by a vendor before - they promised everything in the demo, delivered about 60% of it. These five questions would have saved us six months of frustration. We now use them every single time."

Amit Sharma, Director, Multi-Campus School Group, Surat:
"Question 5 about data portability changed how I think about ERP contracts entirely. I now ask every vendor: 'If I want to leave, what does that look like?' The ones who answer it confidently are the ones worth trusting."

Frequently Asked Questions

Q1: How many ERP vendors should I demo before making a decision?

A: Three to five vendors is the optimal range for most schools. Fewer than three doesn't give you enough comparison points - you may not know what good looks like without contrast. More than five creates decision fatigue and the demos blur together. For a 500-student school in Gujarat, shortlist based on three criteria first: (1) Do they have live schools in your city or region? (2) Do they support Gujarati language? (3) Is their pricing within your budget range? Apply these filters before requesting demos to make sure your demo time is well spent.

Q2: Should I let the vendor control the demo agenda, or should I give them mine?

A: Give them yours. Before the demo, send the vendor a written agenda that includes the five questions in this article. Tell them: "These are the areas I want to focus on. Please structure your demo around these questions." Two things will happen: vendors with strong products will welcome the structure; vendors with weak products will push back or try to redirect. Both responses give you useful information before the demo even starts. A prepared agenda also protects you from the "feature tour" format - where vendors spend 45 minutes showing you everything without showing you the things that actually matter.

Q3: What are the biggest mistakes schools make when choosing an ERP vendor?

A: The three most common mistakes are: (1) Choosing on price alone - the cheapest ERP rarely delivers the support and reliability that Indian schools need, particularly during critical periods like fee collection and exam season. (2) Not involving teachers in the selection process - a system that teachers find frustrating will be underused regardless of how technically capable it is. Run a brief teacher demo before committing. (3) Not negotiating a pilot period - any vendor confident in their product will agree to a 30-60 day pilot with one class or department. If a vendor refuses, treat that as a significant warning sign.

Q4: What should a school ERP contract include that most schools overlook?

A: Four things most principals don't check in contracts: (1) Data portability clause - explicitly states you can export all your data at any time, in a standard format (CSV/Excel), at no additional charge. (2) SLA for critical support issues - defines response and resolution times for system failures, not just general queries. (3) Price lock period - confirms the vendor cannot raise prices for at least 12-24 months after signing. (4) Training coverage - specifies how many training sessions are included, whether refresher training is available, and what happens when you hire new staff mid-year. If any of these are absent, add them before signing.

Q5: How do I evaluate a school ERP vendor's long-term viability? I don't want to switch systems in two years.

A: Four indicators of long-term vendor stability: (1) Client base size and growth - a vendor with 500+ schools and growing is more likely to invest in product development and support. Ask how many schools they had three years ago versus today. (2) Product update frequency - ask when their last major product update was released and what it included. Active development indicates an investment in the product. (3) Funding or financial stability - for Indian EdTech vendors, ask directly: "Are you bootstrapped or funded? What's your business model?" A vendor dependent on VC funding without a clear path to profitability carries risk. (4) Contract terms - a vendor willing to offer annual contracts (not forcing multi-year lock-in) is more confident in their ability to keep you satisfied year after year.