Advisory: finding what is worth automating, before the first line of code
We work out what is worth automating before anything gets built
You find out what not to build, not just what to build
The most expensive automations are the ones built flawlessly for a process that should not have existed.
What you get
A clear order of work
A list of your processes, ordered by what each costs you today and how hard it is to change.
Numbers you can check
Estimates come with how they were measured. Where we cannot measure something, we say so.
What to leave alone
The processes where automating costs more than it saves. There are more of them than you expect.
A plan that does not bind you
The output is yours. You can implement it with us, with someone else, or with your own team.
How it goes
Week 1 — we watch
We sit with the people doing the work and look at what they actually do, not what the procedure says they do.
Week 2 — we measure
We put numbers on volumes, times and errors. Where the data does not exist, we say so rather than estimate prettily.
Week 3 — we prioritise
Each candidate gets a current cost, an implementation effort and a risk. Then we put them in order.
Week 4 — we hand over the plan
You get the document, we walk it through together and answer questions. No sales pitch at the end.
What you own
- Access to the people doing the work
- Whatever data exists, however messy
- The final call on priorities
What we own
- The observation and measurement
- The cost and effort estimates
- The final document and walking you through it
How it is priced
Fixed price per engagement, set by the number of processes assessed
Related services
Frequently asked questions
- What does it cost?
- A fixed price, agreed before we start, based on how many processes we assess. No hourly billing and no surprises at the end.
- Do we have to build with you afterwards?
- No. Roughly a third of clients implement with their own team or another supplier. The document is written to be usable by anyone.
- What will you tell us not to do?
- Usually: processes that change monthly, flows with too little volume to be worth it, and anything hinging on a human judgement nobody can write down as a rule.
- How much of our time does it take?
- Around four hours a week, spread across the people who actually do the work. We do not ask for day-long workshops.
- What if you find nothing worth automating?
- We tell you, and we stop. It has happened. An honest report saying "not yet" is cheaper than a project that fails in month four.