Why most ERP business cases fail
Most ERP proposals die in the CFO’s office for the same reason: they read like a wish list, not an investment case. They lead with features, lean on vendor ROI claims, and count “soft” benefits no one can audit. A business case that gets approved does the opposite—it’s conservative, grounded in your own numbers, and honest about assumptions. This guide walks through how to build one.
A guiding principle throughout: if you can’t defend a number in front of an auditor, don’t count it. Understating benefits and being transparent about assumptions builds far more credibility than an aggressive case that collapses under scrutiny.
Step 1: Establish your baseline cost
You can’t prove improvement without a starting point. Quantify what today’s systems and processes actually cost.
Gather:
- Labor hours spent on manual reconciliation, re-keying, and report-building (hours × loaded hourly rate)
- Month-end close duration and the cost of delayed decisions
- Inventory carrying costs, stockouts, and expedited freight
- Write-offs and error-correction costs
- Current software, hosting, and support spend
These figures come from your finance and operations teams—not from a vendor. That’s what makes them defensible.
Step 2: Identify benefit categories (conservatively)
Group benefits so each is traceable to a baseline number:
- Labor efficiency: hours saved from automation and eliminated re-keying.
- Faster close & better decisions: value of a shorter, more reliable close.
- Inventory & operations: reduced carrying cost, fewer stockouts, less expedited freight.
- Error reduction: fewer write-offs and corrections.
- Risk & opportunity: avoided compliance risk; capacity to grow without adding headcount.
For each, apply a conservative capture rate. If a vendor says automation saves 80% of reconciliation time, model 40–50% in your base case and note the assumption. Never import a vendor’s benchmark as your benefit.
Step 3: Total the investment
Capture every cost category so the case survives scrutiny:
- Subscription/licensing (annual)
- Implementation and configuration (one-time)
- Integrations and data migration
- Change management, training, and internal time
- Ongoing support and administration
Step 4: The formulas
Keep the math simple and auditable:
- Annual net benefit = (Sum of conservative annual benefits) − (Annual recurring costs: subscription + support)
- Total investment = One-time costs (implementation + integration + migration + change management) + first-year recurring costs
- Payback period (years) = Total investment ÷ Annual net benefit
- 3-year net value = (Annual net benefit × 3) − One-time investment
- Simple ROI = (3-year net value ÷ Total investment) × 100%
For a more rigorous case, discount future benefits to present value; a simple payback plus a three-year net value is usually enough to earn approval when the inputs are conservative.
Step 5: Model three scenarios
A single-number forecast invites skepticism. Present a range instead:
| Scenario | Benefit capture | What it shows |
|---|---|---|
| Conservative | ~40% of identified benefits | The case still works even if adoption lags. |
| Expected | ~65% of identified benefits | Your realistic planning number. |
| Optimistic | ~85% of identified benefits | Upside if execution goes well. |
Lead with the conservative scenario. When the numbers work at 40% capture, a CFO listens.
Step 6: Sensitivity and governance
Show which assumptions move the outcome most, usually labor savings and implementation cost, and how the payback shifts if each is 20% worse. Then define governance: who owns realizing each benefit, how you’ll measure it post-go-live, and the checkpoints for course-correction. A benefit with an owner and a measurement plan is credible; one without is a hope.
One-page executive summary template
Give your CFO the whole story on one page:
- The problem: 2–3 quantified pain points (e.g., “close takes 15 days; team spends 120 hours/month on manual reconciliation”).
- The proposal: what you’re recommending and why now.
- The investment: total three-year cost, broken into one-time vs. recurring.
- The return: annual net benefit, payback period, and three-year net value (conservative scenario).
- The scenarios: conservative / expected / optimistic in one row each.
- Key assumptions & risks: the 3–4 that matter most, each with an owner.
- The ask: the specific decision and next step you need.
Frequently asked questions
How conservative is too conservative?
If your base case still shows acceptable payback at ~40% benefit capture, you’ve struck the right balance between credibility and ambition.
Should I include soft benefits like morale?
Mention them as qualitative upside, but don’t put them in the ROI math. Keep the numbers to benefits you can measure.
What payback period is acceptable?
It varies by company and CFO. Many mid-market organizations look for payback within 2–3 years—confirm your CFO’s threshold early.
Next step
Don’t start from a blank spreadsheet. Download the ROI worksheet to plug in your baseline numbers and generate a conservative, auditable ERP business case—complete with payback, three-year net value, and the three scenarios your CFO expects to see.