Open the website of any major Indian school ERP. Click “Pricing”. You’ll almost certainly land on a form that asks for your name, your institution’s name, your phone number, and your role — and then promises that “our team will get back to you with a customised quote.” A demo will be scheduled. A discovery call will be arranged. Somewhere two to four weeks later, after several meetings and a needs analysis, a number will appear in your inbox.
We do something different. Every price for OptiCRM’s self-serve plans — Free, Starter, and Professional — is published on our pricing page. The exact rupees, in plain numbers, with what’s included. No form to fill, no call to schedule, no waiting two weeks to find out whether you can afford us. Enterprise deployments (multi-campus groups, 2,000+ students, custom SLAs and integrations) get a tailored quote because the scope genuinely varies — but we tell you that up-front rather than hiding the standard plans behind the same gate.
This is unusual in our category. It’s worth explaining why we do it, and why almost everyone else doesn’t.
Why ERP vendors hide pricing
There are three reasons, and they’re all rational from the vendor’s perspective.
The first is price discrimination. If you can charge a small private playschool ₹3,000 per month and a 5,000-student college group ₹50,000 per month for what is largely the same software, you’ll make more money. Hiding pricing lets sales teams negotiate each deal individually, anchored against the customer’s apparent budget rather than a published rate card. This works. It also rewards customers who are good at negotiating and penalises those who aren’t — which, in education, often correlates poorly with the quality of the institution.
The second is competitive opacity. If your prices aren’t published, your competitors can’t easily undercut you on price comparisons, and prospects can’t compare you in a side-by-side spreadsheet during their evaluation. This is short-term protective, but it pushes the entire category toward an opaque, sales-led buying experience that frustrates buyers.
The third is sales engagement. A demo request is a captured lead. The pitch goes: once a principal is on a call, the sales team can demonstrate value, handle objections, propose a tailored package, and close. Removing the demo gate means losing this entire conversion funnel. For sales-led organisations, that’s a real cost.
All three of these are valid business reasons. We just don’t think they’re worth what they cost the buyer.
What it costs the buyer
A school principal evaluating an ERP has, conservatively, ten vendors to consider. If each one requires a 30-minute discovery call before sharing a price, that’s five hours of meetings before the principal even knows which two or three are in budget. In our experience talking to schools, this is exactly what happens. Most principals abandon the process halfway through, settle for whatever vendor they spoke to first, or stay on spreadsheets for another year.
The sales-led model assumes the buyer’s time is free. It isn’t. School leaders are running institutions with hundreds or thousands of students. They don’t have a procurement team that can spend a week comparing vendors. They need to look at a price, make a quick judgment, and move on with their week.
What we lose
Publishing our pricing has costs too, and we should be honest about them.
We sometimes leave money on the table. A 1,500-student school sees Professional at ₹15 per student per month and pays the published rate. We have no flexibility to charge more just because they could afford it. That’s the deal.
We also lose some of the consultative selling motion that helps customers understand whether OptiCRM is right for their workflow. A 30-minute call would have surfaced that this institution has a unique fee structure, or runs a hostel, or has compliance requirements specific to their state board. Without that call, some prospects sign up, hit a misfit, and churn.
We’ve decided this trade-off is acceptable. The pricing page is the first contract we make with a buyer: this is what it costs, this is what you get, no surprises. If the misfit happens, we can address it through better self-service onboarding and clearer in-product guidance. We can’t address the loss of trust that comes from a buyer who feels they were quoted artificially.
Where Enterprise is different — and why
Multi-campus deployments, 2,000+ student institutions, and customers who need on-prem options or custom SLAs are the one place we don’t publish a number. That’s not a price-discrimination gambit — it’s that the scope genuinely varies. A 3-campus university group that wants white-labelled mobile apps, dedicated infrastructure, and a custom integration with their existing finance ERP isn’t buying the same product as a 500-student school on Professional. Pretending a single published number covers both would be more dishonest than telling them up-front: “this is custom; let’s talk about what you actually need.”
We’ve kept the trade-off narrow. Everything self-serve is published. Everything custom isn’t. The line between the two is drawn at scope, not at willingness-to-pay.
What this signals
A vendor who publishes their pricing is making three statements implicitly. First: we’re confident our pricing is reasonable, and we’re not afraid for you to compare. Second: we respect your time enough not to require a sales call to find out whether we’re affordable. Third: what you see is what you pay, and we don’t have a separate “premium customer” rate that we’ll quote when we sense you can afford it.
Trust in B2B software is built slowly and lost quickly. Public pricing is one of the small, durable signals of trust that persist after the demo, after the trial, after the contract is signed. We think it’s worth more than the revenue we leave on the table.
If you’re evaluating school management software and you’ve spent more time scheduling demos than evaluating products, you’re not alone. The category is wired this way for a reason — and that reason isn’t you.