A CFO at a ₹90 crore auto component supplier in Faridabad put two proposals in front of me last year and asked which was cheaper. One had a number on the front page that was a third of the other. He'd already decided, more or less, and he wanted me to confirm it.
The two numbers weren't measuring the same thing. One was a licence. The other was a licence plus everything that makes a licence useful. That's not a trick anyone played on him; it's just how these proposals are built, and nobody had told him what was missing from the smaller one.
What is the total cost of ownership of a manufacturing ERP?
What a quote shows, and what it doesn't
Proposals differ enormously in how much they put on the front page. That variation is the single biggest reason two quotes for the same plant can look three times apart and land in the same place.
| Usually on the front page | Usually further back, or absent |
|---|---|
| Licence or subscription | Data migration from Tally and your spreadsheets |
| Number of users | Training, and retraining after attrition |
| Modules included | Annual maintenance, usually a percentage of licence |
| Implementation, as one line | Change requests when your process differs from the standard build |
| Integration with machines, weighbridge, or your customer's portal | |
| Hosting and infrastructure, where it isn't a cloud subscription | |
| Your own people's hours, which are real even though nobody invoices you |
The last line is the one finance teams leave out and operations teams feel. Cleaning item codes, rebuilding BOMs that stopped matching reality years ago, and deciding which of the four spellings of a customer name is correct is unglamorous work, it takes weeks, and it lands on people who already have jobs.
Where the money actually lands
The shape matters as much as the total. A legacy ERP project front-loads: a large year one, then maintenance and change requests. A subscription platform spreads: a smaller year one, then a predictable renewal that you can forecast without a meeting.
Running the three-year number
Here's the arithmetic for the Faridabad plant, using only figures we publish. Forty office and supervisor users. Modern subscription platforms sit in a band of roughly ₹1,000 to ₹3,000 per user per month depending on modules and machine connectivity. Take the middle at ₹2,000: that's ₹80,000 a month, ₹9.6 lakh a year, ₹28.8 lakh over three, and the renewal in year two is the same number as year one.
Against that, a full legacy ERP programme for a plant this size lands somewhere between ₹40 lakh and over a crore once licences, partner implementation, migration, training and the first round of change requests are counted. The gap isn't the software. It's the project structure around the software, and whether you need that structure is a real question with a real answer for some companies.
"I was comparing a licence to a project and calling it a comparison. When I put both on three years with the same lines in each, the cheap one wasn't cheap. It just had a shorter front page."CFO, auto component supplier, Faridabad
The question that works better than asking the price
Ask every vendor to list every invoice you will receive over three years, and who sends each one. It's a harder question to dodge than "what does it cost", it surfaces the partner relationship immediately, and the vendors who answer it fluently are usually the ones who've done this at your size before.
The count matters more than the amounts. One company sending one bill behaves differently from three companies sending six, and not because of the money. When something breaks in month four, the number of companies involved decides whether you get a fix or a conversation about scope.
It's also worth knowing that a proposal you walk away from still leaves you better off than when you started. PPS International took an SAP Business One proposal close to final before the budget stopped it, and the specification written during that evaluation is what made the next rollout quick.
If you want the drivers behind the subscription figure rather than the three-year model, we've broken them down in what actually drives manufacturing software cost in India. And once you're modelling specific vendors, our ranked view of the best manufacturing ERP software in India describes the cost shape of each one without quoting anybody's rate, because those move.
Facto is one subscription, one bill, from us, and our own engineers do the deployment, so the implementation line isn't a separate company's invoice. If you want the three-year model built against your actual user count and modules, talk to our team and we'll put the arithmetic in front of you before anyone talks about a contract.