Automate a 40-Step SOP Without Writing a Single Selector
You probably have a 40-step SOP sitting next to your monitor right now. It describes exactly how your team validates invoices, reconciles accounts, or onboards new employees. The process is stable enough that humans can run it reliably. But the automation you built on top of it breaks every time the system updates a button label, moves a field, or changes its layout. That is the RPA maintenance treadmill. Your team spends more time fixing bots than running them.
Why RPA breaks here
Traditional RPA automates by binding to UI elements using selectors, XPath, or object IDs. These bindings are brittle. When an enterprise application ships a new version, even a minor UI tweak, the selector can break. Your bot stops at that step and requires a developer to revisit the workflow. A Forrester-style study of enterprise RPA costs shows that roughly 30 to 40 percent of automation time goes into maintenance and rework after the initial build. If your team maintains ten bots, two to four of those hours each week are spent on rework. That is not automation. That is maintenance.
What changes with computer use agents
- ●Survives UI changes without rebuilding the workflow. Coasty agents see the screen and act like a human. They move the mouse, click, and type based on visual context instead of a fixed selector.
- ●No brittle selectors required. The agent reads the screen and adapts to new layouts, new applications, or even different browser versions.
- ●Recovers from exceptions instead of halting. If a validation fails or a popup appears, the agent can read the error message and decide the next step, rather than crashing.
- ●Follows the SOP as written. A standard operating procedure in plain English is already almost a prompt. The agent follows it directly, without needing a flowchart bot or a developer to map every click.
- ●Works on legacy systems and Citrix where traditional RPA struggles. Because the agent controls the desktop directly, it can operate in environments that block API calls or rely on virtualized displays.
The one line a VP of automation should remember: selectors break when the app changes, but agents that see the screen adapt.
How to move without the risk
You do not need to rip out all your existing RPA overnight. Start with a single high-pain process that meets three criteria. It should be documentable in plain English, have a clear end-to-end flow, and contain many small, variable steps like validation checks and form edits. Build a prototype with Coasty by feeding the SOP directly to the agent. Compare the time the human takes versus the agent over a week of runs. Track how often the agent needs human intervention versus the RPA bot. If the agent reduces time per run by 30 to 50 percent and requires less rework, expand to similar processes. Use the successful pilot to justify a broader initiative that includes both RPA and computer use agents. The goal is to move the right work to the right automation technology, not to replace everything at once.
The 40-step SOP you wrote down last month does not need to stay a manual process. Computer use agents can follow it without any selectors, adapt to changes, and recover from errors. If you want to see how a Coasty agent can run your own SOP in a live desktop environment, book a demo with the Coasty team at https://cal.com/coasty/15min .