Decide what is readybefore committing resources.

AI readiness puts the business goal, data permissions, technical environment and owners into one decision matrix. The output is a reviewable pilot recommendation, not an unsupported score.

Discuss your scope

Four dimensions, one decision

This is a review tool, not automated approval. Record evidence, gaps and owners; missing inputs remain open rather than being treated as ready.

Dimension	Evidence to bring	Condition to proceed
Business outcome	Current workflow, users, representative tasks and a manual baseline	A testable question and an outcome reviewer
Data and permissions	Redacted samples, data owner, access and update rules	Approved use and explicit access boundaries
Systems and resources	Accounts, interfaces, network constraints and expected load	A usable test environment and listed dependencies
Ownership and acceptance	Business, technical, budget and approval owners	Clear review, approval and stop criteria

Decide the next step

Proceed to pilot

Evidence and owners are ready. Test the agreed task on a bounded dataset before a wider rollout.

Proceed after preparation

The goal is clear, but access or interfaces are missing. Complete the preparation list and review again.

Narrow or defer

Value cannot yet be tested or a critical dependency is unavailable. Record why and revisit when conditions change.

Bound the task
Choose one representative task and record the current method and change to test.
Review evidence
Review the matrix, assign gap owners and state estimation assumptions.
Record a decision
Submit pilot scope, acceptance method and open items for the customer to decide.

Bring to the first discussion

A real task brief, shareable redacted samples, a system inventory and owner roles. Production credentials are not needed for an initial discussion.

Reviewable deliverables

Readiness matrix, gap and dependency log, scenario priorities, pilot scope and acceptance recommendations. Any effort estimate includes its assumptions.

Scope boundary

Assessment uses agreed materials and interviews. It is not a production security audit or release approval. Design, implementation and operations are scoped separately.

Agree inputs and acceptance criteria before scheduling resources and effort.