What should a growing business automate first?

The short answer is that you automate the boring, repetitive task that already slows your team down. The one that happens the same way several times a week, follows a clear rule, and needs no judgement. Not the impressive thing. The tedious thing.

Most businesses get this backwards. They start with whatever sounds most futuristic, a chatbot or a clever report, and end up with a demo that impresses in a meeting and is quietly abandoned two weeks later. The automations that actually stick are unglamorous. That is the point.

Find the task, not the tool

Before looking at any software, spend a week noticing where your people do the same thing over and over. The strongest candidates share three traits. They happen often, they follow a predictable pattern, and they are already a source of low grade friction. If a task is rare, or changes shape every time, or genuinely needs a human decision, leave it alone for now.

A useful test. If you can write the rule for a task in a few sentences of the form if this then that, and it happens most days, it is a strong first candidate.

Common first automations that earn their keep are the plumbing between systems. Moving an enquiry from a form into your CRM. Sending a message when a step is reached. Generating a routine document from data you already hold. Reconciling two lists that should always match. None of these will impress anyone. All of them return time.

Go narrow and deep, then stop

Pick one process. Automate the whole of it. Let it run for a couple of weeks and watch it under real conditions before you touch anything else. This discipline is what separates automation that compounds from automation that becomes a fragile mess nobody trusts. A second layer added on top of an unproven first layer is how businesses end up with systems more brittle than the manual work they replaced.

The goal in the first month is not scale. It is one workflow that runs reliably whether or not anyone remembers it exists.

Where AI helps and where it does not

AI is useful for a narrow set of jobs inside a workflow. Reading messy input and turning it into structure. Sorting or classifying things. Drafting text that a human then approves. It is not a reason to automate. The friction is the reason. AI is occasionally the right tool for one step of the fix.

Be wary of anything that puts a model in charge of an irreversible decision, or that depends on it being right every single time. Automate the stable scaffolding and keep human judgement where judgement is actually needed.

A simple order of operations

1. 1Watch a normal week and list the tasks repeated most often.
2. 2Cross out anything rare, changeable, or heavy on judgement.
3. 3From what is left, pick the one that costs the most time or drops the most work.
4. 4Automate that one thing completely, and only that.
5. 5Run it for two weeks. Measure the time saved and the errors avoided.
6. 6Only then consider the next one.

If you do this honestly, the first automation is usually smaller and duller than you expected, and worth more than the ambitious one you had in mind. That is the job.