# How to choose an AI consultancy in the UK
> A practical buyer guide to choosing an AI consultancy in the UK: delivery evidence, data handling, evaluation, responsibilities and comparable project costs.
Author: Matthew Ford
Published: 2026-10-02

<p><em>Disclosure: this guide is written by Bit Zesty and includes the criteria we would want applied to us. It is not an independent ranking of consultancies.</em></p>

<p>When comparing AI consultancies, a demonstration tells you only part of what you need to know. The proposal also needs to explain what will happen to your data, how the system will be evaluated and who will maintain it. These questions help turn a promising presentation into a supplier decision you can assess.</p>

<h2>1. What have you delivered, and what was your part?</h2>

<p>Ask for an example close to your intended use. What did the supplier build, was it a prototype or a live service, and which parts were provided by someone else? If it is in production, ask how it is monitored, how errors are handled and what it costs to operate. A useful answer makes the supplier's contribution and the limits of the example clear.</p>

<p>Our <a href="/client-stories/microsoft-swiftkey/">SwiftKey work</a> is an example of application engineering around a client's prediction capability: we built a Rails backend and API that accessed users' permitted data and connected it to SwiftKey's prediction engine. It is evidence of that integration work, not a claim that we built the engine itself.</p>

<h2>2. How will you handle our data?</h2>

<p>Ask which systems, model providers and subprocessors would receive information, where it would be processed and what would be retained. Check the proposed access controls and contractual terms against the actual product configuration. Do not assume a provider's general privacy statement answers every question about your deployment.</p>

<p>Ask about the consultancy's own practices too: access management, secure development and its use of AI tools. For any certification, check the current scope and supporting evidence. Our <a href="/technical-assurance/">technical assurance page</a> describes the controls and responsibilities to discuss with us.</p>

<h2>3. Who maintains it after launch?</h2>

<p>Models, source information and operating requirements can change. Ask who will review output quality, investigate failures, manage supplier changes and approve updates. Include human review effort and support in the cost, not just the model API bill.</p>

<p>A proposal for a limited trial can reasonably stop at a findings report. A proposal for a live application needs an operating and handover plan. Make that boundary clear before comparing prices.</p>

<h2>4. Will you consider an approach without AI?</h2>

<p>Some problems are better addressed by an integration, conventional automation or a clearer workflow. Ask the consultancy to explain what judgement or interpretation the AI component adds and why that justifies its cost and risk.</p>

<p>An <a href="/blog/ai-readiness-assessment/">AI readiness assessment</a> starts with one process, its current performance and the evidence needed for an investment decision. If feasibility is still uncertain, a <a href="/services/rapid-prototyping/">focused prototype</a> can test the important assumptions before a larger build is agreed.</p>

<h2>5. How will we judge the result?</h2>

<p>Agree representative examples, success criteria and unacceptable failures before selecting the best-looking outputs. Measures might include handling effort, correction rates, response time and the amount of human review required. Ask how the evaluation covers difficult cases and information the system should refuse to use.</p>

<p>Keep a trial's result separate from a production claim. Passing a small test does not establish how a service will behave with a different workload or after a supplier changes its model.</p>

<h2>6. Who will do the work?</h2>

<p>Ask who will deliver the project, which skills they bring, whether any work is subcontracted and who owns engineering, evaluation and delivery decisions. Agree named contacts, review points and how your technical and operational teams will participate.</p>

<p>For a language-model application, that work may include the interface, retrieval, permissions and human review around the model. Our <a href="/services/ai-gen-ai-development/">generative AI development service</a> describes that implementation scope; it is separate from choosing whether an AI project is worthwhile.</p>

<h2>How to compare the cost</h2>

<p>Ask each supplier to separate assessment, data preparation, implementation, evaluation, deployment and ongoing support. Record the assumptions about usage and human review. A lower quote may cover fewer responsibilities; a larger quote needs a clear explanation of the additional work. Neither price alone establishes delivery quality.</p>

<p>For an initial discussion, bring one process, the systems it involves and the people accountable for it. Our <a href="/services/ai-automation/">AI consulting and automation service</a> explains how we assess the options and agree a useful next step.</p>
