The integrator’s quote runs 48 pages. The summary deck is 20 slides. The executive committee meeting is 45 minutes. And at the end, the answer is: “Let’s revisit this next quarter.” Project dead before it ever got started.
In most cases, it wasn’t the ERP project that was flawed. It was the investment case presentation. The executive committee didn’t see the value because no one showed it from their angle: financial return, risk control, and competitive positioning.
This article gives you the methodology to build an ERP business case that actually gets approved. Not a business case that reassures the IT department, but an investment case that convinces the CEO, CFO, and commercial directors — even the most sceptical ones.
What you will find in this article:
- The 7 components of a structured ERP business case
- How to quantify ROI, TCO, and the cost of inaction
- The 10-slide executive presentation format for C-suite audiences
- Common objections and how to pre-empt them
Why ERP Business Cases So Often Fail to Convince the Executive Committee
The Classic Mistake: Presenting a Cost Instead of a Value
Most ERP business cases presented to executive committees share the same structural flaw: they open with the budget. “This project will cost X over 3 years.” The immediate reaction is to look for ways to reduce, defer, or avoid that number.
The right framing is the opposite: start with what the current situation is costing you. How many hours per month do your teams spend on manual tasks that an ERP would automate? What is the cost of each billing error? What commercial opportunity are you missing because you lack real-time inventory visibility?
A €400,000 investment that generates €130,000 in recurring annual savings is a business decision. A €400,000 cost with no quantified counterpart is an IT expense that can always be deferred.
The C-Suite Thinks in IRR and Payback, Not “Features”
No one in your executive committee will be convinced by “the centralised purchasing module will streamline quote requests.” However, “automating supplier follow-ups will free up 0.4 FTE in the procurement team, equivalent to €24,000 in recurring payroll costs” is an argument the CFO can put in a spreadsheet.
Executive committees analyse an ERP business case using the same tools as an industrial investment:
- Payback period: how many years before the gains cover the total investment?
- IRR (Internal Rate of Return): what annualised return does the investment generate over 5 years, compared to the company’s cost of capital?
- NPV (Net Present Value): is the sum of discounted future cash flows positive?
A business case that does not mention these three metrics is not yet a business case. It is a project intention.
What Each Member of the Executive Committee Needs to Hear
Each executive committee member has a different entry point. Your presentation must address each one:
| Member | Their Primary Question | The Decisive Argument |
|---|---|---|
| CEO | ”Does this support our growth strategy?” | Scalability, group reporting, acquisition capacity |
| CFO | ”What is the exact ROI, and who co-signs the assumptions?“ | 5-year TCO, payback, sensitivity analysis |
| HR Director | ”How many people will suffer through this project?” | Change management plan, measured additional workload |
| CIO | ”Are we risking a migration disaster?” | Technical architecture, cutover plan, reversibility |
| Commercial Director | ”Will my teams lose weeks of productivity?” | Timeline, Phase 1 scope, impact on commercial activity |
A solid business case anticipates these five angles. If you are missing an answer for any one of them, your executive committee will find it — and ask at the worst possible moment.
The 7 Components of a Solid ERP Business Case
A compelling ERP business case is not a document. It is a structured argument in seven steps that holds together from start to finish.
1. Diagnosis of the Current Situation (Cost of Inaction)
Before discussing the solution, document the problem. In 2 to 3 pages maximum: which processes are failing, how frequently, and what is their estimated current cost. Interview business unit directors to co-build this diagnosis. This transforms them into project co-sponsors well before the executive committee meeting.
2. Definition of Functional Scope and Target Scenario
Which processes does Phase 1 cover? Which modules are included or excluded? Which sites or entities are in scope? The scope must be precise and contractually bindable. A vague sentence in your presentation will become a disagreement with the integrator eight months later.
3. Total Project Cost (5-Year TCO)
The TCO covers licences or SaaS subscriptions, integration and deployment, data migration, training, change management, and ongoing maintenance. Present three scenarios: optimistic, realistic, pessimistic. A single number is not credible; a range with explicit assumptions is. Our detailed ERP TCO analysis covers the eight cost items most often missing from initial budgets.
4. Quantifiable Benefits
Productivity gains (FTEs freed up), reduction in DSO (Days Sales Outstanding), inventory optimisation, reduction in billing errors. Each gain must be quantified with an explicit assumption: not a percentage drawn from a generic industry report, but a calculation based on your own data (current number of manual entries, measured error rate, current monthly close days).
5. Non-Quantifiable But Arguable Benefits
Compliance with mandatory e-invoicing requirements, scalability for future acquisitions, reduction of regulatory risk (GDPR, NIS2, CSRD): these are not numbers, but they are arguments the executive committee understands. Present them qualitatively, without assigning them a fictitious euro value.
6. Risk Analysis and Mitigation Plan
Each identified risk (budget overrun, change resistance, loss of a key resource mid-project) must have an estimated probability, assessed impact, and a concrete mitigation measure. A business case that does not address risks is perceived as naive.
7. Success Criteria and Post-Go-Live KPIs
How will you know the ERP delivered on its promises in 18 months? Define 5 to 8 measurable KPIs: monthly close time, error-free order rate, days of inventory coverage, invoice processing time. These indicators give credibility to the announced ROI and allow the executive committee to verify that the investment paid off.
How to Quantify ERP ROI: Method and Calculation Examples
The 5-Year TCO: Your Denominator
Always start with the denominator. A spectacular ROI built on an underestimated TCO will be disproven 12 months after go-live — and your credibility along with it. Our article on the real cost of an ERP project details realistic ranges by company size.
For an industrial SME with €50M revenue (50 users, Tier 2 ERP):
| Cost Item | Realistic Range |
|---|---|
| Licences / SaaS over 5 years | €80,000—€150,000 |
| Integration and deployment | €100,000—€200,000 |
| Data migration | €20,000—€50,000 |
| Training and change management | €20,000—€40,000 |
| Ongoing maintenance over 5 years | €50,000—€100,000 |
| Total 5-year TCO | €270,000—€540,000 |
Quantifying Productivity Gains: The FTE Method
One Full-Time Equivalent (FTE) represents approximately €45,000 to €65,000 in annual employment costs (salary plus employer contributions) for an administrative or accounting profile. The FTE method involves estimating avoidable manual hours, then converting them into a fraction of a full-time role.
Applied example:
| Avoidable Manual Task | Current Hours | Hours After ERP |
|---|---|---|
| Bank reconciliations | 4 hrs/week | 0.5 hrs/week |
| Processing paper purchase orders | 5 hrs/week | 0.5 hrs/week |
| Customer follow-ups and Excel exports | 6 hrs/week | 1 hr/week |
| Total freed | 15 hrs/week | 2.5 hrs/week |
15 hrs - 2.5 hrs = 12.5 hours freed per week, approximately 650 hrs/year. At a loaded hourly cost of €55, this represents €35,750 in recurring annual productivity gains. Get these assumptions validated by the relevant business directors before the presentation: their numbers in your slides are worth ten times more than your own estimates.
Quantifying the Impact on Working Capital
An ERP improves DSO (Days Sales Outstanding) through automated follow-ups and faster invoicing. It optimises stock levels through better demand planning.
DSO impact: For a company with €50M revenue and a current DSO of 55 days, reducing it to 45 days releases €50M x 10/365 = approximately €1,370,000 in cash. This is not revenue but a one-off working capital release, presented separately from recurring gains.
Inventory impact: A 10% reduction in average stock level on a €2M inventory releases €200,000 in cash and reduces storage costs and obsolescence risk.
Calculating Payback Period and IRR
With a TCO of €400,000 over 5 years and recurring gains of €120,000 per year (productivity + data quality + DSO improvement + error reduction), the payback period is €400,000 / €120,000 = 3.3 years. The 5-year IRR is calculated on net annual cash flows (gains minus annual costs). On a 30-minute spreadsheet, you can produce a figure precise enough for the presentation.
Generally accepted payback periods vary by context:
- Regulation-driven projects (e-invoicing mandate, CSRD): payback period is secondary. It is a must-do; the ROI is the reduction of non-compliance risk.
- Manufacturing: 2 to 3 years
- Services and professional: 3 to 5 years
- High-growth or acquisition context: 2 to 4 years depending on target valuation
Always present three scenarios: optimistic, realistic, pessimistic. An executive committee that sees only one number knows you chose the most flattering one.
The Cost of Inaction: The Decisive Argument That Is Often Overlooked
An ERP business case is not symmetric. You compare an investment against its gains, but you must also show what you lose for every year you wait.
Quantifying Hours Lost to Manual Tasks
The FTE method works in both directions. If your teams spend 1,200 hours per year on avoidable manual tasks at an average cost of €50 per hour, that is €60,000 you are already spending, with no additional output, for every year of delay. Over two years of waiting, that is €120,000 sunk. The ERP project starts to finance itself.
Regulatory Deadlines: A Compelling Argument
The EU e-invoicing mandate under Directive 2014/55/EU is progressively expanding, with several member states enforcing B2B e-invoicing obligations and others following suit. Not having an ERP compatible with Peppol or integrated with a certified access point exposes the company to non-compliance risk with potential penalties. This is no longer an opportunity argument: in many jurisdictions it is a legal obligation with a firm timeline.
The same logic applies to NIS2 (cybersecurity for critical information systems), CSRD (sustainability reporting for mid-market companies from 2026 onwards), and GDPR (data processing traceability in commercial and HR workflows).
The Opportunity Cost of Blocked Growth
Your direct competitor has been on SAP S/4HANA Cloud for 18 months. They have real-time visibility on margins by product and by customer. You are still closing the books on Day 12 with a manually reconciled Excel spreadsheet. This operational gap translates into a commercial gap: slower personalised offers, weaker logistics responsiveness, limited capacity to respond to complex tenders.
The cost of inaction is not only euros wasted today. It is market share you will not capture tomorrow.
Structuring the Executive Presentation: The 10-Slide Format
The executive presentation is not the full business case. It is the executive summary that makes the room want to vote for the project.
| Slide | Content | Duration |
|---|---|---|
| 1 | Diagnosis: 3 striking data points on the current situation | 3 min |
| 2 | Target vision and Phase 1 scope | 2 min |
| 3 | Options considered and selected scenario (with selection criteria) | 3 min |
| 4 | Detailed 5-year TCO (3 scenarios) | 4 min |
| 5 | Quantifiable benefits and business-validated assumptions | 4 min |
| 6 | Payback period and IRR (3 scenarios) | 3 min |
| 7 | Timeline and key milestones (phases, go-live, stabilisation) | 3 min |
| 8 | Risk analysis and mitigation measures | 3 min |
| 9 | Project governance (Steering Committee, sponsor, dedicated team, executive workload) | 2 min |
| 10 | Decision requested and next steps | 3 min |
Total: 30 minutes of presentation, 15 minutes of questions. This is the format that works. Beyond that, you lose the attention of the commercial directors and the HR lead.
Key advice: organise a working pre-meeting with the CFO and CIO before the official executive committee session. Have the CFO validate the financial assumptions so they co-sign the ROI in front of their colleagues. Their agreement in the room is worth more than your best slide.
One more principle worth noting: SaaS solutions (Odoo, Sage, SAP S/4HANA Cloud) allow the investment to be treated as OPEX rather than CAPEX. This is not only a cash flow question: in certain contexts, expensing through operating costs is more tax-efficient than capitalising a software investment. An argument worth discussing with your CFO ahead of the presentation.
Executive Committee Objections and How to Answer Them
| Objection | Structured Response |
|---|---|
| ”It’s too expensive” | Compare against the cost of inaction over 3 years. The ERP does not cost X: it costs you Y if you do not invest (and Y > X over 3 years). |
| ”We don’t have time to manage this” | The executive workload is light: one 2-hour Steering Committee per month. Leadership time is 5 to 8% of their calendar, not 50%. The project manager handles day-to-day delivery. |
| ”We just installed [solution X]“ | Present the existing system audit, the vendor roadmap, and the reasons why solution X does not cover the target scope over 5 years (missing features, end-of-support, technical debt). |
| ”ERP projects always run over” | According to Panorama Consulting (2025 report), the average budget overrun is 24%. Projects that spiral by 60%+ are almost exclusively those without formal governance or contractual milestones. Present your governance framework on Slide 9. |
| ”We can wait” | Point to the nearest regulatory deadline (e-invoicing, CSRD) and quantify the non-compliance risk. Waiting is not free: it has a measurable cost. |
3 Mistakes That Sink an ERP Business Case in Committee
Mistake 1: Understating the TCO to Get It Approved
Presenting a deployment cost of €250,000 and then returning 9 months later asking for an additional €180,000 for “unanticipated developments” is the death of your credibility — on this project and every one that follows. An honest high-end range upfront is always better than a humiliating budget amendment. Our complete TCO analysis helps you leave nothing out.
Mistake 2: Building the Business Case with Only the IT Department
The executive committee does not see “their” problem solved if the business case was built in a silo by IT. Interview every business unit director before the presentation. Their numbers in your slides are worth ten times your own estimates, because they will be able to confirm them when their colleagues question them in the room.
Mistake 3: Presenting an Overoptimistic ROI with No Sensitivity Analysis
An IRR of 35% built on a single linear assumption is not credible. An IRR ranging from 22% to 34% across three scenarios, with explicit assumptions, is a serious argument. CFOs and CEOs respect people who acknowledge uncertainty and are wary of those who deny it.
To go deeper on the financial dimensions of your investment case, see our analysis of the real cost of an ERP project, our TCO guide covering the 8 hidden cost items, and our 2026 ERP comparison guide for choosing the right solution.
