Explainer graphic: what RPA is, where it saves money, how it differs from AI agents, and five checks before buying
RPA bots copy clicks and keystrokes; agents decide what to do. The savings depend on which one your job needs.

Somebody in every office spends Friday afternoon copying numbers from one screen into another. Robotic process automation, or RPA, is the software that does that copying for you. Searches for it are climbing again: Exploding Topics lists RPA at 246,000 searches with 287 percent growth, mostly because everyone now wants to know how it differs from an AI agent.

The short answer: RPA is a recorded script that drives a screen the way a person would. It saves real money on boring, high-volume, rule-bound work. It is not intelligent, it breaks when the screen changes, and it is cheaper than you think for one desk and dearer than you think for twenty.

What RPA actually is

IBM describes it as scripts that mix application interfaces with plain user-interface actions: open this app, read that cell, paste it here, click save. The bot works on the presentation layer, so nothing in your existing systems has to change, which is also why it works with old software that has no proper connection.

There are two flavours. An attended bot runs on your own PC while you watch, like a macro with ambitions. An unattended bot runs on a server or virtual machine on a schedule, with nobody logged in. Microsoft's desktop flows docs pitch both at everyone from home users scraping a weather site to a sole trader pulling data off vendor invoices.

Where the savings are real

The market is not small. Gartner's analyst told PEX Network in June 2025 that RPA software earned 3.8 billion dollars in 2024, up 18 percent. IBM cites a Forrester finding that 36 percent of RPA use cases sit in finance and accounting, which tells you where the money is.

Which jobs pay back, and which do not
TaskGood RPA fit?Why
Keying supplier invoices into accountsYesSame fields, same screens, hundreds a month
Copying web orders into a stock systemYesRule-based, runs at night, easy to check
Monthly report built from three exportsYesPredictable, boring, error-prone by hand
Answering customer emailsNoNeeds judgement; that is agent territory
A task you do twice a monthNoBuild time outweighs the minutes saved
Anything on a site that redesigns oftenNoBot breaks with every layout change

The catch is upkeep. A Workato piece from September 2026 calls it an RPA tax: a portal update can break a bot overnight, and every new process adds another bot to test and maintain. Back in 2019, a CIO column quoted Deloitte and EY surveys finding roughly half of RPA projects failed, mostly through broken bots and over-ambitious scope. IBM still cites Forrester's figure that 52 percent of customers struggle to scale.

RPA versus AI agents

An RPA bot follows a fixed path. An AI agent reads a goal, works out steps, and adapts when something unexpected appears. UiPath, the biggest RPA vendor, now describes its bots as the execution layer that agents call: agents plan and decide, robots do the clicking, humans handle the exceptions. We covered what an AI agent is in more detail.

Be careful with labels. In June 2025 Gartner predicted that over 40 percent of agentic AI projects would be cancelled by the end of 2027, and warned of agent washing, where vendors rebrand chatbots and plain RPA as agents. By Gartner's count, only about 130 of the thousands of agentic vendors were the real thing.

So the honest rule: if the task can be written as if-this-then-that, buy RPA and expect it to be dull and reliable. If the task needs reading, judging or negotiating, you need an agent, plus the budget to supervise it.

What it costs a small business

Entry prices are low. Microsoft's Power Automate charges 15 dollars per user per month for attended desktop bots, 150 dollars per bot per month for unattended runs, and 215 dollars on a Microsoft-hosted machine, all billed yearly. UiPath's Community edition is free, and its Basic plan starts at 25 dollars a month with limited robots.

Two caveats from Microsoft's own requirements page. A free personal Microsoft account can build and run attended flows but cannot trigger them from the cloud. And Windows Home PCs cannot run unattended bots at all; you need Pro, Enterprise or Server. Seat and bot pricing is also exactly the kind of bill worth reading twice before signing.

Five checks before you buy

  1. Time the task by hand for a week. If the whole team saves under ten hours a month, keep doing it by hand.
  2. Write the rules on one page. If you cannot, it is not an RPA job.
  3. Ask whether the apps involved have an export, an API or a scheduled report. A file hand-off is cheaper and sturdier than screen-driving.
  4. Decide who fixes the bot when a screen changes, and what the work looks like for the two days it is down.
  5. Start with the free tier and one attended flow on one PC. Pay for unattended bots only once that flow has run clean for a month.

Frequently asked questions

Does RPA need coding?

Not for simple flows. Both Microsoft and UiPath ship recorders and drag-and-drop designers, and IBM notes the low-code approach is the main reason non-technical staff can build bots. Error handling and anything touching money still benefit from someone who can read a log.

Will AI agents replace RPA?

Vendors say the opposite: agents will decide and bots will execute. Gartner's agent-washing warning suggests a lot of what is sold as agentic in 2026 is still deterministic RPA underneath. For a repetitive, rule-bound job, that is fine, and cheaper.

If Friday afternoon is still spent copying numbers, record the task once with a free tier this week, run it attended for a month, and only then decide whether a paid bot earns its keep.