From the outside, RPA platforms like UiPath, Automation Anywhere, and Blue Prism look like the same product category as AI agent platforms. Both automate work. Both replace seat-cost with software-cost. Both pitch the same outcome to the same buyer. The internals are completely different, and picking the wrong tool for the wrong job wastes budget that the procurement committee will remember for two years.
RPA — the model
RPA is deterministic. It executes rules. Either it scrapes the screen — clicking through a UI exactly the way a human would, but faster and without lunch breaks — or it talks to an API directly. The strength is precision: if this exact event happens, do this exact action, every time, with zero variance. The weakness is brittleness. The bot has no model of why it is clicking the button. When the UI changes, the bot breaks. When a new edge case shows up, the bot does the wrong thing confidently.
RPA shines in environments where the inputs are structured, the rules are crisp, and the systems involved do not change often.
AI agents — the model
AI agents are non-deterministic. They understand language. They reason about novel inputs and decide what to do, including deciding to escalate when uncertain. The strength is robustness — when a form changes, when a customer phrases a question in a new way, when an edge case appears, the agent handles it the same way a competent human would. The weakness is variance — the answer to the same question may differ in wording, and the guarantee of identical execution does not apply.
For the architectural picture of how this works in production, see how multi-agent platforms work.
Where RPA wins
High-volume deterministic data transfer between known systems. Invoice processing where the invoice template is fixed and the ERP field map is stable. Payroll runs. Scheduled report generation. Data reconciliation jobs. Anything where you can describe the work as a flowchart with no ambiguous branches.
If you can write the rules in a one-page spec and they will still be true next year, RPA is cheaper and more predictable than an AI agent doing the same job.
Where AI agents win
Anything that touches human language. Customer support. Sales outreach. Qualification. Content generation. Multi-system reasoning where the right action depends on context. Marketing campaigns where the copy needs to adapt. Recruiting workflows where each candidate is a different shape. Anything where edge cases are not the exception but the actual job.
The S.V.I. platform sits in this category, and the structural contrast with RPA is the whole point. An RPA bot is a flat script — no hierarchy, no judgment, no escalation path beyond raising a human ticket. The S.V.I. architecture is the opposite: a three-tier core that scales fractally. Mai sits at the top as the single concierge entry point. Below Mai a Board of Directors handles strategy, prioritisation, and cross-department coordination. Below the Board sit Server-level Agents — the Department Heads, one per functional area, each running its own department.
That same three-tier pattern then duplicates inside every department. The Department Head plays the role of "local Mai" for its own subtree of Managers and Employees. Five visible layers in total — Mai, Board, Department Heads, Managers, Employees — and the pattern is self-similar enough to cover any company at any size. Agent orchestration explained walks through how the layers coordinate.
Headcount is calibrated per client, not a fixed template. Our own SVI Marketing runs roughly 225 agents — 1 Mai, 4 on the Board, 10 Department Heads across our 10 functional areas, around 40 Managers, around 170 Employees. A large enterprise rollout reaches into the thousands. When a novel edge case appears, it climbs the hierarchy until it reaches a layer with the right context to decide — exactly the move that RPA cannot make on its own.
The work itself is assembled with a separate vocabulary that does not get confused with the agent hierarchy. A Bundle is several neural networks chained on one narrow task — for a video script, one model gathers information, one drafts the text, one handles visuals, one edits and verifies. A Scenario is a sequence of bundles for a multi-stage task — script → generation → titles and descriptions produces a finished social-media video. A Module is a reusable block of scenarios covering a whole business function — produce video → publish across networks → first-pass analytics is the "publish video" module. Agent hierarchy is who does the work; Bundle → Scenario → Module is what they assemble.
Hybrid stacks — what enterprises actually run
Most modern enterprise automation runs both. RPA handles the deterministic plumbing — moving data between SAP, Salesforce, NetSuite, and the data warehouse. AI agents handle the language and judgment layer on top — customer conversations, lead qualification, campaign execution, support tickets. The two layers do not compete; they sit at different altitudes of the stack.
SVI Marketing and HandOfHands live in the AI-agent layer. The RPA layer stays where it already is, doing the ETL work it has always done well. /architecture.html shows where the agent platform plugs into existing infrastructure.
Cost comparison
RPA economics are license-plus-development. You pay per bot, per studio seat, and for the implementation team that builds and maintains the workflows. For a high-volume, stable ETL job, the cost per processed record is very low — pennies at scale.
AI agent economics are operated-service. You pay a monthly fee that covers compute, model access, orchestration, and human oversight. SVI Marketing runs from $50/mo for SMB plus an $80 one-time setup (or hourly from $1/hr per agent with no setup), and $1,900 setup plus $2,500 to $5,000 monthly for enterprise. HandOfHands is scoped case by case. Per outcome — qualified lead, resolved ticket, executed campaign — AI agents are typically cheaper than RPA trying to do the same work, because RPA cannot do most of it without expensive custom logic for every edge case.
The right question is which model fits the shape of the work, not which one looks cheaper on a license line.
How to start — the decision framework
For each candidate workflow, ask three questions. Does the input have a fixed structure? Are the rules stable for the next twelve months? Is the output binary-correct or judgment-based? Three yeses point to RPA. Any no points to AI agents. A mixed answer points to a hybrid — RPA for the structured stages, AI agents for the ambiguous ones.
Browse the full module catalogue at /modules.html to see which AI-agent capabilities map to which workflows, or open /chat.html and Mai will help you sort your automation backlog into the right layer.