TL;DR: Indian ERP rollouts routinely overshoot signed budgets by 40-70%, and in some cases hit 200%. The cause is structural. Vendors quote a happy-path go-live. Data migration, customisation, training, and renewals get pushed to a second cheque. The fix is a scope-locked, milestone-paid, partner-led deployment with discipline around contingency, not a sharper RFP. Below is the CFO-level breakdown of where the surprise originates and the pre-signing checklist that prevents it.

Key Takeaways: - The ₹18 lakh surprise is a budgeting failure first, vendor failure second. The CFO signs the second cheque, not the operations team. - Five cost categories drive the overrun: licensing, customisation, data migration, training, and recurring licence/support renewal terms. - Partner-led deployments compress timelines that in-house rollouts tend to inflate. That compression is itself a cost control mechanism. - Milestone-based payments and a meaningful contingency line are non-negotiable for any quote that bundles licence, customisation, and support into a single number. - Frame ERP value to the board as cost per active user, not cost per licensed seat. The gap is your real write-off.

Your ERP budget is wrong before you sign the contract. Six months in, your CFO will sign a second cheque for ₹18 lakhs. The operations team will still be running inventory on Excel. Nobody in the steering committee can explain which of the 15 modules anyone actually uses.

This is not a vendor problem in isolation. It is a budgeting pattern that repeats across Indian mid-market rollouts. Operations signs a CAPEX contract based on a vendor's quote. The system goes live in month four to six. By month nine or ten, the CFO is asked to release a second tranche. Procurement never forecast that tranche.

Research on Indian ERP programmes shows companies routinely spend 40-70% more than the original plan. In some cases, overruns hit 50-200% of the signed figure. The pattern is so consistent it has become a budgeting failure mode. Many of these same companies would never sign a fixed-bid construction contract without a contingency line. Yet they happily approve an ERP implementation cost in India quote that bundles everything into a single figure.

Consider a typical mid-market rollout. A team spends ₹18 lakhs annually on ERP licences. Six months in, they still run inventory in Excel. They wait four days for standard reports. They pay for 15 modules but cannot name a single active user of most of them. The CFO is not defrauded. The CFO inherited a system no one configured properly. Now the CFO is being asked for another cheque to fix it.

The vendor's quote looked honest. So why does the actual bill almost always double?

Every ERP quote you have approved was structurally honest but functionally incomplete. Vendors price the licence, the first wave of configuration, and a happy-path go-live. Data migration, change management, integration testing, and the second wave of customisation are quoted separately. They get absorbed under vague "professional services" lines. The procurement team treats those lines as rounding error.

Three structural problems make this worse.

First, hidden customisation is the single largest source of the surprise. Business processes that look standard in a vendor demo collapse into edge cases the moment real transactions run. GST workflows, multi-entity structures, and legacy data formats are the usual triggers. None of them appear in the demo.

Second, training is treated as a one-time workshop. It is a multi-month capability programme. It gets shortchanged when launch pressure builds. When it is compressed into a launch-day event, adoption stalls. End-users route around the system and back to the spreadsheets they already know. The ERP becomes shelfware with a recurring licence bill.

Third, the timeline itself is a cost variable. An in-house team takes far longer than a partner-led rollout. During that longer window, scope expands. The contingency fund gets quietly consumed. Go-live arrives, and the second cheque is already half-spent.

If the quote is structurally wrong, the answer is not a sharper RFP. So what are you actually buying when you sign that quote?

Five line items produce the surprise cheque.

Software Licensing. Per-user or per-module pricing hides the true OPEX. Vendors quote a Year One number that looks reasonable. The trap is the renewal term. Annual licence and support renewals are standard across Indian ERP rollouts. They compound for the full life of the contract. If the renewal cap is not negotiated at signing, Year Five will cost noticeably more than Year One.

Customisation and Integration. This is the single most underestimated line item. It is the origin of the surprise cheque. It includes legacy data formats, multi-entity structures, and tax workflows specific to India. Vendors quote against a fixed scope of work. The first invoice always includes a change order.

