Reimagine services with AI
Rebuild services from the ground up with AI inside them — live in weeks, better every time.
The idea
A pilot proves something is possible. It doesn't prove it will last.
Most transformation stalls the moment outside help leaves, because the pilot was the point and nobody built the method.
The hard part isn't the technology. It's deciding honestly what AI should own and what it shouldn't. Agents take the repeatable work. People keep judgement, care, accountability and the design of the service itself. Draw that line badly and you either automate the wrong things or automate nothing that matters.
Done well, the service isn't a faster version of the old one. It's a different thing entirely.
How I help
Discover.
Research with the people who use it. Where does it break? What's changed — in their world, the technology, the rules?
Redesign.
Specify what agents handle and what people handle. Configure shared capability rather than build bespoke. Rebuild the human roles around judgement.
Land.
Live, with an owner and a measure — and the people whose roles changed already moved, as part of the redesign rather than after it.
Run and watch.
The team goes lean. When the numbers move, the service goes back into discovery — triggered by data, not by the next restructure.
Alongside it I build the reusable version: templates, decision criteria, and design capability that moves between services rather than sitting idle inside each one. The test isn't the first service. It's whether the tenth is easier than the first.
What you get
- Reimagined services, live in weeks
Each with an owner, a measure, and the people affected already in their new roles.
- Service blueprints
Current state, where it breaks, the future state, and a specified split of what AI does and what people do.
- Redesigned roles
Real role definitions for the people in the new service, with skills mapped and the moves planned.
- A repeatable method
The playbook, templates and decision criteria your teams run without me — including how to choose what is next.
- A lifecycle with triggers
How and when a service goes back into redesign, based on its own numbers.
Why it matters
Reimagined services compound; pilots don't. Each conversion adds to the capability underneath, so the next costs less. And done properly, this moves people into new roles inside a better service rather than making them redundant to it.