I run an AI automation agency. You should know that before you read a word of this, because it means I have an obvious interest in you deciding this is worth paying for.
So here’s my attempt to be useful anyway. Most of what’s written about AI automation cost in the UK is either a pricing page dressed up as a guide, or a range so wide it tells you nothing — “£2,000 to £150,000, book a call to find out.” I’ve put real numbers below, including the ones agencies tend not to mention until month two, and a section on when you shouldn’t spend the money at all.
The prices come from published UK rate cards, not from what I’d like to charge you.
AI Automation Cost in the UK
For a UK SME in 2026:
- A first automation costs £1,500–£5,000 and takes one to three weeks.
- A departmental build costs £5,000–£20,000 and takes four to ten weeks.
- Running costs are £40–£400 per month on top, depending on volume — and over a year these often exceed the build cost.
- A realistic first-year budget for one well-chosen workflow is £5,000–£8,000 all-in.
- Payback should land inside 12 months. If the maths doesn’t get there, don’t do it.
The single biggest mistake I see is businesses budgeting the build and forgetting everything after it.
What you’re actually paying for
“AI automation” covers three jobs that cost very different amounts, and a lot of confusion comes from buyers comparing quotes for one against quotes for another.
Workflow automation connects systems you already pay for so a repetitive task happens without a human. An enquiry arrives, gets logged in your CRM, gets a reply, and the follow-up is scheduled. No model needs to be involved. This is the cheapest work and usually the best first automation.
AI-in-the-loop process work adds a language model where judgement used to be needed. An AI agent reads the enquiry, works out what it’s about, checks the order history via an API, and drafts something a human approves. More expensive than plain business process automation, because it needs prompt design, testing, and a plan for the day it gets something wrong.
Custom AI development builds something that doesn’t exist off the shelf. This is software development with all the cost that implies, and most SMEs don’t need it.
There’s one more thing worth separating out, because it quietly inflates quotes. Marketing automation — email sequences, lead scoring, campaign triggers in HubSpot or similar — is a mature category of its own with its own specialists. Some agencies file it under AI automation and price it at AI rates. If what you actually need is better email nurture, that’s marketing automation and it should cost less. Same goes for AI chatbots bolted onto a website: that’s a product purchase, not a process automation project.
If a quote seems wildly out of line with another, check you’re comparing the same job.
What UK businesses are actually spending and getting
Worth grounding this in something other than vendor claims. The Office for National Statistics published its latest read on AI in UK businesses on 20 July 2026, drawing on nearly 39,000 survey responses. Two findings matter if you’re about to spend money.
First, adoption is now normal: use of at least one AI technology among businesses with ten or more employees has climbed from roughly 12% in late 2023 to around 35%. Among the smallest firms, those with fewer than ten staff, it’s 28%.
Second — and this is the part that should shape your budget — adoption is shallow. The average adopting business uses about 1.6 AI technologies, barely up from 1.4 in 2023. Only 10% of businesses using AI describe that use as extensive. The ONS itself notes this implies limited transformative impact so far.
The government’s own DSIT research, based on 3,500 business interviews, finds around three-quarters of adopters report productivity gains but only about 12% can point to increased revenue. Gartner, meanwhile, expects more than 40% of agentic AI projects to be cancelled by the end of 2027, blaming rising costs and unclear business value.
Read together, that’s a market where nearly everyone has bought AI tools — a ChatGPT licence, Copilot in Microsoft 365 — and almost nobody has automated a process end to end. The gap between those two things is what AI automation agencies exist to close, and what you’re actually paying for. It’s also why the cheap, boring, high-volume workflow beats the ambitious one every time.
UK price bands for 2026
What a UK business should expect to pay, by the size of what you’re trying to automate.
| Engagement | Typical UK cost | Timeline | What you get |
|---|---|---|---|
| Discovery / audit | £500–£2,000 | 1–2 weeks | Process map, shortlist of candidates, costed proposal. Often credited against the build |
| First automation | £1,500–£5,000 | 1–3 weeks | One workflow, live, with monitoring |
| Departmental build | £5,000–£20,000 | 4–10 weeks | Several connected workflows across a function |
| Multi-system programme | £20,000–£50,000+ | 3–6 months | Cross-department, custom integrations, AI agents |
| Custom AI development | £50,000+ | 4 months+ | Bespoke software, bespoke risk |
| Ongoing support | £350–£3,000/month | Continuous | Monitoring, fixes, changes, improvements |
These aren’t my invention. Fixology publishes a first quick win from £1,500 shipping in one to two weeks. Elevate AI publishes pilots at £3,000–£5,000 plus VAT with implementations typically £10,000–£25,000 and support from £350 a month.
On hourly rates: £75–£150 is the usual band for automation work. Consultancy.uk data shows the wider UK consulting market spanning roughly £50 an hour for operational work up to £300-plus for senior strategy. If someone quotes you £300 an hour to build a Zapier workflow, that’s a strategy rate for delivery work.
What pushes the price up
Six things, roughly in order of impact.
1. Integration count
Two systems is straightforward. Six is not — every connection into your existing systems is a point of failure and a thing to test. Price tracks integrations far more closely than it tracks hours.
2. Data quality
If your CRM has three spellings of the same client and half your invoice data lives in a spreadsheet someone maintains by hand, the cleanup is the project. Budget for it honestly or the automation will produce confident nonsense.
3. The cost of being wrong
Automating internal reporting is low stakes. Automating something a regulator inspects is not. Anything touching regulated advice or client money needs audit trails, human sign-off and testing that a low-stakes build doesn’t.
4. Whether a model is involved
Rules are cheap and predictable. Language models need prompt engineering, evaluation, and a plan for the day the output drifts.
5. Custom versus configured
Building on n8n, Make or Zapier is far cheaper than writing bespoke software. Most SMEs never need to cross that line.
6. Volume and concurrency
Something running fifty times a month is a different engineering problem to something running fifty thousand times.
The running costs nobody puts in the proposal
This is where budgets break. An automation isn’t a thing you buy once — it sits on top of tools that bill you monthly and needs someone to notice when it stops working.
The automation platform
This is the one buyers get wrong most often, because the three main platforms bill on completely different units. Zapier charges per task, meaning every action in a workflow. Make charges per operation, meaning every module run. n8n charges per execution, meaning the entire workflow counts once.
That difference compounds hard. A ten-step workflow running 10,000 times a month costs roughly $50 on n8n Cloud, £150–£200 on Make, and £250–£400-plus on Zapier — same work, wildly different invoice. Entry pricing is Make from around $9 a month, Zapier from about $20, n8n Cloud from €20. n8n also has a free self-hosted community edition, which runs on a small server for £5–£15 a month.
The honest caveat: self-hosting isn’t free, it’s just differently expensive. One documented migration of 23 Make scenarios to self-hosted n8n cut tooling from $348 a month to about $12 — but recreating credentials and webhooks ate roughly 40% of the project time. You trade a subscription for maintenance work.
AI model usage
Whichever provider you end up on — OpenAI, Anthropic’s Claude, Google — you’re billed per token, split between what you send and what the model returns. Output costs several times more than input, and caching a long, repeated system prompt cuts the bill substantially. This only applies where a language model is genuinely in the loop; rule-based process automation and classic machine learning carry no per-use model cost at all.
I’m deliberately not quoting per-model rates here — they’ve fallen sharply and repeatedly through 2026, and any figure I print will be wrong within a quarter. Ask your agency to model your actual volume against current rates. For a typical small business running a few automations, £5–£100 a month is the realistic range.
Messaging and telephony
Individually trivial, which is exactly why budgets drift here.
UK outbound SMS through a provider like Twilio runs roughly 4–5p a message. So 500 appointment reminders a month is £75–£100, and 5,000 is £750–£1,000 — the same workflow, ten times the bill. Volume discounts don’t kick in until around 150,000 messages a month, which no SME is going to reach. Add £1–2 a month per phone number, and about 5p per attempt if you’re sending one-time verification codes.
WhatsApp is cheaper but stranger. Meta bills per template message delivered, and the rate is set by your customer’s country rather than yours — roughly £0.038 for a marketing message to a UK number, £0.016 for a utility or authentication one. Replies you send inside the 24-hour window a customer opens by messaging you first are currently free, which is why well-designed flows work hard to keep conversations customer-initiated. Your provider then adds a platform fee on top of Meta’s rate, so the published number is never the number you pay.
One change worth budgeting for now: from 1 October 2026, Meta starts charging for service messages too, at the utility rate, whether or not they fall inside that 24-hour window. If an agency quotes you WhatsApp running costs on today’s model, ask them what happens in October.
Voice is the expensive one. A plain outbound call is about a penny a minute. Route it through an AI voice agent and you’re looking at something like 15p–20p a minute, depending on whether you assemble the stack yourself or buy a managed one. A hundred five-minute calls a month lands around £28–£65 and nobody notices. A thousand lands at £275–£650, which is real money that was never in the proposal.
Maintenance
APIs change, credentials expire, prompts drift, edge cases surface. Expect £400–£1,200 a month for a business running several workflows in production. Over twelve months that frequently exceeds the build cost — which is exactly why one UK consultancy argues businesses underestimate total cost by around 3x by pricing only the build.
A realistic monthly total:
£40–£150 for two or three simple automations with light model use. £400–£1,200 once you’re running a department on it with support included.
Work out the total cost of ownership across 24 months rather than fixating on the build price. That’s the number that decides whether your cost savings are real or just deferred.
Pricing models, and which one protects you
Fixed scope is best for defined work. You know the number, they carry the overrun risk.
Hourly puts you on opposite sides of the table — they earn more by taking longer. Fine for genuinely exploratory work, bad for a build.
Monthly retainer suits ongoing support and iteration. Watch for retainers that quietly become subscriptions to nothing once the work is done.
Outcome share sounds attractive and rarely survives contact with attribution. Whose lead was it?
If scope genuinely can’t be defined yet, buy a short paid discovery to define it, then a fixed price to build it. Don’t sign an open-ended hourly engagement because nobody wanted to do the scoping.
Agency, in-house, freelancer or DIY?
Most UK SMEs land on one of four routes. The honest deciding factor isn’t budget — it’s whether automating is a one-off or a habit you’re going to keep feeding.
| Option | Year-one cost | Choose it when |
|---|---|---|
| DIY | £100–£1,000 | Simple, rule-based, you have someone technical and patient |
| Freelancer | £2,000–£15,000 | Well-defined single build, you can absorb the key-person risk |
| Agency | £5,000–£30,000 | You need scoping, build and maintenance, and can’t justify a hire |
| In-house hire | £52,000–£101,000+ | Automation is continuous and core to how you operate |
The in-house numbers deserve unpacking, because “just hire someone” is the most underpriced option on that list.
For 2026/27, employer National Insurance is 15% on earnings above a £5,000 secondary threshold, and auto-enrolment requires a minimum 3% employer pension contribution on qualifying earnings. Take Glassdoor’s UK average for an AI and automation engineer, £44,564: add £5,935 in employer NI and roughly £1,136 in pension and you’re at about £51,600 before recruitment fees, equipment or a desk. Take IT Jobs Watch’s median UK AI engineer salary of £87,500 — from vacancies posted in the six months to 30 July 2026 — and the loaded cost is about £101,000.
Note also that those two figures describe different jobs at a 2x price gap, and job ads use the titles interchangeably. Know which one you’re actually hiring.
Worth knowing: the Employment Allowance of £10,500 offsets employer NI for many smaller businesses, which narrows the gap. And the ONS data shows what small firms actually do — recruitment of AI-skilled staff runs at about 2% among the smallest businesses, rising to 10% at 250-plus employees. Small firms overwhelmingly train existing people instead. Among businesses citing a skills gap, 62% report retraining staff.
Working out the ROI
The ROI formula isn’t complicated:
(Hours saved per week × loaded hourly cost × 52) − annual running cost = annual return
Then divide the build cost by the monthly net saving to get your payback period.
A worked example. Say client enquiry triage eats eight hours a week of admin time. A £28,000 salary costs about £32,100 once NI and pension are added, which across roughly 1,750 productive hours is about £18 an hour. Eight hours a week at £18 is £7,488 a year. Running costs of £100 a month take £1,200 off that, leaving £6,288. Against a £4,000 build, you’re net positive in under eight months and banking over £6,000 a year after that.
Now notice what makes that ROI work. It’s high-volume, it’s repetitive, and it’s judgement-light. Change it to two hours a week and the same build takes over two years to pay back — at which point don’t do it. Automate the frequent boring thing, not the interesting rare one.
Two honest cautions. First, hours saved are only real if the time gets redeployed; if someone just has a quieter Tuesday, you’ve bought comfort, not return. Second, don’t build the business case on cutting headcount.
The ONS found around half of AI-adopting businesses report no change in workforce size at all, and among those using AI specifically to improve operations, 63% saw no headcount change against 6% reporting a decrease. The return shows up as capacity, error reduction and faster cycle times — not redundancies.
When you shouldn’t spend the money
I’d rather say this than have you find out in month three.
Your process isn’t stable. If it changes every quarter or lives in one person’s head, automate the documented version of it later. You cannot automate something you can’t describe.
Your data is a mess. Fix the CRM first. It’s cheaper.
The volume is too low. Anything under a couple of hours a week rarely clears a four-figure build inside a year.
You want a headcount cut. See above — the evidence doesn’t support it as a business case.
You’re buying because competitors are. That’s how you end up in the 40% of projects Gartner expects to be cancelled.
Twelve questions to ask before you sign
- On money – Is this fixed price or hourly, and what happens if it overruns?
- What will I pay in month two, itemised — platform, model usage, messaging, support?
- Can I see software costs separated from your fees?
- On delivery – Who actually builds this — the person on this call?
- When does the first workflow go live, not the first document?
- On ownership – Who owns the workflows, the accounts and the API keys?
- Is this on my infrastructure or yours, and can I take it in-house?
- If you stop trading tomorrow, what do I still have?
- On compliance and be specific here – For my data, are you a controller or a processor, and where’s the data processing agreement?
- Which model provider processes my data, and in which region?
- If this makes decisions about people — screening, pricing, eligibility — how does that sit with the automated decision-making rules? The Data (Use and Access) Act inserted Articles 22A to 22D into UK GDPR on 5 February 2026, and separate complaint-handling duties took effect on 19 June 2026. The ICO has dedicated agentic AI guidance in its 2026/27 work programme. An agency that blinks at this question hasn’t thought about it.
- On evidence – Show me a workflow you built and the number it moved.
Red flags
- Won’t give a range before a sales call.
- Never mentions running costs.
- Builds everything on their own accounts.
- The demo is a website chatbot.
- Sells an “AI strategy” retainer with no shipped artefact.
- Quotes a headcount reduction as the business case.
- Was founded eleven weeks ago off the back of a course. The loudest content in this category is aimed at people who want to start an agency, not people who want to hire one.
How to run the first project so it actually works
Pick one process. Boring, high-volume, low-stakes. Document-heavy work, enquiry triage and reporting reconciliation are consistently the cleanest wins.
Baseline the number before you start — how many hours, how many errors, how long the cycle takes. You cannot prove a return against a number you never measured.
Define “done” as a live workflow in production, not a document. Add 20% contingency. Review at 30 days against that baseline, and only then decide whether to build the second one.
Get the first one right and the second funds itself.
FAQ
How much does AI automation cost in the UK?
Between £1,500 and £5,000 for a first workflow, £5,000–£20,000 for a departmental build, and £20,000–£50,000-plus for multi-system programmes. Add £40–£1,200 a month in running costs depending on volume and support.
How much does an AI automation agency charge?
Published UK engagement bands run from about £4,000 to £50,000, with hourly rates typically £75–£150. Pilots commonly start at £3,000–£5,000 plus VAT.
Are there hidden costs?
The platform subscription, model API usage, messaging fees and maintenance. Across twelve months these frequently exceed the build cost. Any proposal that doesn’t itemise them is incomplete.
How long does an AI automation project take?
One to three weeks for a single workflow, four to ten weeks for a departmental build, three to six months for a multi-system programme.
How do I calculate ROI?
Hours saved per week × loaded hourly cost × 52, minus annual running costs. Divide the build cost by the monthly net saving for your payback period. Target under twelve months.
Is n8n cheaper than Make or Zapier?
Usually, and increasingly so at volume, because n8n bills per workflow execution rather than per task or per operation. A ten-step workflow running 10,000 times monthly can cost five to eight times less. Self-hosting is cheaper still but shifts cost from subscription to maintenance.
AI Agency or DIY?
DIY works for simple, rule-based automation if you have someone technical. Bring in help when you’re connecting several systems, handling sensitive data, or need it to keep working without you.
What’s a realistic first-year budget for a UK SME?
£5,000–£8,000 all-in for one well-chosen workflow: build, running costs and light support.
If you want a straight answer on what your first automation would cost, I’ll map the process and give you a number. No obligation, and if the payback maths doesn’t work I’ll tell you that instead.
