The first task you automate matters more than the tenth. It shows you how automation behaves in your business: where it saves time, where it needs supervision, and where your own process turns out to be less consistent than you assumed. Choose a first task that teaches that lesson cheaply.
Three rules for choosing what to automate
Rule 1
Automate work that recurs.
A task you handle daily or weekly repays the effort of building around it. One you handle a few times a year rarely does.
Rule 2
Automate only what has a settled rule.
If two people on your team would handle the same case differently, the process needs a decision before it needs software. A system can be no more consistent than the procedure it copies.
Rule 3
Match the autonomy to the cost of a mistake.
A late reminder is a nuisance. A wrong answer on a medical, legal or safety matter can harm someone. The more a mistake costs, the more a person stays involved, and the more qualified that person needs to be.
Applied in order, the rules form a short decision path.
The path never asks whether the technology can do the task. Nearly anything can be automated. The useful question is whether it should be, and how much to hand over.
How much to hand over
Autonomy is not all or nothing. For each task, choose one of three levels:
- Assist. The system prepares the work, such as a draft reply or a sorted list, and a person does the rest.
- Approve. The system drafts the action and queues it. A person approves it before it goes out.
- Automatic. The system acts on its own, inside written limits, and keeps a log of what it did.
For a first project, start at assist or approve. Move a task up a level only after you have watched it work and trust the rule behind it.
Where a mistake would be serious, never go beyond approve. Either keep the task manual, or let the system prepare the work while a qualified person signs off every item before anything leaves. A sign-off only counts if the person reads what they are approving. An approval nobody reads is not a control.
Where to start
These tasks tend to satisfy all three rules: they recur, the rule can be written down, and a mistake is small and easy to correct.
- Acknowledging an enquiry. An immediate reply that confirms receipt and says what happens next.
- Reminders. Appointment, job and payment reminders sent at fixed intervals before the date.
- Follow-up prompts. A prompt to follow up a quote or a quiet lead after a set number of days, with a person approving the message.
- Inbox sorting. Labelling messages and routing them to the right person.
- Re-keying between tools. Moving a form entry into a spreadsheet, calendar or accounting package without retyping it.
- Weekly figures. Counting enquiries, bookings or quotes sent, from data you already hold.
- First drafts. Quotes or replies drafted from your own notes and templates, then checked by a person.
What stays with a person
- Anything with a safety, legal, regulatory or clinical consequence. Keep it manual, or limit the system to preparing work that a qualified person signs off item by item. If you are unsure whether a task belongs in this group, ask someone qualified before you automate it.
- Complaints and upset customers. They call for judgment and some empathy, and a stock reply usually makes matters worse.
- Price exceptions, negotiation, hiring and dismissal.
- Work you do rarely. The setup costs more than the task does.
- Processes you cannot yet describe. Map them first, then decide.
- Work whose outcome you cannot measure. Without a measure, you cannot tell whether the change helped.
Test your own list
List the tasks you are weighing and put each one through the three rules.
A small service business lists four tasks.
| Task | Recurs? | Rule settled? | Cost of a mistake | Verdict |
|---|---|---|---|---|
| Acknowledge a new enquiry | Daily | Yes | Low | Automate |
| Follow up a quote | Weekly | Mostly | Moderate | Draft it, a person approves |
| Handle a complaint | Sometimes | No | High | Keep manual |
| Price an unusual job | Rarely | No | High | Keep manual |
| Prepare a reply to a regulator’s notice | Occasionally | Mostly | High | Draft only, a qualified person signs off |
The first row is the safest. Starting there shows you how automation behaves in your business before you attempt the second.
Understand the process first
Before automating anything, draw the task as it actually runs and ask which steps could go. Tasks that look worth automating often contain a step with no reason to exist. Mapping is a team exercise: everyone who touches the process should take part, because each person sees steps the others do not. Our guide to business process mapping covers the method, with a worked example and a one-page template.
Decide how you will check it
Settle the checks before you build, not after. There are two, and they answer different questions.
Verification asks whether the automation does what you specified. Test it on real examples before it touches a customer, then read its log through the first weeks. Was the message sent at the right time, to the right person, with the right content? Name the person who reads the log, and the date they will do it.
Validation asks whether the automation is doing any good. Pick one figure before you begin: the time a new enquiry waits for a first reply, the share of quotes that receive a follow-up, or the hours a week the task consumes. Record it now and compare it after a few weeks. If it has not moved, the automation was not the remedy, and that is worth knowing before you build a second one.
Decide, too, what counts as wrong and how to switch the automation off. A system you cannot stop quickly is a liability.
When the choice is not obvious
A first task can be automated with tools you already own. Seek advice when a task spans several systems, when you cannot tell which level (assist, approve or automatic) is safe, or when the list is long and no candidate stands out. The free Revenue Leak Report is one way to get an outside view without committing to anything, and the automations page explains how we work.
