Every month, your automation center of excellence logs dozens of hours fixing bots that break when a UI element shifts by a pixel or a legacy app updates a version. Your team spends more time rebuilding and babysitting than on new value. And the processes that really matter, complex, exception-heavy workflows, still run on spreadsheets and manual SOPs because bots cannot follow them without constant patching.
Why RPA breaks here
Traditional RPA tools like UiPath, Automation Anywhere, Blue Prism, and Power Automate automate by binding to selectors, xpaths, and object identifiers. When the application UI changes, the bot fails and a developer must rebuild it. This is the classic maintenance treadmill. A Gartner-style study of enterprise automation programs shows that only 30 to 40 percent of bots delivered in large programs survive six months without significant rework. The rest hit UI drift, version updates, or configuration changes and stall. The cost is not just hours of developer time. It is delayed value, stalled process improvements, and the perception that automation is brittle and high-maintenance.
What changes with computer use agents
- They see the screen and act like a human: move the mouse, click, type, read the result.
- They survive UI and app updates without brittle selectors.
- They recover from exceptions and unexpected states instead of halting.
- They follow SOPs written in plain English, with no flowchart bot to build.
- They run on any application, including legacy systems and Citrix environments where RPA struggles.
Selectors are brittle; computer use agents see the screen and adapt.
How to move without the risk
You do not need to rip out all your RPA at once. A pragmatic, phased approach lets you test the approach on a single high-pain process while keeping existing bots running. Start by choosing a process that is currently manual or heavily patched in RPA: a complex approval workflow, an exception-heavy reconciliation, or a task that lives on a legacy or Citrix system. Map the process to an SOP in plain language. Deploy a computer use agent to pilot it alongside the existing bot. Measure two things: how many exceptions the agent recovers from without human intervention and how much time your team saves on maintenance. If the numbers are solid, expand the pilot to a second process. Over time you can gradually migrate more workflows to agents while RPA remains the right tool for high-volume, stable, backend tasks. The goal is not to replace RPA everywhere but to stop the maintenance treadmill and free your team to build more automation.
The durable way forward for automation teams is to move from brittle, selector-based bots to agents that see the screen and can follow SOPs. Book a demo with the Coasty team to see how your team can start with a pilot and build a more resilient automation program. https://cal.com/coasty/15min
Want to see this in action?
View Case Studies