How to Run Your Own Business Automation Audit in 2 Hours

The most common reason Australian businesses haven't automated yet isn't cost, and it isn't technical complexity. It's that they don't know where to start. When you're inside a business, operating at full pace, every process feels necessary and interconnected - and figuring out which ones to change feels like trying to renovate a house while living in it.

This guide gives you a structured, time-boxed method to cut through that fog. It's the same three-step framework we use at Polaris Labs in client process audits, adapted so you can run it yourself in about two hours. You don't need any technical knowledge. You need a spreadsheet, two hours of uninterrupted time, and honest answers from your team.

At the end of those two hours, you'll have a prioritised list of automation candidates, each scored by ROI potential, and a clear sense of which to tackle first, which to tackle later, and which aren't worth automating at all.

Why Most Businesses Don't Know Where to Start

There's a proximity problem in operational improvement. When you're doing a task every day, you stop seeing it as a task - it becomes part of the furniture. The accounts receivable manager who spends 90 minutes every Monday morning generating the debtors report doesn't think of that as a problem. It's just what Monday morning looks like. The operations manager who copies timesheet data from the field management app into the payroll system every fortnight doesn't experience it as waste. It's just part of the job.

The purpose of an audit is to step outside the process and look at it objectively. That requires two things: a systematic method for surfacing tasks that have become invisible, and a scoring system that converts gut feel into comparable numbers.

The three-step framework does both.

What You'll Need Before You Start

• A blank spreadsheet (Google Sheets or Excel) with columns for: Task Name, Who Does It, Frequency (daily/weekly/monthly), Minutes Per Instance, Error-Prone? (Y/N), Documented? (Y/N), Automation Score (calculated)
• Access to your calendar and inbox for the past 4 weeks
• 30 minutes with each key team member, or a short survey (5–7 questions) sent to each department
• A list of every software tool your business uses

The process inventory is harder than it sounds. You'll think you're done after 15 minutes and have 10 items on your list. You're not done. A typical 5–10 person Australian SMB has 40–80 distinct recurring tasks when you actually map them properly.

How to Surface Hidden Tasks

Use these five methods in combination:

1. The tool audit. Open every software platform your business uses and ask: "What recurring things happen in this tool?" Go through your CRM, accounting software, project management tool, email, calendar, communication tools (Slack, Teams), and any industry-specific platforms. For each tool, list every routine action that staff perform in it.

2. The trigger-action method. Think in terms of "when X happens, someone does Y." When a new enquiry comes in, someone does ___. When a job is completed, someone does ___. When a payment is received, someone does ___. When a new staff member joins, someone does ___. Work through every significant business event and list the manual tasks it triggers.

3. The calendar and inbox review. Spend 15 minutes reviewing your own calendar and inbox for the past 4 weeks. Every recurring meeting that exists primarily to share information (rather than make decisions) is a candidate for replacement by an automated report. Every email thread where you're forwarding information from one person to another is a candidate for automated routing. Every recurring task in your calendar that involves data collection or formatting is a candidate for automation.

4. Team interviews. Ask each team member two questions: "What's the most repetitive thing you do each week?" and "What task do you do that you feel like a computer could do?" You'll get honest, operational answers that reveal the actual day-to-day admin load. Don't skip this step - managers systematically underestimate front-line admin burden because they don't do it themselves.

5. The handover test. For each team member, ask: "If you had to hand your job to someone new today, what written instructions would they need?" The things that don't have written instructions but should - the things being held in people's heads - are often the most important processes to document and eventually automate.

Questions to Ask Your Team

• What is the most repetitive task in your typical week?
• What do you do that involves copying information from one system to another?
• What tasks do you do that have a set schedule (same day each week/month)?
• What recurring emails do you send that look basically the same every time?
• What reports or summaries do you create that pull data from more than one place?
• What tasks do you do that you know a mistake could cause a real problem?
• If you could eliminate one task from your day, what would it be?

By the end of Step 1, you should have a list of at least 25–40 tasks. If you have fewer than 20, you've missed some - go back through your tool list and trigger-action exercise.

For each task in your inventory, score it on a 1–5 scale across four dimensions:

Multiply the four scores together for a combined Automation Priority Score (APS). Maximum possible: 625. Anything above 100 is a strong automation candidate. Anything above 200 is a priority.

A few calibration examples:

• Weekly invoice follow-up emails: Frequency 3, Time 3, Error Risk 3, Strategic Value 4 = APS of 108. Strong candidate.
• Daily timesheet data entry (copied from one system to another): Frequency 5, Time 2, Error Risk 3, Strategic Value 4 = APS of 120. Strong candidate.
• Monthly BAS lodgement review: Frequency 1, Time 4, Error Risk 5, Strategic Value 2 = APS of 40. Low priority for automation (also requires judgment - not suitable for full automation).
• Daily Xero reconciliation: Frequency 5, Time 3, Error Risk 4, Strategic Value 3 = APS of 180. High priority.

