← Blog

AI & Automation · 9 min read

AI for Small Business: What to Automate First (and What to Leave Alone)

A practical filter to pick the first thing to automate: seven good candidates, what to avoid, a 30-day pilot and the guardrails that keep it safe.

A small bakery owner at a counter looking at a laptop that shows a simple workflow diagram, with croissants and a notebook nearby in warm morning light
The first thing to automate is rarely the exciting one. It is the one that makes your Tuesday shorter.

Somewhere right now, a small business owner is watching a video titled "10 AI tools that will replace your whole team" while their actual team is waiting for an answer to a customer's email from Monday. The video is thrilling. The email is boring. And the email is where the money is.

This is the strange thing about artificial intelligence in a small business: the shiny part and the useful part rarely sit in the same place. The shiny part is a talking assistant that writes a poem about your invoice. The useful part is the unglamorous machine that sends the invoice reminder at 9 a.m. on day 31 so that you never again have to write "just checking in" with a dry smile.

This guide is about picking the first thing to automate, because the first choice matters more than the tool. Get it right and you get back hours, confidence and a team that thinks the new thing is useful. Get it wrong and you get a three-week saga that ends with the sentence "we tried AI once and it didn't work." We will cover a simple filter for choosing, the ladder you climb from checklists to AI agents, seven good first candidates, what to leave alone, a 30-day pilot and the guardrails that keep it safe. In the middle there is a tool to rank your own candidates.

Your business does not need a robot butler

Let me say it kindly: the goal is not to have AI. The goal is to have fewer hours spent on work that a machine can do as well as you can, so that you can spend those hours on work that only a person can do. Talking to a worried customer. Choosing a supplier. Inventing the thing you will sell next year.

That reframing helps because it changes the first question. Instead of "Which AI should I buy?" you ask "Which task do I hate, repeat and could write down in five lines?" The answer is almost always smaller and less exciting than you expect, and that is a good sign.

If you lead with the tool, you tend to bend your business around what the tool can do. If you lead with the task, you pick the tool that fits. This is the same order I use in Project Focus: clear goal first, owner second, tool third.

The 4R filter: repeat, rules, risk, relief

Here is the filter I use with owners. It has four questions, and it fits on a napkin. For each candidate task, ask:

  1. Repeat: how often does it happen? Daily and weekly tasks beat yearly ones. A task that happens twice a year is not worth the setup.
  2. Rules: how clear are the steps? If you can write the steps in five lines, a machine can follow them. If the answer is "it depends, I just know," keep it human for now.
  3. Risk: how bad is a mistake? A reminder that goes out a day late is an annoyance. A wrong quote sent to a big client is a problem. Start where mistakes are cheap.
  4. Relief: how much does it hurt? Count hours and also dread. The task that makes you sigh on Sunday night is a strong candidate.

The ideal first project scores high on repeat, high on rules, low on risk and high on relief. In plain words, it is the thing you do all the time, in the same way, where an error is cheap and your enthusiasm is low. That is why the first automation of a business is usually something like confirmation messages, not a strategy document.

The automation ladder

There is not one thing called "automation." There is a ladder with five rungs, and the secret is to climb it one rung at a time.

  • Rung 0: a checklist or a template. No technology at all. A written checklist and a saved reply already remove a surprising amount of chaos. Many "AI problems" are really "we never wrote it down" problems.
  • Rung 1: a rule. If this happens, do that. A form that triggers a confirmation. A reminder three days before an appointment. A tag when a payment arrives. It is reliable, cheap and boring, which is high praise.
  • Rung 2: an AI draft with a human review. The machine writes a first version of a reply, a summary or a report, and a person checks it before it goes out. This is the sweet spot for most small businesses today: big time savings and a human still in charge.
  • Rung 3: an AI agent with limits. The machine answers certain questions or handles certain tasks by itself, inside clear boundaries, and hands over to a person when it is unsure. I explain the sales version in AI agents for sales.
  • Rung 4: autonomous work. Systems that act on their own across many steps. Rare, risky and rarely the right first step for a small business.

Skipping rungs is how projects go wrong. A team that jumps from "nothing" to Rung 3 has to invent the rules, the checks and the safeguards at the same time, while customers are watching. A team that starts with a Rung 0 checklist, adds a Rung 1 rule and then upgrades the writing to a Rung 2 draft has built each layer on something that works.

Overhead view of a desk with a notebook, a pen and three sticky notes arranged in a row as if ranked
The first step of any automation is a ranked list on a very low-tech sticky note.

Seven good first candidates

These tasks tend to score well on the 4R filter in most small businesses. I describe them briefly, since I go deeper into several in seven workflows every small business should run on autopilot.

  1. The first reply to a new lead. People contact three businesses and often hire the first to answer. A quick, friendly, accurate first reply, drafted by a machine and checked by you, is often the most profitable hour you will ever save. Rung 1 (an instant acknowledgment) is a great start, and Rung 2 improves it.
  2. Appointment and booking reminders. Fewer no-shows from one message. Pure Rung 1.
  3. Meeting notes and action items. A machine can turn a recording or a rough note into a summary with who does what by when. Rung 2, with a quick human check, since a summary that invents a decision is worse than no summary.
  4. Invoice nudges. A polite sequence at day 1, day 7 and day 14 after the due date. Everybody hates writing these emails, and they get paid sooner when they are sent.
  5. The weekly report. If you collect the same three numbers every week, a machine can gather them and write two lines. See the weekly review for the numbers worth tracking.
  6. Answers to frequent questions. Opening hours, delivery areas, what is included. A chat assistant that answers from a short list of approved answers and says "let me get a person" for everything else is a safe Rung 3.
  7. Review requests. One friendly message after a happy customer, with a link. It takes ten seconds to automate and gives you years of benefit.

