[ AI readiness · Full playbook ]

// 14 / 20

The buyer's playbook.

The working reference behind AI Automation Readiness Assessment 2026: what to ask, what to watch and how to run the first 90 days.

← Back to the guide
[ RFP questions ]// 01

Questions that reveal real capability.

Ask for a relevant example, the decision made, the result or learning, and the person who would own the work.

  1. 01What measurable problem does this process create?
  2. 02How frequent and costly are exceptions?
  3. 03Which decisions can be deterministic?
  4. 04What data is sensitive or unreliable?
  5. 05What error could harm a person, customer or record?
  6. 06Where must a human approve, override or investigate?
  7. 07How will quality, latency, cost and drift be monitored?
  8. 08What manual fallback operates during failure?
[ Risk ]// 02

Make failure visible before signature.

RiskEarly warningControl
Wrong process selectedLow volume or valuePortfolio scoring
Automating wasteBroken process preservedSimplify first
Unsafe autonomyNo human gateRisk-tiered approvals
Weak dataManual correction dominatesData-readiness work
No operating ownerPilot orphanedNamed product owner
[ Value case ]// 03

Measure outcomes—not activity.

01Annual addressable hoursBaseline ________
90-day target ________
02Cycle-time reductionBaseline ________
90-day target ________
03Straight-through rateBaseline ________
90-day target ________
04Exception and error rateBaseline ________
90-day target ________
05Risk-adjusted valueBaseline ________
90-day target ________
06Run cost per caseBaseline ________
90-day target ________
[ First 90 days ]// 04

Move from evidence to operating rhythm.

01

Days 1–30

Inventory and score candidate workflows

Exit evidenceBaseline, owners, approved requirements and risks

02

Days 31–60

Validate data, prototype bounded pilot and evaluation

Exit evidenceWorking outputs, evidence and decision record

03

Days 61–90

Approve scale, operating controls, monitoring and ownership

Exit evidenceMeasured result, operating owner and next backlog

[ Reference desk ]// 05

Speak the same language.

TermPlain-language meaning
DeterministicSame valid input produces a defined result.
ProbabilisticOutput varies and requires evaluation.
Human gateRequired approval before consequential action.
FallbackSafe manual or alternate route.
ObservabilityEvidence showing workflow behaviour.
DriftPerformance change over time.

[ Playbook in hand? ]

See where you stand.
Take the readiness assessment.