Implementation complexity is a subjective assessment - but you can make it systematic by asking three questions about each high-scoring task:

• Are the inputs structured? A task that draws from well-structured data (a form submission, a spreadsheet row, a CRM record with consistent fields) is easier to automate than one that requires interpreting unstructured inputs (free-text emails, verbal instructions, handwritten notes).
• Are the tools involved in the task available on Make, n8n, or Zapier? Check the connector libraries for your specific tools. Most major platforms (Xero, HubSpot, Salesforce, monday.com, Jobber, ServiceM8, etc.) have pre-built integrations. Custom or niche tools may require API development, which increases complexity.
• Is the process stable? A process that changes frequently (new rules, new exceptions, constant edge cases) is harder to maintain as an automation than a stable, predictable process. Score complexity higher for volatile processes.

On your 2x2 matrix:

• High ROI + Low Complexity: Build first. These are your "quick wins" - significant time savings, straightforward implementation, fast payback.
• High ROI + High Complexity: Plan for second phase. These are worth doing but require more scoping, testing, and potentially an agency to build well.
• Low ROI + Low Complexity: Do later or DIY. Low-stakes, low-effort automations that are nice to have but not transformative.
• Low ROI + High Complexity: Don't automate. The build cost exceeds the benefit. Fix the process manually first, or deprioritise it entirely.

What to Do With Your Shortlist

Once you have your priority matrix, you should have a clear top 3–5 automation targets. The next decisions are: which tools to use, and whether to build yourself or hire someone.

Deciding Whether to DIY or Hire

DIY automation is viable if: the automation involves two tools with native connections on Make or Zapier; the logic is simple (no branching conditions, no edge case handling); and you have someone with moderate technical comfort (comfortable with spreadsheets and willing to follow documentation) who can own the project.

Hiring an agency makes sense when: the automation spans multiple tools with complex logic; the process is customer-facing or financially significant (errors have real consequences); or the time to build it yourself would exceed 20–30 hours (at which point an agency is almost certainly cheaper on a total cost basis).

A Real-World Audit Output (Sanitised)

Here's what the output of an automation audit looked like for a 7-person Melbourne-based professional services firm. We've sanitised the details but this reflects a real discovery session output:

The firm identified 34 recurring tasks in their process inventory. After scoring, their top 5 automation priorities were:

1. Client onboarding document generation - APS 192, Low-Medium complexity. New client signed → automated generation and sending of engagement letter and NDA via PandaDoc, triggered from HubSpot deal stage change.
2. Weekly WIP report - APS 180, Low complexity. Automated Monday report pulling unbilled hours from their time-tracking tool and outstanding invoices from Xero, delivered to the directors via email.
3. Invoice payment reminders - APS 162, Low complexity. Three-touch automated sequence via Xero API: 7 days, 14 days, 30 days overdue.
4. New enquiry routing and CRM entry - APS 144, Low complexity. Website form → CRM contact created → lead assigned and notified via Slack.
5. Timesheet reminder sequence - APS 126, Very low complexity. Automated Friday afternoon reminder to staff who haven't submitted timesheets for the week.

Total estimated time saving from all five automations: 9.5 hours per week. At a fully-loaded cost of $45/hour (professional services firm, slightly above average), that's $427/week or $20,500 per year. The total build cost for all five was $6,800. Payback in 16 weeks.

The businesses that get the most from their automation audit are the ones that treat it as a genuine discovery exercise rather than a justification exercise. Go in without a predetermined outcome. Sometimes the most valuable insight from an audit is that your processes need fixing before they need automating.

One Thing Most Audits Miss

Every business process audit we've run has surfaced at least one significant finding that wasn't on anyone's radar at the start: a process that's being done differently by two different team members, creating inconsistent outputs; a tool nobody uses properly because nobody was trained on it; a weekly report that nobody reads but someone spends 90 minutes creating. These aren't automation opportunities - they're process improvement opportunities that should happen before any automation investment.

The process inventory phase of your audit will surface these. Don't dismiss them as off-topic. Fixing a broken process costs nothing and sometimes delivers more value than automating a functional one.

Your Next Step

If you've completed the audit and you have a prioritised list of automation targets, you have two options. If the top items on your list are simple (two-tool integrations, time-based triggers, form-to-database connections), consider starting with Zapier or Make's free tier and their documentation. If the items are more complex - or if you'd simply prefer to have a professional build something you can rely on - book a free 30-minute session with Polaris Labs and bring your audit output. We'll give you a frank assessment of what's buildable, what it would cost, and whether the ROI justifies the investment.