Most businesses don't need to be convinced that automation could help. The harder question is where to start. There are dozens of manual tasks in a typical week, and picking the wrong one first is how automation projects end up costing more than they save.
A good first automation is usually boring. It's a task that happens often, follows the same steps every time and annoys the people who do it. It isn't the most complicated process in the business, and it's rarely the one with the most opinions attached to it.
Below are seven processes that make good starting points for small and medium-sized businesses in Australia and New Zealand. For each one we cover what the manual version looks like, what can realistically be automated, where a person should stay involved and what you can expect to get out of it. After that is a simple way to score your own list, and the cases where automation isn't the right first move.
What makes a process worth automating first
A strong first candidate usually ticks most of these boxes:
- It happens often. Daily or weekly, not once a quarter. Volume is what turns a few minutes saved into hours saved.
- The steps are the same each time. If you could write it down as "when this happens, do that", it's a good sign.
- It starts with a clear trigger. A form is submitted, a deal is won, an invoice arrives, a job is completed.
- The data lives somewhere reachable. The information is already in a system such as your CRM, Xero, MYOB or job management software, not only in someone's head.
- Mistakes are annoying but not catastrophic. Start where an error means a correction, not a compliance problem or a lost client.
- Someone owns it. One person can say how it should work and will notice if it stops.
1. Lead capture and assignment
The manual version: enquiries arrive through website forms, email, phone and social messages. Someone copies each one into the CRM or a spreadsheet, decides who should handle it and forwards it on. When that person is busy or away, enquiries sit untouched.
What can be automated: capturing every enquiry in one place, creating the CRM record, categorising it by service, location or value, assigning it to the right person and notifying them, and logging it for reporting.
Where human judgement stays: the conversation itself, and anything that doesn't fit the rules, such as an unusual request or a large opportunity that the owner wants to see personally.
Expected benefit: fewer enquiries slipping through, clearer ownership and a reliable picture of what's come in and what's still waiting.
For one Australian real estate office, we connected customer enquiries with property records. An enquiry updates the property record and the right person is notified, so follow-up is no longer a separate step someone has to remember. The office has less manual follow-up and better visibility across the workflow. If response speed is your main concern, we've also written about what happens when every lead gets a fast response.
2. Customer and client onboarding
The manual version: once a client says yes, someone re-enters their details into the CRM, the accounting system and the project tool, sets up access, creates tasks and lets the team know. Steps get skipped, and every new client starts slightly differently.
What can be automated: when the deal is marked won, the client's details flow into the other systems, the standard records and tasks are created, any accounts are set up and the right people are notified.
Where human judgement stays: the welcome conversation, scoping, and any client whose setup is genuinely non-standard.
Expected benefit: less re-keying, fewer errors and a consistent start for every client, even when the usual person is on leave.
For CorIT Tech, an IT services firm, we automated client onboarding so customer details kept in the CRM create the project and its tasks, instead of staff copying them across. CorIT reported saving more than 10 hours of onboarding admin a month, with less repetitive data entry and fewer manual errors. Onboarding is a similar pain point for many professional services firms.
3. Quoting and approvals
The manual version: quote requests arrive with half the details missing. Someone chases the information, builds the quote, waits for a manager to approve it and then often forgets to follow it up.
What can be automated: collecting the required details up front with a structured form, pre-filling what you already know about the customer, routing quotes above a set value or margin to a manager, and updating the quote status in your CRM or job system.
Where human judgement stays: the estimate itself in most businesses. Pricing a job well usually depends on experience, site conditions and the customer relationship. Automation should prepare the information, not make the call.
Expected benefit: quotes that go out faster and more consistently, approvals that don't sit in an inbox, and a clear view of which quotes are still open.
4. Invoice and document processing
The manual version: supplier bills, purchase orders, timesheets and forms arrive as PDFs or emails and get typed into another system by hand.
What can be automated: if your suppliers can send structured invoices, Australia's eInvoicing network (Peppol) lets invoices move directly between accounting systems, and many accounting packages already support it. Where documents still arrive in mixed formats, AI workflow automation can extract the key fields and pass them into your system.
Where human judgement stays: approving payments, and checking anything the system flags as unclear. A good document workflow is designed to send what it isn't sure about to a person, not to guess.
Expected benefit: less retyping, fewer keying errors and documents that are filed in the same place every time.
5. Internal notifications and handoffs
The manual version: work moves between people by memory and messages. The site team finishes a job and tells the office. The office remembers to tell accounts. Someone asks on Slack or Teams whether the paperwork has gone in.
What can be automated: status changes that trigger the next step. A job marked complete in ServiceM8 or another job management system can notify accounts, create the invoice draft and update the customer record.
Where human judgement stays: sign-off points such as quality checks, variations and anything that needs a conversation with the customer.
Expected benefit: fewer dropped handoffs and less time spent asking where things are up to. For trades and field service businesses, the gap between "job done" and "invoice sent" is often where cash flow slows down.
6. Reporting and data consolidation
The manual version: someone exports data from three systems every week, pastes it into a spreadsheet, tidies it up and sends it around. Meanwhile, the same information is kept up to date by hand in several places.
What can be automated: making one system the source of truth, publishing from it to the other places the data needs to appear, and pulling report figures on a schedule into a summary or dashboard.
Where human judgement stays: deciding what the numbers mean and agreeing on definitions. If two managers calculate margin differently, automation will only make that disagreement faster.
Expected benefit: reports that are ready without anyone building them, and fewer inconsistencies between systems.
For Huntress Recruitment, Bullhorn stayed as the system of record. We added dedicated public-facing job fields and standardised how vacancies are published to SEEK and the company's WordPress website. That cut duplicate admin and made published job information more consistent. If this sounds familiar, our article on the hidden cost of tools that don't talk to each other goes deeper.
7. Follow-ups and customer updates
The manual version: chasing overdue invoices, following up quotes, and sending customers "where's my job up to?" updates, all of which happen only when someone remembers.
What can be automated: start with the features you already have. Xero, for example, has built-in automatic invoice reminders that can email customers before or after an invoice is due. Beyond that, quote follow-ups and status updates can be triggered automatically from your CRM or job system.
Where human judgement stays: sensitive conversations such as disputes, hardship, complaints and a long-overdue account that needs a phone call rather than another email.
Expected benefit: consistent follow-up without anyone keeping a list, and customers who hear from you before they have to ask.
How to score your own list
These seven are common starting points, but your business will have its own. List the manual tasks your team does every week, then score each from 1 to 5 on:
- Frequency: How often does it happen?
- Time: How long does it take each time, including checking and fixing mistakes?
- Consistency: Are the steps the same every time?
- Data access: Is the information already in a system that can be connected?
- Pain: How much do errors or delays hurt customers, cash flow or staff?
- Risk (scored in reverse): How bad is it if the automation gets something wrong? Lower risk scores higher.
To estimate time, multiply how often a task happens by how long it takes. As an illustration, a task that takes six minutes and happens 40 times a week adds up to four hours a week. Use your own numbers. A rough count from the people who do the work beats a guess.
Then sense-check the winner. Can you describe the steps in a paragraph? Does one person own it? If so, you've probably found your first project.
When automation isn't the right first move
- The process is still changing. Automating it locks in a moving target. Agree the process first.
- Nobody agrees on the rules. If three people do the same task three ways, standardise it before automating it.
- It happens rarely. A task done four times a year usually isn't worth the setup and upkeep.
- The decision needs judgement. Refunds, credit, pricing exceptions and anything legally significant should keep a person at the decision point.
- The real problem is the software. If you're building workaround after workaround around a system that no longer fits, our article on buy vs build covers when custom software makes more sense.
Start small and make it reliable
Pick one process, automate it properly, check it against the manual version for a few weeks and fix what breaks. Then move to the next. A few habits help:
- Run automations under business-owned accounts, not someone's personal login.
- Decide who gets notified when a sync fails or a record is incomplete.
- Write down what each automation does and who looks after it.
- Measure the time spent before you start, so you can judge whether the change was worth it.
Frequently asked questions
How long does it take to set up the first automation?
There isn't a standard timeframe. A stable task that already lives in a system such as Xero, MYOB, ServiceM8 or your CRM is a smaller piece of work than a process that changes often or sits only in someone's head. What adds effort is unclear rules, missing logins, and exceptions that have never been written down. Once we can see the path from the first step to done, we can tell you what that first slice involves.
Will staff have to change the tools they use?
In most cases, no. People can keep working in the inbox, CRM, job system or accounting package they already know. What changes is that a record, a task or a message appears without someone retyping it. If a product genuinely cannot support the step, that is a separate conversation from automating the work around it.
How do we start small?
Limit the first build to one task the team already repeats, and leave everything else alone. Run that automated path beside the manual one until the person who owns it trusts the result, then decide whether a second task is worth doing. A narrow start is easier to look after, because someone can still explain what it does when it misbehaves.
What should I prepare before I talk to you?
A plain description is enough. Say what kicks the task off, which tools it passes through, who does each step, and what finished looks like. If you know how often it happens and where it usually breaks, add that too. You don't need a diagram, a software shortlist or a budget.
Do we have to replace our current software?
No. Replacing a product is a bigger decision than automating one process, and it is not where we start. If the tools you have can store the information and the steps repeat, we work with them. Replacement comes up when the software itself is what makes the process complicated, not when you simply want the copying to stop.
Get a second opinion on one workflow
If one of these processes sounds like yours, send us a short description of how it runs today, from what starts it to what "done" looks like. We'll review the workflow and come back with an honest view: whether it's a good candidate, which parts to automate, where people should stay involved, and whether there's a simpler fix with the tools you already have.
Learn more about our business process automation work, or ask for a workflow review.