21Labs
Blog

Five Signs a Process Is Ready to Be Automated

2026-07-01

Every owner has a list of jobs they would love to hand to a machine. Some of those jobs are excellent candidates and some will cost more to automate than they ever save. These five signs separate the two groups, and they work whether you plan to use Zapier, Make, n8n or a custom build.

1. The task repeats on a rhythm

Automation pays off through repetition. A task that happens every day, every invoice or every new enquiry gives you thousands of chances to recoup the setup effort. A task that happens a few times a year rarely does.

Picture a physiotherapy clinic that emails a reminder, a pre-visit form and a follow-up to every new patient. That sequence runs for every booking and takes a receptionist a few minutes each time. Across a month, those minutes add up to hours. Compare that with annual insurance renewals: important, but a person can do them in an afternoon.

Count it plainly. Minutes per run, times runs per month, times the hourly cost of whoever does it. If the answer is small, leave it alone.

2. The steps are the same every time

Automation handles rules well. If you can write the task as "when this happens, do that, then that", it is a candidate. If an experienced person says "it depends" at every step, it is not ready.

A quick test: ask two different staff members to describe how they do the task. If the descriptions match, you have a process. If they differ, you have two habits, and you should decide which one is right before building anything.

Some judgement-heavy tasks can still be partly automated. An AI model can draft a reply to a customer email, with a person approving it before it sends. The automation covers the drafting and a human keeps the decision. That is a legitimate pattern, but it needs the human step built in on purpose.

3. The data lives in systems that can talk to each other

Most failed automation projects fail here. The logic is simple, but the information is scattered across a PDF, a shared inbox, someone's spreadsheet and a booking tool with no connection to anything.

Before committing, list where the inputs come from and where the outputs must go. Look for:

  • An API or built-in integration (Xero, MYOB, HubSpot, Google Workspace and Microsoft 365 are well supported by the major automation tools).
  • Structured data, such as form fields, rather than free text buried in attachments.
  • A single source of truth, so the automation does not have to guess which of three spreadsheets is current.

If the data is trapped in paper or in a system with no export, the first project is getting it out, and that is a worthwhile project in its own right.

4. Mistakes are cheap to catch and fix

Start with processes where an error is annoying and not disastrous. Sending a duplicate reminder email is harmless. Wrongly paying a supplier or sending a quote with the wrong price is not.

That does not rule out automating higher-stakes work. It means those builds need approval steps, logs and alerts. A sensible pattern is to let the automation prepare everything and pause for a person to confirm before money moves or a document goes to a client. Build the cautious version first. You can loosen it once you trust it.

5. Someone owns it and will notice when it breaks

Automations drift. A supplier changes an invoice layout, a form gets a new field, a password expires, and the automation quietly stops or does the wrong thing. If nobody is responsible, the failure surfaces weeks later as a customer complaint.

Before building, name the owner. That person should know what the automation does, where to see whether it ran, and what to do when it fails. Good builds send an alert on failure instead of staying silent.

A quick scorecard

Give a process one point for each sign. Four or five points means start. Two or three means fix the gaps first, usually by writing down the steps or cleaning up the data. One or zero means leave it manual for now.

Be wary of any pitch that skips this step and jumps to tools. The tool is rarely the hard part. Our post on why boring automations win explains why the unexciting candidates usually give the best return.

Next step

If you have a list of candidate processes and want an outside view on which ones are worth building, 21Labs can help. We are an agency in Sydney serving businesses across Australia, and workflow automation is the service built for this. Discovery is free and every enquiry gets a reply within 24 hours.

good questions, straight answers

Frequently asked questions

How many times a week should a task happen before automating it?
There is no magic count. Multiply the minutes per run by the runs per month and compare it to the cost of building and maintaining the automation. A five-minute task done daily usually justifies a simple build. A one-hour task done twice a year usually does not.
Can I automate a process that is messy right now?
Fix it first. Automation applies a process faster, including its mistakes. Write down the steps, remove the ones nobody can justify, then automate what is left.
Do I need to code to automate a process?
Not always. Tools such as Zapier, Make and n8n handle many common jobs without code. Anything touching sensitive data or complex rules may justify custom development.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with 21Labs. Both options start with an enquiry.