Your ERP Is Over Budget - Now What?

Your ₹5 crore ERP project has now cost ₹6.5 crore.
The vendor says another ₹1.5 crore is needed.
Your CFO is furious. The board is demanding accountability.

Now what?

Before committing more money, you need to understand *why* the overrun happened. The cause determines whether throwing more money at the problem makes sense—or whether you're throwing good money after bad.

Diagnosis: Why Are We Over Budget?

Root Cause #1: Scope Creep (40-50% of overruns)

Change requests. Requirement changes. "Just add this feature..."

Check: Compare current scope to original Document. How many changes were approved? What's the cost of each?

The decision: If scope additions are genuinely valuable, additional investment is justified. Otherwise, cut scope ruthlessly.

Root Cause #2: Vendor Underestimation (30-40% of overruns)

The vendor said 12 months, you're at month 14. Configuration is more complex than expected. Data migration issues. Customizations take longer than forecast.

Check: Is the vendor meeting their milestones, or are they consistently missing deadlines? Are there delays that appear systemic (vendor capability issue) or project-specific?

The decision: If delays are vendor-driven and they're not catching up, you might need a different vendor. If delays are legitimate complexity, additional budget may be necessary.

Root Cause #3: Poor Project Governance & Leadership (20-30% of overruns)

No clear decision-making. Steering committee meetings are chaotic. Vendor calls the shots instead of the business. CFO/CIO misaligned.

Check: Is there a formal change control process? Does the steering committee meet regularly with clear accountability? Is the CFO leading or reactive?

The decision: If the problem is governance, additional budget won't help. You need to restructure governance frameworks first.

Root Cause #4: Data Quality Issues (10-20% of overruns)

Source system data is messier than expected. Migration takes longer than forecast. Data remediation is more complex.

The decision: Data issues typically require additional investment to fix properly. But negotiate with the vendor on who bears responsibility—sometimes it's shared cost.

The Four Options When Over Budget

Option A: Approve Additional Budget (With Conditions)

When to do this: Scope additions were legitimate business priorities. Vendor performance is solid. The additional ₹X crore is for genuinely critical functionality.

Conditions:

• Get independent assessment of whether additional cost is justified
• Renegotiate vendor contract with firm fixed-price for remaining work
• Establish new go-live date—in writing, with penalties for further delays
• Lock down scope—no more changes
• Establish governance to prevent further creep

Risk: High. This often becomes a slippery slope where you keep approving overages.

Option B: Cut Scope (Reality Check)

Original scope: ₹5 crore, 12 months, includes AP, AR, GL, inventory, purchasing, MRP, advanced analytics

New scope (Phase 1): ₹5.5 crore, 10 months—AP, AR, GL, inventory, purchasing only. MRP + analytics → Phase 2 (post-go-live, 6 months later)

Benefit: You get a functioning, stable ERP 2 months faster. Second phase addresses remaining features after go-live stability.

This is often the smartest path.

Option C: Replace the Vendor (Hard Reset)

When to do this: The vendor is underperforming. Configuration quality is poor. Team morale is bad. You've lost confidence.

Process:

• Hire independent advisor to assess work done to date
• Document vendor failures (contractual basis for termination)
• Bring in new vendor to inherit and complete project
• New vendor remediates poor configuration

Cost: Additional ₹40-60 lakhs for new vendor ramp-up + remediation
Timeline: 2-3 months of overlap, then new vendor takes over
Outcome: Often better than continuing with failing vendor

Option D: Pause & Reassess

When to do this: You don't have clear answers to "why are we over budget?" You need independent diagnosis before committing more money.

Process:

• Bring in independent ERP advisor (2-3 week assessment)
• Diagnose root causes (scope? vendor? governance? data?)
• Map recovery path (add budget? cut scope? change vendor?)
• Establish new baseline (realistic timeline + budget)

Cost of assessment: ₹15-30 lakhs
Potential savings: ₹1-5 crore (by avoiding mistake of throwing more money at wrong problem)

The Questions Your CFO Should Ask Before Approving More Money

1. What specifically caused the overrun? (Get detailed answer, not "complexity")
2. Are these genuine scope additions, or vendor mismanagement?
3. Is the vendor performing to their commitments, or have they lost control?
4. What governance structure do we have? (If weak, more money won't help)
5. What's the realistic new timeline with this additional ₹X crore?
6. What happens if we cut Phase 2 features and go-live with Phase 1?
7. Do we need independent assessment before committing more funds?

The Bottom Line

Over-budget ERP projects rarely fix themselves with more money. They fix themselves by:

• Understanding the root cause (scope? vendor? governance?)
• Making hard choices (cut scope, replace vendor, restructure governance)
• Establishing accountability (CFO-led governance, fixed-price contracts, independent oversight)

Before you write the check for additional funding, make sure you're solving the real problem—not just throwing money at symptoms.