RPA consulting: when a bot is the right answer, and when it is not
Robotic process automation (RPA) uses software that clicks and types through a screen the way a person would. It is a useful tool for one specific situation, and an expensive habit outside it.
When RPA is a good fit
- The system has no usable API, or the vendor charges heavily for one. A legacy desktop ERP is the classic case.
- The task is repetitive, rule-based and high-volume: tens or hundreds of cases a day.
- The screens and inputs are stable. A bot cannot cope with a layout that changes every release.
- The cost of a manual error is moderate, and every run can be logged and checked.
When it is not
If the system offers an API or a built-in import, use that. It is faster, cheaper to run and far less fragile. If the process needs judgement on most cases, a bot will either stall or guess. If the process is badly designed, a bot makes it fail faster. The longer comparison is in RPA vs traditional automation.
How an RPA engagement runs
- Process selection. We score candidates on volume, stability, rule clarity and exception rate, and usually recommend one or two, not ten.
- Design document. Every click, every field, every exception path, agreed with the people who do the task today.
- Pilot. One process, one bot, running in parallel with the manual work for a few weeks with every result compared.
- Controls. Dedicated credentials, least-privilege access, an audit log and a stop button someone knows how to press.
- Run and maintain. Named owner, monitoring, and a plan for when the underlying application updates.
The cost people forget
Licences are the visible cost. The larger cost over three years is maintenance: bots break when a screen changes, a password expires or a pop-up appears. We include a maintenance estimate in every proposal and show the break-even against doing the work by hand, so you can see whether the case holds.
Related work
Where an API exists, process automation on Zapier, Make, n8n or Power Automate is usually the better route. The distributor example in RPA for order entry shows a case where RPA was the right call.
Common questions
Is RPA the same as AI?
No. RPA follows fixed rules and repeats the same steps. It can be combined with document reading or language tools, but the core is rule-following, which is why it needs stable inputs.
Which RPA tools do you use?
We choose by fit and cost: Power Automate Desktop where you are already on Microsoft 365, and dedicated RPA platforms for larger or regulated volumes. We tell you the licence cost before you commit.
How many processes should we start with?
One. A single well-chosen pilot teaches you more about maintenance and controls than a portfolio of five that nobody has time to watch.
Related reading and services
Want to fix a process like this?
Book a free process review. Bring one slow process and leave with three improvement ideas.
Book a free review