What Should a Small Business Automate First?

Most lists of things to automate hand you fifteen tasks and no way to choose between them. The better question is which of your tasks should go first, and that is a ranking problem you can solve in an afternoon. This guide gives a five-question score, a worked example, the usual first winners, and the boundaries (consent, human review) that the top-ranking lists leave out.

What should a small business automate first?

Automate the task that scores highest on five questions: it runs often, it follows rules you can write down, its data is already digital, a failure is cheap to fix, and one named person owns it. That points most small businesses to the same short list:

• acknowledging a new enquiry and alerting the owner;
• booking and reminding for appointments;
• invoice and payment reminders;
• copying form or ad-lead data into one CRM record;
• a weekly report assembled from numbers that already exist.

Where your business differs, your own log decides, not a generic list. The rest of this page shows how to build that log and score it.

Step 1: Count before you choose

For one week, write down every task you or your team repeats. Note three things for each: how many times it happened, roughly how long it took, and where the information came from and went. A shared spreadsheet is enough. Do not trust memory: people remember the annoying tasks, not the frequent ones.

Two warnings from this step. First, a task you do twice a month rarely repays the build, however irritating it is. Second, if the task changes every time (every customer is a special case), the rules cannot be written down and it is not a first candidate.

Step 2: Score each task on five questions

Give each task 0 to 3 on every question and add them up. The questions are ours, a working method rather than a published standard; adjust the weights to your business.

Question	0	3
Frequency: how often does it run?	A few times a month	Many times a day
Rules: can you write the steps as if/then?	Every case differs	Same steps nearly every time
Digital data: is the input already in a form, email, sheet or CRM?	Paper, phone calls, memory	Structured fields
Harm if it fails: what does a wrong run cost?	Money, trust or legal exposure	A mildly late reminder you can fix
Owner: does one person own the process and will notice a failure?	Nobody	A named person who checks it

A score of 12 to 15 is a first candidate. Eight to eleven can wait for a second round. Below eight, leave it alone or fix the process first.

A worked example

This is an illustration with made-up numbers, to show the arithmetic, not data from a real client. A small clinic logs four tasks in a week.

Task	Frequency	Rules	Digital data	Harm if it fails	Owner	Total
Reply to new web enquiries	3	2	3	2	3	13
Appointment reminders	3	3	3	2	2	13
Answering "is this treatment right for me?"	2	0	2	0	1	5
Monthly report to the owner	1	3	2	3	3	12

The two 13s go first. The clinical question scores 5 because it is a judgement call with real stakes: it stays with a person, though a form can collect the details beforehand. The report scores well on safety but runs once a month, so it waits.

What are the usual first wins?

These tasks score well for most small businesses, and each is a separate workflow, so you can start with one.

1. Lead capture and first reply. A form, ad lead or enquiry email creates one CRM record, sends an acknowledgement and alerts a person. Speed matters here: a 2011 Harvard Business Review study by Oldroyd, McElheran and Elkington, titled "The Short Life of Online Sales Leads", concluded that most companies do not respond nearly fast enough. The full figures sit behind the journal's paywall, so we do not quote them. Our guide to automating lead follow-up covers the whole sequence.
2. Booking and reminders. A booking link replaces the back-and-forth, and a reminder cuts no-shows. The rules are simple and the data is structured.
3. Invoice and payment reminders. Reminders before and after the due date are rule-based. Keep the dispute conversation human.
4. Data transfer between tools. Moving a field from one system to another by hand is the classic automation job: high frequency, no judgement.
5. Routine reporting. Pull numbers that already exist into one weekly message. Good for visibility; lower urgency.

At 1920 Agency this is how our own automation grew: daily SEO monitoring, ad performance checks and reports posted to team channels came first, because they were frequent, rule-based and easy to check. The same pattern applies to a business of any size.

What should you not automate first?

• A broken or undefined process. Automation runs a bad process faster. Write the steps by hand first, run them manually for two weeks, then automate.
• Complaints, refunds and sensitive conversations. These need judgement and empathy. Automate the gathering (a form that collects the order number and the issue) and the routing, not the answer.
• Decisions about people. In the EU and UK, Article 22 of the GDPR gives people the right not to be subject to a decision "based solely on automated processing, including profiling" where it has legal or similarly significant effects, and requires "human intervention" and the right to "contest the decision" where such decisions are allowed. A tool that automatically rejects applicants or refuses a service is a legal question first, not an efficiency one.
• Anything nobody will monitor. An unwatched automation fails silently. If no one checks it, it scores 0 on ownership.

What do the ranking lists leave out?

