Diagnostics / AI readiness score

How ready is your company for AI?

10 questions for a COO or CTO about data, process, systems and ownership. You'll get a score out of 100, the two areas to fix first and a suggested first step.

01 / 10Can your team get to the data this work depends on, and can you trust it?
02 / 10Does one named person own the process you'd automate?
03 / 10Can software reach the systems involved?
04 / 10How clear are your security and compliance rules for AI tools?
05 / 10Is there a budget owner for this work?
06 / 10How are errors in this work caught today?
07 / 10Could your team spend time reviewing AI output while it's being tested?
08 / 10How much of this work is automated already?
09 / 10Do you know what one case costs today, in time or money?
10 / 10Is a senior leader sponsoring the work?

How the score works

Four areas, weighted equally.

  • → each answer scores 0 to 3 points; a higher score means more of the groundwork is in place
  • → area score = points ÷ maximum points × 100: Data (questions 1 and 9), Process (2, 6 and 8), Systems & security (3 and 4), People & ownership (5, 7 and 10)
  • → overall score = the average of the four area scores, so each area counts the same
  • → below 40 is low and 40 to 69 is medium: both suggest a Scoping Sprint; 70 or more is high and suggests a Pilot Build, unless any area is below 50
  • → the two lowest areas each get one recommendation, based on the weakest answer in that area; nothing is compared with other companies

FAQ

Questions about AI readiness

What does the AI readiness score measure?

How much of the groundwork for a first AI project is in place: data you can reach and trust, a process with an owner, systems software can connect to, and people with the time and authority to see it through. It doesn't say whether a particular use case is worth building.

Is my score compared with other companies?

No. The score comes only from your 10 answers, using the rules described on this page. Your answers stay in your browser, so there is nothing to compare against.

What should we do with a low score?

Start with the two weakest areas. Most of the fixes are decisions and documentation, such as naming an owner or writing down the data rules, not software. A Scoping Sprint can map the gaps with you and pick the workflow to start with once they're closed.

What is the difference between a Scoping Sprint and a Pilot Build?

A Scoping Sprint reviews the workflow, systems and data, ranks the possible use cases and ends with a written build plan and running-cost model. A Pilot Build connects one chosen workflow to real systems and measures it against an evaluation set and success criteria agreed up front.

Book an AI scoping call

Bring one workflow. We'll tell you if an agent should run it.

Book an AI scoping call →

or write to contact@byteandrise.com · we work under NDA