← All posts
Buyer's guide2026-09-0911 min read

Total cost of ownership

The ₹18,000 School ERP: How a Quote Becomes 20x by the Time It Goes Live

The cheapest school ERP quote in the folder is rarely the cheapest school ERP. This is a worked example, with illustrative figures drawn from publicly published Indian price lists, of how an ₹18,000 headline turns into roughly twenty times that by the end of the first year, and a one-page sheet that makes it impossible for that to happen to you.

A school accounts office desk in late-afternoon light: a stack of invoices on a spike file, a calculator, an open ledger and a steel tea cup, with grey filing cabinets behind.
The quote lands with the principal. The invoices land here, one at a time.

The quote that starts the story

Picture a 1,200-student school, one campus, a principal who has finally decided the registers and the four spreadsheets have to go. Three vendors present. One quote is clearly the lowest: ₹18,000 a year, all modules, cloud-hosted, mobile app, support included. The principal is relieved. The trustee who asked for three quotes is satisfied that due process was followed. The order is signed before the admission season.

Everything in this post is illustrative. The school is invented, the vendor is nobody in particular, and the figures are ranges that Indian school-software vendors and consultancies publish openly in their own pricing guides as of September 2026. Nothing here is a secret. That is the point: every line below is visible before signing, to anyone who knows to ask for it.

By the time the school has been live for twelve months, the finance office has paid out close to ₹3.8 lakh against that ₹18,000 quote. No single invoice looked unreasonable. Each one arrived with a reason. Added together they are about twenty-one times the number the trustee approved.

Line by line: where the twenty times comes from

The headline price was for the software licence. It was accurate. It simply was not the price of running a school on the software. Here is the first year as the accountant eventually reconstructed it, using the kinds of charges that appear, with these ranges, in vendors' own published rate cards.

The total comes to about ₹3,79,000. Not one line is fraudulent, and several are legitimately work that somebody had to do. The problem is that none of them were on the page the trustee approved, and every one of them arrived after the school was already dependent on the system.

  • Licence, as quoted: ₹18,000. All modules, as promised, at the base tier.
  • Per-student activation: ₹100 per student, mentioned on page four of the terms. 1,200 students: ₹1,20,000.
  • Implementation and data migration: ₹45,000. Published setup ranges run from roughly ₹20,000 to ₹50,000; the school's spreadsheets were messy, so it landed at the top.
  • Training beyond the two included sessions: ₹15,000. The teachers who missed the first session needed a third.
  • Parent mobile app, 'premium' tier: ₹30,000. The included app was the browser version. Push notifications and fee payment needed the upgrade.
  • Transport and hostel modules: ₹40,000. 'All modules' meant all core modules. These were add-ons.
  • SMS and WhatsApp: about ₹36,000. Around 40 messages per family per year at ₹0.25 each, plus a WhatsApp Business line billed monthly.
  • Payment gateway markup: ₹75,000. The gateway charged its own fee; the vendor added half a percent on ₹1.5 crore of online collections.
An opened renewal letter and its envelope on a school office desk, a pen across the page, beside a desk calendar with one date circled in red.
The renewal letter is where the structure shows itself.

Year two is where it really bites

The first year is expensive. The second year is where the structure reveals itself. The renewal letter arrives with an escalation of ten percent, which is inside the eight-to-twelve percent range that published guides describe as common. The annual maintenance charge is calculated as a percentage of the 'list value' of the modules, not of the ₹18,000 the school actually paid, so it is larger than the licence itself. The school has changed boards for its senior section; the report-card templates need 'reconfiguration', which is chargeable. Storage of scanned documents has crossed a quota nobody knew existed.

Then there is the quiet arithmetic of dependency. The SMS sender ID that parents recognise belongs to the vendor. The Play Store listing parents installed belongs to the vendor. The receipt numbering sequence, the one the auditor checks, lives inside the vendor's database. The custom fee-defaulter report the accountant relies on was built by the vendor as a paid customisation and is not exportable. Every one of these makes leaving a little more expensive than staying, and that, not the price, is the product being sold.

The lock-in mechanics, named

Lock-in in Indian school software is rarely a villain's plan. It is usually a set of ordinary commercial choices that each make sense to the vendor and together make the exit door very heavy. Naming them is most of the defence, because a school that recognises the mechanism can ask for it to be removed before signing.

  • Export as a service: your data comes back only when the vendor's team runs the export, on their timeline, for a fee.
  • Proprietary formats: the export arrives, but as a backup file only the vendor's software can read.
  • Identity captured: sender IDs, app-store listings, domain names and payment sub-merchant accounts registered in the vendor's name.
  • Configuration as a customisation: fee rules, grading bands and approval chains built by the vendor, billed as work, owned by nobody in writing.
  • Auto-renewal with a narrow window: the contract renews for another year unless notice is served in a 30-day window nobody diarised.
  • Transition assistance: a fee for helping you leave, priced after you have decided to.
  • Deletion on their terms: no stated timeline for removing your students' data from the vendor's systems after exit.

Why this works on schools in particular

The structure works because of who sees which number. The quote lands with the principal or the trustee, who compares headlines. The invoices land with the accounts office, spread across twelve months, each small enough not to be escalated. Nobody in the institution ever sees the total on one page. And by the time anyone thinks to add it up, the school is mid-session, with fee receipts issued, parents on the app and marks entered, and switching feels like changing the engine while the bus is moving.

Procurement rules make it worse, not better, when they reward the lowest quote rather than the lowest total cost. A trustee who insists on three quotes has done the right thing. A trustee who insists that all three quotes be restated as a first-year and three-year total, on a fixed template, has done the thing that actually protects the school.

The one-page total-cost sheet

Every vendor, including us, should be asked to complete the same sheet before a decision is made. If a vendor cannot or will not fill a line, that is the answer for that line. Ask for it in writing, attach it to the order, and make it override any price list.

  • One price per year, on enrolment, with every module and the standard parent and staff apps included. Any excluded module named.
  • Implementation, data migration and training itemised and capped, with what 'messy data' costs stated before the migration starts.
  • SMS, WhatsApp and payment-gateway charges passed through at the provider's rate, or the markup stated as a number.
  • Escalation capped, and the annual maintenance charge defined against the price paid, not a list value.
  • Sender IDs, app-store listings and payment accounts registered in the school's name, or transferable at no cost.
  • Configuration the vendor builds belongs to the school and exports with the data.
  • Full export in CSV or Excel at any time, by the school's own staff, at no charge.
  • Exit assistance priced now, and a deletion timeline for the vendor's copies after exit.
  • Renewal notice terms and the window stated on the front page, not in an annexure.
  • The three-year total, on this sheet, signed by the vendor.

How the SquareCampus licence is built, for comparison

We publish the model rather than the figures, because the figures depend on scoping. The model is one annual institutional licence calculated on student-volume bands, with every module and the standard parent and staff mobile apps included. White-labelled apps under the school's own branding carry a single charge that covers the whole agreed term. Implementation, migration and training are scoped explicitly rather than folded into an unstated blended rate, and your data exports in standard formats whenever you decide to leave. The sheet above is one we are happy to fill in first.

Ask for the sheet, from everyone

See how the SquareCampus licence is composed, then ask every vendor on your shortlist to restate their quote the same way.

← Back to blogSquareCampus · Building calm systems for schools
school erp costschool erp hidden costsschool management software pricingvendor lock-intotal cost of ownership