How much does business automation cost? Real ranges for 2026.

How much does business automation cost? Anywhere from a few hundred dollars for a single connected workflow to six figures for an operations-wide build, and the gap is not a mystery. Providers sell different things under the same word: a form that fills a spreadsheet, a quote-to-cash system across four tools and an AI agent that answers the phone are all "automation", and they sit on completely different price tags.

This guide gives you the ranges that are actually published, who published them, what they leave out and how to turn them into a number for your own business. We read every page on 17 October 2026, and where a figure is our own we say so. We also sell fixed-price automation ourselves, from $250 to $7,120 paid once, so we have put our own price list in the open next to everyone else's. If you already know what you need, request a quote and a person replies within 24 hours.

How much does business automation cost? The short answer

If you want a number for your budget meeting, use this table. Every range is a published figure or one of our own, and the sections below say which.

Where automation price ranges come from, and how far to trust them

Most providers do not publish prices at all, so the research on this topic is thin and biased. Three kinds of source are worth knowing about, and each has a slant.

An agency's own guide

Layer3 Labs, a US agency, publishes "AI Automation Agency Cost", updated on 2 July 2026. It gives ranges by pricing model and by project scope, plus one worked example. It is marketing for an agency that sells these projects, so treat the ranges as one agency's view of the upper-middle of the market. It is useful because it shows the structure of a bill, not because the numbers are a market average.

A survey of published prices

Aumiqx, an agency that builds automations in n8n and code, collected what 48 agencies in 14 countries publish on their own sites or Clutch rate cards, converted to US dollars on 23 September 2026. That is 177 price points, counting each agency once per category at its lowest "from" price. It says more about what the cheaper end of the market advertises than about what a finished project costs, and Aumiqx says so itself: these are entry prices, real quotes land higher once scope is known, and agencies that publish prices skew smaller and newer.

Our own price list

We know one price list very well, because it is ours. Every BoldBellows service page carries three fixed-price packages, paid once, with a delivery window in business days. Where we quote a distribution below, it is computed from the live package prices of all 2,349 service pages, so it matches what you see when you open one. It describes our catalogue, which is narrow by design: named integrations with a defined outcome. It is not the market.

What does your own time cost?

Before you compare providers, price the option nobody invoices you for. Doing the work yourself looks free, and it is the most expensive route for many small businesses once you count the hours.

The US Bureau of Labor Statistics publishes median wages by occupation. We read three of the pages on 17 October 2026. For May 2025 the median hourly wage was $18.27 for receptionists, $21.64 for general office clerks and $24.36 for bookkeeping, accounting and auditing clerks. For comparison, BLS gives $50,980 as the median annual wage for all workers.

Two conclusions follow. A task that takes a clerk five hours a week costs roughly $469 a month in wages alone at the clerk median, a number you can set against any quote. And if you do the work yourself, the figure that matters is what your own hour is worth when you could be selling or serving customers, which is almost always more than a clerk's wage.

DIY automation cost: the subscription is the cheap part

Zapier's pricing page shows its Professional plan starting from $19.99 a month and a Free plan with 100 tasks a month. n8n Cloud's Starter plan is €20 a month billed annually with 2,500 workflow executions. How those units are counted, and why one workflow can cost three different amounts on three tools, is covered in our guide to n8n vs Zapier vs Make. The headline for this guide is simpler: tools are rarely the expensive part of a small automation. The hours are.

Doing it yourself is the right answer more often than people who sell automation admit. If the job is a single trigger and a single action, the tool has a template for it and someone enjoys fiddling with it, you can finish in an afternoon for the price of a subscription. The trouble starts in month two, not month one. Four things turn a free afternoon into a quiet recurring cost:

• The unhappy path. The first version handles the cases you thought of. The duplicate order, the blank field and the app that was down for an hour are where money goes missing.
• Nobody owns it. When the person who built it goes on leave or leaves, the workflow keeps running until the day it does not.
• Silent failure. A workflow that stops without telling anyone looks exactly like a workflow with nothing to do.
• Rework. Every app you connect changes its fields, limits and sign-in rules from time to time, and each change is a small repair job.

None of these is an argument against DIY. They are the items to price in. Count your hours at the wage you would pay someone to do the work and add a monthly allowance for repairs. If the total still beats the cheapest quote you have seen, build it yourself. If an account you built has grown past the point where anyone understands it, that is what our Zapier workflow audit, Make scenario audit and n8n workflow audit services are for: every workflow inventoried, risks rated from run history and a ranked fix list you approve before anything changes.

