Operational maturity criteria

Operational maturity in an ICP tests whether the prospect can absorb a solution and turn it into a working capability. Check the conditions behind the problem: ownership, data, process, technical controls, team behavior, and time to implement. A prospect can show interest, approve a proof of concept, and praise the product while still lacking a path to production or the ability to become a growth-supporting customer.¹ Treat enthusiasm as an invitation to inspect readiness, not as the readiness verdict.

Start with the desired change

Begin with the future state the account is trying to reach. A maturity check is useful when it connects the account's current operating conditions to a concrete change the solution must help deliver.

A practical maturity assessment answers three questions: "Where are we now? What does better look like? And what should we do next?"² Ask what will change if the initiative works, who will notice, and what must be true for the result to reach production.

Use the company vision as the reference point. A company vision is a simple statement with specific objectives that describes the future state of the company or business unit.³ Ask whether the proposed initiative supports that future state, and listen for a business outcome that can guide the buying process. If the answer stays at general interest, keep investigating the operating conditions.

Check the readiness foundations

This pass checks whether the account has the basic ingredients to carry the work. Keep the questions concrete, because vague confidence can hide missing ownership or capacity.

Operational readiness includes the company's data, team, script, and messaging.⁴ For an outbound motion, ask where the data comes from, who will use it, what script or workflow they follow, and which messages have already been tested. For another type of solution, apply the same check to its required inputs, users, process, and communication.

One fit model assigns operational readiness 15 percent of the fit score and defines it through team maturity, implementation capacity, and timeline alignment.⁵ Treat those as separate questions. Who can do the work? What capacity can they give it? When can implementation begin and reach the point where the account expects a result?

Move on when the prospect can describe the work, the people responsible for it, the inputs it depends on, and the timing they expect. A confident answer without those details is a reason to inspect the next area.

Inspect the capability areas

Use capability areas to find the operating gap behind a broad readiness answer. Evaluate each area separately, while remembering that the areas generally depend on one another.⁶

• PeopleOps covers recruiting, developing, retaining, and organizing an AI-ready workforce.⁷ Ask which skills the initiative needs, where those skills sit today, and how the account will cover gaps.
• DataOps focuses on data discovery, access, and use throughout the data lifecycle.⁸ Ask how the team finds the data, who can access it, and what happens as the data moves through the process.
• CloudOps covers the provision and allocation of cloud storage, compute, and other resources.⁹ Ask what resources the initiative needs and how the account will make them available.
• SecOps covers secure code deployment, access to systems and data, and identity resolution across storage, compute, and data assets.¹⁰ Ask how access is granted, reviewed, and removed.
• DevOps covers deploying and managing software through development, test, and production environments.¹¹ Ask how a change moves from an experiment into the environment where customers or internal users depend on it.
• MLOps covers testing, experimentation, and deployment of AI or machine learning models.¹² If the solution depends on those models, ask who owns testing, what qualifies a model for deployment, and how the team handles changes.
• AIOps covers identifying and resourcing AI initiatives within the organization.¹³ Ask how the initiative gets selected, funded, staffed, and connected to the wider operating plan.

These areas give you a sharper conversation than a single maturity label. They also show where a solution may need implementation support, a narrower first use case, or a later buying window.

Check adoption conditions and external signals

A technically capable account can still struggle to integrate a solution if the surrounding culture does not support the change. Use this step to test whether the organization can absorb a new way of working.

A culture that embraces technology supports successful technology integration.¹⁴ Ask how teams respond when a new system changes their workflow, how leaders reinforce adoption, and what happens when the first version creates extra work. Listen for a clear path from initial use to regular practice.

Job requirements can also reveal a company's maturity level.¹⁵ Compare the requirements in an open role with what the prospect tells you about its operating model. If the external signal points to a capability the current team does not describe, ask whether the account is building toward that capability or already depends on it.

Move on when the prospect's stated operating conditions and visible hiring direction point to the same future state. A mismatch gives you a qualification question and may change the timing of the opportunity.

Place the account on a usable maturity map

The output should help you decide how to work the account. Keep the map simple enough to use during qualification, and record the reasons behind the decision.

Some Operational Excellence maturity models use three levels: Logistical, Tactical, and Strategic.¹⁶ Efforts can show characteristics of all three, with maturity determined by organization, structure, consistency, and orientation toward the company vision.¹⁷ Use those dimensions to describe the account's current condition instead of assigning a level from one isolated symptom.

Treat the labels as a guide. A maturity model is a guideline, and an organization may not fit perfectly into one level.¹⁸ No maturity level is inherently good or bad because the appropriate level depends on business context.¹⁹

Write the qualification record in five lines:

1. Current state: what the account can do today.
2. Desired state: what must change for the initiative to succeed.
3. Missing capability: the constraint that could block adoption.
4. Implementation condition: the owner, capacity, access, and timing the account can provide.
5. Next action: the smallest step that will test whether the gap is real.

Keep each criterion specific and measurable. Great ICPs consist of specific, measurable qualities.²⁰ That makes the record useful to the rep who takes the next call and gives you a basis for refining the ICP.

What not to do

These mistakes turn operational maturity into a label with little use in qualification.

• Do not treat the ICP as another name for the Total Addressable Market or as a checkbox exercise for Account-Based Marketing.²¹
• Do not score the account on performance numbers alone. Operational maturity also examines how work is standardized, how problems are solved, how decisions are made, and how improvement is sustained.²²
• Do not force every account into one maturity level. Use the model as a guide and keep the business context in the record.¹⁸

Distinguish an account with a painful problem from one equipped to absorb the fix. Put each account into the motion its operating conditions support, then refine the ICP as products and use cases grow.²³