An AI readiness assessment should not be just a maturity survey

Many AI readiness assessments feel official but do not help a team decide what to do on Monday.

They ask about strategy, data, tools, culture, and governance. The output is a maturity score. The company learns it is “medium readiness” and still does not know which workflow should go first.

That is not enough.

Readiness is scenario-specific

A company is rarely ready or not ready for AI as a whole. One workflow may have clear samples, a strong owner, and low risk. Another may involve sensitive data, unclear rules, and no review path.

The practical unit of readiness is a scenario, not the company.

Value and readiness must be judged together

High-value scenarios are not always good first scenarios. A cross-system automation may have huge theoretical value but be too risky or too messy for the first implementation loop.

Lower-drama scenarios can be better first moves when they are reviewable, measurable, and close to current work.

A useful assessment should place every candidate scenario on the same decision surface:

• Business value: what improves if this works?
• Evidence: what user input, public signal, or internal sample supports the judgment?
• Execution readiness: do data, SOP, owner, and review rules exist?
• Risk boundary: what cannot be automated yet?

The output should be a decision memo

A readiness assessment should not end with a score. It should end with a decision memo:

• Start here.
• Do not start there.
• This is the missing condition.
• Here is the next 7-day internal task.

That format is easier for a founder, CEO, or digital leader to forward and discuss.

Why HEKI starts with a free scenario map

HEKI's first report is deliberately not a long questionnaire. It uses company identity, public context, and one sanitized paragraph to generate a first-cut scenario map.

The goal is not certainty. The goal is a useful first hypothesis: which AI scenario deserves attention first, which direction should wait, and what condition needs to be checked next.

Depth comes later, after the company has a sharper question.