Most organizations I assess are operating at Level 2 or Level 3 of AI maturity. Most of them tell me they are at Level 4 or Level 5. The gap between those two numbers is not a measurement problem. It is the entire reason their AI rollout is failing, and they cannot see it from inside.
I built the AI Maturity Index for one specific reason: I needed a tool that would not let an organization grade itself.
The self-assessment was the disease. Leaders had been reading vendor pitches, watching conference keynotes, and making polite small talk at industry events about their AI rollouts, and they had absorbed a vocabulary that did not match what was actually happening inside their walls. They genuinely believed they were further along than they were. The vendors they were buying from had every commercial reason to confirm the belief. The consultants they were hiring had every commercial reason to design engagements around it. So they invested into a fiction, watched the fiction underperform, and concluded that AI was overhyped.
AI was not overhyped. They were at Level 1 spending Level 5 money.
I know this because I lived it.
I Tried to Skip Levels. I Failed Every Time.
When I started using AI in my own business in early 2025, I had a clear vision of what I wanted to build: a lean operation with great margins and an AI-native team that could operate at a level no human-only structure could match. I could see the destination. What I could not see was the path.
So I tried to take shortcuts.
I started on ChatGPT, building custom GPTs for copywriting, communications, and meeting summaries. The work was useful. It was also entirely manual. Open the right GPT, ask the question, copy the output, paste it where it needed to go. I assumed this was Level 1, the entry point, and that I would graduate to real AI as soon as I could string a few automations together.
So I tried Make. I could not figure it out. I tried n8n. I could not figure it out either. I almost threw my laptop out the window. Multiple times. I had this image in my head of where I wanted to be, and the gap between where I was and where I wanted to be felt insulting.
The diagnosis I eventually arrived at, after months of frustration, was not what I expected.
The tools were not the problem. My foundation was the problem.
I was trying to automate workflows I had not documented. I was trying to integrate systems I had not configured. I was trying to deploy agents to handle decisions I had not yet articulated to myself, let alone to a machine. I was, in the language of the model I would later build, sitting at Level 1, looking at Level 4 and Level 5 capabilities, and trying to skip everything in between.
I went back to the chat window and stayed there. For months.
I built skills. I refined prompts. I documented processes. I taught the AI my voice, my business context, my non-negotiables, my client list, my offers. I did the unglamorous work of organizing my own thinking so something else could pattern-match against it. By the end of that period, I was operating at maybe 80 percent of where I wanted to be without writing a single line of automation code.
That was the lesson the rest of this article is about.
The AI Maturity Index, Six Levels Plain
The Index runs on a six-level scale, zero through five. Each level is a threshold of capability that has to be earned before the next one is meaningful. You cannot deploy at a higher level than your foundation supports. If you try, the deployment fails. The technology gets blamed. The leader concludes AI is not ready. None of that is true. The leader was simply at a different level than they thought they were.
The six levels are:
Level 0: Unaware. No AI use. The team is unfamiliar, resistant, or actively avoiding it. Some leaders at this level have personally tried ChatGPT for a few minutes and concluded it was a toy. Others have not opened it at all. The organization is starting from zero, which is honest, and being honest about Level 0 is the only way out of it. The first move at this level is not a tool decision. It is a governance and ethics conversation. What data is allowed to touch AI. What is not. What the organization stands for in how it adopts. That conversation belongs at Level 0 and continues at every level after.
Level 1: Prompting. AI is used occasionally, by individuals, for one-off tasks. Someone drafts an email with ChatGPT. Someone summarizes a meeting transcript. There is no consistency, no shared system, no documented practice. Each use is a small private experiment. The organization is aware of AI. It is not yet operating with AI.
Level 2: Context. The AI knows the business. Custom instructions, brand voice, templates, frequently used context have been captured and reused. A team can hand the same prompt to the same tool and get a consistent result. Foundation work has begun. Most of the value at Level 2 is concentrated in one or two people who have invested the time to build their personal context layer. The organization is using AI more deliberately, but the deliberateness lives in individuals, not in systems.
Level 3: Workflows. AI handles repeatable processes, not just prompts. Documented procedures exist for how AI is used in specific tasks. Multiple people can produce comparable output because they are running comparable workflows. SOPs reference AI as part of the standard procedure, not as an exception. The work has shifted from I wonder if AI can help with this to this process uses AI at these specific steps, in this specific way, with this specific oversight. This is the level at which AI starts to look like infrastructure rather than experimentation.
Level 4: Integration. AI is embedded across departments. Tools talk to each other. Outputs from one system feed inputs to another. The organization has multiple workflows running through AI, and those workflows are connected. A meeting transcript becomes structured notes becomes a CRM update becomes a follow-up draft, with humans approving at the right checkpoints. Cross-functional knowledge starts to compound. The AI is no longer a side tool. It is part of the operating fabric.
Level 5: Agency. AI executes, monitors, and optimizes with minimal human trigger required. Agents run on schedule, watch for signals, take action within defined guardrails, escalate when something exceeds their scope, and report on what they did. Humans make the strategic decisions. Agents handle the operational follow-through. This is the level most leaders picture when they imagine AI fully woven into their business, and it is the level almost no organization has actually reached.
That is the Index. Six levels. Each one a threshold of capability earned by doing the work the level requires.
Governance and ethics are not a level. They are a thread that runs through every level.
This is the part most maturity models get wrong. They treat governance as something you address when the organization gets sophisticated enough to need it, usually somewhere around Level 4 when the AI starts touching real operational data. By then, the patterns are baked in. The team has been pasting client information into free accounts for months. The shadow tool sprawl is everywhere. The retrofit costs ten times what the original conversation would have cost.
In the MBAIA coursework I teach, governance is standard training across every level. Level 0 organizations have a governance and ethics conversation before they install a single tool. Level 1 organizations document what data goes into AI and what does not. Level 2 organizations have a written policy that names the approved tools, the disallowed inputs, and who owns updating the document. Level 3 organizations bake governance into every SOP that touches AI. Level 4 organizations have audit logs and review cycles. Level 5 organizations have governance instrumented into the agent layer itself, with guardrails that are technical, not just policy.
The work compounds. An organization that addresses governance at Level 0 has it as a habit by Level 3. An organization that ignores it until Level 4 spends the next year cleaning up what it built without it.
The Self-Assessment Vanity, and Why It Costs So Much
When I send the AI Maturity Index to a prospective client, the assessment scores nine departments for for-profit organizations and twelve for nonprofits. Marketing, sales, client delivery, operations, finance, HR, strategy, team and delegation, ethics and governance. Each department is scored on the same six-level scale. The overall score is a weighted average across the departments, with hard floors that cap the displayed level when foundational gaps are present.
The hard floors matter. If the finance department is below Level 1.5, the overall score is capped at Level 3.0, no matter how high the other departments score, because financial visibility is a non-negotiable foundation for anything more sophisticated. If ethics and governance is below Level 1.5, the same cap applies, because deploying autonomous AI without governance is a security incident waiting to happen, not a maturity milestone. If operations and admin is below Level 0.5, the cap applies again, because zero operational foundation means nothing can be systematized.
These floors exist because I have watched what happens when organizations skip them. Almost every floor cap I trigger in the assessment was earned by an organization that had told me, before taking the assessment, that they were pretty advanced with AI.
What was actually happening: a few people on the team had Level 2 or Level 3 personal practice, and the leader had extrapolated that into an organizational claim. Or the organization had bought enterprise licenses for a sophisticated AI platform and assumed that procurement was adoption. Or a vendor had walked in promising agentic workflows and walked out with a six-figure contract before anyone asked whether the organization had documented its current workflows.
The vanity is not malicious. It is structural. Admitting Level 2 in a board meeting feels like admitting the organization is behind. Claiming Level 4 feels like leadership. The incentives in every direction push the self-assessment up. And the people most equipped to push back, the consultants and vendors with skin in the game, are the ones least likely to do it because pushing back closes deals more slowly than confirming.
So organizations confirm themselves into a fiction, write checks based on the fiction, watch the resulting deployment underperform, and conclude that the technology is the problem.
Subscriptions Are Not Maturity
A few months ago I started working with a property and casualty insurance agency in California. Before I walked in, the owner had purchased ChatGPT Teams and Claude subscriptions for the entire staff. The licenses had been provisioned. The accounts were active. The bill had been paid every month for several months.
If you had asked the owner that morning what level his organization was operating at, he would have given you a confident answer somewhere in the Level 3 range. He had bought the tools. He had given the team access. In his mental model, the rollout was underway.
When I sat down with the team, I learned the truth.
The operations manager said she did not use AI like that and did not even like it when Alexa talked to her for too long. The senior producer had what she called very minimal experience with LLMs. The owner himself had told the staff explicitly not to use AI at work until the company formally rolled it out, which had not happened yet, because nobody was sure what formally rolled it out was supposed to mean. Every workflow in the agency lived in human heads or in manual spreadsheets. Sixty to seventy commercial renewals per month tracked in Excel. An entire commercial book of business stored in one producer's memory. Zero documented standard operating procedures.
This was not a Level 3 organization. This was a Level 0 organization that had purchased Level 5 tools and was paying for them while they sat unused.
The fix was not to roll out more tools. The fix was to do the foundation work the organization had skipped. In a two-hour working session, we configured Claude Teams with the correct security settings, built their first Project, captured a live working SOP for their highest-volume workflow by voice dictation, calibrated a prompt library to the business, and committed to a two-week homework phase. By the end of the session, the operations manager said it out loud: It's clicking. I didn't know how good I would get it, but it's clicking.
Same company. Same tools. Same people. Inert for months. Activated to a real Level 2 in ninety minutes, with a clear path to Level 3 over the following six months.
The agency had not failed at AI adoption. They had skipped the foundation, mistaken the receipt for the result, and assumed the gap was the technology. The technology was fine. The on-ramp was missing.
How to Tell What Level You Are Actually At
The diagnostic question is not what tools have we bought. It is not even what tools are we using. Both of those questions are easy to answer in a way that flatters the leader and tells you almost nothing.
The diagnostic questions are operational. They sound boring. They are the only ones that matter.
For Level 1 versus Level 2: Can you hand the same prompt to the same tool and get a consistent result? Does the AI know your brand voice without you having to re-paste it every time? If a new hire opened your AI tool tomorrow, would they have the context they need to produce work that matches your standard, or would they have to start from scratch?
For Level 2 versus Level 3: Is there a documented standard operating procedure that names the AI as part of a specific step in a specific process? Can two different people produce comparable output by following the procedure? Or is the high-quality output dependent on one person who has built their own personal practice?
For Level 3 versus Level 4: Do your AI workflows talk to each other? Does the output of one process flow into another without manual copy-paste? When a meeting happens, does a transcript get processed, do action items land in the right tracker, do follow-ups get drafted, do CRM records get updated, and does a human approve at the right points? Or is each AI use case a standalone island?
For Level 4 versus Level 5: Do agents run on schedule and watch for signals without being asked? When something exceeds their scope, do they escalate cleanly, with the context a human would need to make the decision? Are they auditable? Are the guardrails real? Or is Level 5 a label you have applied to a sophisticated Level 3 operation because it sounds better?
I have run hundreds of versions of these conversations. The most common honest answer at most organizations falls somewhere between Level 2 and Level 3, with significant departmental variation. Marketing might be at Level 3, finance at Level 1, governance at Level 0. The overall score, weighted appropriately, lands in the high 1s or low 2s. That is normal. That is not failure. That is most organizations in 2026.
The dangerous answer is the confident one without the operational evidence underneath it.
Departmental Variance, and the Patterns That Show Up
One thing the Index surfaces that no self-assessment ever does: maturity is not uniform across departments. An organization can be operating at Level 3 in marketing because the CMO is personally good with AI, and at Level 0 in operations because no one has touched the back office. The overall number is meaningful, but the shape of the scoring tells you something the number alone cannot.
A few patterns I see often enough that they have their own diagnostic notes:
High sales, low client delivery. The organization is closing more business than it can deliver. AI in marketing is generating pipeline that the rest of the operation cannot honor. This is not an AI problem. It is a capacity ceiling, and the AI in marketing is making it worse. The fix is to address delivery before scaling acquisition further.
Strong execution, weak strategy. The organization is operationally capable at AI but has no clear strategic frame for why it is doing what it is doing. It is building fast in the wrong direction. The AI is making bad strategy execute faster, which compounds into a more expensive correction later.
High everywhere except team and delegation. AI systems exist, but only one or two people can actually operate them. This is not real Level 3. This is Level 1 with a faster operator. The moment that operator is on vacation or leaves the organization, the system reverts to Level 0.
High AI ambition, weak finance. The leader wants Level 4 or Level 5 capabilities and cannot produce a clean monthly P&L. Financial visibility is a non-negotiable foundation. You cannot make sound investment decisions about AI infrastructure when you cannot see the financial state of the organization clearly. The foundation here is not about AI at all.
Any automation ambition, zero ethics. The organization wants autonomous systems and has no governance, no policy, no documented data handling rules. This is the most expensive mistake on the list. It does not show up as a maturity gap. It shows up later as a security incident, a compliance failure, or a public trust collapse. The cap exists because deploying agency without governance is reckless, not advanced.
These combinations matter because they shape what the right next move actually is. An organization with a Level 2 overall score and weak finance has a fundamentally different first step than an organization with a Level 2 overall score and weak governance. Both look the same on a one-number readout. They are not the same.
What This Means for How You Move
If you are reading this and thinking, we might be at a different level than I have been telling people, the move is not panic. The move is honesty.
There is no shame in being at Level 2. Most organizations are. Level 2 is a real, working maturity stage. There are leaders at Level 2 producing remarkable results because they are doing the work the level requires, and there are leaders at Level 4 producing nothing because they skipped the foundation underneath.
The work at each level is different.
If you are at Level 1, your work is to stop chasing automations and instead build the context layer. Document the brand voice. Capture the templates. Set up the projects, the custom instructions, the canonical references. Get the AI to actually know your business. The investment of attention here returns more capacity than any other single move I see leaders make.
If you are at Level 2, your work is to convert your strongest individual practitioners into shared workflows. Find the person on your team who is producing the best AI-assisted output and get them to articulate the procedure they are running. Turn it into an SOP that names the AI explicitly. Train another person to follow the same procedure and produce comparable output. The unit of measurement at Level 2 to Level 3 is not adoption rate. It is transferability.
If you are at Level 3, your work is to start connecting your workflows. Where does the output of one process become the input to another? Which manual handoffs are eating your time and could be cleanly automated, with humans approving at the right checkpoints? Integration is not a tooling decision. It is an operational design decision, made by humans who understand the flow of work.
If you are at Level 4, your work is to identify the agentic moves that are genuinely safe to make, build the guardrails, and ship one carefully. Agency is not the next inevitable step. It is a category change. The organizations that handle this stage well are the ones that resist the temptation to move everything to Level 5 at once and instead pick the right one or two flows to elevate first.
Wherever you are, the move is to stop pretending you are somewhere else.
The Real Cost of the Vanity
The cost of misreading your own maturity level is not abstract. It shows up in the budget. It shows up in the timeline. It shows up in the team's morale. And it shows up, eighteen to twenty-four months later, in the conclusion that AI was overhyped.
Organizations that buy Level 5 tooling at Level 1 maturity will conclude that the tooling failed. The tooling did not fail. The foundation was not there to support it. The conclusion they should have reached, if they had been able to see it clearly, is that the sequencing was wrong. They needed to be at Level 2 before Level 3 was meaningful. They needed Level 3 before Level 4 made sense. They needed all of Level 4 before Level 5 stopped being a brochure and became an actual capability.
You cannot skip the levels. I tried. The people I work with have tried. Everyone I have ever met who is now operating at Level 4 or Level 5 walked through Levels 1, 2, and 3 first, in order, doing the work each level required. The ones who did the work faster were the ones who stopped pretending they were further along than they were and committed to the foundation. The ones who took the longest were the ones who kept claiming Level 4 in board meetings while operating at Level 1 in practice.
The fastest path through is honesty. The slowest path is the vanity.
The Index exists because honesty is hard to come by when the incentives are pointing the other direction. A diagnostic that does not let you grade yourself is the only kind worth running.
Most organizations are at a different level than they think they are. The ones that build something real in the next decade will be the ones who admitted it first.
Take the AI Maturity Index assessment at jenseregos.ai/assessment. Ten minutes. Nine departments scored. A diagnostic that does not let you grade yourself.
