Nobody decides to answer a lead a day late. It just happens. The form comes in while you are on a job, the email lands behind twenty others, and by the time you reply the buyer has already spoken to somebody else. In a study of 114 B2B companies, fewer than 1 in 100 answered a demo request within five minutes, and the average email reply took 11 hours and 54 minutes (Workato, 2026). Admin does not fail loudly, it leaks: an invoice paid three weeks late, an empty chair at 2pm, a one-star review nobody answered. Here are five jobs where the leak is cheap to plug, with the tool for each, the hours it takes, and the trap to avoid.
- Automate the jobs that repeat weekly, run on rules you could fit on an index card, and cost you money when they slip.
- Your existing tools already send the first reminder free. Build the escalation that happens when it is ignored.
- A person approves anything a customer reads. Software drafts, you sign.
How to tell a job is ready to automate
A job is ready when it passes three tests:
- It happens weekly or more often. Fail this and you spend longer building than the job ever cost you.
- Its rules fit on an index card. Fail this and you are automating a judgement call, not a task.
- Somebody notices when it is late. Fail this and nobody will care whether it runs.
Most of what follows needs rules, not artificial intelligence. Some 38% of US small businesses now use AI somewhere in the business and 25% use it in customer service (Verizon 2025 State of Small Business Survey, fielded by Morning Consult with 600 respondents). Four of the five jobs below are plain if-this-then-that logic with a timer on it. Only the review drafting step is better with a language model. Reach for AI when a step needs writing or judgement.
One more rule, the one most owners skip. Your invoicing software, your booking page, and your payment processor already send a first reminder, free and well written. What none of them handle is the second move: day 14 with the invoice still unpaid, or a customer who books and cancels twice in a row. Automate the escalation, not the reminder.
1. Answer every new lead in under five minutes
Build one path: the form creates a record in your CRM, sends an instant acknowledgement to the enquirer, and pings you if nobody has followed up in an hour. That last step is the one that matters, because the acknowledgement buys you an hour, not a week.
The delay is bigger than most owners think. In the same Workato study of 114 B2B companies (2026), the average email reply arrived 11 hours and 54 minutes after the request and the average callback took 14 hours and 29 minutes. A fifth of the companies never emailed at all and 69% never called. Those using lead routing tools replied in 3 hours and 32 minutes, against roughly 13 hours without.
The free tier of HubSpot CRM or Zoho Bigin will take the record and send the acknowledgement on its own. If your form lives elsewhere, Zapier bridges the two. Budget an afternoon.
The trap is the acknowledgement itself. An auto-reply that reads like a machine kills the interest you just earned. Write one human sentence saying when a real answer is coming, and never promise a time you cannot hold.
2. Chase invoices without becoming the chaser
Turn on the reminders your accounting software already has, then build the ladder that runs after them: a nudge on day 7, a task to phone on day 14, a rule that pauses new work on day 30. The software handles the polite part. The ladder handles the part you keep putting off.
Doing nothing has a price, and in the UK somebody has counted it. Businesses hit by late payment spend about 86 hours a year chasing it and are owed around £17,000 on average, and 28% of businesses surveyed are affected (London Economics for the Small Business Commissioner, 2025). The same research sits behind the government's figure of roughly £11bn a year drained from the UK economy (GOV.UK, 2025). Those 86 hours are more than two working weeks of typing "just following up on the below".
QuickBooks, Xero, and Stripe all send scheduled reminders out of the box, so start there. Chaser and Satago handle the escalation layer once you are running dozens of invoices a month. Below that volume, a scheduled check in Make or n8n that turns an unpaid invoice into a call task does the same work for less.
The trap is a reminder that reaches a client mid-dispute, or one who paid by bank transfer and is waiting on you to reconcile it. Add a hold tag to the customer record and make every step of the ladder check it first.
3. Remind people before they no-show
Send two reminders, not one: a 48-hour note that gives people time to move the booking, and a two-hour note for the ones who forgot it was today. Put a reschedule link in both.
A 2016 meta-analysis of 16 studies of medical appointments found no-shows at 15% where patients were reminded, against 21% where they were not, and attendance at 67% against 54% (BMJ Open, 2016). The detail worth stealing: multiple reminders lifted attendance by about 25% relative to no reminder, a single reminder by about 6%. Your salon or garage is not a hospital clinic, and the study is old, but the shape of the finding is hard to argue with.
Calendly, Acuity, Square Appointments, and Microsoft Bookings all send reminder emails, and most send texts on a paid plan. If yours does not, a Twilio step in Zapier or Make adds the SMS leg in an hour.
The trap is a reminder with nowhere to go. Without a reschedule link you have not prevented a no-show, you have just heard about it earlier. Give people one tap to move the slot and some of them will.
4. See every review the day it lands, reply the same week
Route new reviews to the place you actually look. A Google Business Profile alert goes to Slack or email, a language model drafts a reply in your voice, and you approve or rewrite it before anything is published.
Customers treat this as the minimum. In BrightLocal's survey of 1,026 US consumers, 93% said they expect businesses to respond to reviews and 63% expect that response within two or three days to a week (BrightLocal, 2025). The same survey found 40% are most likely to leave a review when asked by email, which is the other half of this job: an automated request after a finished job is what gives you something to reply to.
Google Business Profile sends review alerts natively, which covers most single-location businesses. Birdeye and Podium earn their fee once you have several locations or platforms to watch. The drafting step is where n8n or Make pays: feed the model the review and a short style guide, and the draft comes back sounding like you.
The trap is auto-publishing. Never let a model post a reply on its own, least of all to a bad review. A clumsy AI response to an angry customer is a screenshot that outlives the complaint. Draft automatically, publish deliberately.
5. Get the weekly numbers without opening five dashboards
Schedule one roll-up: sales, new leads, unpaid invoices, new reviews, no-shows, posted to Slack or your inbox at 8am Monday. Five numbers, one line each. If you have to open a dashboard to understand it, it is too long.
We run our own back office on the same idea, on a daily rhythm rather than weekly. UpAlerts, the job alerts product we build and operate, keeps its reporting in n8n: a scheduled pipeline grades alert quality with a language model under a per-user cost cap, daily growth reports post to Slack, and a global error handler reports any failed workflow before a user notices. The cost cap and the error handler are the parts that get skipped, and they are why it runs unattended. The build is written up on the UpAlerts case study.
Looker Studio emails a scheduled report free if your data already sits in Google's tools. Databox pulls from more sources with less setup. Slack Workflow Builder covers the simplest version, a scheduled prompt asking you for the numbers. Self-hosted n8n is cheapest once the roll-up crosses several systems, at the price of maintaining it yourself.
The trap is a report nobody reads. Keep it to five numbers you would act on, put last week's figure beside each one so the trend needs no thinking, and delete any line you have ignored three weeks running.
Which one to do first
Pick the job that cost you money last month. Two invoices past 60 days, start there. A quote lost to a competitor who called first, start with leads. Your own last month beats any general ordering.
The setup hours below are our estimate for an owner doing this themselves with off-the-shelf tools, not a measured figure. They assume you already use a CRM, an invoicing tool, and a booking page.
| Job | Setup effort (owner hours) | Monthly cost | Needs a developer |
|---|---|---|---|
| Lead reply and follow-up nudge | 2 to 4 | Free tier to low | No |
| Invoice escalation ladder | 2 to 3 | Free tier to low | No |
| Appointment reminders | 1 to 2 | Free tier to low | No |
| Review alerts and drafted replies | 3 to 5 | Low | Maybe, for the drafting step |
| Weekly roll-up report | 3 to 6 | Free tier to mid | Maybe |
On tools, three sentences will do. Zapier is the easiest to start and the fastest to get expensive as your task count grows. Make costs less for the same volume and gives you more control, at the price of a steeper first week. n8n is cheapest at scale and the most flexible, and you host and maintain it yourself, which is a real cost even when the licence is free.
Bring in help at one of two moments: when the job crosses two systems with no connector between them, or when a mistake reaches a customer. Everything else here is a Saturday morning and a free tier. Most of our AI automation work starts with that second opinion: which of the five is worth your Saturday.
Questions owners ask
What should a small business automate first?
Lead replies, in most cases. It is the cheapest of the five to set up, and the delay is measurable rather than a matter of opinion. Fewer than 1% of the companies in the Workato study (2026) answered within five minutes, so the bar is low. The exception: if late payment or empty slots are what hurt you, fix the one that is bleeding.
How much time does automation actually save?
It depends on your volume, and anyone quoting one number for every small business is guessing. The figure worth trusting is the cost of not doing it: UK businesses hit by late payment spend about 86 hours a year chasing it (London Economics, 2025). Size your own case by counting how often you did the task last month. Under an hour a month, leave it alone.
Do I need a developer for this?
Not for lead replies, invoice escalation, or appointment reminders. Those are configuration in tools you already pay for. Help pays off on the review drafting step, where prompts and approval flows are easy to get subtly wrong, and on any job that hands data between two systems with no ready-made connector. If a mistake would reach a customer, have somebody who has built one before check it.
Can automation reply to reviews for me?
It can draft, it should not publish. Of consumers surveyed, 93% expect a response to reviews (BrightLocal, 2025), and they expect a person behind it. A model that writes the first version saves you most of the work and none of the responsibility. Keep the approval step even after the drafts get good, because the one you would have caught is the one that gets screenshotted.
The short version
Three tests decide it: weekly or more often, rules that fit on an index card, and somebody notices when it is late. Turn on the reminders your tools already send, then spend your build time on the escalation nobody has covered. Keep a person in front of anything a customer will read. Do one job this month, not five, and pick the one that cost you money in the last thirty days. If it crosses two systems that do not talk to each other, that is the kind of build AppSol360 does, so tell us which job it is.