What to Automate First in Your Business (A Simple 3-Question Test)

Most business owners know they should automate something. The hard part is knowing what to automate first. Start with the wrong thing and you spend money on a clever system nobody uses. Start with the right thing and your team feels the difference in the first week.

After years of building business software and automation, I use one simple test to pick the first task. This guide walks you through it, with examples, so you can apply it to your own business today.

The 3-question test for your first automation

Look at the tasks your team does every week and ask three questions about each one:

→ Is it daily? A task that happens every day pays back far faster than one that happens once a month.

→ Is it repetitive? The same steps, in the same order, every time. If a person does it on autopilot, a system can do it too.

→ Is it rule-based? Clear rules ("if the invoice is 7 days late, send a reminder") are easy to automate. Tasks that need judgement ("decide if this customer deserves a discount") are not.

The best first automation scores yes on all three. If a task only scores two, keep it on your list for later.

5 tasks that usually pass the test

Every business is different, but these five come up again and again.

1. Copying WhatsApp or email orders into a spreadsheet

Someone reads each message, then types the customer, product and quantity into a sheet or system. It happens many times a day, it's always the same steps, and the rules are clear. An automated flow can capture the details from the conversation and create the order or lead for you. I explain the full setup in how a WhatsApp lead reaches your CRM.

2. Sending the same reminders by hand

Appointment reminders, payment reminders, "your order is ready" messages. Your team sends them one by one, often from personal phones. A scheduled reminder with the right template does it on time, every time, and nobody forgets the Friday batch.

3. Building the Monday report

Someone spends a morning pulling numbers from three places into one report. If the data already lives in your systems, the report can build itself and land in your inbox before you start work.

4. Chasing unpaid invoices

Most late payments aren't refusals. They're forgotten. A polite reminder at 3, 7 and 14 days, stopped automatically when the payment arrives, recovers money without awkward calls.

5. Re-typing data between two tools

Sales in one system, stock in another, accounts in a third, and a person copying numbers between them. Connecting the tools so data flows once removes the typing and the mistakes. If your business runs on many separate files, one system for stock, sales and accounts is often the bigger win.

What not to automate first

Some tasks look attractive but make a poor first project:

→ Anything that needs judgement or a relationship. Pricing a custom job, handling a complaint, closing a big deal. Automate the steps around them, not the decision.

→ Processes that change every week. Automate a process once it's stable, or you'll rebuild the automation every month.

→ Rare tasks. A task you do twice a year rarely pays back the effort.

→ "Everything at once" projects. Big-bang automation is slow, expensive and risky. One small, working automation teaches you more than a year of planning.

How to measure if it worked

Before you automate, write down two numbers for the task: how long it takes per week and how often it goes wrong (missed reminders, typing mistakes, late reports). After a month, check the same numbers. If the time is down and the mistakes are down, automate the next task on your list. This is the same approach I describe in why leads go cold after hours: start small, measure, then grow.

Build, buy or connect?

For your first automation, you often don't need custom software. Many tools you already pay for have automation features. Custom work makes sense when your process doesn't fit those tools, when data has to move between systems that don't talk to each other, or when per-user fees keep climbing. If you're weighing a bigger build, answer the 7 questions before you build custom software first.

A worked example: a small distribution business

Picture a business that sells supplies to shops. Orders arrive by WhatsApp all day. Each evening, one staff member copies them into a spreadsheet, then into the accounting tool, then sends payment reminders by hand on Fridays.

Run the 3-question test:

→ Copying orders: daily, repetitive, rule-based. Yes, yes, yes.

→ Friday payment reminders: weekly, repetitive, rule-based. Two out of three.

→ Deciding credit terms for a new shop: occasional, needs judgement. No.

So the first automation is order capture: the order details from the chat go straight into one system, with the customer and products matched. The staff member who spent every evening typing now checks a list in ten minutes. Once that works, payment reminders are the obvious second step, because the order data is already in the system.

Notice what we didn't touch: credit decisions stay with a person. Automation handles the repetitive work around the decision, not the decision itself.

Frequently asked questions

How much does a first automation cost?

It depends on what has to connect. Many first automations use tools you already pay for and only need setup. Custom work costs more when data has to move between systems that don't talk to each other. Starting with one small, clearly defined task keeps the cost low and predictable.

Will automation replace my staff?

In small and growing businesses, it usually removes the boring part of someone's job, not the job. The time saved goes to customers, sales and the work that needs a person.

How long does it take to see results?

A well-chosen first automation often shows results within a few weeks: less typing, fewer missed reminders, faster replies. Measure the time spent before and after so you know for sure.

What if my process is messy?

Then the first step is to tidy it, not to automate it. Write the steps down, remove the ones that don't add value, and agree on the rules. Automating a messy process just makes the mess faster.

Your next step

Take 15 minutes this week. List every repetitive task your team does, score each one with the 3-question test, and circle the one that is daily, repetitive and rule-based. That's your first automation.

Not sure which task to start with, or how to automate it? Send me a message with your list. I'll tell you honestly which task I'd automate first, and whether you need new software at all. You can also see what I build on my AI automation page.