How to choose an enterprise AI consultancy in the UK

Search for an AI consultancy in the UK and the results mix four kinds of firm that share a label and almost nothing else. Which one you need depends on the problem, and most bad engagements start by buying the wrong kind, not the wrong firm.

The single most predictive question in selection. Firms where strategy and engineering are separate departments produce strategies that engineering quietly rewrites, and systems that drift from the deck that sold them. Firms where the same people write the strategy and the code cannot hide behind the handover, because there is none.

Ask to meet the people who would deliver, not the people who sell. Ask what they personally shipped in the last quarter. A practice that cannot answer that question with named systems is a broker.

Demonstrations are cheap and production is expensive, so production is the evidence that matters. Ask every candidate for one real workflow they took from ambition to a system people use daily, and how long it took.

Then read the numbers with their provenance attached. A figure published by the client, a figure the consultancy measured, and a forecast are three different strengths of evidence, and a firm that blends them into one claim is telling you how it will report your programme too.

Every firm will say the word governance. The separating question is where it lives. If the answer is a policy document and a committee, the controls depend on people remembering them. If the answer is identity and permissions the system enforces, deterministic checks that gate what an agent may do, evaluation that runs on every change and human approval on consequential actions, the controls hold when nobody is watching.

The pattern to look for is the model proposing and something deterministic deciding: an agent drafts, and validators, reconciliations and human gates decide what proceeds. A consultancy that cannot describe its gating pattern in that level of detail has not built one.

Most AI consultancies hold some vendor relationship, and the honest ones state it plainly, because it shapes advice. A reseller attached to one vendor will recommend that vendor. A model-selective practice chooses by workload and production evidence, and can show you systems running on more than one stack.

Partner statuses are worth reading precisely. 1AYM, for example, is an OpenAI Select Partner: a company status that describes a relationship with the vendor, stated so a buyer can weigh it, not evidence by itself that the firm fits your problem. Treat any partner badge the same way, from any firm: as a disclosure to interrogate, not a shortcut past the four checks above.

The end state of a good engagement is that the client owns the code, the architecture, the operating model and the capability, and could continue without the consultancy. Ask directly: what do we own on the last day, who can run it, and what does it cost to keep running.

Firms whose commercial model depends on you being unable to leave will resist that question. That resistance is the answer.

If the problem is a well-served product category, buy the product. If you have strong engineering leadership and a clear architecture, hire or borrow engineers instead of buying design you already have. If nobody senior owns the outcome internally, fix that first, because no external firm can substitute for an absent owner.

A consultancy earns its fee where strategy, architecture and engineering have to move together and the organisation wants to keep the result: taking the first governed workflow into production, standing up the platform and controls around it, and transferring the capability to run it.