AI strategy
AI agents or workflow automation? Choose the simpler system first.
A practical decision framework for choosing between deterministic automation, AI-assisted workflows, and autonomous agents.
October 12, 2026 · 7 min read
The short version
Use fixed workflows for repeatable processes, add AI where judgment is genuinely useful, and reserve agents for work whose path cannot be known in advance.
01
The market is selling autonomy. Most operations need reliability.
AI agents are the loudest idea in business technology right now. The useful question is not whether an agent can perform a task. It is whether the extra autonomy improves the business outcome enough to justify more cost, latency, testing, and operational risk.
A conventional automation follows a path you define. An agent decides which path to take while it works. That distinction matters. Invoice routing, lead enrichment, report generation, and CRM synchronization usually benefit from predictable rules. Research, exception handling, and multi-step investigation may benefit from agentic reasoning because the exact sequence cannot be mapped cleanly in advance.
02
Think in three levels, not two camps.
The choice is rarely ‘automation or agent.’ A more useful architecture has three levels. Level one is deterministic orchestration: triggers, rules, APIs, and validation. Level two adds a model inside a controlled step—for classification, extraction, summarization, or drafting. Level three gives a model tools and lets it decide what to do next.
This layered view prevents over-engineering. A support workflow might use rules to identify the customer, AI to classify intent, a fixed lookup to retrieve account data, and a human approval before any refund. Only the ambiguous cases need an agent to investigate across several systems.
- —Deterministic workflow: the path is known and failures must be easy to trace.
- —AI-assisted workflow: one or two steps require interpretation, but the process remains controlled.
- —Agentic system: the number and order of steps depend on what the system discovers.
03
Use an agent only when the task earns the complexity.
Agents make sense when the work is open-ended, the environment provides useful feedback, and success can be measured. They are strongest when they can inspect results, recover from errors, and stop or escalate when confidence is low.
They are a weak fit for high-volume tasks with a stable path, irreversible actions without review, or processes where no one can define what good looks like. In those settings, autonomy creates a larger failure surface without creating proportional value.
04
A production decision checklist.
Before adding autonomy, document the current process and calculate the cost of a mistake. Then test the smallest architecture that could produce the required outcome. The right system is the least complex one that performs reliably under real conditions—not the one with the most impressive demo.
- —Can the correct sequence of steps be written down? Start with a workflow.
- —Does one step require judgment over messy inputs? Add a bounded model call.
- —Must the system plan, choose tools, and adapt? Consider an agent.
- —Can actions affect money, customers, or records? Add permissions and human review.
- —Can quality be evaluated repeatedly? Build the evaluation set before scaling.
Continue reading
Related analysis
Infrastructure
What MCP changes for business software—and what it does not.
Model Context Protocol can standardize how AI systems connect to tools and data. Here is the business case without the protocol hype.
Applied AI
Context engineering is the difference between a clever demo and useful AI.
Why business AI needs the right information, tools, memory, and boundaries—not one enormous prompt.