What actually happens, week by week.
No discovery theatre, no sixty-slide readout. Five stages, each with something you can look at when it ends.
-
01
Embed
I join the team properly: your channels, your tools, the meetings where the work is discussed and the ones where it is done. I ask a lot of questions in the first days and interrupt very little.
-
02
Map
I trace one process at a time from entry to completion, including the steps that only exist because of a workaround. You get the map, with volumes, handoffs and waiting points marked.
-
03
Rank together
We put the candidates in order by hours returned, how bad a wrong answer would be, and what breaks if the automation fails. Some candidates get marked "leave alone", and that is a real outcome.
-
04
Build in the open
I build the top candidates and get them in front of the people who do the work while it is still a draft. Short cycles, visible progress, no long silence followed by a reveal.
-
05
Hand over
Documentation, a named owner for each automation, a walkthrough for the team, and an honest list of what is still manual and why. Then I get out of the way.
Ways to work together
What I need from you
- Access to the tools the process runs on, at the level the team has
- One named point of contact who can unblock access and answer questions
- Permission to sit in the meetings where the work actually happens
- An owner on your side for each automation before it ships
- Honesty about the workarounds, which is where most of the value hides