From the source
H Company's newsroom post explains how to estimate the cost of keeping scripted RPA bots running, arguing that break-fix hours, re-runs, exception handling and opportunity cost rarely appear on an invoice.
- It lists six numbers teams already have, including how many bots run in production, how many broke last month, average hours to fix a break, loaded hourly cost of the fixers, monthly exception volume and minutes per exception.
- A worked example with illustrative numbers — 120 production bots, 18 breaks at 6 hours and $85 an hour, and 4,000 exceptions at 7 minutes and $45 an hour — comes to about $9,200 a month in maintenance and about $21,000 a month in exception handling, roughly $360,000 a year.
- The post says the resulting cost per bot sorts an estate into stable and valuable bots to keep, fragile and valuable bots on frequently changing screens, and fragile marginal bots to retire.
- It argues computer-use agents, which look at the screen rather than following coordinates, suit the second group, while bots that run reliably should keep running.
- H Company offers a run-cost calculator that shows every formula and needs no email address, and a free Bot Estate Audit delivered in two weeks from an inventory export and two short workshops.





