Skip to content
Koderead

GBP

United Kingdom

Reference-led, sceptical of claims, and fastest to trust a worked example.

A small office reception, a person on the phone

UK mid-market buyers discount vendor claims heavily and weight peer evidence and demonstrable work far more.

Market notes

How buying works in the UK market.

Evidence beats positioning

Claims about transformation land poorly without something to look at. A demonstrable workflow, even a concept one clearly labelled as such, does more than a deck.

Professional services concentration

Accountancy, legal and consultancy firms form an unusually large share of the mid-market, and they face the sharpest version of the productivity-versus-billing problem.

Procurement is lighter, diligence is heavier

Fewer formal procurement hurdles than the US, but more detailed questioning of how something actually works before commitment.

Legacy estates are common

Long-established firms frequently run software with no usable API. Establishing systems access early materially changes the estimate.

Readiness

What decides the design in United Kingdom.

The things that actually change when scoping a build here — ordered by whether they are routine, need scoping, or shape the architecture from day one.

UK engagement readinessScoping checklist
  • Working demonstration firstClaims are discounted here. Something to look at moves further than a deck.Standard
  • UK GDPR lawful basisBasis, minimisation, retention and subject rights specified at design stage.Needs scoping
  • Professional body requirementsFor regulated professions these frequently bind harder than statute.Decides the design
  • Explainability for automated outcomesFinancial services in particular expect firms to explain them.Needs scoping
  • Legacy systems accessLong-established firms often run software with no usable API. Establish early.Needs scoping
  • Lighter procurement, heavier diligenceFewer formal hurdles, more detailed questioning of how it actually works.Standard

Described in general terms to explain how it affects a build. Not legal advice — every engagement assumes you take your own.

Regulatory context

What shapes the design here.

Described in general terms to explain how it affects a build. It is not legal advice, and every engagement assumes you take your own.

  • UK GDPR and the Data Protection Act

    Lawful basis, minimisation, retention and subject rights all apply to automated processing. In practice this means specifying at design stage what data the system touches and for how long.

  • Professional body obligations often bind harder than statute

    For regulated professions, supervision and record-keeping requirements from the professional body frequently constrain a design more tightly than data protection law does.

  • Sector regulators are active on automated decisioning

    Financial services in particular expect firms to explain automated outcomes. Systems that cannot show their reasoning are difficult to defend.

Engagement shape

Typically: a worked demonstration first, then an assessment, then one workflow delivered end to end before any broader commitment.

You know AI matters and you do not yet know where it would apply here.

Working in United Kingdom?

The assessment is the same wherever you are. What changes is how the build gets scoped around the constraints above.

Eleven questions, scored in your browser