Cost of Robotic Process Automation in 2026: Licenses, Bots and ROI

The short answer

These ranges cover licenses, infrastructure and development for US companies in 2026, with development at blended vendor rates. The low end of each band is simple, high-volume processes built by a team in Central Europe, Latin America or Asia. The high end is a US consultancy, complex processes with scanned documents and exceptions, and regulated data. Per bot, development runs about $5,000–15,000 for a simple task, $15,000–40,000 for a typical multi-system process and $40,000–100,000 for a complex one.

One disclosure up front. Gilzor builds custom software, integrations and automation code. We're not an RPA vendor and this article doesn't sell a platform. We do get asked "should this be a bot?" in a lot of first calls, and the honest answer depends on whether the systems involved have APIs. More on that below.

What you actually pay for

Every RPA budget has the same five lines, whatever the platform:

1. LicensesDeveloper seats (UiPath Studio, Automation Anywhere Bot Creator, Power Automate makers), attended or unattended bot licenses, and the orchestration platform that schedules and monitors them. Add-ons like document understanding, AI units or process mining are priced separately.
2. Process discovery and designMapping the process as it really runs, including the exceptions nobody wrote down. A process definition document per bot. This is where 10–15% of the budget should go and where cheap projects cut first.
3. Bot development and testingBuilding the workflow, selectors for every screen element, exception handling, logging, retries and testing against real data. The largest one-time line.
4. InfrastructureUnattended bots need a machine to run on: virtual machines with Windows licenses, access to the target applications (often through Citrix or VPN), a credential vault, monitoring. Hosted options bundle this into the license price.
5. Run and maintenanceFixing bots after application updates, handling exceptions, updating credentials, adding new process variants, renewing licenses. Recurring, and the line most business cases underestimate.

RPA license costs: UiPath, Automation Anywhere, Power Automate

Only Microsoft publishes a complete price list. UiPath and Automation Anywhere publish entry points and quote everything else, so the numbers below combine list prices with what third-party pricing trackers and the proposals we see report. Treat them as anchors for negotiation, not quotes.

Two things about this table matter more than the prices. First, one unattended bot can run several processes if their schedules don't overlap, so you rarely need one license per process. A bot that runs invoices at 6 a.m., reconciliations at noon and reports overnight is one license. Second, the Microsoft price looks small because most companies already pay for Microsoft 365. If your processes live in Excel, Outlook, SharePoint and Dynamics, Power Automate is hard to beat on cost. If they live in SAP GUI, a mainframe terminal and three Citrix-published apps, the enterprise platforms earn their premium with better selectors, orchestration and document handling.

For a sense of scale, Gartner forecast that worldwide RPA software revenue would reach $2.9 billion in 2022, up 19.5% from the year before, with double-digit growth to continue. Most of that money is licenses. The development and maintenance spend around it is several times larger.

What one bot costs to build

Bot complexity is driven by three things: how many applications the bot touches, how structured the input is and how many exceptions the process has. Here's what we see in estimates for development and testing of one production bot, at blended 2026 vendor rates:

The most expensive bot is the one built on a broken process. In first calls we regularly hear a process described in five steps that turns out to have four times as many once someone sits next to the person who does it. A bot automates exactly what it's told, so every undocumented workaround becomes either a feature to build or an exception that lands back on a human. Paying for a proper process walkthrough before development, which our business analysis team does as a separate phase, is cheaper than discovering the process during testing.

Where the money goes over three years

Business cases usually compare year-one cost with year-one savings. That flatters RPA in some ways and hurts it in others: licenses and maintenance recur, development doesn't. Here's a typical mid-size program over three years.

Look at the purple block. Bots interact with applications the way a person does: through the screen. When a vendor moves a button, renames a field, adds a login step or changes a web portal, the bot stops. Industry rules of thumb put software maintenance at 15–20% of build cost a year. For screen-driven bots we budget 20–30%, and more for bots working on external websites you don't control.

The failure numbers explain why. Ernst & Young reported that 30–50% of initial RPA projects fail, and Deloitte's global RPA survey found that only 3% of organizations had scaled to 50 or more robots. The common causes are the same ones we hear about in first calls: bots built on undocumented processes, no owner after go-live and maintenance never budgeted.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→E-commerce · AITaking an AI-built e-commerce SEO platform to production→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

RPA vs custom automation code

RPA is one way to automate a process. The other common ways are workflow tools with connectors (Power Automate cloud flows, Zapier, Make) and custom integration code: a small service that calls the systems' APIs, moves the data and logs every step. The question to ask about every process is simple: can the systems involved be reached through an API?

In first calls, we see the same pattern often: a company asks for RPA quotes for a process that moves data between a CRM, an accounting system and a payment provider, all three with documented APIs. A bot can do it, and will need its license and its fixes every year. An integration does it faster and keeps working when the CRM changes its layout. Our API integration cost guide breaks down what those builds cost per system.

The reverse is just as common. A 20-year-old desktop ERP with no API, a government portal, an insurance carrier's website, a terminal emulator: no amount of engineering makes an API appear, and custom screen scraping is RPA without the tooling. That's where an RPA platform is the right buy.

RPA ROI calculator

Enter the processes you want to automate, how much manual time they take and who would build them. The calculator compares the first-year cost with the labor you get back and shows payback and three-year net value. Run it once per approach to compare Power Automate, an enterprise platform and custom code for the same processes.

