In many enterprises, onboarding a new hire takes weeks. HR sends a checklist, IT hands over credentials, security runs a series of apps, and teams hand out laptops, software, and access. Process owners write SOPs, but someone still has to walk the new person through every step. Meanwhile, the same teams run RPA bots that are supposed to automate the heavy lifting, yet they spend weeks rebuilding bots when the HR portal or security tool changes its layout. The result is a maintenance backlog, stalled onboarding timelines, and processes that only human workers can execute.
Why RPA breaks here
Traditional RPA tools like UiPath, Automation Anywhere, and Power Automate bind to selectors, XPath statements, and object IDs. When the target application updates its UI, these identifiers change, and the bot immediately fails. Teams then spend days or weeks rebuilding and retesting the bot. Industry surveys suggest that 30 to 40 percent of RPA maintenance time goes into rebuilding broken bots after UI changes, not into new automation. A single change to a legacy portal can halt dozens of bots across departments, from procurement to IT service request handling. The process becomes brittle, expensive, and reactive.
What changes with computer use agents
- Survives UI changes because the agent sees and interprets the screen like a human
- No brittle selectors or XPath dependencies to maintain
- Recovers from exceptions instead of halting when something unexpected appears
- Follows SOPs written in plain English, without needing a dedicated flowchart bot
- Works across any application, including legacy systems and virtualized desktops where RPA struggles
Selectors break when the app changes. Seeing the screen makes the bot durable.
How to move without the risk
You do not need to replace all RPA at once. Start with one high-pain process that is SOP-heavy and subject to frequent UI changes, such as new employee provisioning. Document the current steps in plain English, then pilot a computer use agent to run that process. Measure uptime, exception handling, and time saved by human workers. As confidence grows, expand to similar workflows. Keep RPA for high-volume, stable, backend tasks where deterministic control is essential. The phased approach lets you build capability without betting the entire automation program on a single technology.
If RPA bots are breaking every time your applications change, it is time to look at agents that can see the screen and follow your SOPs as written. The Coasty team can show you how to pilot this approach in your environment. Book a demo to start the conversation.
Want to see this in action?
View Case Studies