Data Migration. Rarely a clean ETL job. Legacy spreadsheets, duplicate SKUs, and unstandardised master data inflate the professional services line on most Indian rollouts. Master data has been maintained by humans for years. It has human inconsistencies the vendor's migration script was not designed to handle.

Training and Change Management. The line item CFOs cut first and pay for last. Under-investment here is the direct cause of the "still using Excel" problem six months post go-live. Training is not a cost. It is the difference between shelfware and a production system.

Ongoing Maintenance and Upgrades. Recurring licence and support contracts that recur whether you use the system or not. This is the underutilisation tax. It is where most Indian ERPs quietly bleed their original ROI.

The harder question is why you are still paying for an ERP your teams refuse to use.

Board-ready reporting is the litmus test. If your finance team is still extracting data from the ERP into Excel to build a management deck, the system is shelfware. You are paying full OPEX for partial value.

The pattern is depressingly consistent. A company licenses the ERP for HR, finance, and operations. None of the three modules talk to each other. Another company picked a modern HRMS because the dashboard looked clean. Eighteen months in, the CFO is still exporting to Excel for board reviews. The data lives in the system. The trust does not.

When active usage is a small fraction of paid seats, the second cheque of ₹18 lakhs is almost always spent on a "quick fix." More customisation. A bolt-on BI tool. A third-party connector. None of these address the root cause. The root cause is configuration and adoption. The same ERP software development investment that should have built a working system now funds its recovery. The system was never fully deployed, and you are paying to fix it.

Frame this for the board as cost per active user, not cost per licensed seat. A 100-seat licence with 25 active users is a 75-seat write-off. The CFO does not own the system. The CFO owns the gap.

So the surprise is not really ₹18 lakhs of new software. It is the cost of recovering value from a system you already paid for. How do you build a rollout that prevents both?

Timeline discipline is the single most underappreciated cost control in an ERP programme. A longer project almost always costs more. Every additional month is a month in which scope can expand and the contingency can drain.

Phase 1 - Discovery and Scope Lock. Lock the functional scope, the integration list, and the data migration scope in writing before signing. Anything added after this point is a change order with a price tag. The temptation to "finalise later" is how budgets double.

Phase 2 - Configuration and Customisation. Build against the locked scope. Run UAT with real transactions, not synthetic test data. Freeze scope at the end of this phase. The most common cause of timeline slip is silent scope expansion during configuration. The vendor adds a "small" customisation. The customer adds a "critical" report. Both are unbilled until go-live.

Phase 3 - Data Migration and Training. Run data migration in parallel with training. Treat training as a multi-month programme, not a launch-day event. Role-based modules for finance, ops, and sales. Named completion certificates. This is the phase that prevents the underutilisation tax. It is also the phase most rollouts cut first.

Phase 4 - Go-Live and Stabilisation. Hypercare window. Daily issue triage. A formal sign-off on milestone-based payments before the final tranche releases. Partner-led Odoo implementation projects typically compress this entire arc compared to a drawn-out in-house team rollout. That compression is not a marketing claim. It is a cost control mechanism.

Timeline discipline alone will not save the budget. You also need the contract clauses that turn "we will figure it out" into "here is the price before you approve it."

Five controls separate a defensible ERP budget from an ERP surprise cheque. Run them before you sign. - Demand a module-by-module price breakdown. Explicit per-user costs and annual renewal terms. Reject any quote that bundles licence, customisation, and support into a single figure. A bundled quote is a quote you cannot audit. - Insist on milestone-based payments. Tied to go-live, UAT sign-off, and post-go-live stability. Cap the upfront portion so the vendor still has skin in the game. Hold a meaningful final tranche until the system runs without intervention for a defined stability period. This is the clause that turns vendor promises into vendor accountability. - Build a meaningful contingency line into the budget from day one. If the vendor says you do not need one, that is the clearest signal you do. Vendors who have delivered ERP projects do not push back on contingencies. Vendors who have not, do. - Bake in a data audit clause and a training deliverable. Named roles. Completion certificates. These two line items prevent the underutilisation tax that triggers the surprise cheque six months later. - For [custom ERP or Odoo-based builds](/erp-development), get a fixed-scope statement of work. Name every integration. Every custom workflow. Every report. Before signature. The SOW is the only document that matters when the second cheque arrives.

