Done-for-you builds
One workflow, built into your stack, handed over with a runbook.
Service · AI Automation Roadmap
Find the one workflow worth automating first.
Before anyone builds anything, I sit with the people doing the work and map every hand-off. You get a ranked list of what AI can take over, what it shouldn’t, and the one build that pays for itself.
LengthOne week
FormatInterviews, shadowing, a written map
You end withA ranked roadmap and a no-go list
Next stepBuild it with me, or hand it to your team
This is for you if
- Your team has an AI wishlist and no idea which item to start with.
- Someone is retyping the same information into two or three systems every day.
- You tried a tool or a pilot and it never made it past the demo.
- You want a straight answer, including “not yet”.
It isn’t, if
- You’ve already decided what to build and only need hands.
- You want a strategy deck for the board rather than a working plan.
- Nobody who does the work day to day can spare an hour to talk.
How it runs
What happens, in order.
01
Kick-off
One call to agree which team and which process we’re looking at, and who I need to talk to.
02
Map the work
I shadow and interview the people doing it. Every hand-off, every copy-paste, every place something waits on a person who already knows the answer.
03
Score the candidates
Each workflow gets scored on volume, risk, data quality and how badly it hurts today. Some land on the no-go list, in writing, with the reason.
04
Walk through the roadmap
A working session where we go through the map together and pick the first build. You leave knowing exactly what it would take.
What you get
You keep all of it.
Everything below is yours when we finish, whether or not we work together again.
- A workflow map: every step, hand-off and system involved
- A scored, ranked list of automation candidates
- A written no-go list, with reasons
- A one-page brief for the first build: scope, systems, risks, how we’d measure it
- A recording of the walkthrough session
Questions
The ones people ask first.
Do I have to hire you for the build afterwards?
No. The roadmap is written so your own team or another builder can pick it up. Plenty of people take it in-house.
What if there’s nothing worth automating?
Then the roadmap says so, and explains why. That’s a useful answer too, and it’s cheaper to hear it now than after a build.
Which tools do you use?
Whatever fits your stack. I’d rather build into the systems your team already lives in than add another one.
How much does it cost?
It depends on the size of the team and how many processes we look at. We’ll cover it on the first call, before you commit to anything.
Other services
Managed
I keep it running and add the next workflow when the last one has earned it.
Start with the map.
Forty-five minutes to see whether a roadmap is worth doing. If it isn’t, I’ll tell you.