The score

How the AI readiness score works

The score is one number out of 10. Seven factors go into it. Each one carries a weight, and each one gets scored on the same 1 to 10 rubric our engineers use when they do the guided version, so when a client self-scores a 6.8 and we come back with a 6.5 after the scans, nobody is surprised.

Seven factors, weighted by risk

Identity and permissions carry the heaviest weights, and that's not a philosophical choice. A Copilot license acts as whoever is signed in. If Dave in sales can open the HR share (and in a lot of companies he can, because nobody ever checked), then so can Dave's Copilot. Governance and monitoring are next in line, because sooner or later a cyber insurer or an auditor is going to ask you to prove AI is being used the way your policy claims, and those two factors are the proof. The last three, data quality, people and technology, matter too, just less urgently.

Each factor is scored 1 to 10, then multiplied by its weight and added up. A perfect 10 on identity, at 20%, adds 2.0 to the total. A perfect 10 on technology, at 10%, adds 1.0. That's the whole formula; there's nothing hidden in it.

FactorWeightWhat it measures
AI Governance & Policy15%Policy maturity, enforcement, oversight, compliance alignment
Identity & Access Security20%MFA, privileged access, conditional access, least privilege
Data Governance & Permissions20%Effective permissions, oversharing, external sharing, ownership
Data Quality & ROT10%Redundant, obsolete and trivial data; freshness; retention
Data Security Controls & Monitoring15%DLP, audit logging, insider risk, alerting maturity
Organizational Readiness10%Training, leadership alignment, use cases, ROI tracking
Technology & Integration Readiness10%Cloud maturity, integration, legacy constraints, modernization
Sample report ● AI Capable
7.5OUT OF 10
Overall readiness score
6.0 × 0.15 + 8.0 × 0.20 + 7.0 × 0.20 + 7.0 × 0.10 + 8.0 × 0.15 + 9.0 × 0.10 + 8.0 × 0.10 = 7.5

The four readiness bands

Your overall score lands in one of four bands, and so does each factor on its own. The band is the advice. It says what you can safely do with AI this quarter, not someday.

Below 5.0

⚠ AI Exposed

The governance and data foundations aren't there yet, and switching AI on now would mostly make the existing gaps easier to find.

Do not deploy AI yet
5.0 to 5.9

▲ AI Vulnerable

AI can be used, carefully, but the exposure is real enough that we'd keep it to individual productivity work.

Limited, personal use only
6.0 to 8.4

● AI Capable

You can roll AI out across the company here. The risk stays manageable provided the governance pieces (policy, approved tools, DLP) go in before the licenses do.

Scale with governance
8.5 to 10

✓ AI Mature

AI is governed, monitored and tuned as part of how the business runs; this environment has earned the right to scale it.

Full strategic deployment

The maturity rubric

Here's what each score range tends to look like when we walk into an actual office. The self-assessment puts you on this scale using three questions per factor. On the guided evaluation an engineer does the same thing from scans of your tenant, which takes longer and is a lot harder to argue with.

📋 AI Governance & Policy 15%

Is there a written AI policy? Does anyone enforce it, or is it a PDF on the intranet nobody has opened since the day it was approved? Who is watching, and does any of it line up with the regulations you already live under?

1 to 2No formal AI policy. AI use unmanaged. No defined approved platforms.
3 to 4Policy drafted but not approved or enforced. Limited clarity on data usage boundaries.
5 to 6Policy approved. Approved platforms defined. Governance roles identified but monitoring limited.
7 to 8Policy enforced through technical controls. Review cadence established. Platform approval process formalized.
9 to 10AI governance integrated into enterprise risk management. Formal steering committee. Periodic audit review. Executive reporting in place.
🔐 Identity & Access Security 20%

Multi-factor authentication, how admin accounts are handled, conditional access, and whether people hold more access than their job needs. On the guided evaluation we read this straight from an identity posture scan of the tenant.

