Every operator we meet in 2026 is being pitched three different things under the same banner. The RPA vendor calls it intelligent automation. The workflow tool calls it AI workflows. The agent platform calls it agentic AI. The slides look interchangeable. The technology is not. Buying the wrong one is the most expensive decision a mid-market company will make this year, because the wrong tool does not just underperform. It blocks the right one from being adopted.
This is the practitioner's guide we wish we could hand to every founder before the first vendor call. Three categories, three jobs, one decision rule.
RPA: the macro recorder for the screen
Robotic Process Automation, the UiPath, Blue Prism, Automation Anywhere category, is a bot that drives a graphical user interface the way a human would. It clicks buttons, copies fields, pastes them into the next screen. The rules are hard-coded. The bot has no idea what the screen means. It just knows that at this pixel there is a button, and it should click it.
RPA is unbeatable for one thing: ripping data between two systems that refuse to integrate with each other. Legacy ERP into a portal that has no API. A scanned PDF into an accounting tool. A vendor extranet into a spreadsheet. If the work is mechanical, the inputs are structured, and the screens never change, RPA pays back in weeks.
It fails the moment any of those assumptions move. Screens change. Inputs are messy. Edge cases multiply. The bot breaks silently, then loudly, then expensively. RPA was the right answer for 2018. In 2026 it is the right answer for a narrowing set of problems, and the wrong answer for anything that involves judgement.
Workflow automation: the wiring between tools
Workflow automation, the Zapier, Make, n8n, Workato category, is the wiring layer. A trigger in one app fires an action in another. New row in a sheet, send an email. Form submitted, create a Notion page. Stripe charge, post in Slack. The platform is opinionated about events and connectors, not about the work itself.
It is the right tool when the work is genuinely linear, when the trigger and the action are unambiguous, and when both ends speak through a clean API. Most modern SaaS is built to be wired this way. A good ops team can stitch fifty automations in a quarter and remove ten hours a week from every function.
Where it stops working is the moment the workflow needs to think. The classic failure: a Zap fires, drops a lead into a CRM, sends a template email. The lead is enterprise, the template is for SMB, the rep does not notice for a week. Workflow automation has no opinion on what should happen, only on the order things happen in. Add a hundred branches to model judgement and the workflow becomes unmaintainable. That is the ceiling.
Agentic AI: the operator that reads, decides, and acts
Agentic AI is a different category. The agent reads inputs in their native form, reasons against an objective, picks an action from a set of available tools, and learns from the outcome. It does not need pixel coordinates. It does not need a pre-mapped branch. It needs an objective, a data layer it can read and write to, and a small set of tools it is allowed to use.
The work an agent does well is the work that requires interpretation. Read this inbound email and decide if it is a quote request, a support ticket, or a partnership pitch. Pull together pricing, terms and product fit for this prospect and draft the first version of a quote. Triage these 40 support tickets, answer the routine 60 percent, and escalate the rest with context. None of that is automatable with RPA. None of that fits a Zap.
Agents are also harder to deploy well. They need clean data, a defined objective, guardrails, an evaluator, and a human owner who watches the first hundred decisions. Done wrong they are an expensive parrot. Done right they take the work that used to require a person, and quietly do it at five times the volume.
The decision rule
Strip the marketing and the call is simple. Map the work on two axes. Is the input structured or unstructured? Is the decision rule-based or judgement-based?
- 01Structured input, rule-based decision: workflow automation. Cheaper, faster, no model required.
- 02Structured input, no API at one end: RPA. Only if the integration genuinely cannot be built and the screens are stable.
- 03Unstructured input, rule-based decision: workflow automation with a small model in the middle for parsing.
- 04Unstructured input, judgement-based decision: agentic AI. This is where the model earns its keep.
“The mistake we see most often is buying agentic AI to solve a Zapier problem, or buying RPA to solve an agent problem. The technology is not the issue. The diagnosis is.”
- Derk Disselhoff
What this means for the buying process
Before you sign anything, write the workflow down. Inputs, decisions, outputs, exceptions. Walk it past the person who does it today. Then ask the vendor in the room which of those four boxes their tool is built for. A serious vendor will tell you the truth. A weak one will say all four.
The mid-market companies winning with AI in 2026 are not the ones with the biggest stack. They are the ones who used the right tool for each layer. RPA at the bottom for the legacy bridges. Workflow automation in the middle for the linear wiring. Agentic AI at the top for the work that requires judgement. The layers compound. None of them replaces the others.
The invitation
If you are sitting in front of a vendor deck this week and you cannot tell which of the three categories you are being sold, that is the conversation we exist for. Bring the workflow. We will bring the diagnosis, and the build that follows from it.
