The Hidden Cost of Per-Student Pricing in School ERPs

The Hidden Cost of Per-Student Pricing in School ERPs
← All posts

Most school ERPs in India price per student. ₹X per child per year, scaled across your roll. It sounds proportional. It isn't.

The growth penalty

Add 200 students next year and the bill goes up automatically — without you using a single new feature. Every parent you sign up costs the school more software fees, even though the platform's underlying cost barely changed.

The result: schools cap usage. Don't onboard junior parents. Don't add coaching staff to the system. Run shadow Excel registers on the side. The pricing actively discourages adoption.

The budgeting problem

Per-student pricing makes annual budgets a guessing game. If admissions overshoot or undershoot, your software line item moves with it. Finance hates this.

Flat pricing changes the conversation

Schoolo's three tiers (Starter / Growth / Enterprise) are flat: pick the tier that fits your size band, and that's the cost. Add 50 students mid-year? No invoice change. Onboard every parent? Encouraged, not penalised.

The school knows the cost in advance. The vendor incentive flips: we make money when you stay, not when you grow your roll.

When per-student does make sense

Genuinely usage-based products — SMS gateways, face recognition compute — pass real per-event costs through. That's not the case for an ERP, where 95% of the cost is engineering, not transaction volume. Per-student pricing on ERPs is a margin choice dressed up as fairness.

A worked example

Take a school with 800 students on a typical per-student plan at ₹350/student/year — ₹2.8 lakh annually. Admissions grow to 1,000 over two years, a healthy and desirable outcome. The bill climbs to ₹3.5 lakh with zero new functionality delivered. Under Schoolo's flat Growth tier, that same school pays one fixed number regardless of whether they end the year at 950 or 1,050 students — the vendor absorbs the variance, not the school.

The lock-in effect nobody mentions

Per-student pricing quietly discourages switching, too. Once a vendor has priced you by headcount, any serious evaluation of a competitor means re-negotiating from scratch at a higher enrollment base than when you signed — so schools stay put out of inertia, not satisfaction. Flat pricing removes that asymmetry: your cost to leave is the same as your cost to stay.

Questions worth asking your current vendor

  • Does my bill change if I enroll 50 more students mid-year?
  • Is there a discount for adding staff or coaching accounts, or do those count as billable seats too?
  • What happens to pricing at renewal if my roll has grown 20%?

If any answer is "yes, it goes up automatically," that's the per-student model working exactly as designed — against your growth.

Read more on our pricing page — full breakdown, no per-seat surprises.

If you're moving off a per-student ERP, see our 7-day migration playbook — and if fee collection is part of the switch, our Razorpay setup guide covers that end-to-end.