Back to Blog
Migration

Daniel Kim7 min
⇧+Tab

Your Blue Prism bots are already handling some of the dirty work. But every time the vendor updates a field name or your team rolls out a new portal, a developer has to rebuild the workflow. That is the maintenance treadmill. Most automation leaders I talk to have a backlog of bot fixes that never gets smaller. There is also a second, quieter issue: many standard operating procedures sit in PDFs or wikis that no bot can touch because they aren’t written in a language a robot can follow. That is where computer use agents start to make sense.

Why RPA breaks here

Blue Prism and its peers automate by binding to selectors, XPath expressions, or object IDs. These are brittle. When an element moves, changes class, or gets wrapped in a new container, the bot halts. In large organizations, UI churn is constant. New CRM releases, portal redesigns, and security patches all break selectors. The result is not just lost time. It is a growing cost burden. Industry surveys suggest that maintenance can consume 40, 60 percent of the total automation budget. Every change that requires a developer to rebuild a bot is a direct hit to ROI. The process looks solid on paper, but in production it becomes a patchwork of temporary fixes.

What changes with computer use agents

  • Agents see the screen, so they adjust when UIs change.
  • No brittle selectors or object repositories to maintain.
  • They recover from errors instead of stopping on unexpected states.
  • They can read and follow SOPs written in plain English.
  • They work across any application, including legacy systems and Citrix virtual desktops.

The one line a VP of automation should remember: computer use agents replace fragile selectors with a human-like ability to see and adapt.

How to move without the risk

You do not need to rip and replace everything tomorrow. Start with a single high-pain process where UI changes frequently and the process is documented in a standard operating procedure. For example, an onboarding workflow that touches multiple systems, each with its own portal design. Build a pilot using a computer use agent to follow the SOP step by step. Compare the time it takes the agent to complete the task versus the existing manual effort and the current bot. Measure how often the agent encounters a UI change and how it recovers. Use that data to decide which processes are good candidates for a broader rollout. Over time, you can extend the agent layer to other workflows while keeping your existing RPA for high-volume, stable, backend tasks. This hybrid approach ensures you get the durability of agents where it matters most, without abandoning what is working.

RPA still plays a role in your automation portfolio, but the long tail of changing UIs and SOP-driven work is better handled by agents that can see and adapt. If you want to see how a computer use agent can follow your SOPs and recover from the same interruptions that stop your Blue Prism bots, book a demo with the Coasty team to explore the next step for your automation strategy.

© 2026 Coasty

Backed byYCombinator