Automation consulting
Process assessment and a sequenced automation roadmap with expected returns.
- Engagement
- Fixed-fee, one process family per engagement
- Typical timeline
- 2–3 weeks
- Starts with
- Two mornings beside the team that handles your highest-volume process.
Nobody can tell you how many hours a week go into re-typing the same information, so the case for fixing it never gets made. Ask three managers and you get three numbers, all of them guesses.
Knowing what to automate first, and why.
What we build
Concrete artefacts, handed over and documented.
A measured process map: each step timed, with the person doing it, the systems touched and the rate of rework
A ranked backlog scored on hours returned, errors removed and effort to build
A build-or-buy note per process, with the annual licence cost of the ready-made route written next to it
A decision record on where a no-code tool is sufficient and where it will hit its ceiling within a year
What changes
The hours are measured, so the business case stops being a debate between opinions
The first three candidates are specified well enough for anyone to quote them
Two or three processes get deleted rather than automated, which is always the cheapest result
How it runs
- Days 1–4
01Sit with the work
We time the steps as they are performed. The written process document is usually two years out of date.
- Week 2
02Score
Hours, error rate and effort attached to every candidate, then sorted in front of you and argued over once.
- Week 3
03Roadmap
A sequence with the first three specified, plus the ones we recommend removing instead of automating.
Chosen per project. Named here so you can see the shape of it.
- Miro
- n8n
- Make
- Google Sheets
Questions we get asked
Related work
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.