IDP plus RPA vs a single computer use agent for document workflows
Most large enterprises already run an OCR platform to extract data from invoices, forms, and contracts, and pair it with an RPA bot to move that data into ERP and CRM systems. This two-part stack works for a while, then breaks. A UI update, a new vendor portal, or a slight layout change can stop the bot mid-task. IT teams spend weeks rebuilding selectors and fixing exceptions, while business users wait for the fix. The real cost is not the development hours. It is the accumulated backlog of processes that never get automated because the pain of fixing them outweighs the value.
Why RPA breaks here
Traditional RPA maps every input field to a selector, XPath, or object ID. When the document layout changes, the bot fails. A 2023 industry survey of RPA centers of excellence found that about 30 percent of bot maintenance time goes into fixing selector failures caused by UI updates. For document workflows, this problem is worse because layouts vary by vendor, by version, and sometimes even by user. To keep the bots running, teams rebuild workflows constantly. They also introduce workaround code to handle exceptions, which further increases complexity. The result is a high total cost of ownership that grows over time, not shrinks.
What changes with computer use agents
- ●Survives UI changes , The agent reads the screen, locates the next field or button, and acts. It does not rely on a brittle selector map.
- ●No brittle selectors , There are no xpaths or object IDs to maintain. The agent works as long as the text and layout are recognizable.
- ●Recovers from exceptions , If the document looks different than expected, the agent can retry, ask for clarification, or move to the next step instead of halting.
- ●Follows the SOP as written , A standard operating procedure in plain English is already a prompt. Computer use agents interpret it directly, with no flowchart bot to build and babysit.
- ●Works on legacy and Citrix , Because the agent sees the screen, it can operate in environments where traditional RPA cannot, including virtualized desktops and legacy apps.
The one line a VP of automation should remember: RPA with brittle selectors is a maintenance treadmill, while computer use agents survive change and follow SOPs without extra engineering.
How to move without the risk
You do not need to rip out all RPA at once. Start with a single, high-pain document process that currently runs on IDP plus RPA, or that lives on manual SOPs. Run a pilot with a computer use agent. Measure uptime, error rates, and maintenance effort. Compare that to the cost of keeping the RPA bot alive. If the agent delivers higher uptime and lower maintenance, expand to similar processes. Reserve traditional RPA for high-volume, deterministic backend tasks that rarely change. This phased approach lets you capture value while staying honest about where each technology fits.
The durable way forward for document workflows is not another layer of RPA or another IDP integration. It is an agent that sees the screen and follows SOPs without brittle selectors. If you want to see how a computer use agent can replace IDP plus RPA for your most painful document processes, book a demo with the Coasty team at https://cal.com/coasty/15min .