5 Business Processes You Should Automate This Year

Most automation advice starts with the tool. Someone tells you to buy Zapier, you connect two apps, and six months later you have a graveyard of half-working zaps nobody trusts.

Automation works the other way around. You start with the specific hour of the week that everyone dreads, and you remove it. Here are the five that show up in nearly every business I work with, roughly in order of how much time they give back.

1. Turning finished work into invoices

What it looks like now: someone opens a spreadsheet or a job list at the end of the week, works out what’s billable, types it into accounting software, and emails the invoices. Then they chase the ones that don’t get paid.

What it costs: four to eight hours a week, plus the revenue quietly lost to jobs that never made it onto an invoice at all. That second cost is usually the bigger one, and almost nobody measures it.

What automation looks like: when a job is marked complete, the invoice is drafted automatically from the job data, sent on your billing schedule, and chased on a polite fixed cadence — day 3, day 14, day 30 — until it’s paid.

Keep a human approval step before anything goes out for the first few months. It costs thirty seconds and buys enormous confidence.

2. Getting customer enquiries to the right person

What it looks like now: enquiries land in a shared inbox. Someone reads them, decides who should handle each one, and forwards them. Whoever’s busy that day is the bottleneck, and a handful get missed entirely.

What it costs: less time than invoicing, but far more money. A lead that gets answered in five minutes converts dramatically better than one answered the next day, and “next day” is what a shared inbox delivers when things get busy.

What automation looks like: enquiries are classified as they arrive — by service, location, or value — assigned to the right person, acknowledged instantly with a real answer to the most common question, and escalated if nobody responds within a set window.

The instant acknowledgement matters more than people expect. It’s the difference between a prospect waiting for you and a prospect emailing your competitor.

3. Onboarding a new client or employee

What it looks like now: a checklist someone half-remembers. Accounts get created, documents get sent, someone forgets the one step that only matters in month three.

What it costs: two to four hours per person, plus the harder-to-measure cost of an inconsistent first impression.

What automation looks like: one trigger — a signed contract, a start date — sets off the whole sequence. Accounts provisioned, welcome pack sent, documents requested and tracked, calendar invites created, reminders fired at day 1, 7, and 30. Anything that needs a human decision becomes a task with a deadline instead of a thing someone hopes to remember.

4. The weekly report nobody enjoys making

What it looks like now: someone exports data from two or three systems, pastes it into a spreadsheet, fixes the formatting, writes a summary, and emails it around. Every week. Forever.

What it costs: two to five hours weekly, and the report is stale the moment it’s sent.

What automation looks like: a live dashboard that’s always current, plus a scheduled digest that lands in inboxes with the three numbers that actually drive decisions and a note about anything that moved unusually.

Here’s the part people miss: the goal isn’t a faster report. It’s noticing sooner. A dashboard that surfaces a problem on Tuesday instead of the following Monday is worth far more than the hours saved making it.

5. Chasing documents and signatures

What it looks like now: you need a form, a certificate, an ID, or a signature. You email. They don’t reply. You email again. You feel rude. You email again anyway.

What it costs: small in hours, large in delay. Projects sit blocked on a single missing PDF for weeks.

What automation looks like: a request with a secure upload link, automatic reminders on a schedule you set, validation that the file is the right type, and a notification to you the moment it arrives. Everyone stops feeling nagged, because the system is doing the nagging.

How to pick your first one

Don’t start with the biggest. Start with the one that scores best on this:

• Frequency — daily beats monthly
• Boredom — if the person doing it can describe the rules exactly, it automates cleanly
• Cost of a mistake — low-stakes first; you want to build trust before you automate anything with teeth
• Data already in a system — if the input lives in email attachments and someone’s head, that’s a harder starting project

The best first automation is usually the one people complain about most casually. Nobody escalates the small weekly annoyance, which is exactly why it survives for years.

Two rules that keep automation from breaking

Every automation needs a visible failure mode. Silent failure is worse than no automation at all, because people stop checking. If the invoice sync fails, someone must be told immediately — not discover it at month end.

Automate the process you have, then improve it. Don’t redesign the workflow and automate it in the same step. You won’t know which change caused which problem. Get the current process running by itself first, then optimise it once you can see it clearly.

What to expect realistically

A well-chosen first automation takes one to three weeks and saves a few hours a week forever. That compounds: the second one is faster because the plumbing exists, and the third faster still.

What surprises most people isn’t the hours. It’s that the work becomes reliable. Invoices always go out. Leads always get answered. Nobody has to remember. That consistency is worth more than the time.

---

Not sure which process to start with? Book a free call and walk me through your week — I’ll tell you which one I’d remove first and roughly what it takes.