Questions to Ask Before Buying School ERP Software

A buyer checklist for school ERP demos: who owns the data, backups, support, pricing, hosting, training and what happens if you ever want to leave.

A school ERP demo is designed to look good. Everything is tidy, the sample school has no mistakes, and every button works. Your job in the room is to ask the questions the demo will not answer by itself. Here is a list you can print, take along and score honestly.

Before the demo: decide what you need

Ask your own team first. Sit with the principal, the accountant, a front-office person and one teacher, and write down the three daily jobs each one dreads. A tool that fixes these is worth more than one with a hundred extra features. Bring the list along.

Also decide your constraints: your budget range, the number of students, whether you need hostel or transport, and whether the software must work on a phone.

Data: who owns it and where does it live?

This is the most important section, so spend the most time on it.

  1. Where is our data stored? On the vendor's servers, or on hosting we control? Neither is automatically wrong, but you should know. See cloud or your own hosting.
  2. Who owns it? Ask for the answer in writing, in plain language.
  3. Can we export everything, any time, without asking? Ask them to demonstrate an export of student lists and fee records.
  4. What format is the export? A CSV that opens in Excel is a good sign.
  5. If we stop using you, what happens to our records? You should walk away with everything, in a usable form.
  6. Who at the vendor can see our data? The honest answer should be specific.

Backups and safety

The vendor's brochure may say "secure". Ask what that means:

  • Who takes backups, how often and where are they kept?
  • Have they ever restored one for a customer? Ask for the steps.
  • What happens if the server or hosting fails on a result day?
  • How are staff roles limited, so an office assistant cannot see payroll?
  • What happens to a login when a pupil leaves or a staff member resigns?

If the software is installed on your own hosting, backups are partly your job, and the vendor should say plainly what you need to set up. The security and backup checklist explains what to do.

Fit: does it match your actual day?

Ask them to use your examples, not theirs.

  • Show a family with two children and a sibling discount paying one fee.
  • Show a pupil promoted with unpaid dues carried forward.
  • Show a teacher marking attendance on a phone.
  • Show how your own marksheet layout would print.
  • Show what the principal sees at 9 a.m. without opening a report.

If a feature is "coming soon", treat it as not existing. Buy what works today.

Parents and staff: who uses it?

  • Is the parent and student portal included, or an extra charge?
  • Can one parent see all their children with one login?
  • How do parents and staff reset forgotten passwords?
  • Does each role get its own screen, or one crowded menu for all?
  • Is the language and printout suitable for your school?

Pricing: understand the model, then the number

Ask for a written quote that lists:

  1. The price basis: per school, per student or per module.
  2. What counts as a student, and what happens when strength changes mid-year.
  3. One-time setup, training and migration charges.
  4. Yearly renewal price, and any cap on how much it can rise.
  5. Whether taxes are included.
  6. What happens to price if you add or remove a module.

Work out the cost for your real student count rather than a headline rate. School software pricing models explains the common structures. For My KalviKoodam you can try the pricing page calculator with your own numbers.

Who will actually use it

A product that the principal loves and the front desk resents will fail. Ask each person who will use it daily to try one real task during the demo: the receptionist logs an enquiry, the accountant collects a fee, the teacher marks a class. Watch where they hesitate. Hesitation in a demo becomes avoidance in month two, and avoidance is how schools end up back on paper.

Support and training

  • Who sets it up: the vendor, or you?
  • Is training included, and for how many people?
  • How do you reach support, and in which languages and hours?
  • What is the usual reply time for a problem during fee season or result week?
  • Are updates within a version included in the price?

Ask for the support contact in writing, and test it once before you sign. Send a real question and see how long it takes to answer.

Moving your data in

Migration is where good intentions meet messy spreadsheets. Ask:

  • Can students be imported in bulk from a spreadsheet, and who checks the result?
  • What happens to our existing fee dues and previous year's records?
  • Can we run old and new side by side for a month?
  • How long does a realistic go-live take? See a sample plan in moving from registers to school software.

Talk to another school, and try it first

Ask to speak to a school similar to yours, with a similar size, board and setup, and ask that school what went wrong in the first month. Every product has a hard first month, and the honest ones will tell you what it is. Ask also if you can try the software with realistic data before paying, not just watch a presentation.

Red flags worth noticing

You do not need to be technical to spot these.

  • Answers that change depending on who is asked.
  • A demo that never leaves the vendor's prepared sample data.
  • Pressure to sign before your whole team has seen it.
  • No clear answer to "what happens to our data if we leave?"
  • Prices that rise sharply at renewal with no stated limit.
  • Support described only as "available" with no hours or channel.

None of these alone ends the conversation, but two or three together are a reason to pause.

A simple scorecard

Give each question 0, 1 or 2 points: 0 if the answer is vague or missing, 1 if acceptable, 2 if clear and demonstrated. Add up each section separately. A product that scores low on data, backups or exit is a risk regardless of its other strengths.

Do not rush. A decision made over two weeks and two demos is better than one made in an afternoon because of a festival discount.

Where to go from here

If you would like to put these questions to us, book a demo and bring this list. We will answer what My KalviKoodam does and does not do, and our FAQ covers common questions in advance. To compare more broadly, read how to choose school management software.

Ready to see it with your own school's numbers?

Tell us about your school. We will set up a walkthrough and answer every question.