The RPA Market Is Collapsing

Created on 2026-09-04 — updated on November 3, 2026


The RPA Market Is Collapsing

Reading time: 6 minutes. Author: Hugo S. Nascimento.

Context: This critique was born while auditing IT invoices for an enterprise client paying an external integrator sixty thousand dollars a month just to patch broken UiPath selectors across SAP and remote desktops. Pixel clickers cannot compete with protocol-level autonomous agents.

Executive Summary for Technology Leaders: Legacy Robotic Process Automation vendors — led by UiPath, Automation Anywhere, and SS&C Blue Prism — built an industry on emulating human mouse clicks and DOM selectors over virtual Windows desktops. Whenever an ERP screen or web portal shifts a CSS class, the bots crash, fueling a parasitic maintenance market for systems integrators. Today, hsnlabs replaces fragile screen-scraping bots with protocol-level autonomous agents built on Python, Pydantic v2, LangGraph, and the Model Context Protocol — executing headless transactions directly against SAP, TOTVS, and Oracle APIs while slashing infrastructure and licensing costs by over 80 percent.


Diligence Note and Public Sources

The architectural specifications, licensing structures, and protocol standards referenced in this article are grounded in official vendor documentation:

  • UiPath Unattended Robot and Virtual Machine Licensing Documentation: detailing runtime licensing and desktop infrastructure requirements, available at UiPath Official Licensing Overview.
  • Automation Anywhere Enterprise Platform Architecture: detailing bot runner execution over UI selectors, available at Automation Anywhere Documentation.
  • Model Context Protocol Open Technical Standard: specification for headless protocol integration between AI models and enterprise backends, available at Model Context Protocol Documentation.

1. Why the Legacy RPA Business Model Is Collapsing

The legacy Robotic Process Automation industry pulled off one of the greatest marketing sleights of hand in enterprise software history.

For ten years, vendors like UiPath, Automation Anywhere, Blue Prism, and Microsoft Power Automate Desktop convinced enterprise leaders that emulating mouse clicks on a virtual desktop was the future of digital labor. What Chief Information Officers actually purchased was an expensive, fragile web of glorified macro recorders that break whenever a button moves three pixels to the left.

Enterprises tolerated this fragility because, until recently, there was no alternative for bridging legacy systems that lacked modern APIs. Today, that justification is dead.

Legacy RPA does not understand business logic. It understands screen coordinates, Document Object Model selectors, and optical character recognition bounding boxes. This fundamental design flaw created a misaligned maintenance economy:

1. The Broken Selector Maintenance Tax

Every time an enterprise ERP like SAP GUI, TOTVS Protheus, or an external government portal undergoes a minor patch, changes a CSS class, or updates an input layout, the legacy RPA bot crashes with a fatal exception. The transaction queue freezes, orders pile up, and business halts.

Who benefits from this fragility? Traditional IT outsourcing firms and RPA integrators — such as Stefanini, Accenture, and specialized RPA consultancies — that bill hundred-dollar hourly rates on perpetual maintenance retainers to log in and re-record the broken selectors. Companies spend three times more capital fixing broken robots than they ever saved by automating the original task.

2. The Absurdity of Virtual Machine Farms

To run legacy RPA at enterprise scale, companies must maintain dedicated farms of virtual machines running full Windows desktop operating systems.

Think about the sheer architectural waste: spinning up a heavy desktop environment, allocating CPU and RAM, and paying Microsoft Windows Server licensing fees just so a UiPath or Blue Prism script can open an ERP screen, click three form fields, and hit enter.

3. Annual Licenses for Idle Bot Runners

Legacy RPA vendors charge thousands of dollars annually per unattended bot runner. You pay that license fee every twelve months regardless of whether the bot successfully executed a single transaction or spent half the quarter stuck on an unexpected modal dialog.


[Agentes] x [a Gente] — Beyond the hype: how Agentic AI multiplies and leverages human labor capacity. Bi-weekly field notes published in Hugo S. Nascimento's LinkedIn newsletter with over 1,600 subscribers. Follow on LinkedIn ↗

2. Executive Comparison: Legacy RPA vs RPA Integrators vs hsnlabs Protocol Agents

When a CIO or COO evaluates how to automate high-volume backoffice workflows across finance, tax, and supply chain, three distinct models compete:

Architectural and Financial Vector Legacy RPA Platforms - UiPath, Automation Anywhere, Blue Prism Outsourced RPA Maintenance Squads - Stefanini, Accenture, Legacy GSIs Protocol-Level Autonomous Agents - hsnlabs
Execution Mechanism Surface-level UI screen scraping, DOM XPath selectors, and fragile coordinate clicks Manual human intervention to re-record broken selectors after every portal or ERP update Headless protocol execution via REST, database adapters, RFC/BAPI, and Model Context Protocol
Handling of Document Variance Rigid OCR templates that fail when a supplier changes an invoice layout Requires opening a change request ticket and billing hours to build a new template Semantic parsing bound to strict Pydantic v2 ontologies that handle layout variance natively
Infrastructure Footprint Heavy farms of dedicated Windows Virtual Machines with high cloud and OS licensing overhead Dedicated DevOps and support analysts managing bot orchestrators and VM queues Lightweight Docker and Kubernetes containers scaling dynamically in milliseconds
Licensing and Commercial Model Annual recurring fees per unattended bot runner plus orchestrator platform licenses Monthly squad retainers or time-and-materials billing that profits from bot fragility Fixed-scope engineering delivery with 100 percent client code ownership and zero per-bot license tax
Transactional Safety and Governance Blind macro execution; frequently enters invalid data if a screen lags or shifts focus Reactive post-error cleanup after corrupted batches are discovered by business users Deterministic finite state machines in LangGraph with pre-commit invariant validation

3. How Protocol-Level Agents Replace Screen Clickers

At hsnlabs, we do not build systems that emulate human eyes and hands on a desktop screen. We deploy autonomous agents that communicate directly with underlying system protocols:

  • Headless Protocol Execution: An autonomous agent does not search a display for a button labeled Submit Order. It communicates directly with backend services via database adapters, REST endpoints, Model Context Protocol servers, or command line interfaces. A frontend interface redesign has zero impact on system uptime.
  • Robust Handling of Variance: When a traditional RPA bot encounters an invoice layout with an extra line item, it crashes. When an autonomous agent encounters document variance, it parses the payload against an explicit ontology, extracts the verified entities, and applies business rules without manual code patches.
  • Fractional Infrastructure Footprint: By eliminating heavy virtual machine farms, autonomous agents run inside lightweight containers that scale dynamically with transactional volume. Operating costs drop by more than eighty percent while throughput increases tenfold.

The era of paying millions to maintain fragile screen-scraping bots is finished. Enterprise operations belong to autonomous, protocol-level agents that never touch a mouse.



Article originally published on hsnlabs. Author: Hugo S. Nascimento.

Hugo S. Nascimento
Have a project in mind?
Share it with Hugo, CPTO
Start a Conversation