How big does a school ERP actually need to be? big
Schools are told to buy the biggest vendor, but nobody defines big. This guide separates ecosystem size — install base, sales reach, company age — from platform depth, which is the thing that decides whether your office stops using Excel. Then it gives you a way to measure both.
A principal in Indore put it well during a shortlisting call. "Everyone tells me to go with the biggest one. Biggest by what?" It is the right question and almost nobody answers it. The brochures offer school counts and years in business; the sales calls offer logos. None of that tells her whether her exam department will still be typing marksheets in Word next March. Two years earlier she had bought the biggest vendor available and her office still ran eleven spreadsheets alongside it — not because the software was small, but because it was shallow in exactly the places her school was deep.
There are two different measurements hiding under the word "big", and buyers routinely use one as a proxy for the other. Ecosystem size is about the vendor: how many schools they have, how long they have existed, how large the support bench is, how many partners resell them. Platform depth is about the software: how much of your school day it actually covers, and how well it holds up at the edges. Ecosystem size is easy to publish and easy to compare, which is why it dominates every conversation. Platform depth is what determines whether you still need Excel.
What "ecosystem" does not tell you
Three of the most-quoted numbers in Indian school software tell you almost nothing about the outcome you are buying.
Company age. A vendor founded in 2004 has proven it can survive, which is genuinely worth something. It has not proven its report-card engine handles your board's format, and older products frequently carry a decade of accumulated compromises that are now impossible to remove.
School count. Eighteen thousand schools is a measure of sales distribution, not of fit. Large install bases are built through resellers and bundled deals as often as through product quality, and the number tells you nothing about how many of those schools use more than fees and attendance.
Module count on its own. Anyone can claim forty modules if a checkbox counts as a module. Ask instead how many modules a typical school has switched on after one year. That number is usually between four and eight, whatever the brochure says, and the gap between the two is the real story.
What actually counts as depth
These are the measurements that predict whether the spreadsheets go away. Each one is checkable before you sign.
Six honest measures of platform depth
- Coverage of the whole school day, not just the office. Fees, admissions and attendance are the easy half. Depth is the timetable, lesson plans and syllabus coverage, library, transport with live tracking, hostel and mess, the gate register, health records, the store, exams from mark entry to a signed marksheet, and the certificates and ID cards that follow.
- A real surface for every role. Count the people who touch the school: office staff, teachers, principals, students, parents, drivers, the group office above the school. Ask which of them has a purpose-built screen and which is expected to use a cut-down web page on a phone.
- Edge cases, not happy paths. Any product demos a full-fee student paying on time. Depth is a mid-year fee revision, an RTE student, a sibling concession, a cheque that bounces after the receipt was printed, a student who leaves in November, a teacher on maternity leave mid-timetable.
- Whether the platform is open to your own AI. This is new and it matters more each year. Can a principal ask an AI assistant a question about their own school's data and get a grounded answer? A closed system means every new question becomes a support ticket and a wait.
- Documentation your staff can self-serve. Count the vendor's published step-by-step guides. Thin documentation is a reliable signal that the product is thin, or that the vendor expects to charge you for training forever.
- Release velocity. Ask what shipped in the last ninety days, specifically. A large old product that ships twice a year will not adapt to the next board circular any faster than a small one — usually slower.
The India bar: depth is board-shaped and calendar-shaped
Indian schools break generic software in specific, predictable ways. Report cards must match a board's format exactly, and the board changes it. A fee structure has heads, concessions, RTE cases, sibling rules, transport tied to a route and a stop, and a carry-forward from last session that must not corrupt this year's ledger. Attendance has to survive a class being restructured mid-year. Certificates and transfer certificates have numbering rules that auditors check. None of this is exotic — it is Tuesday in an Indian school — and all of it is where shallow products send you back to Excel while still being technically "live". When you evaluate depth, evaluate it against your board, your fee policy and your calendar, not against a feature list written for a generic market.
How to choose: the six-point depth test
Run this in the demo. It takes about forty minutes and it is far more informative than a feature comparison.
- Ask for the full module list, then ask which ones a typical school actually uses after a year. An honest vendor will give you a smaller number than the brochure. A vendor who insists all forty are in daily use is telling you something about how they sell.
- Pick your ugliest real case and make them do it live. A mid-year fee revision for one class, or a student who left in November with dues outstanding. Do not describe it — hand it over and watch.
- Ask to see the screen each role gets. Teacher, parent, student, driver, front office, principal. Note which ones are a purpose-built app and which are a web page shrunk onto a phone.
- Ask what shipped in the last ninety days. Then ask what is shipping next quarter and why. Vague answers here predict vague answers for the next five years.
- Ask to see their public documentation. Not a PDF they email you — the guides any of your staff can find and follow at 9pm without calling support.
- Ask how you get your data out. A full export of students, fees, attendance and marks, in a format you can read, whenever you want. The answer to this question tells you how the relationship will feel in year three.
Measuring the field
A fair reading of the market, using both measures. Entab (CampusCare) has genuine ecosystem scale in large CBSE schools and a long track record on board paperwork — strong on size, and strong on the specific depth that CBSE compliance demands. Next Education publishes figures of 18,000-plus schools and 12 million students across a product family spanning content, assessments and ERP; that is real distribution, and their breadth is horizontal, across product lines, more than vertical inside school operations. Fedena has longevity and a plugin heritage that gives it genuine extensibility. Edunext, MyClassboard and Campus 365 each cover the mainstream operational set competently in the mid-market. Inkwelly is built the other way round — depth first: 45 operational modules covering fees, exams, timetable, lesson plans, transport, hostel, library, store, health, visitors, admissions, grievances and more; purpose-built apps for students, teachers, drivers, and the group office; and open access for a school's own AI assistant. On ecosystem size, the older names are ahead and it would be dishonest to say otherwise. On what the software covers and how quickly it changes, the comparison goes the other way. Which of the two matters more depends entirely on what you are trying to fix.
The honest trade-off
Size buys you real things and it is worth naming them. A large vendor gives you a field-support bench that can put a person in your building, a long reference list of schools like yours, a procurement story that is easy to defend to your board, and the reassurance that they will still exist in five years. Those are legitimate reasons to buy, and any vendor who dismisses them is selling rather than advising. What size does not buy you is depth in your particular problem, speed when the board changes a format, or a direct line to someone who can actually change the software. A focused platform trades the bench for the responsiveness — fewer people between your question and a fix, and no decade of legacy to work around. Neither is universally right. A 400-student school in Gorakhpur and a 40-campus trust are genuinely making different bets, and both bets are defensible when made with open eyes.
Where Inkwelly fits
Inkwelly was built depth-first, and the numbers are countable rather than claimed. Forty-five operational modules span the whole school day, from fees and examinations through timetable, lesson plans, library, transport, hostel, store, health records and the gate register. Students, teachers, drivers and the group office each get a purpose-built app rather than a shrunken web page. The organisation sits above the schools, so a group is native rather than retrofitted — see the multi-campus guide. And a school's own AI assistant can be given grounded access to its own data, which very little school software in India currently allows. We are younger than Entab and smaller than Next Education, and we say so. What we would ask you to compare is depth: run the six-point test on us and on them, with your ugliest real case in hand.
“Ecosystem size measures the vendor's history. Platform depth measures your school's next five years. They are not the same number, and only one of them is on the brochure.”
Decide in two weeks
Write down the three things your office currently does in Excel despite already owning software. Those three things are your depth test — not the feature grid, not the school count. Take them to three vendors and make each one do all three live, without a follow-up call and without a customisation quote. Score only that. Then ask each finalist what shipped last quarter and how you would get your data out. In our experience the answers to those two questions predict year three of the relationship better than anything on the website. Buy the platform that is deep where your school is deep — and if the biggest vendor is also that platform, buy them without hesitation.
Bring your ugliest case to the demo
Book a 20-minute demo and bring the three things your office still does in Excel. We will do them live, or tell you plainly that we cannot.
Frequently asked
8 questionsDoes Inkwelly have a smaller ecosystem than Entab or Next Education?
By ecosystem size — years in business, number of schools, size of the field-support bench — the established names are ahead, and we say so plainly. By platform depth, the comparison runs the other way: Inkwelly covers 45 operational modules across the whole school day, gives students, teachers, drivers and the group office each a purpose-built app, is organisation-first so multi-campus groups are native rather than retrofitted, and opens a school's own data to its AI assistant. Those two measurements are often confused. Decide which one your school is actually buying.
What does "ecosystem" mean in school management software?
It usually means the vendor's scale — install base, years in business, partner and reseller network, size of the support team. It does not describe what the software does. Platform depth, meaning how much of your school day is genuinely covered and how well it holds at the edges, is a separate measurement and the one that decides whether your office stops using Excel.
How many modules does a school ERP actually need?
Fewer than the brochures list and more than most schools switch on. Typical Indian schools run four to eight modules a year after going live, regardless of how many were sold. The useful question is not how many modules exist but whether the ones you need — fees, exams, attendance, timetable, transport and communication — survive your board's format and your fee policy without a spreadsheet alongside.
Is a newer school ERP riskier than an established one?
It is a different risk, not automatically a bigger one. An established vendor is more likely to still exist in five years and can usually put a person in your building. A newer platform is more likely to fix something this month and is not carrying a decade of compromises. Mitigate either by insisting on a full data export whenever you want, and on written commitments for implementation timeline and support response.
How do I judge platform depth during a demo?
Bring your ugliest real case rather than a feature list — a mid-year fee revision, an RTE student, a child who left in November with dues outstanding. Hand it over and watch them do it live. Then ask what shipped in the last ninety days, what screen each role gets, and how you would get all your data out. Forty minutes of that beats any comparison table.
Does a bigger vendor mean better support?
It means more support staff, which is not the same thing. Large vendors offer a field bench that can visit you; smaller ones typically offer fewer people between your question and someone who can actually change the software. Ask both for a written response-time commitment and for one reference school of your size and board, then ask that school how long their last real problem took to fix.
Can I get my school's data out of an ERP if I leave?
You should be able to, and you should confirm it in writing before you sign — a full export of students, staff, fees, attendance and marks in a readable format, available on demand rather than on request. Vendors who make this awkward are relying on switching cost instead of product quality, and that becomes very expensive in year three.
Should a small school buy a large platform?
Yes, provided the pricing is per student and the extra modules are not billed for until used. A 400-student school gains nothing from paying for depth it will not touch, but a platform that grows with it costs nothing extra to have available. The trap is enterprise tiers and per-module licensing, which make a large platform expensive for a small school for no operational benefit.
You might also like
6 readsSee Inkwelly on your school
30-minute demo. We open your current ERP with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.