AI Strategy

AI Readiness Assessment

Find what must change before an agent belongs in your workflow. Review the data, ownership, controls and operational dependencies together.

Find what must be ready before the use case advances

Workflow suitability
Examine task structure and consequences of error.
Data access
Identify permissions and integration prerequisites.
Human supervision
Name who receives exceptions and can intervene.
Capability gap
Connect missing skills or controls to a next decision.
The scope, team and timing are agreed before an engagement begins.

Decision and fit

Find what must be ready before the use case advances

Compare the engagement with the decision you face

Useful decisionA question worth resolving
Find what must be ready before the use case advances.
NeededAn accountable participant
Business and technology sponsors deciding whether a particular workflow is ready for an agent pilot.
PrerequisiteInspectable source material
The relevant owners can make workflow evidence and agreed inputs available for examination.
Different needA scope mismatch
The request is a formal audit opinion or a readiness certification.
Discuss fit and prerequisites together; a different need may require a separately scoped engagement.

The engagement

Find what must change before an agent belongs in your workflow. Review the data, ownership, controls and operational dependencies together. A focused assessment of a candidate workflow, combining stakeholder interviews, evidence review and a decision workshop.

The decision at stake

A promising use case has moved ahead of the organisation’s ability to supervise and support it.

Suitable situations

  • Business and technology sponsors deciding whether a particular workflow is ready for an agent pilot.

Less suitable situations

  • The request is a formal audit opinion or a readiness certification.

Worked situation

Follow one situation through to a bounded next decision

Illustrative working situation

Illustrative scenario

  1. Starting condition

    The proposed agent depends on data its team cannot access.

  2. Question to examine

    Check the access dependency with the operational owner.

  3. Possible next action

    Sequence the prerequisite before the bounded next step.

Constructed example of the reasoning; no result or client engagement is claimed.

Engagement boundary

Agree the work and its boundaries together

The engagement boundary

In scopeWorkflow suitability
Review workflow suitability, data access and operational dependencies.
DependencyData access
The inputs, authorised access and client participants are confirmed before scheduling.
Client responsibilityReadiness sponsor
Retains organisational decisions and risk acceptance.
BoundaryAdditional implementation
The assessment does not implement a pilot or approve its investment. A blueprint, engineering project or targeted prerequisite work can follow only after the sponsor selects a next step.
Only the agreed workflow, environments and activities form the engagement.

What the work covers

  • Review workflow suitability, data access and operational dependencies.
  • Identify accountable owners, oversight requirements and capability gaps.
  • Sequence prerequisites for a bounded next step.

Scope boundaries

  • Formal certification, legal conclusions and guarantees of safe or compliant behaviour.
  • Implementation or ongoing operation beyond the agreed scope.
  • The assessment does not implement a pilot or approve its investment. A blueprint, engineering project or targeted prerequisite work can follow only after the sponsor selects a next step.

Working sequence

How the work moves from question to handover

What each stage should leave your team with

  1. Walk the existing workflow

    The current task, exceptions and human handoffs.

  2. Inspect the prerequisites

    Evidence for data, integration, ownership and controls.

  3. Separate blockers from improvements

    Blockers separated from later improvements.

  4. Agree a next-step decision

    An explicit proceed, narrow or defer decision.

The sequence is tailored to the agreed workflow, evidence and acceptance criteria.

How the work proceeds

  1. Walk the existing workflow. Describe the task, users, exceptions and current handoffs before considering an agent design.
  2. Inspect the prerequisites. Review available data, integration access, decision ownership, oversight and evaluation capability against actual artefacts.
  3. Separate blockers from improvements. Distinguish conditions that prevent a safe pilot from changes that could be sequenced after a bounded start.
  4. Agree a next-step decision. Facilitate a sponsor workshop and hand over the gap assessment, ownership map and ordered prerequisites.

Decision artefacts

Leave a record the next owner can use

Readiness gap

Illustrative working format

Subject and version
Identify the workflow, configuration or proposal examined.
Workflow suitability
Record the relevant requirement and supporting material.
Human supervision
State the observation, supporting evidence and remaining uncertainty.
Readiness sponsor
Record the next decision, follow-up and unresolved question.
Illustrative structure; final deliverables are agreed for each engagement.

What the work can produce

  • Readiness gap assessment
  • Workflow and ownership map
  • Sequenced prerequisites

Working together

Your team and our team need a clear working agreement

Who contributes and who decides

Client sponsor
Confirms the decision, priorities and people needed to resolve it.
Client technical or process owner
Provides the agreed evidence, access and review of findings or deliverables.
Softlander delivery lead
Coordinates the agreed activities, review points, handover and open actions.
Authorised decision-maker
Accepts deliverables against the agreed criteria and separately decides operational or business action.
Client owners retain business, release and risk-acceptance decisions.

What the work depends on

  • A sponsor and process owner bring current workflow steps, exception examples, system/data access constraints and the people who would approve or operate the pilot. Security and data owners resolve access questions before recommendations are finalised.

Engagement availability

The start date, named delivery roles, review points and fee basis are agreed after confirming the inputs and scope. Duration depends on evidence access, system complexity and the time your decision-makers need to review the work.

Engagement and handover

Agree the delivery model and what completion means

A clear agreement from scope to ownership

Scoped work
Review workflow suitability, data access and operational dependencies.
Indicative handover
Readiness gap assessment; Workflow and ownership map
Review and acceptance
Review the agreed deliverables and record any open items, owners and conditions.
Ongoing work
Assign maintenance and operational ownership; agree additional scope and coverage explicitly.
The statement of work confirms milestones, review responsibilities, fees and change control before the engagement starts.

A focused assessment of a candidate workflow, combining stakeholder interviews, evidence review and a decision workshop.

The team receives a readiness assessment that separates demonstrated prerequisites from missing evidence, identifies blockers and assigns owners to the next actions. The sponsor can choose to proceed, narrow the candidate or defer it with explicit reasons.

The assessment does not implement a pilot or approve its investment. A blueprint, engineering project or targeted prerequisite work can follow only after the sponsor selects a next step.

Relevant reading

A little more clarity

Questions worth asking.

Start with the questions that shape a better decision.

When is AI Readiness Assessment useful?

A promising use case has moved ahead of the organisation’s ability to supervise and support it. Business and technology sponsors deciding whether a particular workflow is ready for an agent pilot.

How would we engage your team?

A focused assessment of a candidate workflow, combining stakeholder interviews, evidence review and a decision workshop. The statement of work confirms the deliverables, review points, fee basis and responsibilities before work begins.

What does our team need to contribute?

A sponsor and process owner bring current workflow steps, exception examples, system/data access constraints and the people who would approve or operate the pilot. Security and data owners resolve access questions before recommendations are finalised.

How do we accept the work and take ownership?

The team receives a readiness assessment that separates demonstrated prerequisites from missing evidence, identifies blockers and assigns owners to the next actions. The sponsor can choose to proceed, narrow the candidate or defer it with explicit reasons.

What happens after the engagement?

The assessment does not implement a pilot or approve its investment. A blueprint, engineering project or targeted prerequisite work can follow only after the sponsor selects a next step.

How are timing and fees agreed?

We scope the work around the evidence and access available, technical complexity and the people needed for review. The proposal confirms milestones and whether fees are based on a defined scope, agreed delivery capacity or a recurring remit. Extra workflows, tests or integrations are agreed as changes rather than assumed to be included.

Discuss ai readiness assessment

Tell us about the decision you are facing and we will confirm whether this service is the right starting point.