Your company has a standard operating procedure for supplier onboarding. It exists in a PDF, a SharePoint page, or a handbook. A team member follows it line by line. A robot built with UiPath, Automation Anywhere, or Power Automate should do the same thing. But five months later the procurement system gets a redesigned UI and the bot starts failing. The developer fixes selectors, the bot runs for a week, and then the finance module updates again. This is the maintenance treadmill that most enterprises know well. The SOP never changes. The automation does, again and again.
Why RPA breaks here
Traditional RPA works by binding to specific UI elements. It uses selectors, xpaths, or object IDs to click a button, fill a field, or extract a value. When the application vendor upgrades the layout, renames a field, or shifts a menu to a different tab, those bindings become invalid. The bot returns an error or clicks the wrong thing. The development team must inspect the new UI, rebuild the selectors, update the bot, and test again. Gartner estimates that 40 to 60 percent of an RPA project’s total cost of ownership comes from maintenance and rework, not from initial development. In many organizations, the backlog of bots needing repair grows faster than the team can fix them. The SOP remains unchanged, and the automation becomes a liability.
What changes with computer use agents
- Agents see the screen and act like a human, moving the mouse, clicking, and typing. They do not rely on brittle selectors or xpaths.
- When the UI changes, the agent recognizes the new layout and finds the next logical step. No selector rebuild is needed.
- Agents recover from exceptions. If a dialog appears, a timeout occurs, or a result is missing, the agent can pause, inspect the screen, and choose a next action instead of halting.
- The SOP is written in plain English. The agent reads it directly and follows the steps without a separate flowchart bot.
- Computer use agents work across any application, including legacy enterprise systems, Citrix environments, and virtualized desktops where traditional RPA struggles.
A VP of automation should remember this one line: when the application changes, the bot should adapt, not break.
How to move without the risk
You do not need to rip out all existing RPA overnight. Start with a process where the SOP is clear and the UI changes frequently. Supplier onboarding, expense report processing, and contract review are good candidates. Choose a single workflow where the team already documents step-by-step instructions. Run a pilot with a computer use agent. Let it follow the SOP and complete the workflow end-to-end in a staging environment. Compare the number of exceptions, the time to fix a broken process, and the effort required to maintain the automation. If the agent handles changes without rework, expand to other similar processes. Reserve traditional RPA for high-volume, stable, backend tasks like batch file transfers or report generation. Over time, you can migrate more work to agents that align directly with your written procedures.
Your SOPs should be the source of truth for automation, not a document that the bot ignores. Computer use agents can follow your doc as written and adapt when the app changes. To see how Coasty agents align with your processes and survive real-world UI updates, book a demo with the Coasty team at https://cal.com/coasty/15min .
Want to see this in action?
View Case Studies