What does AI implementation really cost?

Ask what implementation costs and you will be quoted a build fee. That number is real and it is frequently not the biggest one, and three of the categories below arrive monthly and never stop.

No figures here, because a figure without your context is marketing. What follows is the shape of the bill.

One-time: the build

Design, construction, integration, testing. This is the number in the proposal.

The thing that moves it most is not ambition, it is how many systems have to talk to each other. One process inside one system is cheap. The same process spanning your CRM, your finance tool, and a spreadsheet somebody maintains by hand is a different project with a different price.

One-time: cleaning up data, which nobody quotes

The most commonly missed line and often a large one.

The moment a job needs information from two systems, somebody has to reconcile them: the customer whose name is spelled two ways, the records with no shared identifier, the fields that were used for something else three years ago and never migrated.

Nobody can size this before looking, which is why it is usually absent from a quote and appears later as a change order. Ask directly how it will be handled and priced if your data turns out to be messier than expected. The answer being a named process rather than silence is what you want.

One-time: your own people's time

Real, uninvoiced, and consistently underestimated. Interviews, access, decisions, reviewing what gets built, testing it against reality, learning it.

For a small business this is genuinely material, because the people involved are the same people doing the work that pays for the project.

Recurring: model and platform usage

Usage-based, so it scales with your volume. More conversations, more documents, more work processed means a bigger monthly number.

Ask for the estimate at your current volume and at double it, because the second figure is the one that matters if the project succeeds. A supplier who has not thought about this has not run one at scale.

Recurring: the services underneath

Automation platforms, hosting, messaging, storage, whatever third-party tools the solution depends on. Individually modest, collectively noticeable.

These should be on accounts registered to you and billed to you rather than marked up through a supplier. That is partly about cost and mostly about being able to leave. Why it matters more than any exit clause.

Recurring: somebody watching it

The line most often assumed away, by both sides.

Live automation degrades. Your business changes, source systems change their fields, models get updated underneath you. Some of that breaks loudly and some breaks silently while appearing to work, which is worse.

So either a technical person on your side owns it, or you pay the supplier to, or nobody does and you find out in a few months. All three are legitimate choices. Only the third one is usually made by accident. How this decays.

Recurring: tuning, which is not the same as maintenance

Maintenance is keeping it running. Tuning is keeping it correct as your business drifts from what it was told: new services, changed hours, a policy that shifted.

The first month of real use always produces changes. Ask whether that is included and for how long, because "we will tune it" without a period attached is not a commitment.

The number to actually ask for

Total cost of ownership over two years. Build, plus twenty-four months of everything recurring, plus an honest allowance for data work.

Compare that against the value in the roadmap. A build fee against an annual benefit is a comparison designed to look good, and it is the one you will usually be shown.

Where the cost is worth it

Not the clever part. The dependable part.

Getting something to work is now comparatively easy. Getting it to run unattended, handle the case nobody anticipated, escalate correctly, and behave sensibly at three in the morning is where the engineering lives, and it is invisible in a demo. That is the line worth paying for, and the first thing cut when a price is squeezed.

What we do about the uncertainty

The roadmap carries an estimate per recommendation, including what each one would cost to run rather than only to build, because the run cost changes which items are worth doing at all. Occasionally it changes the recommendation to "buy something existing" or "do not bother".

We price the roadmap as a fixed fee so your exposure is known upfront, and it is yours to execute with anyone. How that works, and how the four pricing models differ if you are comparing proposals.