Your business is ready for AI when it scores well across five dimensions: one specific measurable outcome, AI-ready data, a connectable technology stack, written governance, and leadership willing to redesign the workflow rather than bolt AI onto it. Score each dimension from 0 to 5, then double your data score and your workflow-redesign score, because those two are where projects actually die. A total at or above 28 of 40 means start now. Between 20 and 27, start narrow on one outcome while you close your weakest gap. Below 20, fix your lowest-scoring dimension before you commit budget. The number is not the point. The point is that it hands you a verdict plus the single gap to fix first, instead of a list of things to think about.
This checklist turns "are we ready for AI" from a daunting prerequisite into a decided answer. If you would rather we run this for you, see how we run an AI readiness and data feasibility assessment. Everything below is yours to use on your own, in about ten minutes.
Why is readiness the wrong question (and the right one)?
Most people ask "is my business ready for AI" as if it were a tooling problem. It is not. Across AWS, Microsoft, McKinsey, Deloitte, and Gartner the consensus is the same: readiness is a check across data, technology, processes, and people, and the failure modes are organizational, not technical.
The tools are already everywhere; the value is rare. McKinsey's State of AI found 88% of organizations now regularly use AI in at least one business function, up from 78% a year earlier, yet only about 6% qualify as high performers attributing 5% or more of EBIT to AI. That gap is the readiness gap, and another model does not close it.
So the right question is narrower: are you ready to redesign work around AI, on data the AI can actually use? McKinsey found only about 21% of gen AI adopters have redesigned even some workflows, meaning nearly 80% just layer AI on top of existing processes. Deloitte's 2026 survey of 3,235 leaders found only 30% are redesigning key processes around AI, while 37% use it at a surface level with no process change. The companies that get value are the minority doing the unglamorous work the checklist below measures.
What are the five dimensions of AI readiness?
Every credible authority names the same five, even when they word them differently. AWS lists five assessment steps; Microsoft scores three areas across a five-stage maturity model; McKinsey and Deloitte both reduce it to "can you redesign the work." Synthesized, here are the five, with what each is really testing.
| # | Dimension | The question it answers |
|---|---|---|
| 1 | Outcome | Have you defined one specific, measurable business outcome for the first project? |
| 2 | AI-ready data | Is your data consolidated, representative, high quality, and governed for the use case? |
| 3 | Connectable stack | Can your existing tools connect to AI through APIs and webhooks? |
| 4 | Governance | Are data privacy, consent, and mandatory human-review rules written down? |
| 5 | Leadership and workflow appetite | Will leadership sponsor the project and redesign the workflow, not just bolt AI on? |
Two of these five decide the outcome; the other three are the price of entry. AWS's first step is consolidating where information lives into trusted stores, because everything downstream depends on it, and McKinsey's strongest single finding is that workflow redesign is the factor most correlated with bottom-line impact. So this checklist weights dimensions 2 and 5 double. That one rule is the difference between a score that flatters you and a score that predicts whether the project ships.
How do I score my business in 10 minutes?
Rate each dimension from 0 to 5 using the anchors below. Be honest, and score the business as it runs today, not as you wish it ran. Scoring the fantasy version is how teams talk themselves into a stalled pilot.
| Dimension | Score 5 when | Score 1 when |
|---|---|---|
| 1. Outcome | One outcome with a number and a deadline (cut support response time 40% in 60 days) | "We should use AI somewhere" |
| 2. AI-ready data | Consolidated, clean, owned, governed for the use case | Scattered across apps, no owner, quality unknown |
| 3. Connectable stack | Your CRM, accounting, and support tools all expose APIs you can reach | Closed legacy tools, manual exports only |
| 4. Governance | Privacy, consent, and human-review rules written before the build | Nothing written; you will "sort it out later" |
| 5. Leadership and workflow appetite | A sponsor who will redesign the workflow around the agent | IT side project, no mandate to change how work flows |
Now apply the weighting. The two dimensions where projects die count double:
Total = Outcome + (Data x 2) + Stack + Governance + (Leadership x 2)
The maximum is 5 + 10 + 5 + 5 + 10 = 40. Add your five scores with data and leadership doubled, and read the verdict from the total.
How do I read my score?
The total tells you what to do next, not just how ready you feel.
- 28 to 40: ready, start now. You have an outcome, usable data, a reachable stack, written rules, and a sponsor who will change the work. Pick one workflow and pilot it in 30 to 60 days against your success metric, exactly as AWS recommends, then expand in small waves.
- 20 to 27: start narrow while you close one gap. You are close enough to begin, but one dimension is dragging. Run a contained pilot on your strongest area while you fix the weak one in parallel. Do not wait for a perfect score; readiness is a maturity stage, not a gate.
- Below 20: fix your lowest score first. Starting now would mean joining the 60% of projects Gartner expects to be abandoned. Find your single lowest dimension and close it before you commit budget. It is almost always data or leadership.
The verdict matters less than the next sentence: look at your lowest individual score, because that is the one gap to fix first. A high total with a 1 on data is not actually ready. The doubling is there precisely so a fatal weakness cannot hide behind strong scores elsewhere.
Want a faster, harder-to-fool read? We run this assessment on your real systems and data, then hand back the verdict and the one gap to fix first. Book a free consultation and we will score your readiness together.
Why does AI-ready data carry double weight?
Because it is the single biggest reason AI projects fail, and most companies quietly assume they have it when they do not.
"AI-ready data" is not just "we have a lot of data." Gartner defines it as data that is representative of the problem, of sufficient quality, and governed for the specific use case, with clear definitions, lineage, business rules, and ownership. By that bar, Gartner reports 63% of organizations either lack the right data management practices for AI or are unsure they have them, and the consequence is blunt: through 2026, Gartner expects organizations to abandon 60% of AI projects that are not supported by AI-ready data.
In plain terms, your data is AI-ready when:
- It is consolidated into a few trusted stores, not scattered across accounting, CRM, ecommerce, and ticketing with no single source of truth.
- It is representative of the cases the AI will actually see, not a clean sample that hides the messy real ones.
- It is good enough: complete, current, and consistent for this use case (not perfect everywhere, just trustworthy here).
- It is governed: someone owns it, the fields are defined, and there are rules for how it is used.
If you scored 0 to 2 on data, that is your first gap, full stop, regardless of how the rest of the checklist looks. This is the work most readiness guides bury as one bullet of five. It deserves the double weight.
Why does workflow redesign carry double weight too?
Because buying AI and changing how the work flows are two completely different things, and only the second one pays.
McKinsey's clearest finding is that workflow redesign is the single factor most correlated with bottom-line impact, and high performers are about 3.6x more likely to pursue transformational change. The mirror image is the failure mode: nearly 80% of adopters just layer AI on top of unchanged processes, which is why 88% adoption coexists with 6% real impact.
This is also why leadership sits in the same double-weighted dimension. McKinsey finds CEO-sponsored, top-down AI transformations are far likelier to deliver, because redesigning a workflow means changing who does what, and that needs a mandate IT cannot grant itself. With no sponsor willing to change the work, you can have perfect data and still stall.
The agentic wave makes this sharper, not softer. Deloitte found roughly 74% of companies plan to deploy agentic AI within two years, but only 21% report a mature model for agent governance, and Gartner expects over 40% of agentic AI projects to be canceled by the end of 2027 over cost, unclear value, or weak risk controls. Racing into agents without redesigning the work or writing the governance is the laggard signal, not the leader one.
Do I have to be fully ready before I start?
No. This is the trap baked into most readiness checklists, and it is worth naming.
The standard guides tell you to consolidate your data, write your governance, and upskill your people before you are "allowed" to get value. For a small business with no spare quarter, that reads as: do two quarters of unfunded foundation work, then maybe start. So they never start. The same providers' own numbers show where the do-it-yourself readiness-then-build path leads: 60% of projects without AI-ready data abandoned, only 21% of adopters ever redesigning a workflow, and only 25% of companies getting 40% or more of their pilots into production.
Readiness is a maturity stage you move through while delivering, not a wall you must finish climbing alone. Microsoft's whole model is a five-stage scale (exploring, planning, implementing, scaling, realizing) precisely because the answer is "where are you," not "yes or no." The practical move is the one AWS recommends: define one outcome, pilot it narrow in 30 to 60 days against a clear metric, and close your weakest dimension in parallel rather than up front.
This is also where a done-for-you partner changes the math. You do not have to become AI-ready by yourself before you can get value. The data wrangling, governance, integration, and workflow redesign can all be supplied as a service, and the agent planned, built, and run for you, including the monitoring that keeps it out of the pilot graveyard. If your weakest score is governance, our responsible AI governance and risk work closes exactly that gap.
How to get started
You do not need a transformation program to begin. Right now, score your business 0 to 5 on the five dimensions, double your data and leadership scores, and add them up out of 40. Read the verdict, then look at your single lowest score: that is the one gap to fix first.
If your total clears 28, pick one workflow and pilot it this quarter. If it lands between 20 and 27, start narrow while you close the weak dimension. If it is below 20, fix that lowest score before you spend a dollar on a build. That is the whole method, and it puts you on the right side of the line between the 6% who see real impact and the rest who do not.
If you want the fastest path, skip the self-assessment guesswork. We run the readiness check across all five dimensions on your real systems, weight data and workflow redesign the way they deserve, and hand back a clear ready or not-ready verdict with the one gap to fix first, then close the gaps you cannot close alone and run the agent end to end. Book a free consultation below and we will score your readiness and decide your first move together.