Operations9 min read

How to choose a school ERP: a buyer's guide

A procurement checklist for principals choosing a school ERP: the modules that matter, questions to ask, hidden costs, and protecting your data.

Buyer's GuideSchool ERPLeadership

Buying software is a decision you live with for years

Most principals buy a school ERP once and then run it for five or six years. The demo takes an hour; the consequences last a long time. If the fees module is clumsy, your office staff fight it every morning. If the parent app is confusing, you field the complaints. If the vendor disappears after go-live, you are stuck.

So the question is not "which software has the most features." It is how to choose a school ERP that your office, your teachers, and your parents will still be glad you picked two years from now. This guide is the checklist I would use if I were sitting in your chair, evaluating the whole platform — not just the shiny parent app they show you first.

Take it as a procurement tool. Print it, take it into the demo, and tick boxes.

Start with the modules you actually run on

Vendors love long feature lists. Ignore the length and check whether the modules your school depends on every single day are genuinely good, not just present.

  • Admissions — enquiry to enrolment, with documents and follow-ups in one place.
  • Fees — itemised heads (tuition, transport, books), instant digital receipts, clean dues lists, and *concessions handled properly*. In Indian schools this means RTE, merit, sibling, staff-ward, single-parent and EWS, each with a full audit trail. If concessions are a manual override with no record, walk away.
  • Attendance — daily marking plus the option of biometric or RFID later. Ask which devices it supports; AiraNexus, for instance, integrates with ESSL and Zkteco readers you may already own.
  • Exams and report cards — does it produce *your board's* format? CBSE, ICSE and state boards all differ. Ask to see a real generated report-card PDF for a school like yours, with grades or CGPA, not a blank template.
  • Timetable, homework, HRM and communication — the daily connective tissue.

A useful test: ask the salesperson to log in and complete one real task in front of you — generate a fee receipt for a sibling-concession student, or produce a Class 9 report card. If they fumble or "send it to you later," that is your answer.

You can browse a full module breakdown on most vendor sites; ours lives at /products, with fees, exams and report cards detailed separately.

The questions that separate good vendors from sales decks

Bring these to the meeting. The hesitations tell you more than the answers.

  • *"How long until we are actually live, with our students imported?"* A real timeline, not "depends." (Ours is seven days.)
  • *"Who does the data migration — you or us?"* Importing thousands of students from Excel is where most rollouts stall.
  • *"Show me the support channel and your response times."* Email only? Phone? WhatsApp? What are the stated SLAs during fee-collection season?
  • *"Is the parent app live on Android and iOS today?"* "Coming soon" is fine if they say so honestly — be wary of vague promises.
  • *"Can parents see live attendance and instant absence alerts, or only end-of-day?"*
  • *"Do messages support Telugu, or only English?"* For most of our schools, parent communication in the local language is not optional.
  • *"What does WhatsApp and SMS cost, and is push notification free?"* This is where hidden costs hide (more below).

If you want a head start, /faq and a structured demo cover most of this in one sitting.

Red flags worth walking away over

Some signals are bad enough to end the conversation:

  • No way to export your own data. If you cannot pull your students, fees and results out in a standard format, you are renting a hostage situation.
  • Per-feature pricing that balloons. "Base plan" plus charges for report cards, plus charges for the app, plus charges for each notice. The number on the brochure should resemble the number on the invoice.
  • Pressure to switch on online fee payment immediately. Payment-gateway commissions add up, and many families still prefer paying at the office. A vendor who insists is optimising for their cut. We deliberately [don't push online fee payments](/blog/why-we-dont-ship-online-fee-payments) for this reason.
  • Vague answers on security. "It's all secure, don't worry" is not an answer. Ask for specifics.
  • A parent app that demands you share staff phone numbers. Good systems let teachers and parents chat without exposing personal numbers.

Surface the hidden costs before you sign

The sticker price is rarely the real price. Map the full cost over three years, including:

  • Setup and migration — one-time or ongoing?
  • Training — for office staff and teachers, included or extra?
  • Messaging — push notifications and in-app notices should be free and unlimited. SMS and WhatsApp cost money everywhere because the telecom operators charge per message; the fair model is transparent prepaid recharge packs, which is how we do it. Just make sure you know the per-message rate.
  • Per-student vs per-feature — a flat per-student-per-month rate is easiest to budget. For reference, ours is simple per-student pricing (quoted to your school), billed yearly. A 600-student school can do that arithmetic on the back of a fee receipt; see [/pricing](/pricing).

Cost-effective does not mean cheapest. It means predictable, with no surprise line items when the new session starts.

Data ownership and your exit, on day one

Ask the awkward question early: "If we leave in three years, what happens to our data?"

A trustworthy vendor has a calm, specific answer. Yours should be able to:

  • Export students, fees, attendance and results in standard formats whenever you ask.
  • Tell you plainly where data is stored, who can access it, and how it is protected — role-based access, audit logs, encryption at rest and in transit, daily backups.
  • Speak to India's data law. DPDPA-awareness matters now; a vendor who has never heard of it is behind. We publish our stance on [data protection](/dpdpa) and [security](/safety-security) openly, including the honest note that our ISO 27001 certification is *in progress*, not yet awarded. A vendor willing to tell you what they have not finished is usually more trustworthy than one claiming perfection.

Owning your data on the way in and the way out is not a luxury. It is the difference between a partnership and a trap.

For trusts: multi-campus, concessions and the board

If you run more than one campus, or report to a board or trust, add a layer:

  • Multi-campus under one umbrella — separate logins and permissions per campus, with a consolidated dashboard so the trust sees every school in one view.
  • Concession and audit support — when an auditor or board member asks "show me every RTE and EWS concession this year," the system should produce it in seconds with a full trail. This is also what your [accountant will thank you for](/blog/five-reports-your-accountant-will-love).
  • Reports the board understands — collection summaries, dues, concession totals, headcount, on demand.

These are the features that turn a quarterly board meeting from a scramble into a five-minute screen-share.

Onboarding, go-live and the first hard week

Software is easy; change is hard. Ask exactly what the first two weeks look like:

  • Who imports your existing data, and how messy can your Excel be? (Moving off spreadsheets is a real project — [here's how we approach it over a weekend](/blog/migrate-excel-to-airanexus-weekend).)
  • Will someone train your front office in person or over a call?
  • Is there a named person to reach during the first fee cycle, when things actually get tested?

A good vendor treats go-live as a shared project with a date, not a download link they email you.

The short version

If you remember only a few things: check that the modules you run daily are genuinely good, ask the hard questions about migration and support, hunt down the hidden messaging and setup costs, and confirm you own and can export your data. The flashy app matters, but it is the last 10% — the office workflow and the exit clause are the 90%.

Choose for the boring Tuesday in October, not the demo. The right system makes that Tuesday quiet.

If you would like to walk this checklist against a real platform, book a demo or talk to us — bring your toughest questions. A vendor worth choosing will welcome them.