AI readiness audit.
Five dimensions, one honest score. Before you spend money on a bespoke AI build, find out whether your operation is in a position to actually make it pay back — or which foundations need fixing first. Free. Technical. No deck. No pitch.
Routes through the same booking flow as the discovery call
Why "readiness" matters separately from "need"
The Bottleneck Scorecard answers where is your operation leaking the most? The readiness audit answers a different question: are you in a position to act on it?
Most bespoke AI builds that stall don't stall on engineering. They stall on one of five dimensions the operator hadn't thought about properly before commissioning. The audit surfaces them before the build budget gets committed — so you either fix the gap first, or commission a build with the gap factored into the scope.
The five dimensions
Data
Is the data the AI would need actually structured and accessible? Or is it scattered across PDFs, email attachments, WhatsApp messages, and three different spreadsheets nobody fully owns? Data shape is the single most common readiness gap. A bespoke build can fix data structuring as part of the work — but it adds time and cost, and the operator needs to know that going in.
Process
Is the workflow stable enough to encode? A process that changes every week as the team tries different approaches is not yet ready for automation — automating it just freezes the wrong shape. The audit looks for whether the workflow has settled, or whether the operator is still figuring out the right shape.
Team
Is there someone on the operator's side who can own the build relationship — answer questions, make decisions, sign off on iterations? Not a project manager. A domain expert with authority. Without this person, even a well-engineered build stalls because nobody on the client side can move it forward.
Regulatory shape
Are the relevant constraints actually understood? UK GDPR. Sector-specific regulation (SRA for legal, ICAEW/ACCA for accountancy, MHRA for healthcare, FCA for financial, etc.). Professional-body AI policies. Insurance requirements. The audit identifies which constraints apply and whether they've been considered in the build shape.
Commercial readiness
Is the budget realistic for the scope being considered? Is the operator committed to actually using the system once built, or is this exploratory? Are decision-makers aligned, or is one stakeholder pushing while another is undermining? Most stalled builds stall on commercial readiness, not engineering.
What you walk away with
- A five-dimension readiness map for your operation
- A clear flag on which dimensions are blocking and which are workable
- A recommendation: proceed to build scoping, fix specific gaps first, or bespoke AI is not the right shape for your situation right now
- If gaps need fixing, a list of what specifically and an offer to revisit when they're addressed
How it relates to the discovery call
The discovery call and the readiness audit cover overlapping ground — they're both 45–60 minute technical conversations that end with a costed map. The difference is emphasis. The discovery call leads with "where is your operation leaking?" and ends with a costed build proposal. The readiness audit leads with "are you set up to act on a build?" and ends with a five-dimension readiness map plus build/no-build/fix-first recommendation. Most operators do one or the other depending on which question is louder; some do both.
Related
- Bottleneck Scorecard — 60-second self-diagnostic for where your operation is leaking
- Book a discovery call — the build-shaped version of this conversation
- The three operational bottlenecks — the framework the scorecard is built on
- How to evaluate an AI consultant — once you're ready, how to pick the right consultant
Common questions about the readiness audit
Different question. The Bottleneck Scorecard answers "where is your operation leaking the most?" — it identifies problems. The AI Readiness Audit answers "are you in a position to act on a bespoke AI build?" — it identifies whether the foundations support a build, regardless of where the problems are. Most operators benefit from doing the scorecard first to find the problem, then the readiness audit to check whether they're set up to fix it.
It means five things, scored independently: (1) Data — is the data the AI would need actually structured and accessible, or scattered across PDFs, emails, and spreadsheets? (2) Process — is the workflow stable enough to encode, or does it change every week? (3) Team — is there someone on the operator's side who can own the build relationship? (4) Regulatory shape — are the constraints understood (GDPR, sector regs, professional bodies)? (5) Commercial readiness — is the budget realistic for the scope, and is the operator committed to use the system once built?
45–60 minute technical call. I walk through the five dimensions with specific questions per dimension. You answer; I score. At the end I give you the five-dimension readiness map, flag the dimensions that need work before a build will pay back, and recommend either (a) proceed to scoping, (b) fix specific readiness gaps first, or (c) bespoke AI is not the right shape for your operation right now.
No. The audit is free, the recommendation is honest, and "don't build right now" is a frequent outcome. If a build is the right answer, we move to scoping. If readiness gaps need fixing first, you get a specific list of what to fix and an offer to revisit when those are addressed. If bespoke AI is not the right shape at all, I tell you and you keep the map.
UK businesses considering commissioning a bespoke AI build who want to know whether they're set up to make it pay back before they commit budget. Founder-led businesses and operators with a tight ops team are the most common profile.
Still have a question? Book a discovery call — direct line to me, Dean.
Find out where your build would actually start.
Free 45–60 minute audit. Five-dimension readiness map. Honest build/no-build/fix-first call at the end.
Book the readiness audit