AI Consultant Cost: How to Build the Number Yourself

Every page you have read on this question hands you a range and leaves you standing there with it. Somewhere between two thousand and fifty thousand pounds, best of luck. What none of them tells you is how the number on your own quote was assembled, which is the only thing that would let you judge whether it is fair.

So this is the version I would want if I were buying. Not another table to hold your quote up against, but the arithmetic underneath it. Where a day rate actually comes from, what a firm adds on top of it and why that is sometimes legitimate, and the two costs that never appear on the quote at all.

Everything here with a number attached comes from a source I can point at. Where I could not verify a figure, I have left it out, which is why you will not find the eye watering ROI multiples that decorate most pages on this subject.

What does an AI consultant cost in the UK?

Less than the pricing pages imply, for most businesses. The Department for Science, Innovation and Technology surveyed 3,500 UK businesses with five or more staff and found the median amount spent on AI across 2024 was £2,000. The mean came out at £19,000, and the distance between those two numbers is the whole story: a handful of large programmes dragging the average up while most businesses quietly spend a few thousand pounds. More than a quarter of the businesses already using AI had spent nothing at all.

That gap tells you something useful about what you are being sold. In the same research, 65 percent of businesses planning to invest said they would buy off the shelf applications, and only 22 percent planned anything bespoke.

Most of the demand is configuration work. Most of the quotes are priced as engineering.

Where does an AI consultant’s day rate actually come from?

From the market for contract technical staff, mostly. ITJobsWatch tracks UK job advertisements, and across the six months to 24 August 2026 the median contract day rate for an AI consultant sat at £575, from a sample of 72 adverts. The middle half of that market ran from £531 to £700. The 10th percentile was £463 and the 90th was £734.

That is a far narrower spread than any consultancy pricing page will show you, and the reason matters. ITJobsWatch counts what an employer advertises to hire one contractor for a day. It does not count what a firm invoices, and a firm’s fee is a different animal. Sitting on top of the person doing your work is the sales time, the project management, the hours spent quoting jobs that never closed, and the risk that the build does not work first time and somebody has to fix it for nothing. A firm charging meaningfully above the contractor rate is not automatically taking you for a ride. It is carrying risk you would otherwise carry yourself, and the four tiers of supplier selling this work in Britain each carry a very different amount of it.

If what you actually typed was AI consultant hourly rate, divide by seven. A £575 day is somewhere around £80 an hour of genuine working time.

But I would not buy this work by the hour, and I would be a little wary of anyone keen to sell it that way. Hourly billing pays for time spent, and what you want is a thing that works. Ask for a fixed price against a written scope. If the job cannot be described tightly enough to fix a price to it, it cannot be built properly either.

How to work out what your job should cost

Five moves, in order. They take an afternoon and they will save you more than any amount of comparing tables.

1. Write the job down with a number in it. Not “automate our admin”. Something like: the 40 to 60 supplier invoices that arrive by email each month need the supplier, date, net, VAT and total pulled out and filed as a draft bill in Xero. If you cannot write that sentence, no quote you receive means anything, because two firms will quietly price two different jobs and you will think you are comparing them.
2. Count the systems that have to talk to each other. One system on its own is usually an afternoon. Two systems with a documented way in is a different order of work. Three, where one of them is an ageing piece of software with no export and no interface, is where quotes start disagreeing violently with each other, and it is almost always the reason why.
3. Ask for days and rate separately, never one number. A single figure is unarguable by design. Days multiplied by a rate gives you two numbers you can each push back on, and it forces the supplier to commit to an estimate of effort rather than a feeling about your budget. Anyone who refuses to split it is telling you something worth hearing.
4. Check the rate against something public. The median above is your reference point for one competent person’s day. A firm will sit above it and should be able to say what the difference buys.
5. Add the costs that are not on the quote. Which is the next section, because they are bigger than people expect.

Why do two quotes for the same job differ so much?

Because they are pricing different amounts of risk, not different amounts of skill. Four things genuinely move the number, and none of them is the consultant’s cleverness.

• How clean your data is. If your customer list lives in one system in one format, the work is short. If it lives in a spreadsheet where somebody has been typing county names four different ways since 2019, the cleanup can outlast the build.
• What share of your cases are exceptions. A process that runs the same way nineteen times out of twenty is cheap to automate. The twentieth case, the one everybody in the office knows the story behind, is where the cost lives. Ask a supplier how they intend to handle it, and if the answer is vague the price will move later.
• Whether the output reaches a customer unattended. Anything a human reads before it goes out can be roughly right. Anything sent automatically has to be right, and the testing bill for that is real.
• Whether the software at either end will let you in. Modern tools have a documented way for other systems to connect. Older ones often do not, and the workaround is fragile and slow to build.

