How much does AI automation cost in 2026? Real numbers by project type

Nobody publishes prices in this market. Search for what AI automation costs and you get “it depends”, a contact form, and a discovery call designed to size your budget before a number appears. This article is the opposite: every figure we quote, plus the ranges we see elsewhere, plus the reasoning that turns a process into a price.

Last updated: 27 August 2026.

Where these numbers come from

Two sources, both worth being explicit about because a price guide with no methodology is just an opinion.

The market ranges are observed, not surveyed: published agency pricing, freelance marketplace rates for n8n and Make specialists, and — most usefully — quotes that clients have shown us while deciding between us and someone else. They are ranges rather than averages because the spread in this market is genuinely enormous.

Our own prices are simply published, on the AI automation consultant and small business pages, and repeated below. We are deliberately at the bottom of this market, and the reasons for that are on those pages too — a price this far under the norm should come with an explanation rather than a discount code.

We take no vendor commissions and resell no licences, so nothing here is written to move a subscription.

The four things you can actually buy

Most of the confusion in AI automation pricing comes from comparing quotes for different products. There are four, and they are not substitutes.

The pattern worth noticing: the gap between market and floor widens as the deliverable gets more abstract. A workflow build is a concrete artefact, so the spread is about 5x. A strategy roadmap is a document, so the spread is closer to 15x. Abstract deliverables are where pricing discipline disappears.

The five variables that actually move a quote

Ask two suppliers to price the same workflow and you can get $1,500 and $12,000. Usually neither is dishonest — they have priced different amounts of hidden work. These are the five things to establish before comparing any quotes.

1. How many systems the workflow crosses

The single biggest driver. Each additional system adds authentication, error handling, field mapping, and a new way for things to break. Two systems is a routine build. Five systems is a project, and the cost is not linear — it is closer to quadratic, because every pair of systems is a place where data can disagree.

2. Whether those systems have real APIs

A documented REST API is cheap. A partial API missing the one endpoint you need is expensive. No API at all — a legacy desktop system, a portal with no export — means either browser automation, which is fragile and needs maintenance, or a manual step that stays manual. Ask any supplier to name the integration method for every system before accepting a price. A quote that skips this question is a guess.

3. How clean the source data is

“Read the invoices and put them in the accounting system” is one sentence and two completely different projects depending on whether the invoices arrive as structured PDFs from twelve regular suppliers or as phone photos from two hundred irregular ones. Data quality is where optimistic quotes go to die.

4. Whether a human has to approve

An approval gate is not just a button. It is a queue, a notification path, a timeout behaviour, an audit trail, and a decision about what happens when the approver is on holiday. It typically adds 20-40% to a build — and it is usually worth every cent, because a workflow that acts without oversight on a judgement call is how automation loses a company’s trust permanently.

5. Whether anything is regulated

Personal data, financial records, health information, or anything with a retention requirement changes the design rather than decorating it. Retrofitting compliance after the workflow exists usually means rebuilding it, so this belongs in the first conversation.

Worked example: what a typical first project costs and returns

Run this with your own numbers — it is the same arithmetic our audit applies. The process here is supplier invoices arriving by email and being keyed into accounting software by hand.

A workflow that removes 80% of the keying and routes exceptions to a person saves roughly $7,500 a year on this one process.

Now price it three ways. At our $1,900, payback lands at about three months. At a typical agency’s $9,000, payback is fourteen months — still positive, but now competing with everything else you could do with $9,000. At an enterprise consultancy’s $40,000 including strategy work, this project should not happen at all.

That is the real function of a price guide: not finding the cheapest supplier, but knowing which quotes make the project worth doing.

When the answer is “do not automate this”

The most useful thing a cost guide can tell you is when to stop reading.

• The process costs under ~$300 a month. Even a $900 build needs most of a year to pay back, and the process will probably change first.
• It runs less than weekly. Monthly and quarterly tasks rarely accumulate enough instances to matter, however annoying they are.
• The steps changed in the last quarter. Automating a moving target produces rework you pay for twice. Stabilise and document it first — our SOP generator does this for free.
• Nobody will own it. In a small company an unowned automation dies at the first broken integration, and the money is gone.
• One system in the chain has no integration surface. Browser automation against a closed portal is possible and genuinely fragile. Sometimes the honest answer is that the manual step stays.

A cheaper path than any of this

If your budget is zero right now, the sequence that costs nothing and still moves you forward:

1. Count before you quote. Pick your three most-repeated tasks and get real monthly volumes from the system — search the inbox, count the CRM records. Do not let people estimate; estimates are consistently wrong in both directions.
2. Cost them. Instances × minutes × loaded hourly rate, then add what lateness and errors cost. That second number is often larger than the first.
3. Check the rule test. Could a new hire follow written instructions to do this? If yes, it is automatable today. If not, the buildable version is an approval queue.
4. Check the integration surface. Does every system involved have an API, a scheduled export, or a dedicated mailbox? Anything with none of the three is a blocker, not a detail.
5. Try building the simplest one yourself. If it is a single trigger and a single action, an afternoon in Zapier or Make will do it and you should not pay anyone. Suppliers earn their fee when a process crosses three or more systems, has real exceptions, or needs an audited approval step.

If step 2 puts your top process above roughly $500 a month and step 3 passes, you have a project worth quoting. If it does not, spend the money on sales instead — and be suspicious of anyone who tells you otherwise.

Getting a quote you can trust

Four questions that separate a considered price from a number:

• What is the integration method for each system? Named, not assumed.
• What happens to the exceptions? A supplier who has not asked about your edge cases has not priced them.
• What is the fixed price, and what would change it? “It depends” is fine as a preamble, never as an answer.
• Who owns the workflow afterwards? Source, credentials, and documentation should end up in your accounts. Anything else is a subscription wearing a project’s clothes.