# H Company — RPA maintenance costs: what your bots really cost to run

- Company: H Company (hcompany.ai)
- Announced: 2026-10-20
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://hcompany.ai/newsroom/rpa-maintenance-cost
- Record: https://forck.live/items/35070-rpa-maintenance-costs-what-your-bots-really-cost-to-run
- Subject: Holo

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.

## Evidence

Verbatim from https://hcompany.ai/newsroom/rpa-maintenance-cost:

> Bot licenses are easy to count. The hours spent keeping bots alive are not. Here is how to put a number on them, bot by bot.
> 
> Insights October 20, 2026 · 4 min read
> 
> Picture the automation lead at a mid-sized insurer at 7:10 on a Monday. Overnight, a broker portal moved its policy-number field two inches to the right. Forty-one claims sit in an exception queue. The bot that should have filed them did exactly what it was built to do: it looked for the field where it used to be, didn't find it, and stopped.
> 
> By 9:30 a developer has patched the selector. By noon the backlog is cleared by hand. Nobody records the morning as a cost. It shows up later, spread across a team that never seems to get to the new automations on its roadmap.
> 
> That morning is the line item most automation budgets leave out.
> 
> Licenses are the visible part
> 
> When a scripted-automation program is reviewed, the conversation usually starts with what is easy to count: licenses, infrastructure and the number of bots in production. Those are real costs, and they arrive on an invoice.
> 
> The costs that don't arrive on an invoice are harder to see:
> 
> Break-fix time.

---

Record: https://forck.live/items/35070-rpa-maintenance-costs-what-your-bots-really-cost-to-run
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