Here is an illustrative example, made up for the purpose. A bakery owner, call her Rosa, spends about five hours a week answering messages about pre-orders: "Do you have the 12-person cake on Saturday?" "What are the flavors?" "Can I pick it up at 4?" She writes the same four answers over and over. She starts with Rung 0: a one-page list of her real answers. Then Rung 1: a form for pre-orders that sends a confirmation. Then Rung 2: an assistant that drafts replies from her list, which she reviews in two minutes each morning. She did not "adopt AI." She stopped writing the same sentence forty times. The five hours become one.

What not to automate first

Some things deserve a human for a long time, or forever.

  • Anything you cannot write down in five lines. If you cannot explain the process to a new employee, a machine will not understand it either.
  • Decisions about people. Hiring, firing, performance and pay. The risk of a hidden bias or a plain error is too high.
  • Pricing and discounts that change your margin, until you have rules and limits written down.
  • Legal, medical and financial advice to customers. A machine can be confident and wrong at the same time, and "the computer said so" is not a defense.
  • Sensitive conversations. A customer who is angry, grieving or frightened wants a person.
  • Anything that handles private data before you have checked what the tool does with it. Read the terms, ask where data is stored and never paste information you would not want read aloud in public.

A good test for any candidate: "Would I be comfortable if the customer knew exactly how this was done?" If yes, proceed. If you feel a small cold shiver, go one rung lower.

A person at a desk reviewing a drafted email on a laptop with a pen in hand, about to correct it, with a coffee cup nearby
The machine writes the draft. You sign it, and the pen stays in your hand.

The 30-day pilot

Once you have chosen one task, run it as a small project. If you like structure, the one-page business case in the first part of my PMBOK series fits perfectly. In four weeks:

  • Week 1: map and measure. Write the steps in five lines. Record the baseline: how many minutes it takes, how often it happens, how many errors or complaints. Without a baseline you will never know whether it worked.
  • Week 2: build the simplest version. The simplest tool that does the job, with a human reviewing every output. Name one owner.
  • Week 3: run it and log the mistakes. Keep a short list of everything the machine got wrong, with the date. This is gold. It tells you what to fix and what to forbid.
  • Week 4: measure and decide. Compare with the baseline. Hours saved? Errors? Customer reactions? Then choose: keep, fix or drop. The benefits tracker is designed for that moment, and benefits realization explains the idea.

The decision to drop is as important as the decision to keep, which brings us to the guardrails.

Guardrails that keep it safe

  • A human is accountable for everything the machine sends out. A name, not "the system."
  • A stop rule, written in advance. For example: "If the mistake log shows more than three serious errors in the first month, we pause and review." Surveys of large companies suggest that few have such rules, which is one reason many pilots limp on without delivering value. I discuss one such survey in Gartner's finding that only 13% of CIOs see significant AI value.
  • A sample review every week. Read a handful of outputs. Look for the mistakes that sound right.
  • A privacy habit. Decide what information may go into a tool and what may not, and write it on one page.
  • Tell people. Customers do not mind a helpful automated message. They mind being deceived. And your team will cooperate far more if they know the goal is to free their time, not to replace them. The people side deserves its own attention, as I describe in change management and the people side of projects.

Rank your own candidates

Use the tool below. Replace the sample tasks with your own, rate how often each one repeats and how much it hurts, and see which one the score puts first. Then run it through the other two filters, rules and risk, before you choose.

Interactive tool

Rank your first automation

Loading the tool…

What to do this week

Write down every repetitive task you did last week on a single page. Circle the three that you dislike most. Score them with the 4R filter. Pick the winner, write the steps in five lines, record how long it takes today and decide which rung of the ladder you will start on. You will have done more in thirty minutes than most companies do in a quarter of "exploring AI."

I am writing a weekly series on exactly this, called AI for small business, step by step, starting with where AI helps and where it does not. The publishing calendar shows the dates. And if you would like a hand picking your first automation, or you want an honest second opinion, that is a conversation I enjoy: tell me about your business on the contact page.

What is the most boring task you would happily hand to a machine tomorrow? Tell me in the comments.

More tools. The weekly review and the decision log are free in the toolkit.

Frequently asked questions

What should a small business automate first?

Start with a task that repeats often, follows clear rules, costs little if it goes wrong and hurts to do by hand. Good first candidates are the first reply to a new lead, appointment reminders, meeting notes, invoice nudges, a weekly report, answers to frequent questions and review requests.

Do I need to know how to code to use AI in my business?

Not for most first projects. Many useful automations use forms, templates, scheduled messages and AI assistants that draft text for you to review. What you need is a clear description of the task and a person who owns the result.

Is it safe to use AI with customer information?

It depends on the tool and on the rules that apply to your business. Read the terms, find out where data is stored and whether it is used to train models, and decide in writing what information may go into a tool and what may not. When in doubt, leave personal or sensitive data out and ask a qualified professional.

How much time can a small business save with automation?

It varies a lot, so measure instead of guessing. Record how long the task takes today, run a 30-day pilot with a human review and compare. Small businesses often recover several hours a week on messages, reminders and reports, but the honest answer is in your own baseline.

Monthly newsletter

Everything new, once a month.

One email on the 1st of every month with everything new: articles, series parts, news, website updates, project results, where I am working and the business opportunities I am looking at. No spam.

One email a month, on the 1st. Leave any time.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Be the first to react.

Comments

Loading comments…

Leave a comment

Your name and email create a small profile that shows you are a real person. The email is never shown. The first time, I send you a confirmation link, and every comment is reviewed before it appears. Please keep it respectful and leave links out.

Keep reading

More ideas you may like.

Keep exploring

Related projects and services.

Next step

Let's find the project that moves your business.

Tell me where things are stuck. I will tell you which project I would start with.