What is robotic process automation (and where it breaks)?

What RPA actually does

An RPA bot works at the screen layer. It signs into the same application a clerk uses, reads the fields on the page, and re-types them somewhere else. That is the whole trick, and it is why RPA spread through finance, claims processing, and back-office operations: nothing has to change inside the legacy system, so the first automation ships in weeks instead of quarters.

Why it stalls at scale

Screen-level automation inherits every screen change. A vendor moves a button, a login adds a second factor, and the bot stops. Deloitte's survey of 530 business leaders found 4% of organizations running more than 50 bots, up from 3% two years earlier, while 95% reported that RPA improved productivity. Both numbers hold at once. The first bot pays back; the twentieth funds a maintenance team. One practitioner running production bots put the split at 10% of the effort on the happy path and 90% on error and edge-case handling. List prices compound it, around $8,000 per unattended robot per year before orchestrator licensing.

For teams coming from Zapier or n8n

Those tools connect systems that already talk to each other. RPA exists for the systems that do not, which is also why it is more expensive and more fragile to own.

Where RPA still earns its license

Scope it at 50% of a process, not 95%. One RPA engineer describes a project killed after it covered 60% of incoming volume and then chased a 95% target it was never going to reach. Keep bots on high-volume, stable, audit-heavy steps like invoice matching and record migration. Route the judgement work, reading a reply, deciding the next action, handling the exception, to agents instead.