The Cheaper Way to Fix a Workflow
The cheapest automation is the one you do not need. Before quoting anything, we look for the three fixes that cost almost nothing and remove work permanently.
They are unglamorous and they are frequently enough.
Fix one: remove a step nobody needs
Ask why a document is printed before it is scanned. Why a note is written twice. Why a report is produced that nobody opens.
In most process maps we write, at least one step exists because of a decision made years ago by someone who has since left.
Fix two: make the form complete
Half the rework in professional practices comes from a form that does not ask for everything needed. The client supplies partial information, someone chases it, someone re-keys it.
Add three fields and the chasing stops. That is a better return than most software.
Fix three: stop asking twice
- Same information requested by two people in the same week
- Same document sent to the client twice
- Same question answered in four different emails
Every instance is a signal that the information is not stored where people look for it.
When you still need automation
After those three, if the work is still repetitive and volume-driven, automation earns its cost. It is worth knowing you have removed the free waste first, because otherwise you pay to automate a process you should have deleted.
The threshold question is covered on automation and digital employees.
Why we mention it
Because a practice that fixes the free things first gets more from the deployment and trusts it more. It also makes our work smaller, which is not the commercial instinct but is the correct one.
The agents that remain necessary are listed under specialised AI agents.
What we build
We build automation and digital employees after we have removed what should not be there. Ask us to look at the process first.
Start with one process
Tell us where the hours actually go and we will map it against what an agent can and cannot take. One process, measured before it is trusted. The first conversation is free and usually short.
Pingback: When Automation Makes a Practice Slower, Not Faster
3 November 2026