The one-line versions
- Automation. A program that executes predefined, rule-based steps. Same input shape in, same action out, every time.
- AI workflow. A defined sequence of steps where one or more steps call an AI model to read, classify, extract, draft or decide. You design the path; the AI does the judgement inside it.
- AI agent. A program given a goal and a set of tools, which decides for itself which steps to take, in what order, and when it's finished.
The distinction that matters is who controls the path. In automation and AI workflows, you do. With an agent, the AI does. That single difference drives everything else: reliability, cost, auditability, and what each is safe to use for.
Side-by-side comparison
| Automation | AI Workflow | AI Agent | |
|---|---|---|---|
| What it is | Fixed rules: when X happens, do Y | A designed sequence of steps where AI handles the judgement steps | A goal plus tools; the AI picks its own steps |
| Handles messy input? | No. Inputs must be structured and predictable | Yes. Reads emails, PDFs, free text, photos of invoices | Yes, plus it can go looking for more input on its own |
| Predictability | Total. Same input, same output | High. The path is fixed; only the judgement inside each step varies | Lower. The path itself can change run to run |
| Auditability | Easy | Easy when built properly: every prompt, output and decision logged | Harder. You must reconstruct why it chose the steps it did |
| Typical NZ SME example | New booking lands, send a confirmation text | Inbound email read, classified, customer history pulled from the CRM, reply drafted for one-click approval | "Research this new lead and update the CRM", where the agent searches, reads and writes on its own |
| Running cost | Cents. No AI calls | Low. A few AI calls per item, usually well under $0.10 | Higher. Many AI calls per task, and slower |
| Best for | High-volume, identical, structured tasks | High-volume tasks that need reading and judgement | Open-ended tasks with low stakes or human review at the end |
| Watch out for | Breaks the moment input varies | Needs guardrails and human checkpoints designed in | Unpredictable failures; cost creep; hard to debug |
Table scrolls sideways on mobile.
Which one does your business need?
Work up the ladder, not down it. Use plain automation wherever the input is structured; add an AI workflow where a person currently reads and judges; reserve agents for narrow jobs where an unexpected result is annoying rather than expensive.
A useful test for each rung:
- "Could I write the rule on a whiteboard?" If yes, it's plain automation. Don't pay for AI calls to do an if-statement's job.
- "Does a person read something and make a routine call?" That's the AI-workflow sweet spot: invoice processing, inbox triage, quote drafting, document review.
- "Do I want it to figure out the approach itself?" That's agent territory. Ask whether you'd delegate this task to a new hire with no supervision. If not, don't give it to an agent unsupervised either.
Common myths, corrected
- "AI workflows require training a model." No. Modern workflows use existing large language models via API. There is no model training, and no giant dataset needed; your business rules go in as instructions, not training data.
- "Agents are the upgrade, workflows are the compromise." They solve different problems. A workflow is not a lesser agent, in the same way a production line is not a lesser employee.
- "Automation is obsolete now AI exists." The opposite: good AI workflows contain as much plain automation as possible, because deterministic steps are cheaper, faster and never hallucinate.
- "You need one or the other." Real systems mix all three. Ours typically use automation for the plumbing, AI for the judgement steps, and occasionally a tightly-scoped agent for research-style subtasks with a human checkpoint after.
Frequently asked questions
Is ChatGPT an AI agent?
Out of the box, no. ChatGPT is a model you converse with; it acts only when you prompt it. It becomes agent-like when it's given tools (web browsing, file access, code execution) and a goal to pursue across multiple steps. The same underlying models power automations, workflows and agents; the difference is the harness around them.
What about tools like Zapier and Make?
Classic Zapier/Make flows are plain automation: triggers and structured actions. Both now let you insert AI steps, which turns a flow into a simple AI workflow. Where they run out of road is deep integration (legacy systems, complex business rules, audit requirements), which is when a custom build makes sense. We cover this in our AI workflow automation page.
Are AI agents safe to use in a business?
Yes, for the right jobs with the right guardrails: scoped tools, spending and step limits, full logging, and a human checkpoint before anything customer-facing or financial happens. What's risky is giving an agent broad access to live systems and letting it act unsupervised on high-stakes work.
Which is cheapest to build?
Plain automation is cheapest, then AI workflows, then agents. For NZ SMEs, a custom AI workflow typically lands in the $5,000–$25,000 fixed-price range and pays for itself within 3–6 months. Agent projects cost more to build and more to run, and need a stronger business case. Our 8-step implementation guide covers how to scope this properly.
Will agents replace workflows as the technology matures?
Agents keep improving, and the line will keep moving. But businesses will always want predictable, auditable paths for core processes, for the same reason they use checklists and standard procedures with human staff. Expect agents to take over more of the open-ended edges while workflows keep running the middle.
Not sure which your process needs?
Book a free 30-minute call and describe the task. We'll tell you whether it's an if-statement, a workflow or an agent, and what it would honestly cost. Discovery is always free.
Book a free strategy call