The short answer
Track your team’s repetitive tasks for one normal week, noting how often each happens, how long it takes and which tools it touches. Score each task on time spent, how rule-based it is and the cost of a mistake. Start with a frequent, rule-based task that a person checks anyway, set a measure of success, and automate that one before anything else.
- Copying enquiries into the CRM
- Chasing follow-ups
- Weekly numbers and reports
- Booking and reminders
- First drafts of routine emails
- Pricing and negotiation
- Complaints
- Anything sensitive
- Final say on what goes out
Why start with a list, not a tool
Many small teams know AI matters but have not had time to work out where it fits. The tools pile up unopened because nobody has matched them to a specific task. A week of honest notes about where the time goes fixes that.
How to score a task
| Question | Score 1 | Score 5 |
|---|---|---|
| How much time does it take each week? | Minutes | Hours |
| How rule-based is it? | Judgement every time | Same steps every time |
| How low is the cost of a mistake? | Costly or public | Easily caught and fixed |
Add the three scores. The highest totals are your first candidates.
What usually comes out on top
Moving information between tools, chasing follow-ups, weekly reporting and booking or reminders. They are frequent, follow clear steps, and someone checks them anyway, which makes them safe places to start.
Step by step
- 01
Pick a normal week
Avoid holidays and launches. You want the work that repeats, not the one-offs.
- 02
Log every repetitive task
Each person notes tasks they did more than once: what it was, how long it took, and which tools they used. Rough numbers are fine.
- 03
Add up the weekly hours
Multiply time per task by how often it happens, across everyone who does it. The total is often bigger than anyone expected.
- 04
Score each task
Rate time spent, how rule-based it is (does it follow clear steps?), and what a mistake would cost. High time, high rules, low risk scores best.
- 05
Look for copy-paste between tools
Tasks that move information from one system to another, such as inbox to CRM or spreadsheet to report, are usually the easiest wins.
- 06
Choose one first project
Pick the top-scoring task that a person checks anyway. One working automation beats five half-built ones.
- 07
Set a measure of success
Decide before you start: hours saved per week, faster replies, fewer errors. Write down today’s figure so you can compare.
- 08
Review after a month
Check the measure. Keep it, fix it or stop it, then move to the next task on the list.
Common mistakes
- Monday report, built by handRule-based, done every weekStart here
- Enquiries copied into the CRMRepetitive, low riskGood fit
- Client complaintsNeeds judgement every timeKeep human
- Supplier invoicesProcess differs each timeTidy first
- Starting with the most exciting idea instead of the most time-consuming task.
- Automating a messy process before tidying it up.
- Picking something where one mistake would be costly or public.
- No baseline, so nobody can tell whether it helped.
- Trying to automate several things at once.
Questions
What should a small business automate first?
A task that happens often, follows clear steps, takes real time each week and is checked by a person anyway. Moving information between tools, follow-ups and weekly reporting are common first choices.
How do I know if a task can be automated?
If you could write the steps down for a new starter and they would get it right most of the time, it is a good candidate. If it needs judgement every time, keep it with a person and automate the preparation around it.
How much time can automation save?
It depends entirely on your tasks. That is why the one-week log matters: it gives you your own numbers instead of someone else’s.
Do I need a developer to automate tasks?
Not always. Simple automations can be set up in tools you already use. Work that spans several systems or needs to be reliable every day is usually worth having built and looked after.