What should a small business automate first?
A five-part test for choosing a useful first workflow without automating confusion or creating a brittle chain of tools.
Choose a workflow, not a vague ambition
The loudest annoyance is not always the best first automation. A useful candidate is repeated often enough to learn from, stable enough to describe, and bounded enough that an exception can reach a person.
Begin by observing the real work—not the official process diagram. Note what starts the task, where information comes from, who makes a judgment, what gets copied, what waits, and how the next person knows it is their turn.
Use the five-part readiness test
Score each candidate from one to five across five dimensions. The score does not make the decision for you; it makes the tradeoffs visible.
- Repetition: does this happen often enough to matter and to test?
- Clarity: can the normal path and common exceptions be described?
- Input quality: is the required information available and reasonably consistent?
- Consequence: can mistakes be caught before they affect a customer, payment, or critical decision?
- Ownership: is one person accountable for reviewing and improving the workflow?
Automate the dependable part first
A first release can automate collection, preparation, or routing while leaving approval with a person. That often produces most of the benefit with less risk than trying to automate the entire chain.
Examples include preparing a draft reply without sending it, assembling a report without interpreting it, or routing an intake form while allowing a person to correct the category.
Know what better should look like
Define the evidence before launch: fewer missing fields, faster acknowledgement, less re-entry, clearer ownership, or fewer manual status checks. Measure the workflow, not the novelty of the tool.
If the automation creates more exceptions, confusion, or maintenance than it removes, narrow it or step back. A useful system is allowed to remain small.