Automate first the task that happens often, follows clear rules, costs you money when it's late and currently depends on someone remembering to do it. In most service businesses that's the journey of a new enquiry: the first reply, the follow-up and the booking. Score your candidates with the test below, build the winner properly, and only then move to the next one.
Why "automate everything" projects stall
Large automation projects rarely fail on technology. They fail because the process was never written down, so nobody agrees what the automation should do. Or because five tools need connecting before anything works, so nothing goes live for months. Or because the team doesn't trust the result and keeps doing it by hand.
One journey at a time avoids all three. It's small enough to finish, visible enough that the team notices the difference, and it gives you one clean record to build the next automation on.
Score your candidates: a five-question test
List every repetitive task your team mentions when you ask "what do you do by hand that annoys you?". Then score each one from 0 to 2 on these five questions.
| Question | 0 | 1 | 2 |
|---|---|---|---|
| How often does it happen? | Monthly or less | Weekly | Daily or more |
| How long does it take each time? | Under 2 minutes | 2 to 15 minutes | Over 15 minutes |
| What does a delay or mistake cost? | Nothing much | Annoyance or rework | Lost customers or money |
| Are the rules clear? | Judgement every time | Mostly clear, some exceptions | Same steps every time |
| Does it rely on someone remembering? | No, it's already triggered | Sometimes | Yes, entirely |
The top scorer is your first project. A score of 8 or more is usually worth automating now. Below 5, leave it alone for the time being.
Watch the fourth question closely. A task that needs judgement every time is a poor first automation, however much time it takes. It's a candidate for AI help later, with a person approving the result, but not for step one.
A worked example
Example figures, not client data. A physiotherapy clinic lists four candidates:
| Task | Often | Time | Cost of delay | Clear rules | Relies on memory | Score |
|---|---|---|---|---|---|---|
| Replying to new enquiries | 2 | 1 | 2 | 2 | 2 | 9 |
| Appointment reminders | 2 | 0 | 2 | 2 | 2 | 8 |
| Weekly revenue report | 1 | 2 | 1 | 2 | 1 | 7 |
| Handling complaints | 1 | 2 | 2 | 0 | 1 | 6 |
Enquiries win, reminders come next, and the weekly report follows. Complaints score well on cost but badly on rules, which is the right signal: complaints need a person, and automation's job there is only to route them quickly to the right one.
The usual order for service businesses
Your scores decide, but most owner-led service businesses end up with a similar sequence. Each step makes the next one easier because the data already sits in one place.
- New enquiries. Reply within minutes, answer common questions and book. See speed-to-lead for why this goes first.
- Follow-up. Enquiries that don't book get a short, useful sequence that stops when they book, reply or opt out.
- Bookings. Confirmations, reminders and rebooking prompts, which also cut no-shows. We covered the detail in why show rates drop.
- Handoffs and admin. Passing details from sales to delivery, updating the CRM and filing documents without retyping.
- Reporting. The weekly numbers produced automatically, from the records the first four steps now keep clean.
Notice that reporting comes last. Automating a report built on messy data just produces a wrong answer faster.
What to keep a person on
Automation should handle the predictable work and prepare the rest. Keep a person on:
- decisions involving money or legal commitments
- complaints and upset customers
- messages sent in your name that aren't routine
- regulated advice, such as medical, legal or financial
A good system routes these to the right person quickly, with the context attached, rather than trying to answer them. We list the decisions we never automate in where people must stay in an AI workflow.
Off-the-shelf tools or a custom build?
For a first automation, start with the tools you already pay for. Most CRMs and booking systems include reminders and basic sequences. Connector tools such as Zapier can join the gaps.
Know how connector costs grow before you rely on them. On Zapier, each successful action step counts as a task, while triggers and filters don't, and at your plan limit new runs are held until you pay for more. A five-step automation running on 40 enquiries a day uses 200 tasks a day. We compare the options in Zapier vs custom automation.
A custom build makes sense when the journey crosses several systems, needs rules the tools can't express, or when connector costs and breakages start costing more than the build. Our 14-day sprints are priced from £5,000 to £20,000 and are built in your own accounts, so you own the code and the data. If your tools already cover the journey, you don't need us for this step.
When not to automate yet
Hold off if the process still changes week to week, if nobody can describe the steps the same way twice, or if an existing tool already does it well. In those cases, write the process down and run it by hand for a month first. You'll automate something that works, rather than locking in something that doesn't.
Do this week
Ask each person on your team for the three tasks they'd most like to stop doing by hand. Score every task with the table above, in one sitting, and pick the top one. Then write its steps from start to finish and mark every point where someone waits, chases or retypes something. That list is the brief for your first automation.
If you'd like a second opinion on the scores, book a call and we'll go through your list with you.
