Skip to content
Guide 6 min read

AI agents versus automation: which one you actually need

Agents are the more interesting technology and the wrong answer most of the time. The distinction is simple: automation follows a path you defined, an agent decides the path. You only need the second when the path genuinely cannot be defined in advance.

By Daniellle Bhatt · Updated 13 August 2026 · Plain text

The actual difference

Automation is deterministic. Given the same input it does the same thing, every time, and when it breaks it breaks in a way you can trace. That predictability is a feature and it is worth a great deal.

An agent decides what to do next based on what it finds. That flexibility is genuinely useful when the situation varies in ways you cannot enumerate, and it is a liability when it does not, because you have traded reliability for a capability you are not using.

Use automation when

  • The steps are known and stable.
  • The input arrives in a consistent shape.
  • Being correct matters more than handling exceptions gracefully.
  • You need to explain exactly what happened when someone asks.

Use an agent when

  • The path genuinely depends on what is found partway through, such as research where the next question comes from the last answer.
  • The input is unstructured and varies: documents, emails, transcripts.
  • Enumerating every branch would take longer than the work it saves.
  • A person currently does it and describes their method as "it depends".

What agents need that automations do not

Guardrails, and they are not optional. An unbounded agent will occasionally loop, spend far more than expected, or take a path nobody intended. The controls that matter are revision caps, per-run budget limits, model tiering so cheap work uses cheap models, and human approval gates before anything is published or sent.

In production we run content engines of six to eleven agents each with two human approval gates. Nothing publishes without both. That is not caution for its own sake, it is what makes the system safe enough to leave running.

An agent without a budget stop and an approval gate is not a system. It is an expensive surprise waiting for a quiet weekend.

The practical answer for most businesses

Both, in layers. Automation for the deterministic majority of the process, an agent for the one step that genuinely requires judgement, and a person approving the output. Most of the value is in the automation, most of the interest is in the agent, and confusing the two is how projects overrun.

Want this applied to your business?

Thirty minutes. You describe how the business runs, we tell you which processes are worth automating and which are not. You will get a straight answer either way, and there is nothing attached to it.