How it works
Five steps, always in this order. We simplify before we automate, because automating a mess just gives you a faster mess.
The method
Look first.
Simplify.
Then automate.
The same five steps whether it is one process or a whole operation.
-
01
We watch the work happen
We sit with the people who do the job and follow it from start to finish. Not the procedure document. The real thing, workarounds included.
-
02
We find where the time goes
The re-typing, the chasing, the waiting for sign-off, the spreadsheet that exists because nobody trusts the system. We count the hours each one costs.
-
03
We take out what should not be there
Steps that exist for a customer who left years ago. Approvals nobody can explain. Removing them is free, and it makes the automation smaller and more reliable.
-
04
We build the automation
Connections between the tools you already pay for, workflows that run themselves, small internal tools, and AI where a task genuinely suits it.
-
05
We measure what disappeared
Hours a week. Days to turn something round. Mistakes that stopped happening. Agreed before we start, reported when we finish.
Why we simplify first
Most processes have grown, not been designed.
It is tempting to point software at a process exactly as it stands. But almost every process we see has grown by accretion: a step added for a customer who left years ago, an approval that exists because of one mistake in 2019, a spreadsheet that duplicates the system because someone did not trust it.
Taking those steps out costs nothing. It also makes the automation smaller, cheaper and far less likely to break.
- Fewer steps to automate means fewer places for it to fail
- The people doing the work agree the new version before anything is built
- Quick wins land in week one, not month six
What an engagement looks like
- weeks for a review
- 1 to 2
- weeks for a build sprint
- 2 to 6
- process at a time, done properly
- 1
- black boxes handed over
- 0
weeks for a review
weeks for a build sprint
process at a time, done properly
black boxes handed over
What to expect
Working with us.
A kick-off conversation, then a few hours from each person whose work we are watching, mostly just letting us watch. We try hard not to become another thing on the list.
Both. Watching the work is best done in person, so we come to you for that part. Build work is usually remote, with regular check-ins.
You do. Everything runs in accounts you own, with documentation your team can follow. We would rather you did not need us than be unable to leave.
Everything we build has monitoring, so you find out quickly. Fixing it is either yours to do with the documentation, or ours under an ongoing arrangement. Either way, nothing silently stops.
Start here
Want to know what is hiding in your process?
A free call is the quickest way to find out. Thirty minutes, no obligation, and an honest answer.