Guide

Automate a 40 Step SOP Without Writing a Single Selector

David Park||7 min
+K

Your team has a solid SOP for a finance or operations workflow. Forty steps. Clear instructions. But the only people who can run it reliably are the same analysts who wrote it. Backlogs pile up. New hires struggle. And when you finally build an RPA bot, it breaks the first time the vendor updates the portal, or a user resizes a window. Then you’re back in the rebuild cycle.

Why RPA breaks here

Traditional RPA relies on selectors, object IDs, and xpaths. These are brittle links to a specific UI layout. When a vendor changes a field name or reorders rows, the bot fails. In many enterprises, selector drift now costs an average of five days per incident. That includes investigation, developer time to rebuild, re‑testing, and redeployment. Over a year, a mid‑size RPA estate can spend weeks on maintenance instead of new value. For a 40‑step process that changes quarterly, the cost adds up fast. The bot isn’t just a one‑time build. It becomes a recurring project.

What changes with computer use agents

  • Survives UI changes
  • No brittle selectors
  • Recovers from exceptions
  • Follows the SOP as written
  • Works on legacy and Citrix

Computer use agents see the screen and act like a human, so they work across any app and adapt when the layout changes.

How to move without the risk

You do not need to rip out all RPA at once. Start with one high‑pain process that is SOP‑driven, exception‑heavy, or sits on a legacy platform. Run it as a pilot with a computer use agent. Compare the cost of maintenance against your current bot. If the agent reduces downtime and developer effort, expand to similar workflows. Keep running your stable, high‑volume, deterministic RPA tasks unchanged. That hybrid approach lets you benefit from agents on the long tail where RPA struggles, without abandoning proven work. For many enterprises, this phased path cuts new automation backlog while improving reliability.

Computer use agents finally let you automate SOPs as they are written, without brittle selectors or endless rebuilds. If you want to see how a 40‑step process runs on an agent, book a demo with the Coasty team at https://cal.com/coasty/15min.

Want to see this in action?

View Case Studies
Try Coasty Free