Key Points
- Automation is a system that waits for a trigger, moves or changes data, and takes an action, with no person doing each step.
- Give each task a yes or no on four questions.
- All six share a pattern: high frequency, a recognisable structure and a person who reviews anything customer-facing or financial.
- Some tasks stay with a person because a mistake costs more than the time saved.
- This example uses made-up numbers to show the arithmetic.
- No-code tools suit simple flows.
Automate first the tasks that happen often, follow a pattern even when the details change, and cost little if one goes wrong. Good starting points are data entry between systems, invoice capture, lead routing, weekly reports and follow-up reminders. Keep a person in charge of anything that moves money or speaks to a key customer. Start with one named task, run it beside the manual process, and check its log every week.
What AI automation means
Automation is a system that waits for a trigger, moves or changes data, and takes an action, with no person doing each step. That has existed for decades. Older tools followed fixed rules, so a message that did not match the exact phrase broke the flow.
AI adds judgment to the middle step. It can read an email in messy wording and decide what kind of request it is. It can pull the right fields from an invoice even when each supplier uses a different layout. That makes automation useful for the untidy inputs real businesses receive.
An AI agent is a different idea. Anthropic’s guide to building effective agents separates the two. In short, workflows are systems where models and tools follow predefined code paths, while agents are systems where the model directs its own process. Our post on what an AI agent is goes further. This post is about workflows, which are the right first step for most teams.
Score a task before you automate it
Give each task a yes or no on four questions.
| Question | Yes means |
|---|---|
| Does it happen at least weekly? | The time saved adds up |
| Does it follow a recognisable pattern? | A system can learn the shape |
| Is a wrong result cheap to fix? | Mistakes will not hurt a customer or the books |
| Is the input data available in a system? | The tool can read it without a person |
Our rule of thumb: four yes answers make a strong first task, three make a good one, and two or fewer mean you should wait or redesign the task. This is a judgment tool, not a published standard.
Six tasks to automate first
| Task | What the automation does | What a person checks |
|---|---|---|
| Data entry between systems | Moves form or email details into the CRM or sheet | A sample each week |
| Invoice and document capture | Reads supplier, date, lines and total | Every invoice before payment |
| Lead routing and first reply | Assigns the lead and sends a short acknowledgement | The assignment rules each month |
| Report assembly | Pulls figures from several sources into one format | The report before it is shared |
| Follow-up reminders | Sends check-ins on a schedule from your data | The wording and timing rules |
| Call preparation | Gathers account history and open items into one brief | Nothing, as it is internal |
All six share a pattern: high frequency, a recognisable structure and a person who reviews anything customer-facing or financial. That review step is what keeps the system trustworthy while it earns trust.
What never to automate
Some tasks stay with a person because a mistake costs more than the time saved.
- Relationship judgment. Whether to end a contract, how to handle a sensitive HR matter, what tone to take with an angry long-term customer.
- Final approval of payments. Preparing a payment is fine. Sending the money with no person confirming it is not.
- Work that is new every time. With no repeatable pattern, you are describing a skilled job. Forcing structure onto it produces a brittle system that needs more care than it saves.
- First contact with an angry or high-value customer. Automate the routing so it arrives fast, then let a person reply. The customer-facing side is covered in AI chatbots for business.
Security guidance says the same about high-stakes actions. The OWASP project lists “excessive agency” among its risks for LLM applications and recommends that you “require a human to approve high-impact actions before they are taken”. It also advises giving each tool the minimum permissions it needs, and enforcing authorization in the downstream system, not leaving that to the model.
A worked example: lead routing
This example uses made-up numbers to show the arithmetic.
Before. A form sends each new enquiry to a shared inbox. Someone reads it, decides what it is, types the details into the CRM, picks an owner and replies. If that takes 5 minutes and you receive 40 enquiries a week, it costs 200 minutes, a little over 3 hours, and the reply waits until someone has time.
After.
- The form submission is the trigger.
- The AI step reads the message, labels the request type and pulls out name, company and budget if given.
- A rule assigns an owner by request type.
- The CRM record is created with every field filled.
- A short, plain acknowledgement goes to the sender at once.
- If the AI step is unsure, the enquiry goes to a person with a flag, and no reply is sent.
What stays human. The owner writes the real reply. A person reviews a sample of labelled leads each week, and corrects the rules where the system got it wrong.
Build or buy
No-code tools suit simple flows. Two popular examples are Zapier and Make. On 18 November 2026, Zapier’s free plan offered 100 tasks a month, and its Professional plan started at $19.99 a month billed annually. Zapier counts a task when a step completes, and some AI steps count as more than one. Make’s free plan gave 1,000 credits a month, and most actions use 1 credit. Prices change, so check the pages before you decide.
A custom build earns its cost when your flow has real exceptions, needs judgment at a decision point or touches internal systems that no-code tools do not connect to well.
A quick test: if you can describe the whole workflow in one sentence with no “except when” clause, a no-code tool is probably enough. If you need three “except when” clauses, plan a custom design. This is our rule of thumb. Anthropic’s advice points the same way: find the simplest solution that works, and add complexity only when it demonstrably improves outcomes. For the wider tool picture, read AI tools for business.
Many internal builds fail the same way. Someone builds a flow over a weekend and tests it on two examples. It works until a real input does not match. The tool was fine. The exceptions were never listed before building.
Monitor what you build
An automation that nobody checks is a liability. It can run for weeks and produce wrong output after a connected tool changes its data format or a supplier changes an invoice template. Give each automation:
- An error alert that reaches a named person.
- A log of what it did and why.
- A small test set of real examples that you rerun after any change.
- A monthly review of a sample of outputs.
- One owner who is accountable for all of the above.
Common mistakes
- Picking a task by excitement, not by the score above.
- Automating a process that is already broken.
- Removing the human check on day one.
- Skipping the list of exceptions.
- Building with no alert when the flow fails.
- Measuring nothing before and after, so the gain cannot be shown.
Where to start
Ask three people on your team, separately, which task costs them the most time each week. You will hear the same two or three answers more than once. Score those with the table above, pick the best one, and write down what a correct result looks like before you build anything. Run the automation beside the manual process for a few weeks, compare the results, and widen it only when they match.
How we help
As your Co-Driver, we scope the task, list its exceptions, build the flow and set up the alerts and the review. Read about our AI automation service, or our AI agents service if your work needs more than a fixed flow. If you describe the task, we will tell you honestly whether it is a good candidate.
Frequently Asked Questions
What should a business automate first with AI?
Start with a task that repeats at least weekly, follows a pattern and is cheap to fix when wrong. Data entry between systems, invoice capture and lead routing are common first picks. Keep a person reviewing the output at the start.
What should never be automated?
Keep people in charge of relationship decisions, the final approval of payments, work that is new every time and the first contact with an angry or high-value customer. OWASP advises requiring a human to approve high-impact actions.
Should I use Zapier or Make, or build custom?
Use a no-code tool when the whole flow fits in one sentence with no exceptions. Consider a custom build when the flow has several exceptions, needs judgment or touches internal systems. Check the current pricing pages first, because plans change.
What is the difference between automation and an AI agent?
A workflow follows steps that a person designed. An agent decides its own steps and tools. Anthropic notes that agents often trade cost and speed for performance, so start with a workflow and move to an agent only when it clearly helps.
How do I know the automation is working?
Check the alert channel, read the log and review a sample of outputs each month. Compare time spent and error rates with the manual process you measured before you started.