1 to 2MFA inconsistently enforced. Legacy authentication active. Shared or excessive admin accounts. Multiple standing global admins. No conditional access over users, devices and locations.
3 to 4MFA broadly enabled. Legacy authentication partially disabled. Admin roles segmented but permanent. Conditional access minimal or inconsistent. No formal privileged access review.
5 to 6MFA enforced for users and admins. Legacy authentication disabled. Admin roles segmented. Conditional access applied to privileged roles. Privileged access reviewed periodically.
7 to 8Privileged roles governed just-in-time. Standing global admin roles minimized. Conditional access aligned to risk posture. Privileged roles require a compliant device plus MFA. Quarterly documented access reviews.
9 to 10Standing privilege minimized across all roles. Privileged access only through just-in-time activation. Automated access reviews and expiration. Identity risk signals feed access policies. Identity governance integrated with the security program.
🗃️ Data Governance & Permissions 20%

Who can actually open what, how much has been shared wider than anyone intended, how sharing with outsiders is controlled, and whether each library has an owner who'd notice. On the guided evaluation we don't guess at this; we pull a permissions report across the whole tenant and count.

1 to 2Widespread open permissions. No periodic review. External sharing uncontrolled.
3 to 4Permissions inconsistently managed. Ownership unclear. Oversharing likely but not quantified.
5 to 6Role-based permissions defined. Periodic reviews conducted but not automated.
7 to 8Regular permission audits. External sharing tightly governed. Clear data ownership accountability.
9 to 10Automated permission governance. Continuous monitoring. Zero-trust access principles embedded.
🧹 Data Quality & ROT 10%

How much redundant, obsolete and trivial content (we call it ROT) is sitting in your libraries. The classic case is a price list with ten copies in ten folders, where Copilot cheerfully quotes the 2019 one. Also whether the rest is current, and whether retention rules exist and anyone enforces them. We inventory the workspace for this on the guided evaluation.

1 to 2Significant stale data. No retention enforcement. Unknown data inventory.
3 to 4Retention policies exist but are not enforced. Large volumes of aging content unmanaged.
5 to 6Retention applied to key repositories. Some ROT cleanup underway.
7 to 8Active lifecycle management. Defined archival strategy. Clear data freshness standards.
9 to 10Automated retention enforcement. ROT minimized. Data continuously optimized for AI readiness.
🛡️ Data Security Controls & Monitoring 15%

Data loss prevention, audit logging and insider-risk handling, and the question underneath all three: when something fires, does the alert reach a person who does something about it, or does it land in a mailbox nobody reads? The guided evaluation scores this from a data security posture report.

1 to 2Limited logging. No DLP controls. Minimal visibility into AI-related activity.
3 to 4Basic audit logs enabled. No DLP policies. Insider risk program not established.
5 to 6DLP policies in place for key data types. Audit logging active. Insider risk awareness growing.
7 to 8DLP enforced across endpoints and cloud. Insider risk program operational. AI activity monitored.
9 to 10Advanced DLP with AI-aware policies. Continuous monitoring. Automated incident response. Full audit trail.
👥 Organizational Readiness 10%

Has leadership agreed on what AI is actually for here? Has anyone trained the staff, or did they learn from YouTube? Are the use cases written down anywhere, and is somebody measuring whether they paid off?

1 to 2No AI training. No defined adoption strategy. AI use ad hoc.
3 to 4Leadership aware but no structured education. Limited use-case definition.
5 to 6Formal training delivered. Use cases identified. Adoption measured informally.
7 to 8Structured AI enablement program. Clear communication strategy. ROI metrics tracked.
9 to 10AI embedded in operational strategy. Continuous training. Measured productivity and risk-reduction outcomes.
☁️ Technology & Integration Readiness 10%

How much of the stack lives in the cloud, whether the systems talk to each other or rely on someone re-keying data on Fridays, which legacy pieces are holding things back, and what it would cost to move them.

1 to 2Legacy systems limit AI integration. Minimal API support.
3 to 4Hybrid environment. Integration possible but constrained.
5 to 6Core systems cloud-enabled. APIs available but underused.
7 to 8Modern, cloud-native architecture. Integration supports AI augmentation.
9 to 10Strategic platform alignment. AI-native tools integrated into workflows. Infrastructure optimized for scale.
The AI readiness equation
AI Value = ( Strong Processes + Trusted Data + Clear Governance + Secure Identity + Prepared People + Modern Systems ) × AI

AI multiplies whatever strength is already in the building. Because it's a multiplication, a low number in any one term drags the whole product down, and that's why the rubric keeps steering you toward your weakest factor instead of toward buying more AI.

Read the strategy behind the score →

See your own score

Twenty-one questions, about 15 minutes, and the results are scored on exactly the rubric you've just read.