The default (five typical processes, 60 manual hours each per month, built by a Central European team on an enterprise platform) comes out at about $65,000 to build, $26,000 a year in licenses and VMs and $16,000 in maintenance. It frees about $88,000 of staff time a year and pays back in around 17 months. Switch to Power Automate and payback drops to about ten months, mostly because the license line shrinks. Switch to custom code and the build cost rises, but the running cost falls enough to beat the enterprise platform on three-year value. Push the manual hours down to 15 and watch the enterprise option stop paying back at all: volume, not technology, decides RPA ROI.

The calculator counts freed staff time at full loaded cost. In practice the savings arrive as capacity (the same team handles more volume, closes the books faster, stops hiring temps for the quarter-end peak) more often than as headcount reduction. For reference, the US Bureau of Labor Statistics put the median wage for bookkeeping, accounting and auditing clerks at $49,210 a year in May 2024, about $23.66 an hour before benefits and overhead. A loaded cost of $33–40 an hour is a fair default for back-office work.

RPA, low-code or custom code? A quick check

Six questions about your processes and systems. The result points to the approach that usually gives the lowest cost of ownership for that profile.

The hidden costs of RPA

These are the lines that don't make it into the vendor's ROI slide, roughly in the order buyers discover them:

One more cost doesn't appear in any invoice: the processes you can't change because a bot depends on them. Once a bot is built around a screen, improving that screen, upgrading the application or reorganizing the team means touching the bot too. Teams with dozens of bots often find their automation has become the reason legacy software stays.

Rates by region for RPA and automation work

Licenses cost the same wherever your developers sit. Development and maintenance don't. Here's a 1,200-hour program (six typical bots or integrations with discovery, testing and hypercare) at 2026 rates for senior automation developers:

Automation work has an unusual time-zone profile. Discovery needs a lot of overlap: someone has to watch the person who does the job, ask about the exceptions and confirm the edge cases. Development and maintenance need much less, and a team ahead of US time can fix a bot that broke overnight before the US business day starts. Gilzor's teams are in Poland and Cyprus, which puts us in the Central European row: offshore for US clients, with a few shared hours in the US morning. Our guide to nearshore software development rates compares the regions in more depth.

How to reduce the cost of RPA without breaking the automation

1. Pick processes by volume, not by annoyanceThe process everyone complains about may take six hours a month. Rank candidates by hours times frequency and automate the top of the list.
2. Use APIs wherever they existMost RPA platforms can call APIs too. A bot that reads one legacy screen and posts the result through an API is cheaper to maintain than one that clicks through four applications.
3. Pack processes onto fewer botsSchedule unattended work so one license and one machine serve several processes. This alone can cut the license line in half.
4. Start on the platform you already pay forIf you're on Microsoft 365, prove the value on Power Automate before buying an enterprise platform. Move only when you hit its limits.
5. Fix and standardize the process firstEvery variant you remove is an exception path you don't build, test or maintain.
6. Test bots like softwareRegression tests against a staging copy of each application catch breakages before production does. Our QA team builds suites like these; the economics are in our guide to test automation cost savings.
7. Budget maintenance from day oneA business case without 20–30% a year for upkeep is a business case for a bot that will stop working.

Three budgets, worked through

Typical requests from US companies, priced with the ranges above. Illustrative, not Gilzor quotes.

1. Accounts payable at a 200-person distributor

Invoices arrive as PDFs by email, get keyed into a desktop accounting system with no usable API and matched to purchase orders in Excel. About 160 staff hours a month. Two Power Automate Process bots with AI Builder for invoice extraction, plus two Premium makers: under $5,000 a year in licenses. Build and testing about 300–400 hours: $18,000–26,000 with a Central European or Latin American team, $48,000–64,000 with a US firm. At a loaded $35 an hour and 70% automation, the bots free about $47,000 of staff time a year.

2. Claims intake at a regional insurer

Eight processes across a policy administration system on a terminal emulator, a carrier portal and a document management system. Enterprise RPA with document understanding, four unattended robots, a credential vault and audit logging. Licenses around $45,000–70,000 a year depending on negotiation. Build about 2,000–2,600 hours: $100,000–170,000 offshore or nearshore, $260,000–420,000 onshore. Maintenance budget of $30,000–45,000 a year, mostly for the carrier portal bot.

3. Order sync for a B2B SaaS company

Orders flow from a web shop to a CRM, an invoicing tool and a warehouse system, all with REST APIs. The first quote they got was for three RPA bots. A custom integration service with queues, retries and an error dashboard takes about 450–600 hours: $27,000–39,000 offshore, $70,000–96,000 onshore. Hosting runs under $150 a month, there are no bot licenses and it processes orders in seconds rather than in scheduled batches. For builds like this our web development team handles the service and the monitoring.

FAQ

How we approach automation at Gilzor

We build custom integrations, automation services and the internal tools around them, and we start every automation request the same way: a walkthrough of the process and a check of which systems can be reached through an API. Where they can, we write integration code your team owns, with no per-bot license. Where a legacy screen is the only way in, we say so, and RPA may be the right tool for that part. We price discovery, build and maintenance as separate lines so the three-year cost is visible before you commit. When the automation needs to read documents or emails, our AI and ML team adds extraction and classification. If automation is one piece of a larger program, our guide to digital transformation cost covers the bigger budget.