Before you start · Chapter 02
What to automate first with AI
AI automation only pays off when it targets the right work. Pick the wrong process and you magnify the wrong thing. This chapter helps you find the first workflow to automate.
“The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency.”
Bill GatesCo-founder, MicrosoftThe Road Ahead, 1995How to find processes to automate
Start by listing your repetitive, rules-based tasks. These are jobs done the same way every time. Look across sales, support, finance and operations.
Signs a task is ready to automate
The best candidates share a few traits. The more that apply, the better the fit.
- It follows clear, repeatable rules.
- It happens often — daily or weekly.
- It moves data between systems.
- It rarely needs human judgement.
- Mistakes are costly or slow to fix.
AI automation examples by team
Not sure what is automatable? These are common wins by function.
| Team | Common AI automations |
|---|---|
| Sales | Lead capture, enrichment, follow-up, CRM updates |
| Support | FAQ answers, ticket routing, status replies |
| Finance | Invoice processing, approvals, reconciliation, reporting |
| Operations | Data entry, onboarding, scheduling, alerts |
| Marketing | Content drafts, campaign reports, list hygiene |
How to prioritise what to automate first
Not every task is worth automating first. Score each one by impact and by effort. High-impact, low-effort work comes first. Skip low-impact, high-effort work for now.
Here's a quick way to score your candidates. Rate each from one to five, then act on the winners.
| Task | Impact (1–5) | Effort (1–5) | Verdict |
|---|---|---|---|
| Invoice processing | 5 | 2 | Do first |
| Lead follow-up | 4 | 2 | Do first |
| Custom report builder | 3 | 5 | Later |
| One-off data cleanup | 2 | 3 | Skip |
Define a measurable automation outcome
Then define the outcome you are buying. A clear metric lets you brief agencies and judge results. A vague goal does not.
| Vague goal | Measurable outcome |
|---|---|
| Improve support | Cut first-reply time to 5 minutes |
| Save time on invoices | Process invoices in 3 hours, not 3 days |
| Get more leads | Follow up every lead within 2 minutes |
Key takeaways
- List your repetitive, rules-based tasks first.
- Rank them by impact and effort.
- Start with high-impact, low-effort work.
- Define a measurable outcome before you build.
Know the service you need?
Jump to agencies that specialise in it — by service, industry and location.
Browse by serviceSources & further reading
Frequently asked questions
What should I automate first with AI?+
Start with a workflow that is repetitive, high-cost and frequent. Score your tasks by impact and by effort. The first project should be high impact and low effort. Avoid starting with your hardest, most critical workflow — prove value on something contained first.
What can AI automation actually do?+
AI automation handles rules-based, high-volume work. Common wins include lead follow-up, ticket routing and invoice processing. Others are data entry, reporting and status replies. If a task follows clear steps and happens often, AI can take it on. Keep a human for the edge cases.
How do I decide which processes to automate?+
List your repetitive, rules-based tasks across sales, support, finance and operations. Rank each by how painful and how frequent it is. Then rank by effort to automate. High-impact, low-effort work comes first. Low-impact, high-effort work can wait.
What business processes are best for AI automation?+
Rules-based, high-volume work suits automation best. Common wins include lead qualification, customer support and data entry. Others are invoice processing, document processing, CRM updates and reporting. If a task follows clear steps and happens often, it's usually a strong candidate.
How do I calculate ROI before automating?+
Estimate the time each task takes and how often it runs. Multiply to get hours spent per week or month. Put a cost on those hours, then compare against the build and running cost. A clear before-and-after number makes the case easy.
Should I automate a process that isn't working well?+
No — fix or simplify it first. Automation locks in whatever it is given, good or bad. If a workflow is messy or full of exceptions, streamline it before you automate. Automating a broken process just makes the mess run faster.
How do I map my workflows for automation?+
Write down each step a task takes and the tools it touches. Note who does each step. Mark where people wait, re-key data, or copy between systems. Those handoffs are where automation pays off. A simple list is enough to start.