AI Readiness Scorecard

Where is your company ready for AI, and where isn't it?

Twenty statements across data, process, people and governance. Score each one 0, 1 or 2, add up each section, and see where to focus first.

Score each statement: 0 · Not true · 1 · Partly true · 2 · True

Data

  1. The data behind your most important decisions lives in systems you can query, not in spreadsheets on someone's laptop.
  2. You know which system is the source of truth for customers, orders and products.
  3. Someone owns data quality, and errors get fixed at the source.
  4. You could export a year of the data a pilot would need within a week.
  5. Documents that drive work (contracts, orders, tickets) are stored where software can reach them.

Data total: / 10

Process

  1. Your most repetitive workflows are written down, step by step.
  2. You can say what each of those workflows costs today, in hours or errors.
  3. Exceptions and edge cases have a known owner and a known path.
  4. Changes to a workflow go through a review before they ship.
  5. You measure the outcome of a process, not just whether it ran.

Process total: / 10

People

  1. A named leader owns AI adoption, with time set aside for it.
  2. The people who do the work are involved in choosing what to automate.
  3. Staff use AI tools at work today, with guidance on how.
  4. Someone in-house can evaluate an AI vendor's claims.
  5. Teams have time in their week to learn a new way of working.

People total: / 10

Governance

  1. There is a written policy on what data can go into AI tools.
  2. You know which AI tools are in use across the company.
  3. AI output that reaches a customer is reviewed by a person, or checked automatically.
  4. Security and legal know how to assess a new AI tool, and how long that takes.
  5. Each AI project has a success measure agreed before it starts.

Governance total: / 10

Reading your scores

  • 8 to 10 in a section: a strength. Lean on it when you pick your first use case.
  • 4 to 7: workable. A pilot can start, but plan to close the gaps as part of it.
  • 0 to 3: the likely reason a pilot would stall. Fix this first, or pick a use case that doesn't depend on it.

Your lowest section is usually the one to work on first. A high total with one very low section still means a pilot is likely to stall there.

Let's find where AI pays off in your business.

Thirty minutes with Daniel. No pitch deck: you talk about your business, I tell you honestly where AI fits and where it doesn't.

Book a 30-minute AI conversationTake the AI Adoption Check