Approach
A clear path from AI experiments to everyday operations
Every engagement follows the same five steps. Each one ends with something you keep and spells out what I need from your team.
01
01Assess
We start with the three business questions, then take stock of what you've already tried: The licenses, the prompts people built themselves, the pilot that stalled. We talk to the people doing the work and record today's numbers as the baseline.
At the end of this step: A written picture of what's working, what's stalled, and what to stop, plus the metrics we'll hold the work to.
Your part
About an hour with leadership, plus access to the pilots.
02
02Envision
With the real picture in hand, we set direction. Where does AI change how the business runs in 12 to 18 months? Which workflows get you there? We survey every candidate and map the top two in depth, then rank them by value and readiness.
At the end of this step: A vision leadership can defend and a ranked roadmap.
Your part
One leadership working session.
03
03Build
We take the top workflow and build the smallest version that works, with your team, on your real work. Nobody sits through separate training. They learn by building. Steps that exist out of habit get cut before anything gets automated.
At the end of this step: One workflow running in everyday use.
Your part
One named owner, 2 hours a week, protected on a calendar.
04
04Govern and manage change
Two pages of ground rules: What AI can touch, what it can't, where people review, how data flows, and what to do when something goes wrong. Then we plan the change itself: Who needs to know what and when, who champions it on each team, how people learn on real work, and how the new workflow replaces the old one instead of running beside it. We measure against the baseline from step one throughout, at the process level and never to grade individuals.
At the end of this step: Ground rules and a change plan your team helped write, plus a before and after number for each metric.
Your part
Sign-off and help building out the ground rules and change plan.
05
05Expand(optional)
For teams that want to keep going: The next workflows on the roadmap, a vision that gets refreshed as you learn, and ground rules that grow with you.
At the end of this step: AI across teams, not just in one corner.
Your part
A standing check-in, as often as it's useful.
What stays with you
Everything I build is yours and runs without me.
- ✓Plain-English documentation
- ✓Maps of how each workflow runs
- ✓Training for the owner and the team
- ✓Accounts and admin access in your name
- ✓A handover session
What makes this work
Three things, agreed before we start:
- 1
A workflow that matters: Not a science project.
- 2
One named owner: Without an owner, the workflow reverts within a month.
- 3
Two protected hours a week: The most ignored requirement and the one that decides whether any of this sticks.