The best way to automate business processes is to start with the ones you already run every week, using the software you already pay for, one process at a time. Pick a process that is repetitive, rule-based and annoying: invoices typed into Xero or MYOB, approvals chased by email, a report rebuilt in Excel every Monday. Map it as it really happens, cut the steps that add nothing, then automate what's left with the simplest tool that will do the job. Many small automations need nothing more than settings you haven't switched on or an inexpensive app. Bigger ones, where several systems are involved, are where it pays to get help.
Step 1: Pick the right process to start with
Good first candidates share four traits:
- It happens often. Daily or weekly, not once a year.
- It follows rules. The same steps every time, with few judgement calls.
- It involves retyping. Information is copied from one place to another.
- People complain about it. The people doing it already know it's a waste of time.
Common examples: supplier invoices keyed into the accounts, sales orders retyped into a job or stock system, timesheets copied into payroll, purchase approvals chased by email, and the weekly report put together by hand from several spreadsheets.
Avoid starting with something that changes every time, needs a lot of judgement, or only happens a few times a year. Automating those rarely pays back.
Step 2: Map the process as it really happens
Sit with the person who does the work and write down every step, including the workarounds nobody mentions: the spreadsheet on their desktop, the email to a colleague to double-check a figure, the step that only happens on Fridays.
For each step, note:
- what triggers it,
- which system or file the information comes from,
- where it ends up,
- and what happens when something is wrong.
This is the most valuable step and it costs nothing. Most businesses find steps that can simply be dropped.
Step 3: Simplify before you automate
Automating a messy process gives you a fast messy process. Before building anything:
- Remove steps that add nothing, such as approvals nobody actually checks, or copies kept "just in case".
- Agree one way of doing it, if different people do it differently.
- Decide where each piece of information lives. One system should be the master copy for customers, items and jobs.
Sometimes this step fixes most of the problem on its own.
Step 4: Use what you already have first
Before buying anything, check what your existing software can already do:
- Xero and MYOB have bank rules, repeating invoices, invoice reminders and email-to-bills features that many businesses never switch on.
- Your job, CRM or stock system may already have a built-in connection to your accounting software.
- Microsoft 365 includes Power Automate, which handles simple approvals and notifications.
If a setting or a built-in connection does the job, use it. It's the cheapest and most reliable automation there is.
Step 5: Choose the simplest tool that fits
- One app sending simple data to another: a ready-made connector from the app marketplace is usually enough.
- A few simple "when this happens, do that" steps: a no-code tool such as Zapier, Make or Power Automate.
- Several systems, large volumes, or data that has to be exactly right: a properly built integration, with error checks and alerts.
- Steps that need reading or judgement, such as invoices in many layouts: AI for the reading step, with a person approving the result.
No-code tools are great for small jobs. They get harder to manage as more steps, more systems and more exceptions pile up, especially if one person built them and nobody else understands how they work.
Step 6: Build in a check, then measure
Every automation should tell someone when it fails. A silent failure, where invoices quietly stop flowing and nobody notices for a fortnight, is worse than the manual process it replaced. Before you start, note how long the process takes and how often it goes wrong. After a month, check again, so you know whether it worked.
When it's bigger than a do-it-yourself job
It's usually worth getting help when:
- the process crosses three or more systems,
- the data has to be exactly right, such as money, stock or payroll,
- you've tried a no-code tool and it keeps breaking or needs constant fixing,
- you run several companies or sites,
- or nobody in the business has the time to own it.
That's the work we do: mapping the process with your team, simplifying it, and building automation around the software you already use, with alerts when anything needs attention. See business process automation and workflow improvement.
Frequently asked questions
What business processes should I automate first?
Ones that happen often, follow the same rules every time and involve retyping information from one place to another, such as supplier invoices, sales orders, timesheets, approvals and regular reports. Start with the one your team complains about most.
Do I need new software to automate my processes?
Often not. Xero, MYOB and Microsoft 365 already include automation features many businesses don't use, and many apps have built-in connections. Start there before buying anything.
Is Zapier enough for business automation?
For small, simple automations between two apps, often yes. It gets harder when processes involve many steps, several systems, large volumes or data that must be exactly right. That's when a properly built integration with error checks is the better choice.
How do I know if automation is working?
Measure the process before you start (time taken, errors, delays) and again a month later. Also make sure the automation alerts someone when it fails, so problems are caught the same day.
If you've mapped a process and it's clearly bigger than a quick fix, book a free initial chat. We'll tell you honestly whether a setting or an app will do, or what building it properly would involve.