Identify the decision a system will change and the person who has authority over that decision before any contract is signed; if either detail is missing, the purchase is a demonstration. Applied to AI-powered analytics in the UK, that test predicts more of the result than model choice, vendor size or headline price, and it is what separates the three shapes below.
Three shapes, named as the things they are
Three shapes reach UK buyers, and they are not one product at three prices.
Decision-led in-house analytics is a small internal group that writes a decision inventory first, builds the pipeline feeding those decisions second, and adds models third. Its output is a set of decisions that used to run on judgement and now run on a documented number.
The assistant layer is a natural-language query surface bolted onto a warehouse, lakehouse or BI estate you already operate. It is sold per seat, deploys in weeks, and exists to shorten the distance between a question and a report that already exists somewhere.
The managed analytics programme is a platform vendor or delivery partner that takes contractual responsibility for the data platform and for the models sitting on top of it, usually under a multi-year agreement with a service wrapper.
| Attribute | Decision-led in-house | Assistant layer | Managed programme |
|---|---|---|---|
| What it reads | Any source it can lawfully join | The curated semantic layer | Broadly, under a data processing agreement |
| What it writes | Three to ten reviewed fields per decision | Query log and cache only | Whatever the contract scopes |
| Data quality burden | Your staff, narrow scope | Unchanged, sits with whoever owns the warehouse | Moved into the contract |
| Time to first usable output | Weeks to months, slower than the sale | Days to weeks | Months |
| Who repairs it after drift | You | The vendor | The service commitment |
| Failure mode | Slow, visible and fixable | Fluent answers built from uncurated joins | Decided by clauses you did or did not read |
Step 1. What each shape may read, and what it may write
Read scope gets all the attention. Write scope determines your obligation.
Decision-led work accesses data it can lawfully join under an existing lawful basis and writes to a short list of operational systems through a reviewed interface. Typical write scope is three to ten fields per decision, versioned, with a named approver.
The assistant layer accesses the semantic layer of the warehouse and writes no operational data. Its only writes are the query log, which is thin but genuinely useful, and a cache.
The managed programme accesses data broadly under a data processing agreement and writes into whatever the contract scopes. That scope sentence is the one buyers read last and should read first.
The ICO's guidance on AI and data protection prioritises accountability and governance and requires a data protection impact assessment before processing likely to result in high risk to individuals. A shape that writes into a decision about a person needs that assessment and a contestable route for the person affected, which the ICO sets out under Article 22 of the UK GDPR. A shape that only views a report does not. That difference is the entire reason to separate the two boundaries.
Step 2. Where the data quality burden lands
All three shapes need clean data. Only one of them lets you choose how much cleaning you buy.
Advania's analysis of AI data analytics makes the split in tooling terms: AI data analytics automates collection, cleaning and analysis, and it lets an analyst move onto interpretation, while manual methods spend the same effort on labour a model can carry. On that account the reclaimed analyst time is the first measurable return, and it arrives before any model does.
Decision-led analytics places the burden on your own staff, but only for the domains named in the decision inventory. Narrower scope, deeper work.
The assistant layer leaves the burden exactly where it found it. If your semantic layer is curated, the assistant looks impressive. If it is not, the assistant generates fluent answers from uncurated joins, which is worse than returning no result, because the reader cannot tell the difference.
The managed programme moves the burden into the contract. You pay for it either way. The difference is whether the agreement includes a measurable quality target with linked remedies, or a best-efforts clause that looks good but has little effect. Advania reaches the same conclusion from the tooling side: A system is only as good as the data fed into it, and poor quality data generates misleading output regardless of the algorithm in front of it.
Step 3. How each shape ages, and who repairs it
Every shape decays. The question is whose budget absorbs the decay and how quickly the repair happens.
Decision-led analytics ages slowly and locally. The model drifts, someone retrains it, and the decision definition stays stable, so the review conversation is short. You own the decay and you can see it coming.
The assistant layer ages on the vendor's schedule. Product news provides updates on feature changes, access changes and deprecations, and because you built no software, you have little internal record of what the system was ever meant to do.
The managed programme ages as a commercial matter. Refresh cycles become a service commitment inside the contract, which is either the strongest position of the three or the weakest, depending entirely on the service levels and exit terms you negotiated.
Step 4. What each shape generates in UK paperwork
Public sector standards are now specific enough that private buyers borrow them, and this section is a shortcut through the useful parts.
The Data and AI Ethics Framework published by the Government Digital Service, updated in December 2025, sets out principles across transparency, accountability, fairness, privacy, safety, societal impact and environmental sustainability, and pairs them with a self-assessment tool maintained alongside project documentation.
PublicTechnology reported in October 2026 that the Government Functional Standard for Digital moved from a single mention of AI to more than sixty. The standard now expects that data assets used in AI systems are recorded with their purpose, provenance, quality, limitations, access conditions and retention requirements.
The Government Analysis Function AI hub collects approved guidance in one place, including the AI Playbook for the UK Government and its ten principles, and runs a cross-government AI community that meets monthly.
Against that, the three shapes generate very different volumes of paper. Decision-led work creates it naturally, because the decision inventory and model records already exist. The assistant layer generates a data protection note. The managed programme delivers whatever the vendor's assurance pack contains, and the pack is worth reviewing for what is absent as much as for what is present.
Published UK figures worth carrying into the business case
Figures below come from HP's UK AI roadmap guide and QuantumXL's implementation guide.
| Measure | Published value |
|---|---|
| Typical enterprise AI implementation timeline | 18 to 24 months (HP) |
| AI projects failing to deliver expected business value | around 70 per cent (HP) |
| Projected UK AI business value by 2030 | £2.1 trillion (HP, citing PwC UK Economic Analysis) |
| Share of companies reporting measurable ROI | 25 per cent (QuantumXL) |
HP's guide also notes that UK organisations must work to ICO guidelines, UK GDPR and sector rules such as FCA requirements for financial services, and that governance has to run through the deployment and continue past the approval. QuantumXL's guide presents the same point as a sequence: define the business problem and the outcome measure first, assess readiness second, build the cross-functional team third, scale what worked fourth, and govern it in production fifth.
Where each shape sits against four thresholds a UK buyer can check
Four thresholds separate a working deployment from an expensive one, and each shape answers them differently.
| Threshold | Decision-led in-house | Assistant layer | Managed programme |
|---|---|---|---|
| Named decision owner exists before go-live | Yes, by construction | Rarely; the tool is bought for a team | Named in the statement of work if you ask |
| Data provenance recorded per field | Yes, for the fields the decision uses | No; the semantic layer is treated as given | Contracted, at the granularity the vendor supports |
| Human review of outputs with authority to overturn | Built into the write path | Not present | Depends on the service definition |
| Exit route documented and tested | You hold the code and the records | You hold the query log | Negotiated into the termination clause |
The pattern is consistent across all four thresholds. The format used for operations contains the most evidence, because it must. The form that only shows data has the smallest capacity. The managed programme includes whatever the contract states, which is why the scope and exit sentences deserve a second look before legal review closes.
What to do in the next ten working days
- Write the decision inventory. List every decision the analytics programme is expected to touch, with an owner's name against each one.
- Run the data protection impact assessment on the first decision that concerns an individual, using the ICO chapter on accountability and governance as the checklist.
- Ask the vendor for the two scope sentences, the read scope and the write scope, in writing, and file them with the contract.
- Walk the four thresholds above and mark each shape red, amber or green. Items marked red are sent to the procurement lead before signature.
Sources
- Artificial Intelligence (AI) guidance, best practice and standards
- Data and AI Ethics Framework
- Guidance on AI and data protection
- AI Roadmap Strategic Implementation Guide for UK Businesses
- AI Implementation Strategy: A Step-by-Step Guide for Business Leaders
- How AI data analytics will revolutionise business
- GDS makes AI updates to government's digital governance standards


