The Final LeapCollaterals & Engagements
← LibraryMeasure

Value & ROI Model

How to build a business case a CFO will accept: the J-curve, value drivers, the costs everyone forgets, the mandatory sensitivity table, and what we refuse to put in a model.

8 min readFor: Engagement leads, client finance partnersStage: Measure
The governing rule

The client supplies the money; we supply the engineering deltas and the method. No currency figure appears in a deliverable unless the client's finance function sourced or ratified the input. That is not caution for its own sake — it is what makes the number survive contact with the CFO.

J-curve of AI value realisationA curve dipping below the baseline before rising, with the three causes of the dip labelled.Starting baselineLearning curveVerification taxPipeline adaptationCrossoverFramework: DORA, The ROI of AI-assisted Software Development (2026.1)
The assumption that decides the answer: how long you spend below the line.

The model shape

Net value
Σ value drivers − Σ costs − instability tax
First-year ROI
net value ÷ total first-year investment
Payback
months until cumulative net value crosses zero, after the dip

Value drivers

DriverWhat we measureClaim discipline
Capacity releasedLead-time and wait reductionOnly value if reinvested — state explicitly what it was spent on, or finance will
Rework reductionRework share, revert rate, churnThe most defensible driver: measurable without heroic assumptions
Incident cost avoidanceChange failure rate, recovery timeClient's incident cost model only, never benchmark-derived
Time to marketOne named flagship commitmentSpecific beats comprehensive
Onboarding and knowledge accessTime to first meaningful contributionSupported by the evidence that AI helps most on unfamiliar code
− Instability taxIncrease in change failure rate, recovery time, unplanned workA mandatory negative line, even when it is zero

Costs

  • Licences and seats — including unused seats; they are real cost.
  • Inference and infrastructure where usage-priced.
  • The verification tax: reviewer minutes × loaded cost. The cost everyone forgets; naming it is a credibility moment.
  • Enablement and change time, including deliberate unassisted practice.
  • Platform and pipeline investment — often the largest and most durable item.
  • Governance, audit and security: the real burden of adoption has shifted here.
  • Consulting fees. Omitting them invites exactly one question.
  • The J-curve dip, shown as an explicit line and never buried.

The sensitivity table is mandatory

AssumptionLowBaseHigh
J-curve dip depth10%15%25%
J-curve duration2 months3 months12 months
Share of released capacity reinvested25%50%80%
Verification tax per AI-assisted PRmeasured −30%measuredmeasured +50%
Change-failure-rate movementimproves 10%flatworsens 20%
Present the range before the point estimate

A CFO who sees the range first trusts the estimate; one who sees the estimate first interrogates it. The twelve-month duration column is the one that changes the conversation — in DORA's own calculator it flips an illustrative positive case to a negative first-year return.

When the client has no cost data

  1. Physical units onlyEngineer-days released, incident hours avoided, rework share reduced. Many boards are satisfied by this and it is fully defensible.
  2. A client-chosen placeholder rateApplied transparently with the arithmetic shown, so finance can substitute their own figure. Their number, their model, our method.
  3. Defer the money modelTo the quarter-two review, and use quarter one to establish the physical deltas. This is the usual recommendation.
Never

Fill the gap with an industry average. A single unsourced currency figure contaminates every number beside it.