How much does a freelancer cost for automation?

A freelancer sits between doing it yourself and buying a finished service. Layer3's guide puts freelancers at $50 to $150 an hour. Aumiqx did not survey freelancers, but its published agency hourly ranges had midpoints running from $37 to $250 with a median of $74, so a freelancer rate in the $50 to $150 band sits inside what the market publishes.

The attraction is flexibility: you can buy an hour, ten hours or a month. The cost is that the meter is yours. The more loosely the job is defined, the more hours it takes, and the hourly model pushes all of that uncertainty onto you. Layer3 makes the same point about agencies, warning that open-ended hours shift all budget risk to the buyer and that hourly-only agencies are a risk on complex builds.

The practical rule is to ask any freelancer for a fixed price against a written scope and to treat an hourly estimate without a cap as a ceiling you have not been told about. That is the logic behind our own model: every service page states a price range and a delivery window before you talk to anyone. If you cannot yet write a scope, our guide to writing an automation brief shows what to put in it.

How much do automation agencies charge?

An agency sells a team, a process and accountability, on a project budget, which is why published ranges are wider than for any other route. There are two quite different sets of numbers, and mixing them up is the commonest mistake in cost research.

What agencies advertise as "from" prices

What one US agency says projects cost

Layer3's guide describes a different, higher band, for US agencies selling end-to-end builds to companies.

The two sets of numbers are an order of magnitude apart for the same words, "single workflow". Layer3's is $5,000 to $15,000 and the survey's median entry price is $1,000. Both can be true. They describe different providers, geographies, amounts of discovery and testing, and definitions of what is included. A price is only comparable once you know what it covers.

Fixed-price automation services: what our own prices look like

The fourth route is a catalogue: a provider that has done a particular integration many times sells it as a product with a fixed price and fixed scope. That is how BoldBellows works, and it is the cheapest route when your job matches a listed service. It is not an option when it does not, in which case we quote it.

Here is the shape of our own price list, computed from the live package prices of all 2,349 service pages when this guide was written. Each service has three packages, so we looked at the cheapest and the most expensive of the three for every service.

A few examples show how scope, not cleverness, moves the price. All figures are the live package range for each service, paid once, with the delivery window in business days.

The pattern is the useful part. A two-app data move costs a few hundred dollars. Anything that touches money, such as invoices or accounting records, costs more because the edge cases are expensive when they go wrong. Anything with AI in it costs more again, because it needs testing against real examples and a plan for when the model is unsure.

In-house or outsourced: when to hire an automation specialist

At some size, automation stops being a project and becomes a function. A company with dozens of workflows, several systems of record and frequent changes may be better off with a person whose job it is. None of the sources we read publishes a reliable salary for automation specialists, so we do not quote one. If you are weighing this route, price it as salary plus tools plus management time, and compare the total with a retainer.

For most small businesses the in-house route arrives later than expected. A better first question is whether the work is continuous or a handful of projects with long quiet periods between. Quiet periods are what fixed-price services and short retainers cover well, and if you are not sure which you are, a one-off audit settles it for the price of a single package.

What makes automation cost more or less?

Layer3 names three drivers as the biggest: data quality, the number of integrations and how much custom logic the job needs. In our experience those three, plus a few more, explain nearly every difference between two quotes for work that sounds the same.

Read down the "what to ask" column before you ask anyone for a quote. A provider who can answer all eight in one reply has done this before. One who quotes without asking any of them is guessing, and you are paying for the guess.

Automation cost in year one: the build price is not the whole bill

Buyers compare build prices and forget the rest. Layer3 gives a worked example that shows why that misleads: an accounts-payable automation priced at $12,000 for the core build and $4,000 for two integrations, plus a $2,500 monthly retainer for support. Its first-year total is roughly $46,000.

That ratio is not a law, and plenty of providers sell the build without a retainer. The lesson is to ask for the first-year number, not the build number, and to ask what the monthly figure covers. Our approach is to keep the one-off price and the running cost separate on purpose: you pay once for the build, your tool subscriptions stay with the platforms, and upkeep is optional.

Ongoing automation costs: subscriptions, usage, upkeep and monitoring

A finished automation is not a finished expense. Four ongoing costs matter, and a fair quote lists them separately.

How to budget for upkeep

Edana, a Swiss digital agency, writes that a common rule estimates annual maintenance costs at 15 to 25 per cent of the initial development cost, and presents it as a starting point to adjust for criticality, technology and service-level needs. It also notes that third-party APIs, cloud services and software licences add variable and sometimes unpredictable costs.

