What Should a Small Business Automate First?
2026-11-10
Automate the task that happens often, follows clear steps and does little damage if it goes wrong. Enquiry handling, appointment reminders, invoice chasing and report assembly are common winners.
Score each candidate
List ten tasks your team grumbles about. For each, answer four questions.
- How often does it happen? Daily beats monthly.
- How long does it take each time? Minutes across dozens of repeats add up.
- Does it follow rules? If a new hire could do it from a checklist, a tool can.
- What if it goes wrong? An email reminder sent late is mild. A wrong payment is not.
Pick the task with high frequency, clear rules and low risk. Ignore anything that depends on one person's gut feel.
A hypothetical
Picture a physiotherapy clinic where reception copies new patient details from a web form into the booking system, then sends a confirmation. That job is frequent, rule-based and easy to check. An automation can pass the form data to the booking system (usually through an API) and send the confirmation, and staff only handle exceptions.
Before you build
- Write the current steps down. Many tasks are messier on paper than people assume, which is why business process mapping exists.
- Fix the process first if it is broken. Automating a bad process makes errors faster.
- Decide who checks the output and how errors are reported.
- Measure the baseline: how long it takes now.
Keep the first project small enough to finish. The goal is a working example your team trusts.
21Labs designs and builds these with workflow automation, starting with a free discovery.
Frequently asked questions
- Should the first automation be the biggest time sink?
- Only if it is also simple and low risk. A quick, visible win builds trust in the approach. Save the large, tangled process for after the team has seen one automation work.
