What does AI implementation actually cost — and why the question is usually wrong

If you search "how much does an AI consultant cost," you will find day rates ranging from £400 to £2,000, a few LinkedIn posts about value-based pricing, and approximately zero useful answers.

That is not because the information is hidden. It is because the question is wrong.

The price is not the problem. The scope is.

Why day rates mislead you

When a founder asks what an AI consultant costs, they are usually trying to answer a different question: can we afford to get this work done, and will we get something real at the end of it?

A day rate does not answer either of those questions.

A specialist charging £800 a day with a clear brief, defined deliverables and four weeks of focused work will almost always cost you less — and deliver more — than someone at £500 a day on a vague engagement that drifts for three months.

The unit is wrong. You are not buying days. You are buying a defined outcome from someone with the right capability to deliver it.

The real cost driver is scope clarity

Here is what actually determines what AI implementation costs:

• How clearly you can describe the problem. Vague inputs produce vague proposals. If you cannot say what the current process looks like, where it breaks, and what good looks like at the end, you will get day rate estimates and open-ended engagements.
• Whether you have defined success criteria. "We want to use AI in our sales process" is not a brief. "We want to reduce the time our team spends on post-call notes by 60% within eight weeks" is a brief. One attracts exploratory conversations. The other attracts people who have solved it before.
• The complexity of what you are connecting. Implementing a simple AI workflow on clean data is not the same as integrating a language model into a legacy CRM with messy historical records and three internal stakeholders who disagree on the output format. Scope determines price. Clarity unlocks scope.
• The provider's deployment model. Some specialists work on time and materials. Others work on fixed-scope engagements with defined outputs. Some offer productised services — a specific outcome for a specific price — because they have done it enough times that the scope is predictable. That last category is often the most efficient option for early-stage teams.

What a capability brief does that a budget conversation cannot

Most organisations approach this backwards. They set a budget, go looking for someone who fits inside it, and then try to get that person to define the scope for them.

The problem is that you are asking the provider to do two jobs: sell themselves and design the engagement. That creates incentives that do not always point in your direction.

A capability brief flips this. You start with the work that needs doing: the problem, the current state, the outcome you want, the constraints you are working within, and the timeline you are operating to. You define the engagement before you find the person.

When a provider sees a well-structured brief, they can respond to the actual work rather than guessing what you need and pricing conservatively to protect themselves. The conversation becomes about fit and delivery, not about justifying a number.

Better brief. Better response. Better engagement.

How to read a provider before you talk price

Before any conversation about cost, look for three things in a provider's profile or proposal:

• Scope they have owned. Not tools they have used. Not platforms they are certified in. Work they have actually defined and delivered. What did the engagement look like? What were they responsible for?
• Outcomes they can point to. Vague claims about "improving efficiency" are easy to make. Specific outcomes — reduced processing time, a working integration, a deployed tool used by the team daily — are harder to fake.
• How they handle constraint. Ask what broke, or what they would do differently. Experienced providers have stories about where things got complicated. That is not a red flag. Absence of any such story probably is.

A structured capability profile should give you most of this before the first call. If it does not, that is information too.

The number you actually need

There is no universal answer to what AI implementation costs. A focused four-week automation build for a ten-person team is a different engagement to an AI strategy review for a scaling company with three product lines.

But here is what you can know before you talk to anyone:

If you can describe the work clearly — problem, current state, desired outcome, timeline, constraints — you will get sharper responses, more relevant providers, and a number you can actually evaluate.

If you cannot describe it yet, the first thing to buy is clarity. Not a consultant.

If you have AI, product, automation or engineering work that needs doing in the next 30 to 60 days, submit your first capability brief. The platform walks you through the key sections and surfaces relevant providers from there.

Submit your capability brief: https://www.deployed.works/launch/cohort-1