Most AI business cases fail for the same reason: they lead with technology and leave the money for the appendix. Executives don't approve AI projects. They approve business outcomes with positive ROI. The AI is just the mechanism.
Here's how to build an AI business case that gets funded.
Why AI Business Cases Fail
- Technology-first framing: "We need a machine learning platform" vs. "We can reduce claim processing time by 60%, saving €2.4M annually"
- Vague benefits: "Improved efficiency" and "better insights" don't get budget approval. Quantified outcomes do.
- Underestimated costs: Data preparation, governance, change management, and ongoing operations often 3-5x the initial model development cost
- No risk adjustment: Presenting best-case ROI without acknowledging execution risk, data quality risk, and adoption risk
- Missing the comparator: What happens if we don't invest? The cost of inaction is often the strongest argument.
The Business Case Framework
Step 1: Define the Business Problem
Start with the problem, not the solution:
- Problem statement: Specific, measurable business problem with quantified current impact
- Current state metrics: Processing time, error rate, cost per unit, customer satisfaction score — whatever metrics define the problem
- Cost of the problem: What does this problem cost annually? Include direct costs, opportunity costs, and risk costs.
- Stakeholder impact: Who is affected? Customers, employees, regulators, partners?
Step 2: Quantify the AI Solution
Cost Model
Total Cost of Ownership
- Data preparation (30-40% of total cost): Data collection, cleaning, labeling, pipeline development, ongoing data maintenance
- Model development (15-20%): Experimentation, training, validation, testing
- Infrastructure (15-20%): GPU compute, storage, networking, ML platform, monitoring tools
- Governance and compliance (5-10%): Documentation, risk assessment, regulatory compliance, audit preparation
- Change management (5-10%): Training, communication, workflow redesign, adoption support
- Ongoing operations (recurring): Model monitoring, retraining, data pipeline maintenance, infrastructure costs, support
Benefit Quantification
- Cost reduction: Labor savings (be specific about FTE impact), error reduction (cost of errors × error reduction), processing speed improvement
- Revenue increase: Higher conversion rates, better customer retention, new products/services enabled by AI
- Risk reduction: Reduced regulatory fines, fewer security incidents, better fraud detection
- Strategic value: Competitive positioning, market entry, customer experience improvement — harder to quantify but important to articulate
Step 3: Risk-Adjusted ROI
Don't present a single ROI number. Present a range:
- Conservative case: 50% of projected benefits, 120% of projected costs. This is the "things go wrong" scenario.
- Base case: Expected benefits and costs based on comparable implementations
- Optimistic case: Full benefit realization with on-budget delivery
- Probability weighting: If you can estimate probability of each scenario, present expected value
Step 4: Cost of Inaction
What happens if you don't invest?
- Competitive risk: Competitors adopting AI gain cost or capability advantages
- Regulatory risk: AI Act and related regulations create obligations that require AI governance investment regardless
- Talent risk: Top technical talent leaves for organizations with modern AI infrastructure
- Accumulating technical debt: Manual processes become more expensive to maintain as scale increases
Kubernetes Recipes
Practical guide for container orchestration and deployment — hands-on patterns you can use today.
View on Amazon →Business Case Template
Executive Summary Structure (1 page)
- Business problem: 2-3 sentences with quantified current cost
- Proposed solution: What we'll do (not how the technology works)
- Expected outcomes: Quantified benefits with timeline
- Investment required: Total cost over 3 years (capex + opex)
- ROI: Risk-adjusted ROI range and payback period
- Risk of inaction: What we lose by not investing
- Ask: Specific approval requested — budget, timeline, resources
Common Mistakes
- Selling AI, not outcomes: Executives buy outcomes. Lead with the business problem and the measurable improvement.
- Year 1 ROI expectations: Most AI initiatives have a 12-18 month payback period. Set expectations for year 2-3 returns.
- Ignoring change management costs: The technology is often 50% of the investment. People, process, and governance are the other 50%.
- No phasing: Present a phased approach with early milestones and decision points, not a monolithic 3-year program with a big-bang delivery.
- Comparing to perfection: Compare AI performance to current human performance, not to theoretical perfection. 85% AI accuracy beats 70% manual accuracy.
Need help building the business case?
Open Empower runs fixed-fee AI Opportunity Assessments from €18,000 — we score, size and sequence your AI use cases against business value, risk and EU AI Act / DORA / GDPR fit. The output is a CFO-ready business case and a 12-month plan, in 2–3 weeks.
See the AI Opportunity Assessment → · AI Readiness Assessment pricing → · Book a 30-min scoping call →
ServiceNow Basics: IT Automation & AI-Powered Workflows
Design AI-powered workflows in ServiceNow for IT operations. In collaboration with Starweaver.
Start on Coursera →
Luca Berton
