A rollout ships features on a calendar. A readiness path advances only when a gate proves it is safe to. The first 12–18 months prove Finance can run governed AI-native workflows across cash, spend, and trust – while building reusable architecture, data, control, evidence, and benefits-validation capability.
The question is never simply “what’s next.” It is “what has earned the right to be next.” Every advance below sits behind a gate that must pass first.
01 · THE CRITICAL PATH
Readiness, sequenced – each step earns the next.
The path is causal, not calendar-driven. Nothing here is a feature to ship; each step is a precondition for the one below it.
01
Adopt service classes, maturity gates, and first-wave MVA
The governing decision: agree how work is classified and what each maturity level requires, before anything is built.
02
Approve runtime, identity, tool, connector, and data allowed-use patterns
The architecture patterns every later workflow will inherit – decided once, up front.
03
Validate first-wave ownership and data access
Confirm who owns each workflow and that the data it needs is reachable and permissioned.
04
Create first-wave data products and metric definitions
Define DSO, spend, revenue-evidence, and benefits metrics on certified, source-linked data.
05
Create the calculation registry and first-wave calculations
Governed Finance math lives in registered, versioned services – never in an agent.
06
Establish evidence, source-linking, and logging
Every output carries lineage and every action is logged, from the first pilot forward.
07
Establish workflow / action tracking and the support model
Work becomes managed and traceable, with a support path before production, not after.
08
Run bounded pilotsGATE
First live workflows, deliberately narrow – cash, spend, and trust testbeds only.
The gates are the roadmap. The phases just wait on them.
Six windows over 12–18 months – but the windows are not the story. Between each sits a gate: a named set of conditions that must pass before anything advances. Nothing flows past an unpassed gate.
READINESS
decisions before build
0–3 MONTHS
foundation & pilot readiness
3–6 MONTHS
bounded pilots & architecture proof
6–12 MONTHS
productionize where gates pass
12–18 MONTHS
scale & gated expansion
LATER
conditional only
Before Pilot
runtime – identity – tools – connectors – allowed data use
platform strategy – cost model – scaled operations
Each blue gate holds the track until its conditions are met – readiness, proven, not scheduled.
↔ scroll the track
03 · THE SEVEN WORKSTREAMS
Seven lanes, one timeline, every lane through every gate.
The work runs in seven parallel streams. Each advances through the same phases in lockstep – none races ahead of the gates. Read a lane left-to-right to follow one workstream through time, or a column top-to-bottom to see everything a single phase demands.
Workstream
READINESS
0–3 MO
3–6 MO
6–12 MO
12–18 MO
LATER
Architecture foundations
adopt service classes, maturity gates, first-wave MVA
approve runtime, identity, tool, connector, data allowed-use & trust-boundary patterns
stand up pilot components and logging
harden production architecture for selected workflows
Each lane advances left-to-right through the same phases · italic = later / conditional · none races ahead of the gates
04 · THE PROVING GROUND
Three testbeds. Not the full vision – the proof of it.
The first wave is deliberately narrow: three disciplines chosen because each has a clear owner, reachable data, and a measurable outcome. They prove the pattern; they are not the destination.
CASH
DSO & collections
Cash risk surfaced as it forms, routed to an owner, validated against cash that actually arrived. The clearest owner, the most reachable data.
GATE – productionize toward Level 3 only where identity, evidence, and control gates pass.
SPEND
Vendor & software spend
Renewal overpayment, under-utilization, and drift surfaced before lock-in, routed to the budget owner who can act.
GATE – productionize toward Level 3 only where ownership and data-access gates pass.
TRUST
Revenue controls evidence
Control evidence assembled continuously, source-linked, audit-ready by construction – the trust discipline of the three.