Which tasks should a small business automate first?

Start with a task that happens every week, follows the same steps each time, and costs you something you can see when it goes wrong. In many small businesses that’s an enquiry waiting for a reply, an invoice that goes out days after the work was done, or a report someone puts together by hand every Monday. Keep first sales calls, apologies and anything about hiring with people.

Pick one task, not five. Our automation projects start with one process, and this is how we’d choose it.

Three questions that pick the first task

Take each task your team repeats and ask:

1. Does it happen at least once a week? A weekly task runs about 50 times a year, so the time it saves adds up, and within a month you can see whether the automation works. A yearly job like the stock count can be painful and still be a poor first pick: you’d wait a year to see it run, and by then the steps may have changed. Runs also build trust. A step stops needing a person’s OK only once its log shows a track record (more in our post on approval steps), and a track record takes runs.
2. Does it follow the same steps each time? Ask the person who does it to write the steps down. If they fit on a page and someone new could follow them, the task passes. If half the steps start with “it depends”, it doesn’t pass yet. Messy inputs are fine. Reading a free-text email or a supplier’s PDF is what we use AI for in a workflow, and anything it isn’t sure about goes to a person. What has to be settled is what happens next.
3. Does it cost something you can see when it goes wrong or runs late? You should be able to name the cost: a guest who booked somewhere else, a payment that came two weeks later, a Monday morning gone. If you can’t name it, you won’t be able to tell later whether the automation helped.

Three yeses make a first candidate. If several tasks pass, start with the one whose mistakes are cheapest to undo, so the first weeks carry little risk.

Three tasks that usually pass

Enquiries that wait for a reply

A restaurant gets booking requests by email, through its website and on WhatsApp. Someone checks the reservation book and writes back when they have a minute, which on a busy day can mean the next afternoon. By then the guest may have booked somewhere else.

The requests come in every day, get the same handling every time, and a lost booking is easy to see. In the example on our home page, the workflow checks for free tables, drafts a reply in the guest’s language and adds the booking to the reservation book. Dan only decides on groups larger than 10. Quote requests at a haulier or a travel agency have the same shape.

Invoices that go out late

Many small firms invoice at the end of the month from delivery notes or timesheets, so a job finished on the 3rd gets invoiced on the 30th. Payment terms usually count from the invoice, and so do the EU’s late payment rules: when a contract sets no payment date, interest is due 30 days after the client receives the invoice. Every day an invoice waits to be written pushes back the day you’re paid.

Invoicing passes all three questions. Jobs finish every week, the steps are fixed (job done, invoice drafted from the order or the timesheet, invoice sent), and late payments show in the bank balance. Once automated, the invoice is drafted the day a job is marked done. It moves money, so the draft waits for a person to approve it before it goes to the client.

Reports put together by hand

Every Monday someone exports last week’s sales from the online shop, the till and the accounting app, pastes them into a spreadsheet and sends the totals round. It happens every week, the steps are the same by definition, and the cost is plain: two hours a week comes to over 100 hours a year, and every number copied by hand can be copied wrong.

A report is often the safest first automation. It stays inside the business, so the person reading it catches a mistake before anything reaches a client or a supplier.

The work to keep with people

Some work passes all three questions and should still stay with a person. In each case below, a workflow can take over the admin around it.

• First sales calls. A new client is deciding whether to trust you, and you’re finding out what they actually need. The booking can run on its own: on our own site you pick a slot and the invitation goes out without anyone typing it. The call is with a person.
• Apologies. When an order goes wrong, the customer wants to hear from someone who can put it right with a refund, a replacement or a phone call. A workflow can spot the complaint in the inbox, pull up the order and flag it straight away. A person writes the reply, in their own words.
• Anything about hiring. Choosing who to hire is a judgement about a person, and EU law adds rules for AI used in it. The AI Act lists AI used “to analyse and filter job applications, and to evaluate candidates” as high-risk (Annex III, point 4), which brings extra duties for any business that uses it; our AI Act post has the details. Confirming that an application arrived and booking interview slots can be automated. The shortlist and the decision stay with people.

Try it on last week

1. List the tasks your team did last week. Calendars, the sent folder and the shared drive will jog your memory. Fifteen or twenty lines is plenty.
2. Run each one through the three questions: weekly, same steps, a cost you can name.
3. Cross out first sales calls, apologies and hiring decisions, but keep the admin around them on the list.
4. From what’s left, pick the task with the biggest cost you can name. If two are close, take the one whose mistakes are cheapest to undo.
5. Sit with the person who does it and write down every step as it happens today.

Then describe it in the automation plan. You get the steps back, with what runs on its own, where a person signs off and the time it could save.