15 Questions to Ask Before Buying School ERP Software

Print the questions and take them to every vendor meeting. Write the answer you actually heard, not the answer you hoped for. Ask the vendor to confirm the important ones by email, because a verbal promise from a sales executive is hard to enforce a year later.

The questions are grouped into five clusters: the product, your data, money, support and the contract. A fuller treatment of the same decision lives in our school ERP buying guide; this post is the field version you can carry into a room.

1. Can you set up our board’s report card live, in this meeting or a trial? A good answer is a yes, with a date. A weak answer is “our team will customise it after purchase”.
2. Which of the features you just showed are in my plan, and which are extras? Demos often show the top plan. Ask for the plan list in writing.
3. How do teachers mark attendance and enter marks, and how long does it take? Ask to see it on a phone as well as a desktop, with a full class of forty.
4. What can parents do in the app, and does it work on an entry-level Android phone? Ask which languages the parent screens support.

Watch who drives the demo. If the salesperson clicks only through prepared paths, ask them to hand the mouse to your accountant.

1. How do you bring in our existing student and fee records, and what do we have to clean up first? Expect a template and a plan, not “send us your Excel”.
2. Where is our data stored, and who at your company can open it? The answer should name the hosting arrangement and mention access controls.
3. How often are backups taken, and when did you last restore one? A vendor that has never tested a restore does not have a backup, only a hope.
4. Can we export everything at any time, and in what format? Fees, students, attendance, marks and documents, in open formats.

What to listen for

Specifics. “Daily backup to a separate location, restore tested every quarter” is an answer. “Industry-standard security” is a slogan. The Digital Personal Data Protection Act places obligations on the school for children’s data, so a vendor should be comfortable discussing consent, retention and breach handling, as described in DPDP Act 2023 and school data.

1. What is the total cost over three years, with every extra listed? Setup, training, messaging, gateway, apps, branches, storage and taxes. Compare using the method in School ERP price in India.
2. When parents pay online, where does the money go and how soon do we receive it? Direct settlement to the school account is the thing to look for.
3. What can the price do at renewal? Ask for a cap or a lock. Plans and what they include should be as visible as on a pricing page.

Never accept “we will give you a special price” without the written number. If the offer is genuine it can be put in a quote.

1. Who will onboard us, for how long, and who is our contact after that? Look for a named person and a schedule, not a general helpdesk.
2. What are your support hours and response targets, and what happens during a result day or fee deadline? Ask for an escalation route that reaches a human within an hour for urgent issues.

Also ask how new teachers get trained when staff change at the start of a session. A school rarely has the same faculty two years in a row, and training that ends after the first week leaves you exposed.

1. What happens to our data and access if we stop paying, or if you stop operating? Look for a notice period, an export window and a deletion promise.
2. Which schools like ours use the product, and may we call two of them? Choose references your own size and board, not the vendor’s showcase customer.

A reference call is the cheapest due diligence available. Ask the other principal what went wrong in the first month, how fast support responded, and whether they would pick the product again knowing what they know.

Score each question 0 to 2: 0 for evasive, 1 for acceptable, 2 for specific and documented. A total below 20 out of 30 means you have unresolved risks; push for written clarification or move on. Do not let a single impressive feature outweigh unanswered questions about data and support, since those are the ones that hurt after signing.

If a vendor refuses to answer several of these, treat that as a result. If you want to see how a vendor can answer the product questions in practice, you can use the admission and fee pages of any shortlisted system as a starting reference, then ask for a live demonstration against your own scenarios. A demo with us works the same way, and we encourage you to bring this list.

Some behaviours should end a conversation early. A vendor who asks you to pay a large sum before any trial, who will not state a price until a manager “checks”, or who promises that the product will “automatically file” government returns is telling you how the relationship will go.

Be equally wary of a demo that never leaves a single logged-in account. Ask to see the teacher login, the parent login and the accountant login, each with its own limits. If a teacher can open salary data or a clerk can delete a receipt without a trace, you have found a control problem that will cost real money later.

Look at how the vendor treats your unusual requests. A school that follows a state-board pattern, runs a Saturday timetable or collects fees in six instalments will hit unusual cases weekly. “That is not possible” in the first meeting is more useful to hear than “yes, no problem” followed by silence after the contract.

After the purchase

Treat the first ninety days as part of the decision. Set three measurable goals, such as every class marking attendance by 9.30 a.m., all fee receipts issued from the system, and one report card cycle completed without Excel. Review them with the vendor on a fixed date. A partner who welcomes that review is the one you wanted.