AI Readiness Diagnostic
Awaiting input
Statement of ambition
Reframe hypotheses
Perceived value
Enablement depth
Gap signal
Transformational
Not on radar
Ready to
redesign
Vision ahead of infrastructure
Scaling
what works
Ambition and delivery aligned
Experimenting
without a blueprint
Tools in use, structure missing
Capability
without strategy
Ahead of their own thinking
Waiting for signal
Enter what the client says to begin
Absent
Structural
Live mode
Client
Suggested probes
What's driving the AI conversation internally — board, team, or clients?
Value
Where has AI actually shown up in how people work day-to-day, even informally?
Depth
If this goes well in two years, what's different about the company?
Value
Add client context. Live feed from AI transcribers coming soon. Cmd+Enter to analyse.
Transformational
Not on radar
Ready to redesign
Vision ahead of infrastructure
Tap to explore ↓
Scaling what works
Ambition and delivery aligned
Tap to explore ↓
Experimenting without a blueprint
Tools in use, structure missing
Tap to explore ↓
Capability without strategy
Ahead of their own thinking
Tap to explore ↓
Absent
Structural
Ready to redesign
Leadership sees AI as transformative but the org hasn't been rebuilt around it. The vision is real — the infrastructure isn't. This client is a good candidate for a transformational program.
Value axis — where they are ↑
Transformational
"AI redefines what we are."
  • Board-level commitment with real governance
  • Resources allocated, identity-level change underway
Strategic advantage
"AI opens opportunities we couldn't see before."
  • Leadership actively sponsoring initiatives
  • Starting to restructure around AI-native thinking
Depth axis — where they are →
Absent
"Nothing real has happened yet."
  • No AI infrastructure or usage in place
  • Data not ready; organisation not yet AI-literate
Tactical
"Individuals use AI tools on their own."
  • No org-wide approach or mandate
  • Informal use of ChatGPT, Copilot, etc.
  • Pockets of experimentation, nothing coordinated
Process-level
"Some of our workflows now include AI."
  • One or more workflows meaningfully changed
  • Pilots completed or actively running
  • Some end-users beginning to work alongside AI tools
Key insight
The gap between ambition and infrastructure is the engagement. Start by mapping what exists, then build the path from where they are to where they want to go — structure, stack, and people together.
Scaling what works
Strategic clarity and operational depth are aligned. They've redesigned the factory, not just swapped the motor. The work here is acceleration, governance, and compounding the advantage they've already built.
Value axis — where they are ↑
Transformational
"AI redefines what we are."
  • Board-level commitment with real governance
  • AI reshaping competitive positioning and identity
  • Resources allocated, not just enthusiasm expressed
Strategic advantage
"AI opens opportunities we couldn't see before."
  • AI as a source of new revenue or market opportunity
  • Leadership actively sponsoring AI initiatives
  • Decision-making augmented by AI-generated insight
Depth axis — where they are →
Structural
"Big parts of the organisation have been redesigned around AI."
  • Customer-facing services rebuilt around AI-native workflows
  • Roles and team structures significantly changed
  • Technical stack: data, APIs, agent frameworks operational
  • Formal adoption programmes running; AI champions active
  • End-users trained and working alongside AI as standard practice
Operational
"AI is running at scale and we're managing it."
  • AI in production across multiple functions
  • Monitoring, drift detection, cost-per-task tracking
  • Incident response and SLAs defined for AI systems
  • End-users have feedback channels into AI performance
  • Continuous improvement loops in place
Key insight
This client has done the hard work. The engagement is about what comes next — scaling, governance, staying ahead of the curve, and making the advantage compound rather than plateau.
Experimenting without a blueprint
AI tools are in use — sporadically — but there's no institutional structure around them. The opportunity: build the coordination layer that turns individual gains into institutional ones; set strategies and directions to ensure usage is tied to a greater purpose.
Value axis — where they are ↑
Not on radar
"We haven't really thought about it."
  • AI absent from strategy conversations
  • Few clients here will be calling us — but some will
Surface adoption
"We use AI tools where it's convenient."
  • AI as a productivity feature, not a strategic lever
  • Vendor-led rather than internally mandated
  • No change to how the org thinks or operates
