The 10/90 Rule of RPA: Building Is Easy, Maintaining Is Everything
Most RPA work is not building. It is maintaining. The ratio is roughly 10% build, 90% maintain.
Where the 90% of Effort Goes
That sounds wrong until you have done it. Building a desktop automation takes maybe a week. Keeping it alive over the next 12 months is where all the engineering time goes.
UI updates break existing workflows. A vendor pushes an update, a button moves, a field gets renamed. Your automation keeps clicking where the button used to be.
New edge cases appear that did not exist during testing. A dialog you have never seen before. A patient record in a format your parsing code does not handle. A date field that accepts slashes at one clinic but dashes at another.
The VM environment degrades. Memory leaks after thousands of runs. Session timeouts. OS updates that restart the machine at the worst possible time.
A field that loaded in one second now takes three because the server is under heavy load. Your automation clicks too early and types into the wrong input.
None of these are hard to fix individually. But they happen constantly. And each one needs a human to investigate, understand, and resolve.
This is why RPA teams grow linearly with the number of automations. It is not the building that drives headcount. It is the maintenance.
What Changes the Maintenance Equation
The approach that changes this equation has two parts:
First, catch failures the moment they happen. If your engineer gets a real-time alert with screenshots and execution context, the fix takes ten minutes. If they find out Monday morning from a customer complaint, the investigation takes half a day.
Second, build agents that handle the common failure modes automatically. An agent that can detect a misclick and retry, dismiss an unexpected dialog, or adapt to a moved button eliminates the majority of maintenance tickets before they reach a human.
Most of the "maintenance burden" in RPA is actually an "investigation burden." Reduce the time to understand what went wrong and the whole equation changes.
Want to see this in action?
We ship EHR automations in weeks, not months. See what production looks like for your workflows.
Book a Demo