Business Case and ROI
Why you need a business case
ITIL v5 adoption is an investment, not an expense. Like any investment, it requires a structured business case that quantifies costs, benefits, risks, and expected returns. Without one, ITIL adoption becomes an IT project rather than a business decision, and it will struggle to secure sustained funding and executive commitment.
Building the business case
Step 1: Define the problem statement
Articulate the business problems that ITIL v5 adoption will address. Use evidence, not generalizations:
| Weak Problem Statement | Strong Problem Statement |
|---|---|
| "Our IT operations need improvement" | "Unplanned downtime cost the business $2.4M in lost revenue last year; 43% of incidents were preventable with existing knowledge" |
| "We need better processes" | "Change failure rate is 18% (industry benchmark: 5%), causing 6.2 hours of additional unplanned work per failed change" |
| "Customers are unhappy with IT" | "Customer satisfaction score is 3.1/5.0; 67% of complaints relate to resolution speed and communication quality" |
Step 2: Quantify current costs (the "do nothing" scenario)
Calculate the ongoing cost of not adopting ITIL v5:
| Cost Category | How to Calculate | Example |
|---|---|---|
| Incident cost | (Average resolution time x hourly cost of affected staff) x incident count | 500 incidents/month x 2 hours x $150 = $150,000/month |
| Downtime impact | Revenue per hour x downtime hours | $50,000/hour x 120 hours/year = $6M/year |
| Change failure cost | (Change failure rate x total changes) x average remediation cost | 18% x 200 changes/month x $5,000 = $180,000/month |
| Knowledge loss | Replacement cost when key staff leave without documentation | 2 departures/year x $150,000 = $300,000/year |
| Compliance risk | Potential fines, audit remediation costs, insurance premiums | Varies by industry and regulation |
| Opportunity cost | Revenue lost because IT cannot deliver new capabilities fast enough | New product delayed 6 months = estimated $2M in deferred revenue |
Step 3: Estimate adoption investment
| Investment Category | Items | Typical Range |
|---|---|---|
| Training | ITIL v5 Foundation and advanced certifications for key staff | $500-2,000 per person |
| Consulting | External advisory for assessment, design, and implementation support | $50,000-500,000 depending on scope |
| Tooling | ITSM platform enhancements, AI/AIOps tools, observability stack | $50,000-1M depending on scale |
| Internal effort | Staff time dedicated to the transformation programme | 2-5 FTEs for 12-18 months |
| Change management | Communication, training materials, workshops | $20,000-100,000 |
| Ongoing operations | Continual improvement, practice management, maturity assessments | 1-2 FTEs ongoing |
Step 4: Project benefits
Quantify expected improvements based on industry benchmarks and your own baseline:
| Benefit Area | Industry Benchmark | Annual Value (example: 500-person IT org) |
|---|---|---|
| Incident reduction | 20-40% fewer incidents after maturity Level 3 | $360,000-720,000 |
| Faster resolution | 30-50% improvement in MTRS | $200,000-400,000 |
| Change success | Change failure rate from 18% to 5% | $280,000 |
| Improved productivity | 10-20% reduction in unplanned work | $500,000-1,000,000 |
| Customer retention | 5-15% improvement in satisfaction | Revenue retention multiplier |
| Compliance readiness | ISO audit pass without remediation | $100,000-500,000 in avoided costs |
| Staff retention | 10-20% reduction in IT turnover | $150,000-300,000 |
Step 5: Calculate ROI
Simple ROI formula:
ROI = (Total Benefits - Total Investment) / Total Investment x 100%Example calculation:
| Item | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Investment | $800,000 | $200,000 | $200,000 |
| Benefits | $400,000 | $1,200,000 | $1,500,000 |
| Net value | -$400,000 | $1,000,000 | $1,300,000 |
| Cumulative | -$400,000 | $600,000 | $1,900,000 |
Three-year ROI: ($3,100,000 - $1,200,000) / $1,200,000 = 158%
Payback period: ~14 months
Conservative estimation is credible. When presenting to the board, use conservative assumptions. Overinflated projections create unrealistic expectations and erode trust. Show a "conservative," "expected," and "optimistic" scenario.
Step 6: Assess risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Adoption takes longer than planned | Medium | Medium | Build 20-30% time buffer into the plan |
| Organizational resistance slows adoption | High | High | Invest in Change Leadership from day one |
| Benefits take longer to materialize | Medium | Medium | Plan for quick wins to demonstrate early value |
| Key sponsor leaves the organization | Low | High | Ensure multiple executive sponsors |
| Technology costs exceed estimates | Medium | Medium | Phase technology investments; start with existing tools |
Presenting to the board
What boards care about
| Board Interest | How to Address |
|---|---|
| Revenue impact | Connect ITIL improvements to revenue protection and growth enablement |
| Risk reduction | Quantify compliance, security, and operational risk reduction |
| Competitive position | Show how ITIL maturity improves speed to market and customer experience |
| Cost optimization | Demonstrate efficiency improvements and waste reduction |
| Strategic alignment | Connect ITIL adoption to the organization's strategic plan |
Presentation structure (one-page executive summary)
- Problem: What business problem does this solve? (2-3 sentences with financial impact)
- Solution: ITIL v5 adoption addresses this through... (2-3 sentences)
- Investment: Total cost over 3 years (one number, with breakdown available)
- Return: Expected benefits over 3 years (one number, with breakdown available)
- Timeline: Key milestones (3-5 milestones)
- Ask: What decision do you need from the board?
Non-financial benefits
| Benefit | Measurement |
|---|---|
| Improved decision-making | Faster, data-driven decisions at all levels |
| Reduced key-person dependency | Knowledge documented and shared; lower single-point-of-failure risk |
| Better employee experience | Higher engagement, lower burnout, improved retention |
| Organisational agility | Faster response to market changes and customer needs |
| Innovation capacity | Less time on firefighting means more time for innovation |
| Stakeholder confidence | Customers, partners, and regulators see a well-managed organization |
Related pages
- Executive Summary (strategic overview for board context)
- Measuring Success (KPIs and metrics)
- Implementation Roadmap (where investment is allocated)
- Decision Framework (adoption models and timing)
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass