What are RPA tools, in practical terms? Software that operates existing screens the way a person would, clicking, typing, reading, without an API connection underneath. Most comparisons of these tools line up vendor licence prices side by side, as if the licence fee is the cost. It isn't, not even close. This covers what you're actually paying for, structure first, vendor second.
What Are RPA Tools?
What they do. RPA software tools automate a task by operating a system's own interface, the same screens a person already uses, rather than connecting through an API. That makes them useful for exactly the systems that don't offer a good API to connect to.
Where a typical RPA tools list stops short. Most RPA tools list content stops at naming the big vendors and comparing their licence prices. That comparison answers a much smaller question than the one a buyer actually needs answered, which is what the total cost looks like once the licence is just one line item among several.
Licensing Is a Minority of What You're Paying For
Independent cost breakdowns put licensing at roughly a quarter to a third of total RPA spend, with the rest going to development, infrastructure, and ongoing maintenance. Gartner's forecast that worldwide RPA software spending would reach $2.9 billion in 2022, up 19.5% year over year, frames the market this licensing question sits inside, a market growing fast enough that the cost-structure question only gets more relevant, not less.
The Real Cost Lever: Attended vs. Unattended
Attended bots: cheaper, human-triggered. An attended bot runs on a person's own machine, triggered on command to handle a repetitive step inside a task that person is already doing. It's the cheaper end of RPA tools because it doesn't need its own infrastructure.
Unattended bots: pricier, need their own compute and a schedule. An unattended bot runs independently, on its own schedule, without a person triggering it. That independence is exactly what costs more: it needs dedicated compute and a live connection to something that can schedule and monitor it.
Orchestrator: the licence most buyers forget to scope. An orchestrator is the control layer that schedules, monitors, and logs every bot, attended or unattended. It's often quoted separately from bot licences, which makes it easy to underbudget when a buyer is comparing headline licence prices instead of the full stack.
Credential store: bots need stored logins, and that's a security decision, not a footnote. An unattended bot needs somewhere to securely store the login credentials it uses to access other systems. That's a genuine security requirement, not a checkbox, and it's largely absent from comparison content that focuses on licence price instead.
Development and maintenance sit underneath all four of these and are consistently the highest real cost, even though it's the line most absent from vendor comparison content. Building the automation is only the start; keeping it working when a screen changes, a field moves, or a system gets upgraded is ongoing work for as long as the automation runs, and it's the cost that a one-time licence comparison never captures.
What You're Actually Paying For, Component by Component
Bot licence (attended)
What it covers: A bot that runs on a person's machine, triggered on command
Why it's easy to miss when scoping: Looks cheap in isolation, but doesn't scale past one person's workload
Bot licence (unattended)
What it covers: A bot that runs independently on its own schedule
Why it's easy to miss when scoping: Needs dedicated compute and a live orchestrator connection, both cost extra
Orchestrator
What it covers: The control layer that schedules, monitors, and logs every bot
Why it's easy to miss when scoping: Often quoted separately from bot licences, and easy to underbudget
Development and maintenance
What it covers: Building the automation and keeping it working when a screen changes
Why it's easy to miss when scoping: Consistently the largest real cost, even though it's absent from most price comparisons
Credential store
What it covers: Secure storage for the logins bots use to access systems
Why it's easy to miss when scoping: A genuine security requirement, not a checkbox
Where Burhani Fits
We work with RPA platforms including UiPath and Automation Anywhere as part of process automation engagements, scoping the full cost structure, not just a licence quote, before recommending an approach. "RPA for SAP" covers a specific vertical use case, and "Workflow Automation Tools" compares tool categories against an approval chain's needs; this post is about cost structure specifically, across any RPA use case. This fits a buyer who wants the real number before committing. It's not a fit for someone who just wants a licence quote to compare against another licence quote.
FAQs on RPA Tools
What are RPA tools?
RPA tools are software that operates an existing system's interface the way a person would, clicking, typing, and reading screens, to automate a repetitive task without needing an API connection underneath.
What is the difference between an attended and unattended bot?
An attended bot runs on a person's machine, triggered on command as part of a task they're already doing. An unattended bot runs independently on its own schedule, which needs its own compute and a live orchestrator connection, and costs more as a result.
What does an orchestrator do?
An orchestrator is the control layer that schedules, monitors, and logs every bot running across an organization. It's typically licensed separately from individual bots, which makes it a common line item buyers forget to scope in early.
Is licensing the highest cost in an RPA project?
No. Independent cost breakdowns put licensing at roughly a quarter to a third of total spend. Development and ongoing maintenance, keeping automations working as the underlying screens change, is consistently the higher real cost.
How do RPA tools store login credentials securely?
Through a dedicated credential store that keeps bot login details encrypted and separate from the automation logic itself, rather than embedded in a script. It's a genuine security requirement for any unattended bot accessing systems on its own schedule.
The Bottom Line
The licence price is the smallest part of the real question. Attended versus unattended, the orchestrator, development and maintenance, and the credential store together decide what an RPA project actually costs, long after the licence comparison table has stopped being useful.
Talk to our team about the task you're automating, and whether it needs to run with or without someone triggering it.
