Home › Guides

What to automate first in a small business

A simple way to choose your first automation: five tests, the usual best candidates, what to leave alone, and a two-week plan. About 7 minutes to read.

Ask ten people what a small business should automate first and you'll get ten answers, usually based on whatever tool they sell. A better answer is: it depends on your numbers. Still, the reasoning is the same in almost every business, and you can apply it in under an hour.

The five tests

Run each candidate task through these five questions. A good first automation passes all five.

1. Is it worth it?

The task should happen often, at least several times a week, and take real time each run. Work out runs per week × minutes per run ÷ 60. Anything under about 30 minutes a week is rarely worth building first, unless delays cost you money. A slow reply to an enquiry, for example, can lose the job.

2. Are the rules clear?

Can you write the steps on one page with no "it depends"? "If an invoice is 7+ days overdue and unpaid, send reminder A" is clear. "Reply to unhappy customers appropriately" is not. Judgement-heavy work isn't a good first project.

3. Are the inputs clean?

Good automations start from structured, digital data: a form, a calendar event, a row in your accounting system. If the inputs are handwritten notes, scanned PDFs or a spreadsheet everyone formats differently, fix that first. Or pick another task.

4. Is it safe to automate?

Ask what happens if it misfires. A duplicate internal notification is harmless. A wrong amount on a payment, an email to your whole customer list, or a leak of personal data is not. First automations should be easy to undo, low-stakes and not customer-facing in a risky way. Where customers are involved, check your anti-spam and privacy obligations.

5. Is someone ready to run it?

Every automation needs an owner who checks it, fixes it when an app changes, and switches it off if something goes wrong. If nobody will look at it for a month, it's not ready.

The usual best first candidates

In most service businesses, trades, clinics and studios, these tend to pass all five tests:

• Enquiry auto-reply and alert. The form arrives, the enquirer gets a helpful acknowledgement, and you get an instant alert and a logged lead. Low risk, frequent, and it speeds up replies.
• Appointment reminders. Calendar data is already structured, and fewer no-shows are often worth more than the time saved.
• Overdue invoice reminders. Clear rules and a direct link to cash flow. Read paid status straight from your accounting system so you never chase a paid invoice. Leave escalation to a human.
• Weekly numbers digest. Internal only, so it's very safe. It turns 30–60 minutes of copy-and-paste into a short email.
• Bills and receipts filing. Attachments go to one folder with a log, ready for your bookkeeper. Check first whether your accounting software already offers this.

What not to automate first

• Anything that pays money or changes bank, payroll or tax data.
• AI replies sent straight to customers. Use AI to draft, and have a person send.
• Bulk outbound email or cold outreach. The legal and deliverability risk is high, and it's easy to damage your domain's reputation.
• Processes that change every month or that only one person understands.
• Big multi-system projects such as a full CRM migration. Do those once you've built a couple of small wins.

A quick scoring method

If you have several candidates, give each a score from 1 to 3 on four things:

• Value (hours saved, or the cost of delays)
• Clarity of rules
• Input quality
• Safety (3 = very safe)

Add them up. Anything scoring 10–12 is a strong first candidate. Anything scoring 4–6 can wait. For a fuller version that estimates hours saved, cost, ROI and payback for each task, see our AI automation audit template guide.

A two-week plan for your first automation

1. Day 1: time the task for real over the next few runs, and write the rules on one page.
2. Day 2: tidy the inputs, for example consistent columns and date formats in the sheet.
3. Days 3–4: build it in your tool of choice. That might be n8n, Make, Zapier, or the automation features already in your CRM or accounting software. Send everything to yourself first.
4. Day 5: run it with real data but a human approval step.
5. Days 6–14: check the results daily, fix edge cases, and note the time you actually saved.
6. Day 14: decide whether to keep it, remove the approval step if it's safe, or roll it back. Then pick the next candidate.

Starting small matters more than starting with the "best" task. One working automation teaches you more about your processes and tools than a long wish list. If you want ready-made starting points, our guide to n8n workflows for small business covers nine common ones.