What should an audit or a first session cost?

The UK suppliers who publish their prices, and most do not, sit noticeably lower than the guides suggest. Elansio lists AI training at £449 plus VAT for a 60 minute session covering up to twenty people, and £980 plus VAT for a half day. Optimus Consulting publishes a £995 audit alongside a £1,250 day rate. My own AI Opportunity Audit is £500, fixed, and it comes off the cost if you go on to build with me.

Judge any of these on what you are holding when it ends, not on the fee. If you walk out with a prioritised written roadmap that somebody else could pick up and build from, you bought a piece of work. If you walk out with a slide deck and a proposal for a larger engagement, you bought a sales meeting and paid for the privilege of attending it.

What is not on the quote?

Two things, reliably, and together they can add a third again to what you thought you were spending.

The first is VAT. Every figure in this article, and on every pricing page you have read this week, is exclusive of it. At 20 percent that is not a rounding error. If your business is VAT registered you reclaim it and the question is only about cash flow. If your turnover is under the £90,000 registration threshold you cannot reclaim any of it, so a £5,000 build genuinely costs you £6,000 and the guides never say so.

The second is what the thing costs to keep running. Independent UK suppliers put platform fees at roughly £40 to £150 a month for a live automation, which lines up with what the tools actually charge. Claude Pro is $20 a month and includes Claude Code, or $17 if you pay for a year up front. n8n is free if you run it on a server you control, and starts at €20 a month hosted. Zapier and Make both have free tiers that will carry a small workflow. None of these vendors publishes a UK price list, so what lands on your card depends on the exchange rate that day and your card’s fees.

There is a third cost nobody invoices you for, which is somebody in your business checking the output for the first few weeks. Budget an hour a week for it and be pleasantly surprised.

How do you check a quote in ten minutes?

Open four tabs. This is the part almost nobody does, and it changes how the next conversation goes.

1. ITJobsWatch. Look up the role you are buying and note the median and the 75th percentile day rate. Now you know what one person’s day costs on the open market.
2. The government’s Digital Marketplace. Suppliers selling to the public sector through the cloud buying framework have to publish their day rate cards. You can read what a firm charges buyers who negotiate considerably harder than you do, and it is public.
3. The supplier’s own website. A firm that publishes a price has already decided it can defend that price to everyone. A firm that will only quote after a discovery call has decided the number should depend on you.
4. Companies House. How long have they existed, and how many people stand behind that day rate? A one person operation charging a consultancy rate might still be the right call, but you should know which you are buying.

What is the least you can spend and still get something working?

Under £30 a month, if the job is one you already understand. That is not a rhetorical flourish, it is what the tooling costs. A Claude Pro subscription includes Claude Code, which will sit on your own machine and write and run a working automation against your own files while you describe what you want in plain English. It is genuinely usable by someone who does not write software, and the honest limit is your patience rather than your technical skill. If you want to see what that first hour looks like before you commit an evening to it, I have walked through a first session start to finish.

The reason I keep pointing people at this is not modesty about my own fees. It is that the first automation somebody builds themselves changes what they buy afterwards. They stop asking what an AI consultant costs and start asking whether this particular job is worth a consultant at all, which is a much better question and usually has a cheaper answer. That is why I work the way I do.

Pay for help when the work crosses systems that were never designed to speak to each other. Or when you have looked at it for two evenings and got nowhere, which is also a perfectly good reason.

I publish my own number because I got tired of reading pages that would not. £500, sixty minutes, fixed, credited against the build if you carry on with me. You can hold that up against the £995 and the £1,250 above and decide for yourself what each one is buying.

The figure I would rather you took away, though, is £2,000. That is the median UK business, and it is nothing like the number the pricing guides have been preparing you for. Most owners are not buying a transformation programme. They are buying a bit of help with one specific job that has been annoying them for a year, and then doing the next one on their own.

If you do not yet know which job that is, the free AI Opportunity Scorecard takes two minutes and gives you an estimate of the hours and money leaking out of your week. If you already know exactly which job it is, book the Audit and we will build the first working version of it together while you watch. Either way, work your own number out before you accept somebody else’s.