Dashboard

What to Automate First in a Small Business

Rank tasks by how often they repeat and how cheaply a mistake undoes. Three popular candidates score well on time saved and should not go first.

Cecilia Iona
Cecilia Iona
Senior Editor, AI & Product
30 October 20261 min read

What to automate first in a small business is not the task that wastes the most time. It is the task that repeats often and whose mistakes are cheap to undo. Those two properties, frequency and reversibility, decide whether your first automation builds confidence or burns it, and the biggest time sink in the business usually fails the second test badly.

Score your candidates on both before you build anything. The ranking that comes out is frequently not the one you expected.

Score each task on frequency and reversibility

Take ten minutes and a list of the repetitive work in your business. For each item, two numbers.

Frequency. How many times a week does this happen? Not how long it takes, how often it occurs. A two-hour monthly task is a worse first candidate than a three-minute daily one, because the daily task gives you twenty times as much feedback in the first month. You will find the edge cases fast, and edge cases are what you are really trying to discover.

Reversibility. If the automation gets it wrong, how expensive is the recovery? Rate it on three levels:

  • Cheap: a draft nobody has seen yet, an internal note, a categorisation you can re-run. You fix it and nothing happened.

  • Awkward: something a colleague acted on, a report someone half-read, a tag that spread into other systems.

  • Expensive: anything a customer saw, anything involving money leaving the business, anything you have to apologise for.

Multiply high frequency by cheap reversibility and you have your first automation. The task should be something that happens most days and whose worst realistic failure costs you ten minutes.

What to automate first in most small businesses

Across small businesses the same shapes keep coming out on top, and they share a structure: the AI produces a draft, a human approves it, the human keeps the final say.

  • Drafting routine replies. Common customer questions where the answer is nearly the same every time, with you sending the message.

  • Categorising and tagging inbound work. Sorting enquiries, receipts or tickets into buckets. If a tag is wrong you change it.

  • Extracting data from documents. Pulling totals and dates from supplier invoices into a sheet. Frequent, tedious, and checkable at a glance.

  • First-pass summaries. Condensing a long thread or call so whoever picks it up next is not reading forty messages.

None of those are exciting, which is the point. A boring first automation that works every day for a month is how you build the judgement to attempt a harder one. If you are not sure whether the business is ready for any of this yet, the checklist in signs your small business is ready for AI automation comes before this exercise.

Three tasks that score well on time saved and should not go first

These come up constantly in planning conversations and all three are reversibility traps.

Replying to customers automatically. High frequency, genuinely time-consuming, and a failure is visible to the person whose opinion of you matters most. Automate the draft, not the send. Our guide to automating customer support with AI is about doing this in the right order rather than not at all.

Anything touching invoices or payments. The time saving is real and the failure mode is money moving incorrectly. Use AI to read and check invoices, not to pay them.

Posting to social accounts unattended. Cheap to set up, publicly embarrassing to get wrong, and a deleted post is not actually undone.

Run the first one for a month before adding a second

The temptation after a success is to automate three more things that week. Resist it, for a practical reason: you cannot tell which automation caused a problem when four of them changed at once, and small businesses do not have the observability to untangle it afterwards.

  1. Pick the highest-scoring task and automate only the draft or classification step.

  2. Keep a human approval step even where it feels unnecessary. You are buying information about failure rates.

  3. Write down what you expected to save and check it at four weeks. The method in measuring AI ROI for a small business is more useful here than a general sense that things feel faster.

  4. Only then remove the approval step, or add a second automation. Not both.

The governance part you cannot skip

Two things need writing down before the first automation touches customer data, and both are short.

First, an internal rule about what staff may and may not put into these tools. Our template for an AI use policy for a small business covers the practical version, which fits on a page.

Second, if you are in the UK or handling UK personal data, the ICO's guidance on AI and data protection is structured around the data protection principles and includes a chapter on accountability and governance, with material on what to consider in a data protection impact assessment. Note that the guidance dates from March 2023 and the ICO says it is under review, so treat it as the current starting point rather than the final word. The practical upshot for a small business is modest: know what personal data goes in, know where it goes, and be able to say so.

Neither of those is a reason to delay. They are a reason to pick a first automation whose data footprint you can describe in a sentence, which is another argument for starting with internal drafts rather than customer-facing sends. The wider landscape of what tends to work is in our AI for small business guide.

Common questions

Should I automate the task I hate most?

Only if it also scores well on frequency and reversibility. Hating a task is a good reason to want it gone and a poor guide to whether it is a safe place to start.

How long should the first automation take to set up?

If it takes more than a few days, the scope is too large for a first attempt. Narrow it until it is small, then widen once it works.

What if the automation is right 90 percent of the time?

That is fine for a reversible task with a human approving, and not fine for an irreversible one. The same accuracy is acceptable or unacceptable depending entirely on what happens in the other 10 percent.

How did this land?

About the author

Cecilia Iona
Cecilia Iona

Senior Editor, AI & Product

Cecilia leads the Swarmz editorial desk. She has spent a decade turning complex AI and product topics into writing people actually finish, and she owns the blog's quality bar.

Share

Get the next post in your inbox

One email a month. Product updates, engineering posts, and the best of Built with Swarmz.

I agree to receive emails about AI building tips and Swarmz product news. Unsubscribe any time.