What Does It Cost to Automate a Manual Process? (Real Numbers)

Ask the internet what it costs to automate a business process and you will get a page of automation agencies quoting ranges with no sources, plus a few numbers that have been photocopied between blogs so many times nobody remembers where they started. The average payback period that is always suspiciously precise. The first-year return that is always suspiciously round. None of it helps you budget anything.

So here is the version with checkable numbers in it. We sell automation, which means you should read our conclusions with the same suspicion you would read anyone else's; that is exactly why every price in this article is either published by the vendor charging it, fetched from their own pricing page while writing this, or published by us where you can hold us to it.

Automation is priced three ways

Strip away the branding and nearly everything on the market charges you in one of three shapes: by the task, by the document, or once.

By the task. The workflow platforms meter what they execute against a monthly allowance. Zapier's Professional plan starts at $19.99 a month billed annually for 750 tasks a month, and the meter is the product: 10,000 tasks costs $129 a month, 50,000 costs $289, all billed annually. The free tier covers 100 tasks a month, which is genuinely enough to find out whether the approach fits your process before you spend anything. We wrote about where this model runs out of road in custom automation vs Zapier; the short version is that the price scales with your success at using it.

By the document. The document-extraction tools charge per thing processed. Docparser's Starter plan is $32.50 a month billed yearly, which buys 1,200 parsing credits a year, a credit being one document of up to five pages. That is $390 a year, and at full use it works out to about $0.33 per document; their Business plan at $133 a month billed yearly covers 12,000 credits, about $0.13 per document if you use them all. Note the phrase "at full use": the subscription does not care whether your volume shows up, so a quiet quarter quietly raises your per-document price. At the top of this category, enterprise extraction platforms barely publish prices at all. Rossum's entry plan is listed at "starting at $18,000 per year", everything above it is quote-only, and the minimum contract is a year.

Once. The third shape is a custom build: someone maps your process, builds the automation around your actual systems, and hands you the result. You own it, and there is no meter. This is what we sell, and our prices are on the site rather than behind a discovery call: a free consultation, then a €1,200 fixed process audit if you want the plan without committing to a build, then the build itself from €3,500, with most projects landing between €8,000 and €30,000, fixed. One price, you own the code, no subscription, no per-user fees.

How to actually compare them

The three shapes only look incomparable. The comparison is volume, multiplied out over the years you intend to keep running the process.

At small volume, the subscriptions win and it is not close. A hundred documents a month uses a $390-a-year plan to the last credit, and no custom build we could quote beats $390 a year. If that is your situation, take the honest answer and the cheap plan, and revisit when the volume grows. The same goes for simple task automation: if everything you need fits in Zapier's allowance and its connectors genuinely cover your systems, you are done, and you should not let anyone, us included, talk you into a build.

The arithmetic turns over as volume and specificity climb. Zapier's 10,000-task tier is $1,548 a year billed annually; five years of it is $7,740, comfortably past our €3,500 starting price for a build you would then own outright, and that is before counting the hours your staff spend working around the parts a generic connector does not cover. Document tools turn over the same way: 12,000 documents a year on Docparser's Business plan is $1,596 every year, and at Rossum's published entry point you are at $18,000 every year. Against numbers like those, a one-time €8,000 to €30,000 build stops sounding expensive and starts sounding like arithmetic. The scope is not identical, a bespoke build and a SaaS plan never are, but the direction of the comparison is exactly the one the subscription vendors would rather you did not run: their price repeats annually and follows your growth; a build's price happens once and then stops.

What usually tips the decision is not even the meter. It is the fit. The subscription products automate the standard version of your process, and most real back offices have a standard part plus a stubborn remainder: the supplier whose invoices come in sideways, the approval step that only exists because of one client, the scanner on the local network that no cloud tool can see. That remainder is what your staff still do by hand next to the tool you are paying for, and it is the part a custom build is actually for. If the process touches local hardware or has to run on your own server, the comparison collapses entirely, because the subscription products were never candidates.

What moves a custom quote up or down

The honest answer to "why is the band €8,000 to €30,000 and not one number" is that a few concrete properties of your process set the price, and you can estimate where you sit before talking to anyone.

The biggest is how many systems the automation touches. Reading a document and writing rows into one place is the bottom of the band; keeping an ERP, an accounting package and a warehouse system agreeing with each other is not. Next is what happens when the input is ugly: a process that can park anything doubtful for a human costs meaningfully less to build than one that must resolve every case on its own, which is why we will usually argue for the review queue. The current state of your data matters, because cleaning up years of inconsistent naming is work someone has to price. Local hardware and on-prem requirements add scope but are often the entire reason the project exists. And a process that changes shape every month should be scoped smaller, or the build will be chasing a moving target at your expense.

None of this requires trusting our numbers. It requires trusting your own: your monthly volume, your hourly cost of the manual work, and the published prices above. We keep a calculator that does the multiplication for you, and if the manual work you are pricing is currently a hiring decision, we did that comparison end to end in before you hire a data entry clerk. If a vendor's quote leans on the letters AI to justify its size, Monday's piece on what is actually inside an "AI-powered" tool is the companion read.

And if you want the number for your specific process rather than a band, that is what the audit is for: €1,200, fixed, and you get the plan and the quote whether or not you build with us. Tell us what the process is and we will tell you which of the three price shapes it belongs in, including the two we do not sell.