In 2026, school ERP software in India is advertised at 15 to 40 rupees per student per month, with flat annual plans from about 9,000 rupees for the smallest schools. A 500-student school reading that number expects to pay around 1.5 lakh a year.
It will pay 1.8 to 3.2 lakh in the first year. The advertised price is routinely 40 to 60 percent below the real first-year cost, and the gap is not hidden in the small print. It is in five lines that nobody puts on the comparison page: setup and data migration, the SMS pack, the payment gateway percentage on every fee you collect, the mobile app, and the hardware.
This guide itemises all of them, then works out the only question that actually has a different answer for different schools: whether a group should ever build its own.
The quick-reference table
| How it is sold | Typical price | Fits |
|---|---|---|
| Per student per month | 15 to 40 rupees, falling to 5 to 15 at scale or on lean plans | Most cloud ERPs, most schools |
| Per student per year | 100 to 500 rupees | The same thing, billed annually, often with a discount |
| Flat annual plan by school size | 9,000 to 75,000 for schools under 500 students | Small schools, and the easiest plans to compare |
| Mid-size school, all modules | 75,000 to 2.5 lakh a year for 500 to 1,500 students | The band most private schools land in |
| Large institution or group | 5 to 12 lakh a year and up | Multi-campus, hostel, transport fleet, several boards |
| Custom build | 10 to 25 lakh once, then 15 to 25 percent a year | Groups, not single schools. The arithmetic is below |
Per student per month is the headline, and it behaves exactly like per vehicle in fleet software, per flat in society management software or per bed in hospital software: a small number attached to a large multiplier, quoted without the things that sit beside it.
Why the advertised price is 40 to 60 percent short
Here is the first year for a 500-student school on a mid-range plan, with every line a vendor would charge separately.
| Line | Year one |
|---|---|
| Subscription at 25 rupees a student a month | 1.5 lakh |
| Setup, configuration and data migration | 15,000 to 30,000 |
| Staff training, usually priced per session after the first | 10,000 to 25,000 |
| SMS pack for attendance alerts, fee reminders and notices | 8,000 to 15,000 a year |
| Payment gateway at 1.5 to 2 percent of fees collected online | 30,000 to 80,000 on a 4 crore fee book at partial adoption |
| Parent mobile app, where it is charged as an add-on | 15,000 to 50,000 |
| Biometric or RFID hardware, if you take attendance or transport | 25,000 to 1.5 lakh, one time |
| Total, year one | 1.8 to 3.2 lakh |
The payment gateway is the line that compounds. At 1.75 percent, a school collecting 4 crore in fees online pays 7 lakh a year in transaction charges, which dwarfs the software entirely. Most schools avoid that by keeping bank transfer and cheque as the default and offering online payment as a convenience, and the ones that do not usually pass the fee to parents, which is its own conversation at the AGM.
The question that saves the most money: who absorbs the gateway percentage, and does the quote assume full online adoption? A proposal that quietly assumes every parent pays online is a proposal with a seven-figure line hidden in it.
The seven things that move the price
- Student count, and where the band breaks. Most vendors price in bands rather than linearly. A school of 480 students and one of 520 can pay very different rates for the same software, so ask where the next band starts before you sign.
- Modules, and which are bundled. Fees, admissions and attendance are usually core. Transport, hostel, library, canteen, inventory, HR and payroll are commonly add-ons, and transport is the one most schools discover they need in month two.
- How fees are structured. A flat termly fee is simple. Concessions, sibling discounts, staff-ward waivers, late fees, transport slabs by distance and part payments are where school billing actually lives, and where cheap ERPs break first.
- Communication volume. SMS is charged per message. A school sending daily absence alerts to 500 parents sends 15,000 messages a term before it sends a single notice. WhatsApp is cheaper per message and has its own template rules, which we cover in our WhatsApp cost guide.
- Hardware. Biometric devices for staff and student attendance, RFID cards and readers for the gate, GPS units for buses. The software vendor will quote the bundle; the hardware is usually the larger number.
- Boards and compliance. CBSE, ICSE and each state board want different report card formats, and the reporting a school owes the authorities is not the same in every state. Ask to see a generated report card for your board before you buy.
- Who administers it. Every school ERP needs one person who owns it, usually the head clerk or an administrator. Schools that do not name that person before go-live are the ones still running the old register a year later.
When a group should build, and when no school should
For a single school, never. The arithmetic is not close.
| Scenario | Product cost a year | Against a build of about 14 lakh |
|---|---|---|
| One school, 500 students | 1.5 to 3.2 lakh | Pays back in five to nine years, before upkeep |
| One school, 1,500 students | 2.5 to 5 lakh | Pays back in three to five years |
| A group of five schools, 4,000 students | 12 lakh and up | Pays back inside two years |
| A group or chain above 8,000 students | 24 lakh and up | Pays back inside a year |
The crossover sits somewhere above three to four thousand students under one management. Below that, buy, and spend the difference on the data migration being done properly.
Even above it, price is rarely the reason groups build. The reasons are that a group needs one view across campuses that no product gives it, that fee structures differ by campus in ways products will not model, and that the group wants its own app in parents' hands rather than a vendor's. What a group is buying at that point is a multi-tenant platform with each campus as a tenant, and the cost drivers for that shape are in our SaaS development cost guide.
Where the build money goes, if you are that group
| Work package | Person-days |
|---|---|
| Discovery: fee structures per campus, the board requirements, what the office actually does | 6 |
| Students, guardians, enrolment, sections, promotion and transfer between campuses | 10 |
| Fees: structures, concessions, late fees, part payments, receipts, defaulter reports | 14 |
| Payments: gateway, reconciliation against the bank, refunds | 7 |
| Attendance: daily, period-wise, biometric integration, absence alerts | 8 |
| Examinations: marks entry, grading schemes per board, report cards | 10 |
| Transport: routes, stops, slabs, and tracking if you take it | 8 |
| Staff: HR records, leave, payroll inputs | 7 |
| Parent and teacher apps, on the phones they actually own | 12 |
| Reports for the management and for the authorities | 5 |
| Testing, migration of two years of records, and a parallel term | 11 |
| Total | 98 |
At the blended 16,000 rupees a person-day we use across these guides, that is about 15.7 lakh, with a first usable version in twelve to fourteen weeks and 15 to 25 percent of the build a year in upkeep. Call the range 10 to 25 lakh depending on how many of transport, hostel, payroll and examinations you take on.
Fees and examinations together are 24 of the 98 days. The parent app, which is what gets demonstrated, is part of 12. That ratio is the right one, and a proposal that inverts it is selling you a shop window.
What breaks first, and it is never the feature list
Schools rarely abandon an ERP because it lacked a module. They abandon it for one of four reasons, and all four are visible in a demo if you know to look.
The fee structure does not fit. Indian school fees are not a flat number. There is a sibling discount, a staff-ward concession, a transport slab by distance, a late fee with a grace period, a part payment the principal agreed to in person, and a term where the board changed something. An ERP that models fees as an amount times a count will be fought by the accounts office within one cycle, and the office will win, because it has to produce correct receipts.
The report card is not your report card. Every board, and in practice every school, has a format it will not compromise on. If the system cannot produce it exactly, the school exports marks to Excel at results time and the ERP becomes a data entry exercise with no output.
Parents do not install the app. Attendance alerts and fee reminders only save the office time if parents actually receive them. If the app is the only channel and half the parents never install it, the office ends up calling them, which is the work the software was bought to remove.
The register keeps running. The surest sign of a failed implementation is the paper register still being filled in alongside the system, usually because one person does not trust the data migration. That is a reason to spend money on migration rather than on modules.
The costs that are not in the quote
| Cost | Typical size | When it surprises you |
|---|---|---|
| Data migration done badly | 15,000 to 30,000 to do once, or a term of corrections | When last year's fee balances do not match the register |
| The SMS pack running out | 8,000 to 15,000 a year, more with daily alerts | Mid-term, when alerts stop silently |
| Payment gateway percentage | 1.5 to 2 percent of online collections | On the first full fee cycle |
| Report card format changes | A change request per board update | In the week before results |
| Per-user charges for teachers | Some vendors charge per staff login | When you add the whole teaching staff |
| Training the next administrator | A session each time the role changes | Every year or two, which is how often it changes |
| Exit and data export | Rarely free, sometimes not possible | When you try to leave |
GST at 18 percent applies to the software invoice. School fees themselves are exempt, which trips up proposals that quote inclusive and exclusive figures in the same document.
How to read a school ERP quote
Six checks, ten minutes.
- Ask for the first-year total, not the monthly rate, with setup, training, SMS, gateway, app and hardware all in one number.
- Ask them to generate your report card, for your board, with your grading scheme, in the demo.
- Ask them to model your fee structure, including the sibling discount and the staff-ward concession, before you sign anything.
- Ask who pays the gateway fee and what the quote assumes about online adoption.
- Ask what a teacher login costs and whether every teacher needs one.
- Ask how you export every student, fee receipt and mark if you leave, and get the answer in the contract.
How to spend less without a worse system
- Start with fees, admissions and attendance. They are most of the value. Add transport and hostel in year two when you know what you need.
- Keep bank transfer as the default and offer online payment as a convenience rather than the only route.
- Use WhatsApp rather than SMS for notices where you can, and keep SMS for the alerts that must arrive.
- Buy hardware separately unless the bundled price genuinely beats what you can source.
- Migrate once, carefully. Opening fee balances that are wrong poison a whole academic year of reports.
- Name the administrator before go-live, and write the handover into the role rather than into one person's memory.
When a school should not buy an ERP at all
- Under about 150 students, where a good spreadsheet, a payment link and a WhatsApp group genuinely do the job, and the ERP adds administration rather than removing it.
- Mid-academic-year, unless something is actually broken. Switching in March, with fees and examinations both running, is how implementations fail.
- When nobody will own it. An ERP without a named administrator becomes a second system to keep updated alongside the register, which is worse than either alone.
Questions people ask
How much does school ERP software cost in India?
Advertised at 15 to 40 rupees per student per month, or 100 to 500 per student per year, with flat plans from about 9,000 a year for the smallest schools. A 500-student school typically pays 1.5 lakh in subscription but 1.8 to 3.2 lakh in the first year once setup, training, the SMS pack, the payment gateway and any hardware are counted.
Why is the real cost higher than the quoted price?
Because five lines are quoted separately or not at all: setup and data migration at 15,000 to 30,000, training at 10,000 to 25,000, the SMS pack at 8,000 to 15,000 a year, the payment gateway at 1.5 to 2 percent of everything collected online, and the parent app where it is an add-on. Hardware for biometric attendance or transport sits on top of all of it.
What does a school ERP cost for 1,000 students?
Roughly 2 to 4 lakh a year in subscription at mid-range per-student pricing, and 2.5 to 5 lakh all in for the first year. Ask where the vendor's price bands break, because a school just over a band boundary can pay noticeably more than one just under it.
Should a school build its own ERP?
A single school, no. At 500 students a product costs 1.5 to 3.2 lakh a year against a build of about 15.7 lakh, which is five to nine years of subscription before upkeep. Building makes sense for a group above roughly three to four thousand students, where the real reason is usually one view across campuses rather than price.
What does it cost to build a school management system?
Ten to 25 lakh depending on how many of transport, hostel, payroll and examinations you include. The worked estimate above comes to 98 person-days and about 15.7 lakh, with a first usable version in twelve to fourteen weeks and 15 to 25 percent of the build a year in maintenance.
Is there free school management software?
There are free tiers and genuinely free options, and for a very small school they can work. The limits appear in fee structures, board-specific report cards, support and data export rather than in the feature list. Check all four before committing a school's records to one.
How long does implementation take?
Six to twelve weeks for a single school, and the work is mostly yours rather than the vendor's: student and guardian records, two years of fee history, opening balances, and the staff learning it. Start at the beginning of an academic year or a term, never in the middle of an examination cycle.
What about the payment gateway fee, can it be avoided?
Partly. Most schools keep bank transfer and cheque as the default and offer online payment for convenience, which holds the percentage down. Some pass the fee to parents explicitly. What you should not do is accept a proposal that assumes full online adoption without pricing the percentage, because at 1.75 percent on a 4 crore fee book that is 7 lakh a year.
Getting a real number
If you run one school, this guide should have pointed you at a product and told you which five lines to add to the quote. If you run a group and the per-student fees have grown into a project, that is the conversation worth having, and it starts with your fee structures rather than with features. What that looks like is on our web and SaaS development page.