What process automation cost really includes

Most automation proposals are wrong in the same direction. They price the build and go quiet about everything that happens after it. If you want an honest process automation cost for your business, the number you need is the three year total: the build, the monthly runtime bills, the exceptions nobody scoped, and the person who still opens the dashboard on Monday morning to check it did what it said.

We're two people who build these systems ourselves. That means we're still around in year two, not just at the launch demo, and it has changed what we think belongs in a quote.

Where the process automation cost actually lands

There are five buckets. Vendors usually quote one of them.

Discovery and documentation

Somebody has to write down what the process currently does, including the bits that live in one person's head. If you do this yourself it costs you internal time. If a consultancy does it, expect to pay for a week or two of work before a line of code exists. Skipping it doesn't remove the cost, it moves it into the build as rework.

The build

This is the part everyone prices. It's also the part that has fallen in cost the fastest, because the tools got better and the models got good enough to write most of the glue. A workflow that would have been a six week integration project a few years ago is often a few days now.

Runtime

Every run costs something. Platform fees, per task pricing, API calls, model tokens, hosting. This bucket scales with volume, which is the opposite of the build. It's also where an automation that looked cheap at 200 runs a month becomes an argument at 20,000.

Breakage

Systems change underneath you. A supplier redesigns their portal, an API version gets retired, a field gets renamed in your CRM. Budget for someone to fix things a few times a year, or accept that the automation quietly stops working and nobody notices for a fortnight.

The human who stays

Almost no useful automation runs at 100 percent. There's an exception queue, and somebody works it. If the process has a 15 percent exception rate, you haven't removed the job, you've made it smaller and changed its shape. Price the smaller job honestly.

Workflow automation vs RPA, and why the bills differ

These two get sold as the same thing and they cost very different amounts to own.

Workflow automation connects systems through their APIs. Tools like Zapier, Make and n8n sit in this category, along with anything custom your team writes against documented endpoints. The connection is defined by a contract, so it breaks loudly when it breaks at all. Pricing is usually per task or per run, and the floor is genuinely low. A solo consultant posting on Reddit described running a working side business stack for under 30 dollars a month: a scraper pulled off GitHub, a cheap Claude subscription, a nocode database, and Zapier holding it together. That's a real cost profile, not a marketing one.

Robotic process automation works at the screen level instead. The bot clicks buttons, reads fields, and types into windows the way a person would. Nothing in the target system needs to change, which is exactly why RPA sells so well into banks, insurers and anyone running software from 2004. The cost profile is worse in three places: per bot licences, an orchestration layer you have to run, and brittleness. When a vendor moves a button, a UI level bot doesn't throw a clean error. It carries on and does something wrong.

The short version. If the systems have APIs, use workflow automation and pay per run. If they don't, RPA is a bridge, and you should price it as a bridge with an expiry date rather than a permanent piece of infrastructure.

How robotic process automation works when it's the right call

A robotic process automation build starts by recording a person doing the task, then turning that recording into a script with proper waits, retries and assertions. The assertions are the whole game. A bot that checks "is this the invoice screen, and does the total field contain a number" before it types recovers gracefully. A bot that assumes the screen loaded in 800 milliseconds fails at month end when the server is slow.

What we'd skip: full enterprise RPA suites for a process running a few hundred times a month. The licence and orchestration overhead swamps the saving. Browser automation with a modern agent tool covers a lot of what RPA was sold for, and that layer is getting cheaper. Cloudflare launched Kitesurf in August 2026, a cloud hosted browser built for AI agents rather than people, which drops the visual furniture and uses less CPU and memory than Chromium for tasks like screenshots and HTML extraction. They built it in 12 weeks and it already passes over 215,000 web platform tests. When the runtime layer under your automation gets that much cheaper, the per run economics of screen level work change with it.

How to document process automation before anyone quotes on it

This is the highest return hour you'll spend, and you can do it without us. A vendor quoting from a vague description is pricing risk, and you pay for that risk whether or not it shows up.

Record the person doing the task once, screen and voice together. Then write down, in order, every step they took, including the ones they didn't mention because they're automatic. Note which system each step touches and who owns the login. Write the decision rules as if/then sentences: if the invoice is over 5,000 euro, it goes to Marieke. Count how many times the task ran last month. Then, and this is the part people leave out, count the exceptions. Go through last month's cases and mark every one that didn't follow the happy path, then group them.

That exception list determines the cost more than anything else in the document. A process with two known exception types is a fixed price job. A process with eleven, three of which are "it depends, ask Jan", is a discovery project pretending to be a build.

One more thing to capture: what happens today when the step is done wrong. If a mistake costs 20 euro and gets caught by the next person, you can automate aggressively and accept some error. If a mistake means a customer gets billed twice, you need approval gates, and those gates are a permanent running cost, not a one off.

