PreviewYou're previewing CFO AI Ledger. Sign in to use it.Sign in
← All decisions
Value measurement

How to measure AI ROI

When it comes up

When approving AI business cases, reporting AI value to the board, renewing AI contracts, or when sponsors report hours saved and you need to know what it is worth.

Your options

Hours saved × loaded cost

Fits when: Early pilots in well-understood processes where time is the main benefit.

Watch out: Overstates value unless the time becomes cost out, avoided hires or measured new output.

Cash and P&L impact (cost out, avoided cost, revenue, working capital)

Fits when: The use case changes a budget line, a hiring plan, DSO or a revenue metric.

Watch out: Attribution: other changes happen at the same time; needs baselines and ideally a holdout.

Unit economics and quality (cost per item, error rate, cycle time, forecast accuracy)

Fits when: High-volume processes and decision-support use cases.

Watch out: Quality improvements must be tied to consequences (write-offs avoided, decisions changed) to count as value.

Portfolio return (total AI spend vs total measured benefit)

Fits when: Board and investor reporting across many use cases.

Watch out: Hides poor performers inside the total; needs use-case-level tracking underneath.

How to decide

  1. Baseline first: volume, time, cost, error rate, cycle time.
  2. Pick the value mechanism per benefit: cost out, avoided cost, redeployed capacity, quality, revenue.
  3. Model it in the ROI builder: NPV, payback, sensitivity, break-even adoption.
  4. Track monthly against the case: adoption, unit outcome, run cost.
  5. Report two lines: P&L value and capacity/quality value, separately.
  6. Aggregate to a portfolio view for the board, with use-case detail available.

Trade-offs

Hours saved are easy to measure but rarely cash; P&L measures are credible but slower and harder to attribute; unit economics are precise but narrow; portfolio returns tell the board the big picture but can hide failures.

Real examples

What to check first

  1. Whether a baseline exists for each use case.
  2. How each benefit line becomes cash, capacity or quality.
  3. Whether run costs (seats, tokens, people) are tracked against the case.

Learn and use

Sources

Last reviewed 2026-10-01.