AI Readiness Assessment
A scored readiness position, a ranked shortlist of use cases marked viable or blocked with the reason, and a written baseline so any later benefit claim can be checked.
| How it is bought | Paid assessment, and the usual first engagement |
| Duration | 2 weeks |
| Written for | Organisations under pressure to 'do something with AI' that do not yet know which use case is viable |
Most AI programmes fail on data, ownership and evaluation rather than on models, and those problems are cheap to find now and expensive to find in month nine.
What you receive
Named artifacts, not activities. If one of these is not delivered, the engagement is not complete.
- A scored readiness position across data, ownership, evaluation, operations and regulatory exposure
- A ranked shortlist of candidate use cases, each marked viable, blocked or not worth doing, with the reason
- The blockers, each with a named owner and an estimate of effort to clear
- A written baseline for the top use case, so any later benefit claim can be checked
- A one-page position an executive can act on without reading the rest
How it runs
- Week 1: interviews with the process owners, the data owners and whoever holds the budget. Review of the systems the use case would touch.
- Week 2: scoring, shortlist, and the readout. The readout is a working session rather than a presentation.
What this deliberately does not include
Published with the same prominence as the deliverables. A scope with no stated exclusions is a scope that will be argued about later, and the argument always happens at the worst possible moment.
- Building anything. This produces a decision, not a system.
- A vendor or model recommendation. That belongs after a use case is chosen.
- A benefit forecast. Nothing has been measured yet, so any number would be invented.
How you know it is finished
You can name the use case you are starting with, why the others were rejected, and what has to be true before it ships.
What you need ready
A list of candidate use cases if you have one, access to the people who own the affected processes, and half a day of the budget holder's time.
Every engagement starts with a written scope confirmation before any invoice is raised. Nothing here is a click-to-buy: we confirm what you need, agree the scope in writing, then invoice. If the scoping conversation shows that a smaller engagement, or none at all, is the right answer, we say so before anything is signed.
We use privacy-friendly analytics by default. Optional analytics cookies load only if you accept.