By 2026 most enterprises will still run automation on a mix of legacy RPA and human SOPs. The cost is clear: a backlog of broken bots, endless rebuilds, and processes that only people can execute. The opportunity is to treat SOPs as prompts and run them on agents that actually see and adapt to the screen.
Why RPA breaks here
Traditional RPA engines like UiPath, Automation Anywhere, Blue Prism, and Power Automate rely on selectors, XPath strings, and object IDs. When a vendor upgrades a UI, rebrands a page, or moves a control to another layer, the bot halts or produces wrong output. Industry estimates suggest that 30 to 40 percent of RPA maintenance time is spent relinking or rebuilding bots after the simplest UI change. One large European insurer reported that a single HR onboarding bot required a full rebuild every 12 weeks, costing nearly €70,000 annually in development and rework. That is the maintenance treadmill: every UI update forces a new human cycle.
What changes with computer use agents
- Survives UI changes. Agents see the screen and use natural language to locate elements, so a button moving three pixels to the right does not break the workflow.
- No brittle selectors. No more fragile XPath or ID mapping. The agent reads and reasons about the visual layout instead of relying on fixed references.
- Recovers from exceptions. When a field is empty, a CAPTCHA appears, or a network error occurs, agents can pause, ask for guidance, retry, or switch to an alternative path rather than crashing.
- Follows the SOP as written. A standard operating procedure expressed in plain English is already a prompt. Agents can interpret those steps and execute them directly across any app.
- Works on legacy and Citrix. Agents operate at the OS level, so they can run on terminal servers, virtual desktops, and Citrix environments where traditional RPA struggles or requires expensive adapters.
Legacy RPA is excellent for high-volume, stable, backend tasks. Computer use agents are the durable answer for changing UIs, exception-heavy processes, and SOP-driven workflows.
How to move without the risk
You do not need to rip out all RPA at once. Start with one high-pain process where the UI changes often or the process is largely SOP-based, such as order entry, vendor onboarding, or compliance file collection. Map the process to a written SOP, then run a small pilot using a computer use agent. Measure how many failures and rebuilds disappear, and how much time the process saves. Expand to adjacent workflows once you see the pattern. Keep RPA for workloads with predictable, stable UIs and heavy volume, and let agents handle the long tail. This phased approach lets you benefit from new automation patterns without rolling into a single vendor overnight.
Your SOPs are already automation prompts. The question is whether you’ll run them on bots that break on every UI change or on agents that see and adapt like a human. To explore how computer use agents can replace brittle bots and turn SOPs into durable automation, book a demo with the Coasty team at https://cal.com/coasty/15min .
Want to see this in action?
View Case Studies