What school management software costs in India

The two pricing models

Subscription products charge per student per year. That looks inexpensive at 200 students and stops looking inexpensive at 800, because the bill grows with exactly the success you were hoping for. There is usually an implementation fee on top, and often a charge to get your data out.

Owned software costs more upfront and nothing recurring beyond hosting. It makes sense when the roll is large enough that per-student pricing exceeds ownership, or when your process genuinely does not fit a product.

Neither is the right answer in general. Which one wins depends on your roll, your growth plan and how unusual your process is.

The number to compare: five-year total

A quoted annual licence is not a price. The comparable figure is the five-year total, and it has five parts. Ask both kinds of vendor for it in writing. The ones who will not give it are telling you something.

• Licence or build cost, over five years at your projected roll rather than today's
• Implementation: configuration, data setup and the vendor's time
• Training, including the staff who join after go-live
• Migration of historical data — fee records, student history, attendance
• The cost of leaving: export fees, format, and whether you get your data at all

What moves the number on a custom build

If you are scoping an owned system rather than a subscription, these are the factors that change the figure. They are the same drivers we publish on the pricing page, applied to schools.

• Number of distinct user roles and permission levels — the Little Lumos portal needed four: superadmin, admin, teacher and parent
• Whether multi-tenancy is needed now or later. Adding it afterwards is a rewrite, not a feature
• Integrations with systems you already run, such as accounting or a payment gateway
• Volume of historical data to migrate, and what condition it is in

Where per-student pricing quietly breaks

Most general-purpose school ERPs are thin in the same four places: inventory, expenses, event management and daily activity records. For a secondary school those are edge cases. For a preschool they are the day.

That gap is usually filled with a spreadsheet alongside the ERP, which means you are paying per student for a system that still does not reconcile with how the office works. When you compare costs, count the spreadsheet.

It is also the reason the portal we built exists. The client needed automated fee generation, attendance, daily activities for parents, an admission pipeline, expenses, inventory, events and notifications in one system. No product fitted, and the pieces they were combining did not reconcile with each other.

Most schools should buy

If a product covers most of what you need and you can adapt to the remainder, buying is faster, cheaper and less risky. We will say so on a first call rather than take the project.

Building becomes the better answer in three situations: when your process is the thing that makes you distinctive and no product accommodates it; when per-student licensing across a growing roll exceeds the cost of owning a system; and when you need the modules products treat as edge cases.

Before you sign anything

Two questions decide more than the price does. Who holds your data, and what happens on the day you want to leave. A school that cannot export five years of fee and attendance history is not choosing a vendor, it is choosing a landlord.

Ask for the export format before you sign, not after. A CSV of everything is a different proposition from a PDF of some of it.