The Real Reason Your RPA Center of Excellence Has a Six Month Backlog
Your RPA center of excellence is not understaffed. It is structurally blocked. A typical large enterprise reports that up to 70 percent of RPA maintenance time goes into fixing selector issues and adapting to minor UI changes. Each broken bot can require eight or more hours of developer time to rebuild. When the backlog hits six months, the team is not waiting for more bodies. They are waiting for a more durable automation pattern that does not break every time a form layout shifts or a release moves a button a few pixels.
Why RPA breaks here
Traditional RPA tools such as UiPath, Automation Anywhere, Blue Prism, and Power Automate rely on brittle selectors, HTML IDs, XPaths, CSS classes, or image-based targets. Automation behaves predictably only when these selectors remain stable. In practice, apps and websites update frequently. A patch can change an ID, reorder a list, or introduce dynamic classes. When the selector no longer matches, the bot halts or behaves unpredictably. Industry estimates suggest that more than 60 percent of RPA workflows break on a given UI change. Each outage requires a developer to locate the new selector, update the activity, and retest. That is a rebuild-on-every-change cost. For a midsize enterprise with hundreds of bots, those rebuilds accumulate. The center of excellence spends its time on maintenance instead of new projects. The backlog grows until leadership sees a six-month wait for any new automation.
What changes with computer use agents
- ●Survives UI changes because agents see the screen and act like a human, not a selector hunter.
- ●No brittle selectors required. Agents read the interface and adjust dynamically.
- ●Recovers from exceptions and unexpected states instead of halting. If a message appears or a form is incomplete, the agent can interpret the context and self-correct.
- ●Follows the SOP as written. A process described in plain English is already a prompt. Computer use agents can consume it directly, without building a flowchart bot.
- ●Works across legacy desktops, Citrix environments, and virtualized terminals where traditional RPA struggles due to accessibility and rendering constraints.
The one line a VP of automation should remember: traditional RPA builds brittle bridges to fragile targets, while computer use agents see the interface and adapt, so you stop running a maintenance treadmill and start scaling automation.
How to move without the risk
You do not need to rip out all RPA at once. A pragmatic, phased path minimizes disruption. First, identify one high-pain process that is currently blocked in the backlog. Look for workflows that involve frequent UI updates, exception handling, or handoffs that rely on human judgment. Document the process as a standard operating procedure in plain English. Run a pilot with a computer use agent on that process. Measure the time it takes the agent to complete end-to-end compared with the current manual or RPA approach. If the agent reduces cycle time or handles edge cases better, expand to similar workflows. Over time, the share of your automation portfolio that relies on computer use grows while the brittle selector-based bots are retired. This approach lets you keep what works in high-volume, stable backends and replace the rest with agents that survive change.
What this means for your roadmap
The six-month backlog is not a capacity issue. It is a pattern issue. When you move from selector-based bots to agents that see and adapt, you reduce rebuild cycles and exception handling overhead. You free your development resources to build more automation instead of fixing broken bots. You also unlock the long tail of SOP-driven work that has been impossible to automate at scale. The result is a more resilient automation portfolio that can keep pace with application updates and changing business requirements.
If your RPA center of excellence has been blocked by a six-month backlog, the real reason is not headcount. It is a reliance on brittle selectors and rebuild-on-change processes. Computer use agents change that equation by seeing the interface and adapting to it. To see how your own high-pain workflows could run on agents instead of selectors, book a demo with the Coasty team at https://cal.com/coasty/15min .