Run this checklist and the ₹18 lakh surprise shrinks to a line item you can defend in a board meeting. The next five years look very different when you do, and the vendor that survives this filter is the one worth keeping on speed dial for the next five.

A correctly scoped ERP deployed under timeline discipline eliminates the second-cheque problem entirely. There is no surprise because the scope, the price, and the deliverables were locked before signature.

Systems that go through this discipline are still running in production years after deployment. The per-year cost of ownership drops because the customisation debt was paid down early, not deferred. The original CAPEX decision defends itself in every board review.

Indian enterprises running custom ERP and Odoo-based stacks for finance, inventory, and operations do so on budgets the CFO can actually forecast. Board-ready reports on day one. No Excel fallbacks. Renewal terms locked at signing. The system is the system of record. The finance team trusts it.

The same engineering rigour that keeps a production system stable for the long term keeps a custom ERP alive. The discipline is identical. Locked scope. Milestone delivery. A partner who treats post-go-live as the start of a long-term relationship, not the end of a sales cycle.

How much does ERP implementation cost in India for a mid-sized company?

Total ERP cost for a mid-sized Indian company varies widely by licence model, customisation depth, and integration scope. Cloud-based and open-source deployments sit at the lower end. Heavily customised enterprise ERP sit at the upper end. Always budget an additional contingency line. The headline figure is not the real one.

What are the hidden costs of ERP implementation that vendors don't quote upfront?

The four most common hidden costs are data migration, especially from legacy spreadsheets and duplicate masters. Customisation beyond the demo workflows. Training and change management. Annual licence renewals that compound over the life of the contract. These four categories are where the typical 40-70% budget overrun originates.

How long does ERP implementation take in India?

A partner-led ERP implementation in India typically takes a few months from kickoff to stabilisation. In-house deployments routinely stretch much longer. During that stretch, scope expansion and scope creep consume the contingency budget before go-live. The timeline is itself a cost variable. Longer projects almost always cost more.

How can a CFO prevent ERP cost overruns?

Lock the functional scope and integration list in writing before contract signature. Demand milestone-based payments, with a meaningful final tranche held back until the system is stable post go-live. Build a contingency line into the budget. Treat training and data migration as first-class line items, not afterthoughts. CFOs who enforce these four controls consistently stay inside the original estimate.

Why is my company still using Excel after going live on ERP?

Almost always a training and configuration problem, not a software problem. End-users route around an ERP when the system does not match their actual workflow. They route around it when reports are slow. They route around it when no one trained them properly on the parts of the system that map to their daily tasks. The fix is rarely more software. It is configuration, role-based training, and a deliberate change-management plan that runs well past go-live.

Research and references cited in this article:

• ERP Implementation Cost: Full Pricing Breakdown in 2026
• ERP Implementation in 2026: A Complete Guide to Costs and Hidden Expenses - ERPPILOT.com
• ERP Implementation Cost Calculator | 2026 Pricing Guide
• ERP Software Development Costs: Complete Pricing Guide for 2026
• ERP Software Development Cost: Steps, Timeline & Budget
• Budget Overruns in ERP Projects - DaroSoft
• ERP Implementation Failure Statistics: Key Causes & Business Risks
• Why ERP Implementation Projects Fail: Key Reasons and Fixes
• 55% of ERP projects exceed budgets. Here’s how to avoid it.”
• Why ERP Projects Go Over Budget And How To Prevent It
• Plan Ahead: Your 2026 ERP Budget Planning Checklist - Encompass
• 10 ERP Implementation Best Practices for a Successful Rollout in 2026