← All whitepapers

Delivery guide

The 90-day plan for a first governed AI capability

By Richard White ·

Free, no form.

Abstract

What an engagement actually looks like, week by week. This fifteen-page guide lays Frame, Prove, Build and Run across thirteen weeks with three decision gates, so a buyer and their procurement team can see what will be delivered, what evidence each gate needs and what happens if the evidence is not there.

It defines the measurement contract (what counts as a useful completion and what the cost per useful task is measured against), the release criteria that must survive a tightening calendar, the review routes, such as model risk, privacy and security, to start in week two, and a representative team with the time it asks of your people.

Day 90 is a review point, not a completion date: evidence supports proceeding, narrowing scope or stopping. Build continues by release past it, and Run begins when approved work reaches real users. The guide ends with a one-page brief to bring to a first conversation.

Decision it supports

Whether to commit to Frame and Prove for one workflow, and what your own team must supply.

What you will produce

A workflow brief and evidence plan to anchor your thirteen-week delivery plan: current and target work, baseline, dependency owners and release conditions.

See it worked through in a guide

Claims package 1.1.0 · 26 October 2026. Synthetic worked example: team A, group disability, region 2. Read-only preparation of the assigned case; examiners retain every case decision. Hold candidate 1.0.0 after an unrelated employee’s claim is returned. In the synthetic decision, accept 1.1.0 for a monitored team A rollout only after prior-claims history is disabled and the remaining scope passes a fresh evaluation. All figures, evidence and sign-offs in that guide are invented; the paper provides the underlying method.

In the paper

Three passages, as published

Honest cost

When no task meets the useful-completion criteria, report the cost and zero completions.

Release criteria

Protect the release criteria when the calendar becomes tight.

Past day 90

Because Build typically takes eight to sixteen weeks per release, it runs past day 90.

Keep reading

Read next

Stay informed

Subscribe to whitepapers and updates

Hear from Richard White when new whitepapers, practical guides and Studio updates are available. Subscribing is optional; every whitepaper remains free to download.

We use your email for these updates. Reply to any update or email rwhite@rjlsol.com to unsubscribe. See our privacy notice.

Next step

Discuss this paper against your own program.

A free sixty-minute working session with Richard on your top gaps. You leave with a one-page summary within three business days, and three next questions.