AI Workforce Transformation. A function rebuilt in 45 days.
A structured playbook for rebuilding a how a function operates around AI - the roles, the workflows, the decision.
TRANSFORMATION · PEOPLE + AGENTSWhat this engagement is
Tools don't transform functions; operating models do. This engagement takes one function and redesigns how its work actually flows: which tasks agents handle, which decisions people own, what gets measured, and how the team's week changes as a result.
The playbook was proven on our own operations first. Our delivery organization runs on the same platform we deploy for clients, with every specification reviewed and every release approved by a person, which is why 45 days is a schedule rather than a slogan: two weeks to map the function's work and decision rules, four weeks running the new model in shadow, then in production.
What you have on day 46 is a function that runs differently, with your people on judgment work, agents on volume work, and performance measured continuously from the Company Brain.
The numbers behind it
What ships
Verb mapping
The function's real decisions, captured from live work rather than from org charts.
Role redesign
Human attention repointed at exceptions, quality and improvement.
Agent rollout
Volume work moved to gated agents with confidence floors.
Shadow → production
The new model runs beside the old until the metrics say switch.
Enablement
Your team trained to author skills and tune policies themselves.
Outcome dashboard
The function's new metrics, live from the brain.
How the engagement runs
Six phases, forty-five days, one function rebuilt around AI.
Proof from production
We ran the playbook on ourselves first
“Before offering it to anyone, we rebuilt our own delivery, QA and support functions around AI in 45 days. Eight production agents now run our operations, with every exception owned by a named person.”
Questions teams ask
Is this a layoff program in disguise?
No. The playbook redistributes work: agents take the volume, people move up the checkpoint chain to judgment and exceptions. Your team designs the target model with us, which is why it holds after we leave.
Why 45 days?
Long enough to rewire one function properly, short enough to hold the organisation's attention. Scope discipline is the feature: one function, measured against its own baseline.
What if our function is too messy for AI?
Messiness is what the baseline phase is for, and the messiest functions gain the most. The undocumented workarounds we surface in week one usually become the first workflows worth automating.
What happens after day 45?
The function is yours, with its measurement cadence and its workflows feeding your intelligence layer. Some teams keep us alongside for the next function; nothing about the model requires it.
We stopped buying projects and started owning capabilities.
Pick your function. Own the intelligence behind it.
Discover one opportunity, engineer one capability and deliver one measurable outcome, then scale.