The first five things a small business should automate
Not the clever stuff. The five repetitive jobs that quietly eat a day a week in almost every small business — and what to do about each one.
Most small business owners don’t need more software. They need fewer things falling through the cracks. Automation has a reputation for being complicated, but the best starting points are usually the dull, repetitive jobs already eating up someone’s afternoon every week. Get those working quietly in the background and you free up real hours, not hypothetical ones. Here are the five we’d look at first with almost any SMB, in roughly the order we’d tackle them.
1. Acknowledge and route every enquiry the moment it arrives
What breaks without it: a form gets submitted, or an email lands, and it sits in an inbox until someone happens to check it. Nobody owns it. If the person who normally replies is out or on a job, the enquiry waits, and the person asking has often already contacted someone else by the time anyone responds.
What the automation actually does: the moment a form is submitted, the enquirer gets an instant message confirming it’s been received and setting a realistic expectation (“we reply within one working hour”). At the same time, the enquiry is routed to the right person based on simple rules — service, location, or value — and logged somewhere everyone can see it. If nobody actions it within an agreed window, a reminder goes to a manager.
Roughly how long to set up: half a day to a day, depending on how many rules you need and whether it’s plugging into an existing form tool or a CRM.
How you’d know it worked: the time between enquiry and first human reply drops sharply, and it stops depending on who’s at their desk. Nothing sits untouched overnight.
2. Chase quotes and invoices automatically
What breaks without it: a quote goes out and is never followed up because everyone assumes someone else will do it, or chasing feels awkward. Invoices go unpaid longer than they should, not because customers won’t pay, but because nobody reminded them. Cash flow suffers for a reason that has nothing to do with the quality of the work.
What the automation actually does: every quote sent is logged with a date. If it hasn’t been accepted within a set number of days, a polite follow-up goes out automatically. Invoices work the same way in reverse: a reminder before the due date, another the day it’s overdue, and a third a week later with a note to the owner if it’s still unpaid.
Roughly how long to set up: a day or two, mostly spent getting the wording right and connecting it to whatever you already use to send quotes and invoices.
How you’d know it worked: fewer quotes go cold, invoices get paid closer to their due date, and nobody’s keeping a spreadsheet of who to chase this week.
3. Send appointment reminders to cut no-shows
What breaks without it: a slot gets booked, then simply forgotten by the customer. The business loses the time, the staff member is idle, and there’s usually not enough notice to fill the gap with someone else.
What the automation actually does: as soon as a booking is made, a confirmation goes out straight away. A reminder follows roughly a day before, by text or email, with an easy way to reschedule if they can’t make it. For appointments where no-shows are especially costly, a second, shorter reminder a couple of hours before adds another layer without anyone lifting a finger.
Roughly how long to set up: a few hours if your booking tool already has this built in; closer to a day if you’re wiring it together yourself.
How you’d know it worked: your no-show rate drops, and the last-minute “are we still on for tomorrow” calls mostly stop.
4. Build a welcome sequence for new customers
What breaks without it: someone signs up, pays, or books in, and then hears nothing. They’re not sure what happens next or who to contact with a question. That uncertainty turns into “just checking in” emails and calls someone then has to answer manually, one at a time.
What the automation actually does: the moment someone becomes a customer, a short sequence kicks off. First, a welcome message that sets out exactly what happens and when. Then, a day or two later, anything practical they need — access details, documents, next steps. A week or two in, a check-in to catch problems early, before they turn into a complaint. None of it needs to sound automated; it just needs to be written once, properly, and triggered reliably.
Roughly how long to set up: a day or two to write the sequence and connect the trigger.
How you’d know it worked: fewer “what happens now” messages, and customers getting to their first real use of your product or service faster.
5. Take the weekly admin off someone’s plate
What breaks without it: someone loses a chunk of Friday afternoon copying numbers from one spreadsheet into another, or pulling the same report together by hand every week. It’s tedious, easy to get wrong, and usually the first thing skipped when the week gets busy — exactly when you need it most.
What the automation actually does: the systems you already use — booking tool, accounting software, CRM — get connected so information moves between them on its own. A report that used to take an hour to assemble gets generated and sent out on a schedule. Data that used to be typed in twice only gets typed in once.
Roughly how long to set up: anywhere from a day to a week, depending on how many systems are involved and how messy the data is to start with.
How you’d know it worked: the task simply disappears from someone’s to-do list, and the report arrives on time every week without anyone chasing it.
None of these need a big technology overhaul. Most of them can be built with tools you probably already pay for, connected together properly.
Where to start
Don’t start with the automation that sounds most impressive. Start with the one causing the most complaints — from customers, staff, or you. If enquiries are going cold, fix that first; it’s usually costing you the most. Pick one, get it working properly, check it’s actually doing what you think it’s doing, then move to the next. Five working automations built one at a time beats five half-finished ones built in a rush.