Every business has data. Almost no business has data its AI can actually use. The pattern repeats sector after sector: companies pour budget into pilots without ever opening the underlying data, then look surprised when the model returns confident nonsense. The cost is rarely the pilot itself. The cost is two years of progress built on a foundation that was always going to give way.
What data readiness actually means
Data readiness is not a tooling question. It is whether the information your business runs on is accurate enough, accessible enough, and well-governed enough that a machine can act on it without producing damage.
Most organisations confuse "we have lots of data" with "we have usable data". They are not the same thing. The first is a storage problem. The second is a foundations problem, and it is the one AI exposes. Solving it is what our data strategy engagement exists to do.
Quality
Is the data accurate, complete, and current? Stale records are not a minor annoyance. They are the fastest way to get an AI system to make confidently wrong decisions at scale. Audit your top three datasets for the percentage of records last verified within the last twelve months. The number will be lower than you think.
Governance
Who owns each dataset? Who can access it? Who is accountable when it produces a wrong answer? In most organisations, the answer to all three questions is the same: IT, probably. That is not governance. That is the absence of governance dressed up as a job title.
Accessibility
Can the people who need the data actually get to it, in something close to real time, without raising a ticket and waiting three weeks? If the answer is no, your AI projects will inherit that same friction. Models that cannot reach the data they need are not AI projects. They are demos.
Structure
Is your data organised in a way a machine can use, or is it trapped in spreadsheets, PDFs, scanned contracts, and the heads of three people who are about to retire? Unstructured data is not unusable, but the work to make it usable is most of the project, and it is rarely scoped honestly upfront.
Lineage
Where did the data come from? When was it captured? What rules were applied to it on the way in? If you cannot answer those questions for the data your AI relies on, you cannot trust the output. Lineage is the boring discipline that separates AI you can audit from AI you have to defend.
The four readiness bands for Data
Our audit scores your data readiness from 5 to 20 across five questions, giving you one of four bands. The bands describe how much groundwork you have left, and how seriously you should treat what is sitting underneath your AI initiatives today.
- Ready17–20
Foundations are sound. Pick the right bets.
Your data is accurate, current, and accessible. You have clear ownership and a documented governance model. Lineage is traceable. At this band you can run AI projects with confidence that your inputs are not going to ambush you. The risk now is over-confidence: AI still magnifies whatever sits downstream of the data.
- Progressing12–16
Real gaps, fixable in order.
Most established businesses sit here. You have decent data in some domains and weaker data in others. Governance exists in pockets. Accessibility is uneven. The work is real but tractable: pick one domain, get it to ready, then move to the next. Trying to fix everything at once is how programmes drift for two years.
- Developing7–11
Most AI pilots will fail until this is sorted.
Significant gaps in quality, governance, or access. Some datasets are good, but they sit in systems that cannot talk to each other. Ownership is unclear. At this band the honest answer is that AI investment will not pay back until the foundations close. Spend the money on the groundwork instead. It will be cheaper in the long run.
- Critical5–6
Stop. Fix the foundations before another pound gets spent.
Data is fragmented, stale, or untrusted. No one is sure who owns what. Spending on AI tools at this band is not investment, it is decoration. Stop the pilots. Map the data estate. Get one source of truth working. Then come back to AI when you have something it can stand on.
Why most teams get this wrong
After running this audit across more than a hundred organisations, the same four patterns repeat. Each is human, not technical. Each is fixable. Each kills more AI investment than any model limitation we have ever seen.
They confuse "we have lots of data" with "we have usable data"
Volume is a comfort blanket. We have heard "we are a data-rich business" from leadership teams whose customer records were split across three CRMs that disagreed on what counted as a returning customer. The question is never how much data you have. It is whether any two systems return the same answer to the same question.
They treat data quality as IT's problem
Data quality is owned where the data is created, not where it is stored. If sales reps can close a deal without filling in fields they consider boring, those fields will be empty, and no amount of data engineering will fix it. This is a people and capability problem dressed up as a technology problem.
They run pilots on the prettiest dataset, not the messiest
Every business has one clean dataset and quietly pretends it is representative. AI pilots get scoped against it because that is where the demo will look good. The pilot reports as a success, the rollout meets reality, and seven-figure programmes come apart at exactly this step. The pilot dataset has to be the awkward one. Combined with broken process, that is the most expensive failure pattern we see, and it is why we built the process pillar alongside this one.
They never actually look at their own customer data
It is uncomfortably common to find that senior leaders have not opened the underlying records in years. Reports get reviewed. Dashboards get scrolled. The actual rows do not get inspected. The first time anyone really looks at the data is when an AI system makes a public mistake based on it. By then it is a press release.
What good actually looks like
"Data ready" does not mean perfect. It means honest. Honest about what you have, where it lives, who is accountable for it, and what the gaps are. Most organisations that get this right are not the ones with the cleanest data. They are the ones that have stopped lying to themselves about it.
42%
of companies abandoned most of their AI initiatives in 2025, up from 17% the year before. The figures are not a story about bad AI. They are a story about businesses that built on foundations that could not hold the weight.
The bar is roughly this. You can name the three or four datasets that matter for your AI use case. You know who owns each one. You can describe its quality, currency, lineage, and access pattern without consulting a third party. When something is wrong, you know who fixes it and how long it takes. The formal side of all this sits in the governance pillar, which is where the rules get teeth.
None of that is glamorous. None of it sells consulting decks. But it is the difference between AI that delivers a measurable return and AI that becomes an expensive lesson. The Deep Dive report walks through your specific gaps and the order to close them.
How the audit measures your data readiness
The Data pillar in our audit is five questions, each scored 1 to 4: quality, governance, accessibility, structure, lineage. The score totals to a number between 5 and 20, which places you in one of the four bands above. Five questions sounds small. After more than two decades inside these projects, we have not found ones that signal more honestly with less.
The free 7-minute version gives you the band, the score, and a teaser of your biggest gap. The £97 Full Report gives you the full pillar-by-pillar diagnosis. The £497 Deep Dive takes that further with a 30 / 60 / 90 day plan personalised to your sector and size. All three start the same way. If you would prefer to talk to a consultant about data specifically, we also offer data strategy as a standalone engagement.