School management software price in India: what schools actually pay

Ask three school ERP vendors for a price and you will get three numbers that cannot be compared: one per student per year, one flat annual fee for a module bundle, one “starting from” figure that assumes a configuration nobody runs. This guide converts all of them into one comparable number, and then lists the costs that are not in any of the quotations.

The four pricing models, and what each really costs

Per student, per year

The most common model in India. Typically ₹15 to ₹60 per student per year, with the lower end buying attendance and fees only and the upper end including a parent app and exams. It sounds small until you multiply: a school of 900 students at ₹40 is ₹36,000 a year, every year, and the number rises with your admissions.

Watch for the minimum. Many vendors set a floor of 500 or 750 students, so a school of 300 pays the same as a school of 750.

Flat annual licence

A bundle for ₹25,000 to ₹1.5 lakh a year depending on modules. Easier to budget and better value for a large school, but the module boundaries are where the margin lives — transport, library, hostel and payroll are usually outside the base bundle.

One-time licence plus AMC

An older model, still common with regional vendors: ₹1 lakh to ₹4 lakh once, plus annual maintenance at 15 to 20 percent. You get a perpetual licence to that version. You do not get the source code, and major version upgrades are usually a fresh licence.

Custom build

₹3.5 lakh to ₹9 lakh depending on modules, plus maintenance at 12 to 18 percent a year. You own the code, the database and the hosting. This is the only model where the software bends to your fee circular rather than the reverse.

The same school, four ways

A 900-student CBSE school wanting admissions, fees with online payment, attendance, exams, report cards and a parent app. Five-year view, because school software tends to stay longer than anyone plans.

On this table the per-student model wins outright, and for many schools that is the correct answer — which is worth saying plainly, because this guide is published by a company that builds custom software.

What the table leaves out is whether the cheap option does the job. If your fee structure has term heads, three transport slabs by distance, a sibling concession, a staff-ward concession, RTE students and a late fee with a seven-day grace period, and the product supports two of those, then the clerk is still maintaining a parallel Excel sheet and you have bought a ₹2 lakh attendance system.

The costs that are not in the quotation

These are the five that schools discover in month three, in rough order of how often they surprise people.

• Message credits. SMS and WhatsApp are almost always billed separately. A school sending fee reminders, absence alerts and notices can easily run past ₹15,000 a year in messages. WhatsApp utility messages are currently around ₹0.12 each before GST — the arithmetic is in our WhatsApp Business API pricing guide.
• Payment gateway charges. One and a half to two percent on every fee payment, and on ₹6 crore of annual fees that is ₹9 to ₹12 lakh. Decide early whether the school absorbs it or the parent pays a convenience fee, and get that decision in writing before go-live.
• Data migration. Your existing student, fee and staff data is in a shape nobody designed. Cleaning and importing it is real work, often quoted as an extra, and it is the step most likely to delay a go-live.
• Training, repeatedly. Office staff and teachers need separate training, and school staff turn over. Budget for a refresh every year, and insist on a short recorded video for new joiners rather than a one-off session.
• Modules you will want later. Transport with bus tracking, library, hostel, inventory. Each is a line item. Ask for the price of all of them at the start, when you still have negotiating leverage.

Where custom actually starts making sense

Not as often as software companies suggest. In our experience the threshold is one of three situations, and if none of them applies to you, rent.

1. Above roughly 600 to 800 students, where per-student pricing compounds and the five-year totals converge.
2. Where the fee structure genuinely cannot be configured. Multiple concession types stacking, distance-slab transport, RTE handling and term-wise heads with different late-fee rules is the combination that most often defeats a product.
3. Where connectivity is unreliable. If your office loses internet regularly, a cloud-only ERP is unusable on exactly the days fees are collected. A desktop application that works offline and syncs later solves this, and almost no rented product offers it. We built a coaching institute ERP on precisely that basis — the detail is in the Maths Walah case study.

Multi-branch is a fourth case, but it is really the first one in disguise: three branches of 500 is a 1,500-student licence.

What to standardise before you buy anything

Half the pain of a school ERP implementation is not the software. It is discovering, during configuration, that nobody can state the rules precisely. Do this first and every quotation you receive gets more accurate:

• Write your fee structure as a table: head, class, amount, frequency, and which concessions apply to it.
• Decide the late fee rule exactly — amount, from which day, and who can waive it.
• Pick one report card format and get it signed off by the principal before build, not during.
• List who may see what: can a class teacher see fee dues? Can the accountant see marks?
• Agree the academic calendar dates that drive everything — term boundaries, exam windows, fee due dates.

Those five documents are worth more to a vendor than a two-hour meeting, and they make quotations comparable because everyone is pricing the same thing.

The short version

Under 500 students with a straightforward fee structure: rent, on per-student pricing, and negotiate the message credits. Above 800 students, or with a fee circular no product can express, or with unreliable internet: build, and insist on owning the code and the hosting.

Between those, write down your fee rules first and let the quotations tell you. Our school ERP budget planner gives an indicative custom range in a few clicks, and the school management software page shows what each module actually does.

Frequently asked questions