← All guides
Guide · Business Value

How Do You Build an AI Business Case the Board Will Approve?

Last reviewed: 23 July 2026

An AI business case for the board answers four questions in a fixed order: Why now? What does it deliver? Can we execute? What does it cost, and when do we see results? Only 6% of companies see AI ROI in under a year — promising six months anyway costs you credibility at the next budget request.

Which four sections does the board expect?

An AI business case follows different logic than a classic project proposal. It answers four questions in this order — and no other: strategic imperative, business value projection, readiness & risk, investment & roadmap.

1 · Strategic imperative · ½ page

Why now and not later?

Market data, competitive position, the current window of capability — the frame that justifies urgency.

2 · Business value projection · 1 page

What does it deliver concretely?

Value drivers, KPI targets, ROI model and benchmarks — in numbers the board can verify themselves.

3 · Readiness & risk · ½ page

Can we execute this?

Readiness score, the three biggest risks and their mitigations — honest, not dressed up.

4 · Investment & roadmap · 1 page

What does it cost, when do we see results?

Investment plan, milestones, quick wins, and a realistic ROI timeline.

Which KPIs fit which archetype?

A one-size-fits-all KPI framework fits nobody. AI Starters primarily measure readiness — whether the foundation holds. AI Scalers measure leading indicators — whether scaling is on track. AI Transformers measure lagging indicators — whether AI measurably contributes to results.

Only 6%
see AI ROI in under 12 months
13%
reach ROI within 12 months
2–4 years
expected by the majority for full ROI
Readiness KPIs

Starter: data quality score, governance bootstrap. Scaler: API coverage, MLOps maturity. Transformer: knowledge graph quality, agent governance maturity.

Leading KPIs

Starter: first use case live, readiness score. Scaler: use cases in production, adoption rate. Transformer: use cases enterprise-wide, automation level.

Lagging KPIs

Starter: EBIT impact, cost reduction. Scaler: ROI per use case, time-to-value. Transformer: revenue lift, market share.

Two design rules apply regardless of archetype: every KPI needs a baseline value — no measuring without a before-value. And a maximum of five active KPIs per use case; more creates reporting overhead, not insight. Readiness KPIs are reviewed weekly, leading KPIs monthly, lagging KPIs quarterly.

Anti-pattern

Board rule: communicate the ROI timeline honestly. A business case promising payback in six months loses credibility — and with it the next budget request. An honest timeline with clearly named quick wins convinces a board more reliably than an optimistic projection that gets disproven at the first quarterly review.

Glossary

Lagging IndicatorLeading IndicatorAI Value CanvasBusiness Case

Fill in the business case using a template

The AI Value Canvas in the product guides you through all four sections and automatically maps KPIs to your archetype.

Open the Use-Case Scoring →

FAQ

How long should an AI business case for the board be?

Three pages total: half a page imperative, one page business value, half a page readiness & risk, one page investment & roadmap. Anything longer rarely gets read.

What if ROI really only shows up after 3 years?

Name that honestly — and back it up with concrete quick wins in year one. Most companies need 2 to 4 years for full ROI; that's not a red flag, it's the norm.

Do KPIs change as a company moves from Starter to Scaler?

Yes, deliberately. Readiness KPIs fade into the background, leading KPIs move into focus — the framework grows with the archetype, not the other way around.

How many KPIs should a single use case show in the business case?

A maximum of five active KPIs. More per use case mostly creates reporting overhead, not more decision-relevant insight.

DO

Daniel Ostner

From Chapter 3 of the Enterprise AI Guide book

View book →

Related guides