An AI readiness assessment is a scored diagnostic of whether your organisation can actually ship and run AI — not whether AI could theoretically help you. It looks at five operational dimensions, produces a score per dimension, and names the gap to close first. It is a triage instrument, not a strategy document, and that distinction is most of what separates a useful one from an expensive one.
The reason it exists: 91% of mid-market firms use generative AI, but only 25% have it integrated into core operations (RSM, 2025). That 66-point gap is almost never a shortage of ideas. It's one of five things being missing, and an assessment's whole job is telling you which.
The five dimensions
- Data — does the knowledge the system needs live somewhere queryable, or in inboxes, PDFs, and people's heads? Poor data readiness is the top obstacle data leaders name for moving pilots to production (Informatica, 2025).
- Process — is the workflow stable and documented enough that a correct outcome is definable? A process that changes weekly can't be automated; it can only be chased.
- Tooling — can software authenticate into your systems and write, not just read? This is where homegrown internal tools and expensive integration tiers surface.
- Team — is there anyone who will own the system after launch, and enough technical capacity to be a real counterpart during the build?
- Alignment — do the people funding it, running it, and being changed by it agree on what success is? This is the quietest failure and the most fatal.
You'll notice none of these are about the model. That's the point. Model capability is not your constraint in 2026 — it's the least of your problems and it improves without you doing anything.
What a good assessment produces
Three things, and nothing else:
- A score per dimension, so the weak one is visible rather than averaged away. A single composite number is worse than useless — a company strong on four dimensions and broken on one has a specific problem, not a mediocre overall grade.
- A named first move. One thing to do next, chosen because it unblocks the most.
- An honest verdict on timing — including not yet, when that's the answer.
What it should not produce is a roadmap, a maturity curve with your logo on it, or a list of fifteen use cases ranked by excitement. Those are the deliverables of an assessment sold as the front end of a longer engagement, and they're the reason "readiness assessment" has a slightly bad reputation.
Readiness of the organisation vs. readiness of the workflow
These are two different tests and you want both to come back clean.
The five dimensions above are the organisational test — can this company operate a live AI system at all. The workflow test is separate: is this specific piece of work worth automating, and is it automatable? That one turns on volume, whether a right answer is knowable, and whether anyone owns the metric — we cover it in five signs your business is ready for an AI agent.
A company can pass one and fail the other in both directions. Great data and tooling but no workflow that costs enough to justify a build. Or an obviously painful, high-volume workflow inside an organisation with no owner and no alignment — which fails despite the business case being excellent on paper.
When you don't need one
Skip it if you can already answer these without discussion: which workflow, what it costs you today, who owns the number, and whether software can reach the systems involved. If those four are genuinely settled, an assessment will confirm what you know and cost you two weeks. Go scope the build.
Skip it too if you've shipped production software before and have engineers who can evaluate the integration surface themselves. Readiness assessments are most valuable to organisations that haven't done this — which is most of the mid-market, and no criticism of anyone.
Don't skip it if two or more of the five dimensions make you hesitate, if a previous AI attempt stalled and nobody agreed on why, or if the people funding this and the people whose work changes have never been in the same conversation.
Free triage vs. a paid diagnostic
They answer different questions, and conflating them is how people overpay.
A free assessment is triage. Ours is six questions across the five dimensions, scored, with a recommended first move, in a few minutes. It tells you roughly where you stand and what's weakest. It cannot tell you what to build, because it hasn't looked at your systems.
A paid diagnostic looks at the actual workflow and data and ends with something real. Ours is the AI Transformation Sprint at $25,000 — two weeks, ending in a deployed pilot and a costed build plan rather than a slide deck, and it credits toward the build it scopes. That's the version worth money: a diagnosis that leaves working software behind, which is the Audit phase of how we run everything.
The rule of thumb: use the free one to find out whether you have a problem. Pay for a diagnostic only when it ends in something that runs.
