Use traditional automation (rules and RPA) for steps that never vary and use structured fields; use an AI agent for steps that need reading, judgement or handling exceptions. A workflow often contains both, so the decision is made per step: the agent reads and decides, the rules or bot type, and a person approves what sends, pays or changes records.
Mapping a workflow step by step and assigning each step to the cheapest reliable tool is the two-week AI Opportunity Audit ($2,900 CAD plus applicable taxes, fixed). Send a written request describing the workflow, or call +1 (613) 867‑7767.
What counts as traditional automation?
Two families of tools, both driven by rules a person wrote:
- Rules-based workflow tools such as Zapier, n8n, Make or Microsoft Power Automate: when an event happens in one app, run fixed steps in others through their APIs. Our Zapier vs n8n vs custom comparison covers the choice between them.
- RPA (robotic process automation) such as UiPath or Automation Anywhere: a bot works the user interface of systems without usable APIs, clicking and typing as scripted.
An AI agent receives a goal, uses a language model to decide the next step, calls the tools it is allowed to use and checks the result. Definitions and the agent loop are in our agentic AI guide.
AI agents vs RPA vs rules: side by side
| Rules-based workflow | RPA bot | AI agent | |
|---|---|---|---|
| How it decides | Fixed if/then rules | Fixed script | Model chooses steps at run time |
| Input it handles | Structured fields via API | Structured fields on screens | Emails, PDFs, scans, free text |
| When input changes | Rule fails or skips | Bot breaks | Usually copes; may err |
| Exceptions | Sent to a person | Sent to a person | Resolves many, escalates the rest |
| Predictability | Full | Full while screens stay the same | Lower; needs tests, logs, approvals |
| Cost per case | Lowest | Low | Higher: model calls per step |
| Typical build | Hours to days | Days to weeks | Weeks, with a test set of real cases |
| Audit | Rule history | Bot logs | Step and tool-call logs, by design |
Each column wins somewhere, which is why one workflow often uses two or three of them.
Where does traditional automation win?
When all of these hold for a step:
- The steps never change, or change rarely enough that updating the rule is trivial.
- Inputs are structured: the same field, same format, same system.
- No reading or judgement: every case follows the same rule.
- Predictability is required: the output must be identical every time.
Typical wins: copying records between systems, scheduled reports, posting values that are already calculated, creating accounts from a fixed form, reminders on a date. Automations of this kind are part of our AI workflow automation service, often with no model involved at all.
Where do AI agents win?
When at least one of these holds:
- Inputs vary: contracts, invoices from hundreds of suppliers, client emails, scanned forms.
- Exceptions are common and people currently handle them by hand.
- The step needs a decision: which category, which team, which policy applies.
- Language is involved: summarizing, extracting terms, drafting a reply, translating.
- The environment shifts: supplier portals and documents change their layout.
Typical wins: shared-inbox triage with draft replies, invoice and form extraction, contract intake, routing support tickets with a proposed answer, completeness checks on applications.
The hybrid build: agent, rules and a person
Assign each step to the tool that handles it reliably at the lowest cost.
The same split works for loan files, claims intake and client onboarding: the agent reads documents and drafts summaries, rules and bots move structured data, and a person makes the decision. RPA platforms are moving the same way: UiPath markets a platform for agentic automation that combines agents, robots and people, and Automation Anywhere sells "agentic process automation". Combined builds are our RPA + AI automation service; systems without APIs are covered by legacy system integration.
Five questions to assign each step
Map the workflow first, then ask these for every step.
- Is the input always the same structured field? Yes: rules or RPA. No: agent.
- Does the step involve reading or writing language? Yes: agent.
- How often does the step hit an exception? Rare: rules, with exceptions sent to a person. Common: agent, with escalation.
- How often does the step change? Rarely: rules. Often, or the source documents change: agent.
- What does an error cost? High: whichever tool runs it, a person approves before the action.
Our rule of thumb: when exceptions are a large share of cases and each takes a person several minutes, an agent on those cases usually pays for its model calls. Check with numbers: the AI agent ROI framework shows the calculation, including review time.
Limits on both sides
- Agents err. Language models give confident wrong answers. Keep tests on real cases, logs of every step and approval before consequential actions. When a step needs the same output every time with no review, use deterministic rules.
- Agents can be steered by what they read. An email or document can carry instructions aimed at the agent. Treat everything it reads as data and keep write actions behind approval.
- RPA is brittle. A changed screen or field stops the bot; budget for maintenance and monitor failures.
- Rules tools hit a ceiling. Long chains of conditions in Zapier or n8n become hard to maintain; at that point a coded workflow or an agent may be simpler. See custom agents vs Zapier.
How to get started
- Map one workflow: steps, systems, volume per month, minutes per case, exception rate.
- Assign tools per step with the five questions above.
- Build the rules first where they suffice; they pay back quickly.
- Pilot the agent on the variable steps, with approval on, against the baseline.
- Widen autonomy only on steps where the measured error rate is low.
Remolda designs and builds AI agents, rules-based automation and the hybrid of both for Canadian organizations, in English and French. The agent pilot is the six-week AI Pilot Sprint, a fixed-price package at $9,800 CAD. In our experience a first agent reaches a working pilot in about six weeks; it depends on system access and the number of exceptions.
Not sure which tool fits your workflow? Send a written request with the steps and systems involved. We reply within one business day and say which steps need an agent, which need rules and which should stay with a person.
Sources
- UiPath: platform for agentic automation (agents, robots and people)
- Government of Canada: Guide on the Use of Agentic Artificial Intelligence (review step before actions that change records)

