What does an AI readiness assessment actually tell you?
Which three things to do first, which two to refuse, and what has to be fixed before either works. Three weeks, a written report, a 90-day plan, and a data and tooling audit. You keep all of it whether or not we do the next part.
- What AI users say about their own work
- What they say about their organization
- AI lets me spend more time on high-value work
- I fear falling behind if I do not use AI
- I am producing work I could not a year ago
- It feels safer to focus on current goals than redesign work
- Leadership is clearly and consistently aligned on AI
- I am rewarded for reinventing work with AI, even when results miss
Organizational factors explained more than twice the reported AI impact of individual ones (67% versus 32%). The bottleneck is rarely the tool.
Source: Microsoft, 2026 Work Trend Index: Agents, human agency, and the opportunity for every organization (2026). 20,000 full-time workers in 10 countries, 18 February to 7 April 2026, fielded by Edelman Data x Intelligence.
Data table
| Item | Group | Value |
|---|---|---|
| AI lets me spend more time on high-value work | What AI users say about their own work | 66% |
| I fear falling behind if I do not use AI | What AI users say about their own work | 65% |
| I am producing work I could not a year ago | What AI users say about their own work | 58% |
| It feels safer to focus on current goals than redesign work | What they say about their organization | 45% |
| Leadership is clearly and consistently aligned on AI | What they say about their organization | 26% |
| I am rewarded for reinventing work with AI, even when results miss | What they say about their organization | 13% |
- Listenweek oneInterviews with the people who do the work, about four hours in total. Read access to the systems in scope.
- Lookweek twoRead the data and the tooling as they are. Draft the usage and data-handling policy. Most "fix that first" findings come from here.
- Writeweek threeFindings, the ranked list, the refusal list, the 90-day plan with owners. A readout where every line gets defended.
You keep everything produced, whether or not there is a next part.
AI Readiness Assessment
Why start here
Every company that has asked us for help with AI has had the same first problem: nobody knows which of the eleven ideas on the whiteboard is worth doing, and the loudest one is usually not. An assessment replaces the argument with a ranked list, each item carrying the hours it saves, the data it needs, and the risk it brings. The refusal list is the part people keep.
It is three weeks because that is how long it takes to talk to the people who do the work, read the systems, and write something a board can act on. A one-week version produces a slide deck. A three-month version is consulting for its own sake.
What the three weeks look like
Week one, listen. Interviews across departments with the people who do the work, about four hours in total. What takes the time, what gets redone, where the spreadsheets live that nobody admits to. Read access to the systems in scope.
Week two, look. We read the data and the tooling as they are. Data condition decides most AI outcomes before a model is chosen, and this is where the “fix that first” findings come from. We also draft the usage and data-handling policy, because the first deployment needs something to be governed by on day one.
Week three, write. Findings, the ranked list, the refusal list, the 90-day plan with owners. Then a readout with your leadership team where we defend every line. You get the raw material behind the findings too, not only the conclusions.
What you walk away with
A written report, a ranked opportunity list, a refusal list, a 90-day plan, a data and tooling audit, and a draft policy. All of it is yours. If the next step is with us, it starts from this document. If it is with your own team, it still starts from this document.
Who it is for
Mid-market companies with a leadership team asking what to do about AI and no one who owns the answer. MSPs deciding what to offer clients and what to run internally. Engineering organizations where AI coding tools have spread with no governance and someone has noticed. If that is not you, the services overview is a better place to start.
What you get
- Written findings: where AI fits in this organization and where it does not, in plain language a board can read
- A ranked opportunity list, each item with the hours it saves, the data it needs, and the risk it carries
- The refusal list: the two or three things everyone is excited about that should not be done, with reasons
- A 90-day plan with named owners, in the order the work has to happen
- A data and tooling audit: what you have, what condition it is in, and what has to be fixed first
- A one-page usage and data-handling policy draft, so the first deployment has something to be governed by
- A readout with your leadership team, and the raw material behind every finding
Questions we get
- Do we need this before an implementation sprint?
- Yes, unless you have done something equivalent in the last six months. Every sprint we have seen go wrong started without one. It is also how we decide whether to take the engagement.
- What do you need from us?
- Access to the people who do the work, not only the people who manage it. About four hours of interviews across departments, read access to the systems we are assessing, and one person on your side who can get us answers. No slide decks.
- Is this a sales process for the next engagement?
- It qualifies both of us. Roughly a third of assessments end with a recommendation to do nothing for now, or to fix data first with your own team. That recommendation is in writing and it is the same fee.
- Who actually does the work?
- The people who will do the next part if there is one. Nobody hands off. The team has run engineering, QA, operations, and IT inside real organizations, which is why the findings are about what your teams can actually execute.
- What if you find nothing worth doing?
- Then the report says so, with the reasons, and you have saved the cost of finding out the expensive way. It happens. It is also useful to have in writing when the board asks again next quarter.
How it starts
Three weeks, fixed scope. You keep everything produced, whether or not there is a next part.