Who this is for
Business owners and IT leaders evaluating whether their organisation is ready to invest in AI — and what to fix first if not.
Question this answers
Are we actually ready for AI, or will we waste money on a project that fails because the foundations aren't there?
What you'll leave with
- The five dimensions of AI readiness and how to assess each one
- A self-assessment checklist you can score in 30 minutes
- What to prioritise fixing if you're not ready yet
- Common mistakes organisations make when evaluating AI readiness
What is AI readiness?
AI readiness is the honest answer to a simple question: if we started an AI project tomorrow, would it succeed?
Too many organisations jump into AI because a competitor mentioned it, or because a vendor promised transformation, or because a board member read an article. They spend $50K on a proof of concept that fails — not because the AI didn't work, but because their data was a mess, their processes were undefined, or nobody actually owned the project.
A readiness assessment prevents that. It takes 30 minutes of honest evaluation and tells you where you stand across five dimensions.
The five dimensions of readiness
AI readiness isn't one thing. It's a combination of data, process, technology, team, and business case readiness. You need all five to be at least "acceptable" for an AI project to succeed. Weakness in any one dimension can derail the whole thing.
1. Data readiness
AI needs data to work with — whether that's business documents for RAG, transactional records for automation, or historical data for forecasting. The question isn't "do we have data?" (everyone does), it's "is our data usable?"
Data readiness checklist
- The data we want AI to use is digitised (not just in paper files or people's heads)
- Key data fields are populated for at least 80% of records
- Data formats are reasonably consistent within each system
- We know where the data lives and who owns it
- Duplicate records are not a major, unmanaged problem
- Data has been updated within the last 12–24 months
- We have at least some data governance or quality checks in place
2. Process readiness
AI automates processes. If the process isn't well-defined, AI can't automate it. Many businesses discover during an AI project that the real problem wasn't technology — it was that nobody had documented how the workflow actually works.
Process readiness checklist
- The process we want to automate is clearly defined (documented or at least well-understood)
- We can describe the inputs, steps, and outputs of the process
- The process is currently performed consistently (not different every time)
- We know how long the process takes and what it costs in staff time
- The process has a clear owner who can make decisions about changing it
- There's a measurable outcome (time saved, errors reduced, throughput increased)
3. Technology readiness
You don't need cutting-edge infrastructure. But you do need systems that AI can connect to. The most common blocker isn't missing technology — it's legacy systems with no APIs.
Technology readiness checklist
- Our core systems (CRM, ERP, document management) have APIs or can export data
- We have (or can provision) cloud infrastructure (AWS, Azure, or GCP)
- Our IT environment is reasonably modern (not running on unsupported operating systems)
- We have someone who can manage or coordinate IT changes
- We're comfortable with cloud-hosted solutions for non-sensitive data
- We can provision user accounts, API keys, and access controls without a 6-month process
4. Team readiness
AI projects need a sponsor (someone with authority and budget), a subject matter expert (someone who knows the process), and someone to coordinate. You don't need data scientists or ML engineers — your AI partner provides those.
Team readiness checklist
- We have executive sponsorship for this project (someone who will protect the budget and priority)
- A subject matter expert can dedicate 4–8 hours per week during the project
- Someone is nominated to coordinate between the AI partner and internal teams
- The team affected by the change is aware and broadly supportive (or at least not hostile)
- We have a realistic timeline in mind (not "live in two weeks")
- The organisation has successfully adopted new technology before
5. Business case readiness
A clear business case isn't just "AI would be cool." It's a quantified statement: this process costs us X hours per week, AI could reduce that by Y%, the investment is Z, and the payback period is N months.
Business case readiness checklist
- We can articulate the specific problem AI will solve (not just "improve efficiency")
- We can quantify the current cost of the problem (hours, dollars, error rates)
- We have a realistic budget range in mind ($20K–$80K for most single-workflow projects)
- The expected ROI justifies the investment within 12 months
- We understand this is a project with iteration, not a product we install
Scoring your readiness
Count how many checklist items you ticked across all five dimensions. Here's what your score tells you:
| Score | Readiness level | Recommendation |
|---|---|---|
| 25–30 | Ready | You're in good shape. Proceed to scoping a specific AI project with an implementation partner. |
| 18–24 | Mostly ready | You can start an AI project, but address your specific gaps early. Share your assessment with your AI partner so they can help navigate the weak areas. |
| 12–17 | Prepare first | Some foundational work needed. Focus on data quality, process documentation, or stakeholder alignment before committing budget to AI. |
| Under 12 | Not yet | Significant gaps exist. A readiness workshop can help prioritise what to address. AI is likely 3–6 months away. |
Common mistakes
- Waiting for perfect readiness — no organisation is 100% ready. If you're at 18+, start. You'll learn more from a real project than from further preparation.
- Skipping the business case — enthusiasm isn't a strategy. If you can't articulate the problem and quantify the cost, the project will lose priority when something urgent comes along.
- Underestimating change management — the technology usually works. Getting people to use it is the hard part. Budget time and effort for training, communication, and feedback.
- Choosing the wrong first project — don't start with your most complex, politically sensitive workflow. Pick something with clear data, a willing team, and a measurable outcome.
- Assuming you need data scientists — you don't. You need a good AI implementation partner and internal subject matter experts. The AI engineering is their job, not yours.
Next steps
If you scored 18 or above, you're ready to explore a specific AI use case. Start with our AI ROI Calculator Guide to build the business case, or book a free consultation to discuss your assessment results.
If you scored below 18, focus on the dimension with the lowest score first. Our team can help with data readiness assessments, process mapping, and technology audits — all of which set you up for a successful AI project when the foundations are in place.
Key takeaways
- AI readiness isn't about having perfect data or cutting-edge infrastructure — it's about having "good enough" foundations across five key areas
- Most organisations are ready for at least one AI use case — even if they're not ready for a full transformation program
- The biggest blocker isn't usually technology — it's unclear processes and uncommitted sponsorship
- A 30-minute self-assessment can tell you whether to proceed, prepare, or pause
- You don't need to score perfectly. You need to know which gaps to close first