Operational improvement
"AI makes what we do work better."
  • Focused on efficiency, cost reduction, time savings
  • Existing workflows improved, not reinvented
  • No challenge to the underlying business model
Depth axis — where they are →
Absent
"Nothing real has happened yet."
  • No AI infrastructure or usage in place
  • Organisation not yet AI-literate
Tactical
"Individuals use AI tools on their own."
  • No org-wide approach or mandate
  • Informal use of ChatGPT, Copilot, etc.
  • No shared standards or prompt practices
Process-level
"Some of our workflows now include AI."
  • One or more workflows meaningfully changed
  • Pilots completed or running
  • Some end-users beginning to work alongside AI tools
Key insight
The tools are there, the intent isn't fully formed yet. The engagement starts with helping leadership articulate what they're trying to achieve — then building the structure that makes individual experimentation add up to something.
Capability without strategy
Operational capability exists — often bottom-up or engineering-led — but leadership hasn't formed a strategic view. The work is sense-making and strategic coordination before building more.
Value axis — where they are ↑
Not on radar
"We haven't really thought about it."
  • Leadership unaware of what's been built beneath them
  • AI absent from strategy conversations despite operational reality
Surface adoption
"We use AI tools where it's convenient."
  • Leadership sees AI as a tool, not a strategic lever
  • Unaware of the depth of capability that already exists
Operational improvement
"AI makes what we do work better."
  • Sees the capability in efficiency terms only
  • Has not connected it to competitive or strategic opportunity
Depth axis — where they are →
Structural
"Big parts of the organisation have been redesigned around AI."
  • Technical stack exists and is functioning
  • Engineers shipping AI into products and workflows
  • End-users interacting with AI without always knowing it
Operational
"AI is running at scale and we're managing it."
  • AI in production across multiple functions
  • Monitoring and improvement loops in place
  • End-users engaged with AI outputs, often without strategic framing
Key insight
The capability is real — the strategic frame isn't. Start by surfacing what already exists and what it's worth. Then build the leadership conversation that gives purpose to the work:

  • Surface the strategic value of existing capability
  • Connect engineering work to the leadership agenda
  • Create a strategic POV that gives purpose to the work — this may mean reworking what's there
Y axis — Perceived value of AI
  • Board-level commitment with real governance
  • AI reshaping competitive positioning and identity
  • Resources allocated, not just enthusiasm expressed
  • Build vs. buy vs. partner decisions actively made
  • AI as a source of new revenue or market opportunity
  • Leadership actively sponsoring AI initiatives
  • Starting to restructure around AI-native thinking
  • Decision-making augmented by AI-generated insight
  • Focused on efficiency, cost reduction, time savings
  • ROI framing is common — payback period talk
  • Existing workflows improved, not reinvented
  • No challenge to the underlying business model
  • AI as a productivity feature, not a strategic lever
  • Tool-driven rather than outcome-driven
  • Vendor-led rather than internally mandated
  • No change to how the org thinks or operates
  • AI absent from strategy and planning conversations
  • No internal mandate or awareness
  • Risk of disruption without knowing it
X axis — Depth of enablement
  • Customer-facing services rebuilt around AI-native workflows
  • Roles and team structures significantly redesigned
  • Technical stack: data, APIs, agent frameworks operational
  • Formal adoption programmes running; AI champions active
  • End-users trained and working alongside AI as standard practice
  • Change management actively addressing resistance
  • AI in production across multiple functions
  • Monitoring, drift detection, cost-per-task tracking
  • Incident response and SLAs defined for AI systems
  • End-users have feedback channels into AI performance
  • Continuous improvement loops incorporate user input
  • One or more workflows meaningfully changed
  • Pilots completed or actively running
  • Human-in-the-loop thresholds being defined
  • Some end-users beginning to work alongside AI tools
  • Early adoption programmes or informal training underway
  • Results tracked, not yet systematically
  • No org-wide approach or mandate
  • Informal use of ChatGPT, Copilot, etc.
  • No shared standards or prompt practices
  • Pockets of experimentation, nothing coordinated
  • No AI infrastructure or usage in place
  • Data not ready; no integration architecture
  • Organisation not yet AI-literate