Automation for Small Business: What to Automate First — and What to Leave Manual

Automation advice tends to come in two flavours: breathless ("automate everything") and fearful ("robots will lose your customers"). Both miss the point. Automation is just delegation to a machine, and like any delegation it works brilliantly for some tasks and terribly for others. The skill is knowing which is which.

The three tests for automating a task

A task is a good automation candidate when it passes all three:

• Frequent — it happens weekly or more. Automating a quarterly task rarely repays the set-up and upkeep.
• Rule-based — you can write the decision as "if this, then that" without the word "usually".
• Low blast radius — if it misfires, the damage is small and visible, not silent and compounding.

What to automate first

In most small businesses the same handful of winners come up again and again:

1. Appointment scheduling and reminders. Booking links and automatic SMS/email reminders remove hours of back-and-forth and cut no-shows.
2. Invoice issue and payment chasing. Recurring invoices, automatic receipts, and polite scheduled reminders for overdue accounts. Most accounting platforms do this natively.
3. New-enquiry acknowledgements. An immediate, honest auto-reply — "we've got it, you'll hear from a person by X" — buys you response time without losing the lead.
4. Data moving between systems. Anywhere a human re-types information from one screen into another is an error factory. Connect the systems or use an integration tool.
5. Backups. If a backup depends on someone remembering, it is not a backup. Schedule it, then test the restore.

What to leave manual

Some work should stay human even though a tool could technically do it:

• Anything involving judgement about a person — complaints, sensitive pricing conversations, bad-news calls. Templates can help; sending should stay deliberate.
• Approvals that exist as a control. If the point of a step is that a human checks it, automating the click removes the control while keeping its appearance — worse than having no control at all.
• Low-volume, high-stakes work. One-off contracts, unusual quotes, anything where the cost of a silent error is large.

Build the manual version first

The reliable path to a good automation runs through a boring intermediate step: a written manual procedure. Do the task by checklist for a few weeks first. The checklist flushes out the exceptions — the client who must never get the standard reminder, the invoice type that needs a human eye — while a person is still there to catch them. Automate the checklist once it has stopped changing, and keep it in your ops manual as the fallback for the day the automation breaks or the tool is retired. An automation with no written manual equivalent is a single point of failure with a subscription fee.

Start embarrassingly small. One reminder email, one recurring invoice, one form that writes into a spreadsheet. Small automations that run for years beat ambitious ones that get abandoned in a fortnight — and each small win teaches you what your tools can actually do before you bet a core process on them.

Keep your automations from rotting

Every automation is a small piece of infrastructure that someone must own. Keep a one-page register: what the automation does, what triggers it, where it runs, and who gets told when it fails. Review it twice a year — automations built on someone's personal account, or on a tool you have since abandoned, are the classic silent breakages.

For security when connecting systems, follow the basics the Australian Cyber Security Centre publishes for small business: unique credentials for each service, multi-factor authentication on anything that can move money or data, and remove access when tools are retired.