We read the pages that currently rank for this question on 2 November 2026. They are mostly vendor posts that list tasks. A short one gives three selection criteria with no method. A long vendor list covers fifteen tasks with a short "what not to automate" section. Another cites one statistic that it traces to a blog. None of the pages we read gives a way to rank your own tasks, and none says what breaks: failed runs, expired logins, nobody owning the workflow. None of them covers consent for automated messages or human review of automated decisions. Those are the three sections above and below that a first automation needs most.

What consent and rules apply when automation talks to customers?

If your first automation sends marketing texts, the rules arrive before the build does. In the US, the FCC's rules at 47 CFR 64.1200(a)(2) bar autodialed or prerecorded telemarketing calls unless made with "the prior express written consent of the called party", and the rule defines that as a signed written agreement that clearly authorizes the seller to deliver such messages to a stated number. A pre-ticked box does not give you that. Carriers also expect registration for business texting, which the GoHighLevel setup checklist walks through, and WhatsApp expects opt-in. UK, EU and WhatsApp rules differ; our consent section on lead follow-up sets them out. This is general information, not legal advice; check your own case with a qualified adviser.

Email acknowledgements to someone who just filled in your form are a lower-risk first step, because the person asked you to get in touch.

Which tool should you use?

The score picks the task; the task rarely needs an expensive tool. A one-trigger workflow runs on Zapier, Make or n8n, and bigger customer-facing flows suit an all-in-one platform such as GoHighLevel. Our comparison of n8n, Make and Zapier shows how each bills, and GoHighLevel vs HubSpot helps if you are choosing a CRM. Add AI last: draft a reply, summarize a call, classify an enquiry, with a person approving until the step has proved reliable.

How do you run the first automation without it going wrong?

1. Write the rule in one sentence. "When a form is submitted, create a contact, email the lead, and notify Sam." If it needs two paragraphs, split it.
2. Name an owner who will check it weekly.
3. Add failure alerts. Send errors to a channel someone reads. Most automation problems are quiet ones: an expired credential, a changed form field, a usage limit.
4. Test with real examples, including the odd ones: a blank field, a duplicate lead, a lead who replies at once.
5. Measure before and after. Record time per run, manual fixes and failed runs for a month, then decide whether to keep, change or expand.
6. Add the next one only when this one is stable.

Should you build it yourself or get help?

A single trigger with one or two actions is a fair do-it-yourself job. Help pays when there are several systems, consent rules, deduplication, stop conditions and an owner to find. If you want a second pair of eyes on your task log, our AI and automation service starts by mapping the job before quoting; see what an automation agency costs for market rates and what to ask before you buy.

Sources

• Oldroyd, McElheran and Elkington, "The Short Life of Online Sales Leads", Harvard Business Review, March 2011, https://hbr.org/2011/03/the-short-life-of-online-sales-leads (checked 2 November 2026; article text is paywalled, only the title, authors, date and teaser were verified)
• 47 CFR 64.1200, Delivery restrictions, https://www.law.cornell.edu/cfr/text/47/64.1200 (checked 2 November 2026)
• Regulation (EU) 2016/679 (GDPR), Article 22, https://gdpr-info.eu/art-22-gdpr/ (checked 2 November 2026)
• Competitor pages read for the gap analysis: Workast, "5 Things Every Small Business Should Automate"; GoDaddy, "15 tasks every small business should automate"; theophilusmorkporkpor.com, "What should a small business automate first?" (checked 2 November 2026)

Frequently asked questions

What should a small business automate first?

The task with the best score on frequency, clear rules, digital data and low harm if it fails. Common winners are acknowledging new enquiries, booking appointments, invoice reminders and copying form data into a CRM. Your own task log will beat any generic list.

How do I decide which process to automate?

Log repeated tasks for a week, then score each on how often it runs, how clear the rules are, whether the data is already digital, what a failure costs and whether someone owns it. Start with the highest total and run it for a month before adding another.

What should a small business not automate?

Do not automate a process that is still broken or undefined, complaints and refunds that need judgement, and decisions that significantly affect a person without a human able to review them. Automate the preparation around those tasks instead: gathering information, drafting, routing and reminders.

Do I need consent to automate texts or WhatsApp messages to customers?

Usually yes for marketing messages. US federal rules require prior express written consent for autodialed or prerecorded telemarketing calls, and carriers and WhatsApp have their own opt-in expectations. Collect consent on the form and store it with the contact record.

Is AI the first thing to automate with?

No. Start with rule-based steps that need no judgement: routing, reminders, record updates. Add AI to a step that is already running reliably, for example drafting a reply that a person approves.

How do I know the automation is working?

Measure the task before you start, then after a month. Track time per run, number of manual corrections and failed runs. If you cannot measure it, you cannot tell whether it helped.

Should I build it myself or hire someone?

A single trigger and one or two actions is a fair do-it-yourself job. Several systems, consent rules, error handling and ongoing ownership are where small-business builds usually fail silently, and where outside help earns its fee.