Opinion · AI agents and workflows

Agents Solve Problems. Workflows Solve Them Once.

When to reach for an AI agent, and when to reach for a workflow.

menu_book Start reading
Scott Harris
Written by
Scott Harris
Chief Technology Officer
Read time
5 min
Published
Sep 2026

For eight years running, I brought a new cohort of graduates into a fintech business. Same intake every autumn: bright, keen, and slightly terrified of the client reporting. My job was to train them, empower them, and point them at the real work: report writing, QA, documentation, configuring how clients got their numbers.

The best ones always did the same thing. They didn't just get through the task in front of them, they automated it. A grad who spent a fortnight untangling a fiddly client reporting configuration would build it so the fiddly part never came back, then go looking for a harder problem. That is what good looks like: solve it once, properly, and bank the result.

Now imagine the opposite. Imagine that instead of banking anything, I hired a brilliant new graduate every single week, briefed them from scratch, and asked them to solve the exact same problem. The same reconciliation, the same reporting config, the same QA pass, over and over, forever. Nobody would let that run for long, and rightly so, because it's an absurd way to burn talent, time and money.

That, more or less, is the difference between an AI agent and a workflow.

01 · Agency

When you want agency, use an agent

An agent is that brilliant graduate on their first day. You hand it an open problem, give it some tools, and let it work out the path for itself. It reasons, it adapts, and it improvises its way to an answer. That is exactly what you want when the problem is genuinely new: messy inputs, no fixed route, and a destination you can describe but not yet map.

Think investigation, research, or the first triage of something nobody has seen before. When the value is in figuring out how, agency is the entire point, and that is where an agent earns its keep.

02 · Determinism

When you want determinism, use a workflow

Here is the slightly less glamorous truth: most business is not new. It is the same shape, over and over. A refund, a KYC check, a month-end client report, an incident response. You already know the steps, you know who signs off, and you know what "done" is supposed to look like when it fails as well as when it works.

That is not a place for improvisation. What you want is the same correct outcome every time, an audit trail you can stand behind, and a human in the loop at the points that matter. That is a workflow: a known business process, encoded once, and running reliably ever after.

Asking an agent to reason its way through a settled process on every single run is just the every-week-graduate again in a smarter suit. It is slower, it is less predictable, and as we will get to, it is not cheap.

03 · The trick

The trick: workflows can hire agents

None of this is really agents versus workflows, and the most interesting systems happily use both.

The skeleton

The workflow gives you the reliable skeleton: fixed steps, clear ownership, and handoffs that actually happen.

The judgement

Then, at the one point where a task genuinely calls for judgement, you drop AI in to do the thinking.

The result

You get the creativity where it helps and the guardrails where they count.

Pull the intent out of a scruffy client email, summarise a case file, or classify the odd request that refuses to fit the usual buckets. That is agency applied to the single subtask that needs it, sitting inside a structure that stays predictable everywhere else.

04 · Cost

Cleverness has a meter running

There is a commercial edge to all of this too. Every time an agent reasons from scratch, you pay for it in tokens, and solving an already-solved problem from first principles is about the most expensive way there is to get an answer you already had.

A workflow encodes that answer once and then runs it a thousand times for little more than the cost of running it. That frees you to spend your AI budget on the problems that are actually new, rather than re-deriving your reporting logic every month-end. Think of it as caching your best graduate's work instead of re-hiring them each week and hoping they land on the same conclusion.

05 · Structure

The power needs a frame

AI is genuinely astonishing, and the temptation is to point it at everything and let it loose. But raw capability with no structure around it is just a very confident intern with no oversight and access to the company credit card.

The organisations getting real value out of this are not agonising over agents versus workflows. They treat the workflow as the frame that holds everything together, giving them determinism, control, auditability and human sign-off, and then they place AI agency exactly where it earns its keep. It is the whole idea behind how we think about workflows at Next Matter: give the process a solid structure first, then let AI do the genuinely clever bit inside it.

So hand your agents the interesting problems, and let your workflows carry the rest, on rails, every time. Your graduates, and your budget, will thank you for it.

Keep reading

Bring a process and we will show you where the agent belongs

A reconciliation, a KYC check, a month-end report. We will map the deterministic frame and the one step where AI actually earns its keep.