AI readiness assessment: who it is for
This assesses the conditions around a possible AI project rather than the technology itself: whether your records are retrievable, whether processes are written down, whether decisions have owners, and whether anyone has time to run something new. Those factors decide whether adoption holds.
( The Detail )
What this tool tells you
A weak result means the groundwork comes first, not that AI is unsuitable for you. It deliberately does not tell you which tool to buy, what it will cost, or how long a build takes. It is a read on your starting position, and it cannot see parts of the operation you did not describe honestly.
Using it well
This is aimed at owners and operators who already suspect there is a better way to run a recurring part of the business, but do not yet have language for what is actually wrong. It assumes no technical background and no existing AI work.
It is less useful if you have already scoped a specific build and know the data sources, the rules and the owner. At that point the constraint is delivery rather than diagnosis, and a direct conversation will get you further than a structured questionnaire.
How to approach it
Begin with the decision rather than the tool. Name the recurring judgement this affects, the information it depends on, and the person accountable for acting on the result. That framing keeps the first build small enough to inspect and useful enough to matter.
Keep a human review point in the loop until the quality and the failure modes are understood. A system that shows its working - what it drew on, where it is uncertain, and what it deliberately left alone - is one a business can keep running after the initial build.
( Next Step )
Start small enough to review, but on a workflow important enough to show whether a better system is worth building.