What should a small business automate first?
By Aaron Melton,
Automate the process your team repeats most often with the least judgment involved: the one where the steps are the same every time and the only variable is who does the typing. Measure how many hours it consumes each week before you build anything, and skip anything that does not clear a payback you can state in months.
Why the first choice matters more than the first build
Most automation projects that disappoint did not fail on the technology. They failed at selection. Someone picked the process that was most annoying, or the one the vendor demoed, or the one that sounded most like "AI", and it turned out to be rare, or full of exceptions, or dependent on a judgment call nobody could write down. The build was fine. The target was wrong.
The first automation also sets the tone for everything after it. If it pays back visibly within a few months, the second project is easy to approve. If it drags, the whole idea gets shelved.
The three tests
We apply three tests to every candidate process, in this order.
Frequency. How often does it happen? Daily beats weekly, weekly beats monthly. A task that takes an hour but happens twice a year is not worth a build. A task that takes six minutes and happens forty times a day is.
Judgment. Could you write the steps down so that a new hire could do them correctly on day one without asking a question? If yes, it is a candidate. If the honest answer is "it depends," find out what it depends on. Sometimes the dependency can be written down too. Sometimes it cannot, and that is a signal to automate around the judgment step rather than through it.
Cost of error. What happens when the process goes wrong today? If a mistake is caught quickly and cheaply, the automation can run with light supervision. If a mistake reaches a customer or a regulator, the automation needs a review step, and the payback calculation has to include it.
A process that scores well on all three is the first project. A process that scores well on two is a second project. A process that scores well on one is a conversation, not a build.
Measure before you build
Before we build anything, we want three numbers: how often the process runs, how long each run takes, and what an hour of the person doing it is worth to the business. Multiply those out and you have the monthly cost of doing nothing. Compare that to the cost of the build and you have a payback period.
We publish a free calculator that does exactly this arithmetic, with a sensitivity table so you can see what happens if your estimates are off by 20 percent in either direction. If the payback is under a year, the project is usually worth doing. If it is over a year, we say so and suggest a different first project.
What this looked like for one client
A regional electrical contractor asked us this exact question. We ran a readiness assessment: seven stakeholder interviews across four departments, a written report with a risk register, and a prioritized backlog. The process that ranked first was not the one anyone had pitched. It was time-tracking compliance: high frequency, low judgment, real cost of error. Leadership chose it at the read-out and moved straight into a paid implementation.
When you cannot tell
If you cannot rank your own processes with confidence, that is normal, and it is what our readiness assessment is for. It is a fixed-fee engagement that produces the ranked list, with the reasoning written down, whether or not you build with us afterwards.