A second source, Wavect, a software agency, published a directional benchmark of 24 anonymised software-as-a-service products over 2023 to mid-2026. Median yearly maintenance spend was 24 per cent of the original build cost in year one, 21 per cent in year two and 26 per cent in year three, with a suggested band of 25 to 45 per cent for integration-heavy products because vendor APIs and webhooks drift. Wavect describes the result as directional, not a representative survey, and the products it studied are software products, not automations. We use it for one reason: it points the same way as Edana, that the budget for upkeep is roughly a fifth of the build every year, not zero.

For the payback model below we use 20 per cent a year, the middle of Edana's range. Yours may be lower if the automation is small and stable and higher if it connects to systems that change often. If you would rather buy monitoring than watch it yourself, we sell it per platform: Zapier error monitoring and fix, Make.com scenario monitoring and maintenance and n8n error monitoring and recovery, each paid once.

Automation ROI: a payback model you can check

Prices only mean something against the value of the work they replace. Here is a simple model in which every input is stated, so you can swap in your own.

• Value of time: $21.64 an hour, the BLS median for general office clerks in May 2025. Wages only, so it understates the true cost of an employee hour.
• Tool subscription: $30 a month for one workflow. This is our assumption, in line with the entry plans described above.
• Upkeep: 20 per cent of the build price per year, spread monthly (the middle of Edana's 15 to 25 per cent rule).
• Hours saved: the amount of routine work the automation fully removes. We show four levels, from 2 to 30 hours a week.

Read the table as a map, not a forecast. Down the left, how much routine work you remove. Across the top, what you pay. The cells with payback under a year are the ones to chase first, and any cell that reads "Does not pay back" should stop you buying. A small, cheap automation pays back quickly even when it saves only a couple of hours a week. An expensive build needs a large, certain saving, and the larger the build, the more it pays to prove the saving first.

The model leaves out several things in both directions. It ignores the value of fewer mistakes, faster responses and work that never gets done at all today, and it ignores the time you spend explaining the work to the provider and testing the result. Use it to rule options in or out, not to promise a return.

When automation is not worth buying

Aumiqx's page makes a point that is rare in sales material: if the task happens a few times a month, do not hire anyone for it. The model above shows why. At two hours a week the wage saved is about $188 a month, and a $5,000 build takes more than five years to pay back once tools and upkeep are counted (a $15,000 build never does).

Equally, do not read a long payback as a verdict on the idea. A job that takes one hour a week but carries a costly failure mode, such as an invoice that is sometimes sent twice, can be worth fixing for reasons that have nothing to do with hours saved.

How to compare automation quotes

A fair comparison starts by making the quotes comparable. Put the same questions to each provider and write the answers in one grid. If a provider will not answer one of them, that is information too.

Three patterns usually signal a quote to question: a price far below every published range for the type of work, a price with no description of what is included, and an hourly meter with no cap on work you cannot define yet. Layer3's guide includes a list of red flags for overpaying that points the same way.

The best defence is to start small. Aumiqx lists discovery and audit work at a median of $1,283 and notes that several agencies deduct it from the build price. A paid audit tells you what the whole project would cost before you commit to it, and it is cheap compared with discovering the same thing halfway through a build. Our own audits start at $1,505 for Zapier and $1,835 for Make, quoted in writing first.

Hidden automation costs that never appear on a quote

• Your own time. Someone must explain the process, answer questions and test the result. Budget a few hours for a small job and much more for a large one.
• Access and approvals. Getting admin access to a system, or a security sign-off, can take longer than the build.
• Training. The people affected need to know what changed and what to do when it fails.
• Parallel running. The sensible way to launch is to run the old and the new way side by side for a while, which costs extra effort and is worth it.
• Cleaning up what was already wrong. Automation reveals duplicate records, missing fields and inconsistent names. Fixing them is often a larger job than the automation.

None of these is an argument against buying. They are the reason to ask for a first-year figure and to name an owner on your side.

How to spend a first automation budget

If you are spending money on automation for the first time, the order matters more than the amount. Start with the work that is both frequent and painful. Buy the smallest thing that removes it. Keep the records and the accounts in your own hands. Review after a month, and only then decide whether to buy the next piece.

If you already have automations that someone else built, the next best use of money is an audit of what exists. It shows what is dead, what costs too much and what could fail without warning, and it prices the repair before you spend. Where the problem is the bill itself, our Zapier task usage and cost optimization and Make.com operations cost optimization services find where the usage goes and cut it, with the savings measured.