What Can I Automate in My Small Business? 15 Tasks You Shouldn't Be Doing Manually
Fifteen jobs worth handing to a machine, plus the ones you shouldn't — and how to tell which is which before you buy anything.
Automation has an image problem. It sounds like a robot replacing someone, or a $400-a-month stack of tools you'll never finish configuring.
What it usually is: the third time this week you typed the same address into a different box. That's the candidate. Not the exciting work — the typing.
Here are fifteen of them, then the more important part: how to tell which of yours is worth automating and which you should leave alone.
Getting work in
1. Routing an enquiry
A form arrives. Someone has to notice it, work out who deals with it, put it somewhere, and remember to reply. Every step is a place it gets dropped — and a dropped enquiry is the most expensive failure on this page, because you never find out it happened.
Automated: the form lands, the right person is notified, a record is created, and the sender gets an immediate "got it, I'll reply by tomorrow". That last line is worth more than the rest combined.
2. Following up on a quote
Most quotes that never convert were never chased. Not because you didn't care — because Tuesday happened. A scheduled nudge at day three and day ten recovers work you'd otherwise lose, and it doesn't need to be clever.
3. Intake forms
If your first call is spent collecting information you could have had in writing beforehand, you're paying for that call twice. A structured intake form means the conversation starts at the useful part.
4. Asking for reviews
Nobody enjoys asking. A message that goes out a few days after the job is done, at the moment they're most pleased with you, removes the awkwardness by removing you from it.
Scheduling and money
5. Booking appointments
The classic. Four emails comparing calendars, replaced by a link. If you're still doing the four emails, this is the highest-value hour on the list and the tools are cheap or free.
6. Appointment reminders
A reminder the day before reduces no-shows, and no-shows are pure loss. This is the single most reliable payback in small-business automation.
7. Invoice reminders
Chasing money is the job people put off most, and it's the one automation is kindest for — a polite scheduled reminder isn't personal, doesn't require you to work up to it, and gets paid faster.
8. Recurring invoices
If you bill the same customers the same amount every month and you're doing it by hand, stop this week.
Keeping people informed
9. Status updates
Half the phone calls in some businesses are "any news on my job?". Every one of those is a customer feeling uninformed and you being interrupted. An update when the status changes eliminates both.
10. Customer onboarding
The welcome, what happens next, what you need from them, the things everyone asks in week one. You've written it all before. Write it once properly and let it send itself in the right order.
11. The emails you send constantly
Not a newsletter — the twelve replies you retype every month. Directions. Your rates. The form. What to have ready. Templates are automation's easiest win and barely count as technology.
Inside the business
12. Moving information between systems
This is the big one, and it's the one people don't recognise as a task because it's invisible: you type a customer's details into the booking system, then the accounting system, then the spreadsheet. Nobody scheduled that work and it's eating your week.
If you're re-entering the same information in more than one place, that's the clearest automation signal there is — and if it's bad enough, it's the signal for something more than automation.
13. Reporting
Exporting three files on the first of the month and pasting them into a spreadsheet to produce the same summary as last time. A dashboard that's always current costs less than the twelve mornings a year you're spending, and you'll actually look at it.
14. Generating documents
Quotes, contracts, certificates, worksheets — anything where you duplicate last month's file, change four fields, and hope you caught all four. Generating it from the record removes the whole category of "the wrong client's name was on page three".
15. Creating the tasks that follow an event
A deposit clears, so: schedule the visit, order materials, add to the calendar, brief whoever's doing it. Same four things every time. That's a checklist, and a checklist that creates itself is a checklist that doesn't get skipped when you're busy.
What makes something worth automating
Not everything repetitive is worth it. Four tests — a task needs most of them, not one.
| Test | Good candidate | Leave it alone |
|---|---|---|
| Frequency | Weekly or more | A few times a year |
| Variation | Same steps every time | Every instance is a judgement call |
| Rules | You can write the rule down in a sentence | You'd say "it depends" |
| Cost of error | Annoying, and recoverable | Someone gets hurt, billed wrongly, or misinformed |
And the arithmetic, which takes two minutes: minutes per time × times per month × 12. Twenty minutes, twice a week, is about 35 hours a year. That's a week of your life you can now put a price on, and compare honestly against the cost of fixing it.
if you can't write the rule down, a machine can't follow it. that's the whole test.
What should stay human
This matters more than the list above, because the fastest way to make automation hated is to automate the wrong thing.
- Anything where the person is upset. A complaint, a mistake, a bereavement, a bill someone can't pay. An automated reply here is worse than a slow human one, every single time.
- The first real conversation with a customer. You can automate getting to it. Don't automate being in it.
- Judgement. Whether to make an exception, whether a job is a good fit, whether that price is right for that customer.
- Anything you can't explain. If a customer asks why they got that email and nobody can tell them, you've built a liability.
- Delicate work done rarely. Payroll corrections, tax, anything legal. Low frequency, high cost of error — exactly the wrong quadrant.
When automation becomes overkill
Three failure modes I see repeatedly:
- The maintenance exceeds the saving. A chain of seven steps across four tools saves twenty minutes a week and breaks monthly. You've bought yourself a hobby.
- Nobody knows what it does. Automations built by one person, undocumented, still firing two years later. The scariest email in a small business is one nobody can account for.
- It automates a broken process. If the process is wrong, automating it means being wrong faster and more consistently. Fix the process on paper first — sometimes that's the whole project, and it's free.
What this looks like when it's done properly
A real example from my own workbench, because I'd rather show you one than describe one.
Clip It & Zip It exists because drawing was never the slow part. Turning a sheet of artwork into something sellable — cutting out every piece, resizing, checking edges, generating previews, packaging it up — was hours of clicking. So the build is a pipeline that does that: it slices the sheet, generates the derivatives a listing needs, and packages the collection into the file a customer downloads. One collection ships 27 clipart files plus 3 frames.
The drawing is still done by a person. That was never the point. The point is that the expensive part wasn't the skilled part — and that's true in most small businesses, which is why this list is mostly typing.
It's still in development, and I'll say so rather than pretend otherwise. You can see where it's up to on the workbench.
How to work out what to do next
For one week, keep a note every time you think "I've done this before". Don't change anything, just note it. At the end you'll have your list, in your own words, ranked by how much it irritated you — which is a surprisingly good proxy for how much it's costing you.
Then, for the top one or two: check whether something you already pay for does it. A lot of automation is a setting in a tool you own, not a project. If it isn't, that's worth a conversation — and it may turn out to be a small piece of software rather than an automation.
Natalie Zingg
I build websites, custom software, dashboards and automation for small businesses — and I build my own products in public, so you can see the work rather than take my word for it.
Still doing one of these by hand?
Tell me which one and how often. Some of these are a twenty-minute setup in a tool you already pay for — I'd rather point you at that than sell you a build.
Tell me what's repetitive