Give that document to three vendors and you'll get three quotes you can actually compare. Give them a paragraph and you'll get three numbers measuring three different things.

The line item nobody budgeted for

If your automation calls a language model, your runtime bill has pricing behaviour that doesn't work like traditional software. It isn't only per token, it's per token with cliffs.

OpenAI's Codex ships with a model catalog whose gpt-5.6 entry lists a 272,000 token context window, while the published spec for the model is 1,050,000. That 272,000 figure is also where the API reprices: past that many input tokens, the whole request bills at 2x input and 1.5x output, including the tokens below the line. OpenAI's stated reason for the cap is cache read cost rather than the billing threshold, but the practical effect for anyone building on top is the same. Cross a boundary you didn't know about and your per run cost jumps.

What this means for the automation process for a business running at volume: measure cost per run in production, not in a demo. A document processing flow that handles a two page invoice for a fraction of a cent can handle a 90 page contract for a hundred times that, and the 90 page contracts are the ones that arrive at quarter end. Set a hard token ceiling per run, log the cost of every execution, and put an alert on the monthly total. We've seen more automations killed by a surprise bill than by bad output.

The flip side is that some work has become cheap in a way that's worth checking before you scope a big build. Backflip AI released a model that turns 3D scans and mesh files into editable parametric CAD models, work that used to need real CAD expertise and hours per part. Their CEO Greg Mark says most factories have digital models for under one percent of their parts. Four reconstructions are free and paid plans start at 20 dollars a month. If a 20 dollar tool does 80 percent of the job you were about to commission, buy the tool.

How to judge the top process automation companies

Every list of top process automation companies is either an ad or a summary of who spends most on marketing. Judge on the answers to a few questions instead.

Ask what the bill looks like in month 18. If they can't produce a number, they've never had a client reach month 18, or they'd rather you found out later. Ask who owns the code and where it runs. A build that lives inside a vendor's proprietary platform is a rental, and the rent goes up. Ask what happens when it breaks at 11pm on a Sunday, and get the answer in writing with a response time attached.

Then ask them to tell you which part of your process they wouldn't automate. Anyone who says all of it either hasn't read your document or is selling licences. The honest answer usually includes at least one step that should stay manual because it runs twice a month and involves judgement.

Size matters here in an unobvious way. A large firm gives you process, insurance and a delivery team, at a day rate that includes the account manager and the sales cycle. Two people who build the thing themselves give you a lower rate and direct access, with concentration risk you should think about honestly. We're the second kind, and you can see what that covers on our AI services. Neither shape is wrong. What's wrong is paying enterprise rates for a build a small team could ship in a fortnight, or handing a compliance critical process to a solo freelancer with no handover plan.

The arithmetic, done properly

Take the ops lead who spends 6 hours a week copying invoice data between a supplier portal and your accounting system. Across 46 working weeks that's 276 hours a year. At a fully loaded 40 euro an hour, the process costs roughly 11,000 euro a year to run by hand.

Now the other side. Suppose the build is 8,000 euro, the runtime is 60 euro a month, and exceptions still take that person 1 hour a week instead of 6. Year one costs 8,000 plus 720 plus about 1,840 in remaining labour, so around 10,560. Year two is roughly 2,560. Over three years you're at about 15,700 against 33,000.

That looks decisive, and the sums are right, but the saving is only real if one of two things happens. Either the freed 230 hours go to work that generates value, or headcount actually changes. Otherwise you've bought yourself a calmer Tuesday, which is worth something, just not 11,000 euro a year. Be honest with yourself about which one you're buying, because your finance team will ask.

Also add a line for the year the vendor changes their portal and someone spends two days fixing it. It happens roughly once per integration per couple of years in our experience, and leaving it out is how a sound business case turns into a disappointing one.

When you shouldn't buy this yet

If the process changed twice in the last six months, wait. You'll pay to automate a shape that no longer exists. If the volume is under a few hundred runs a month and the task takes two minutes, the arithmetic rarely works once you include maintenance. If nobody in the business owns the process end to end, fix that first, because an automation with no owner becomes an unmaintained script within a year.

And if the exception rate is above about a third, you don't have an automation problem, you have a process problem. Automating chaos gives you faster chaos and a monthly bill.

What to do in the first month

Pick one process. Not the biggest, the most repetitive one with the clearest rules. Document it using the steps above, including the exception count. Time how long it takes today across a full month, not a good week.

Then build the cheapest version that could work, and run it beside the human for two weeks without switching anything off. Compare the outputs line by line. You'll find things the person does that nobody wrote down, and you'll find them while it's still cheap to fix.

Only once that comparison is clean should you turn off the manual path, and even then keep the cost log running. The number that tells you whether the whole thing was worth it is the one you read in month 18, not the one on the proposal.