Across experience, platform, data, and ways of working — assessed lightly where that's enough, audited deeper where it isn't, and turned into a full strategy only once it's earned that.
Outcome: an honest scorecard, a ranked backlog, and the decision that unlocks the next twelve months.
Assessment is the precursor, not the strategy itself — it scores what's there and produces a directional recommendation, scoped only to the pillars a given problem statement actually calls for. Audit sits underneath it, verifying anything Assessment couldn't confirm with confidence, at whatever depth that verification needs. Strategy only starts once the ground is solid — it's where the full roadmap, the named decision, and the handoff into the other seven Strategy-layer practices actually happen. Each layer is broken out on its own below.
Every engagement starts at Assessment. Whether it moves into Audit, and how far into Strategy it goes, depends entirely on what Assessment finds — not on a fixed package. Assessment and Strategy are never the same deliverable; Audit is the layer that decides whether Strategy has solid ground to build on.
Assessment, Audit, and Strategy all score against the same four pillars — they just go to different depths and cover different scope. Every other strategy practice — Technology, Data, AI, Content, Brand, RevOps, Roadmap — is a drill-down module underneath one or more of these four.
Customer journeys, IA and content architecture, conversion paths, mobile/web parity, personalization, accessibility, design-system maturity.
Axelerant's edge — DesignArchitecture posture (composable / DXP / headless / hybrid), infrastructure, integration debt, engineering org shape.
Infrastructure & technical debt live hereSource-of-truth mapping, CDP/warehouse fit, governance and quality, activation and AI readiness.
Usually the weakest pillarEach pillar breaks down into concrete sub-dimensions — the actual things a practitioner scores, not an abstract category. No single engagement necessarily touches all 36: Assessment scopes in only what the problem statement calls for, Audit narrows further to whatever needs verifying, and Strategy works with whatever's already in scope by the time it starts. Data and Operating Model split evenly at eight apiece; Experience and Platform carry a few extra, for the reason explained below.
Content repositories, Digital Asset Management, and the commerce/ERP transaction layer don't sit neatly inside one pillar — they're systems, not experiences. They're evaluated primarily under Platform, as the systems of record, with a direct line back to Experience, since that's what those systems power. B2C and B2B journey differentiation sits under Experience for the same reason in reverse: it's a customer-facing distinction, but it depends entirely on what the Platform and commerce layer can actually support.
Evidence gathering, scoring, and roadmap negotiation are kept as separate steps on purpose. Assessment covers Phases 1–3 below — Phase 4 belongs to Strategy, and only runs once the ground underneath it is verified.
Stakeholder map, document intake, and a heuristic pass on the public surface — so interviews test hypotheses, not start from zero.
Interviews weighted by suspected risk, live product/tech walkthroughs, documentation review, analytics and heuristic audit — every finding tagged to a source.
Sub-dimensions scored independently first, cross-pillar contradictions caught in a practitioner-only workshop, before anything rolls up.
Scorecard and ranked backlog presented, the single unlocking decision named out loud, direct handoff into Roadmap & Sequencing.
Five levels gives enough room to separate "foundational but inconsistent" from "barely functional" — two very different situations that a coarser scale would flatten into one. At Assessment stage, these scores are directional — evidence-backed, but not yet audit-verified.
A sub-dimension's score is the answer to all three at once — aligned, low-risk, and competitive is what earns a 5. Failing even one of the three usually caps the score, regardless of how strong the other two look.
The four rubrics below are illustrative — one per pillar, picked to show what a concrete scoring conversation actually sounds like. Every one of the 36 sub-dimensions listed earlier gets the same treatment during a live assessment: five specific levels, not just a number on a scale.
| 1 — Absent | No coherent architecture. Ad hoc plugins and one-off scripts glued onto a legacy monolith. |
| 2 — Emerging | A migration toward something more composable has started, but most of the estate is still monolithic. |
| 3 — Developing | A modern architecture — headless, DXP, or hybrid — is in place for core surfaces, but legacy pieces persist elsewhere. |
| 4 — Advanced | The architecture is composable and consistent across most properties, with clear ownership per component or service. |
| 5 — Leading | Architecture is a genuine competitive asset — new capabilities ship as independent services without touching the core, and the pattern is documented and reused across the business. |
| 1 — Absent | No shared components. Every team builds UI from scratch, with inconsistent inline styles across pages. |
| 2 — Emerging | A components library exists but is undocumented and inconsistently adopted across teams. |
| 3 — Developing | A documented design system is in place and adopted by some teams, but not enforced elsewhere. |
| 4 — Advanced | The design system is the default build path, versioned, with contribution guidelines teams actually follow. |
| 5 — Leading | The design system is a shared product across teams and regions, drives measurable delivery-speed gains, and has a dedicated owner maintaining it. |
| 1 — Absent | No unified customer record. Identity resolution is done manually, if at all. |
| 2 — Emerging | A homegrown or partial CDP exists, but coverage is incomplete and teams don't trust the data in it. |
| 3 — Developing | A CDP is in place and integrated with one or two core systems, but activation use cases are still limited. |
| 4 — Advanced | The CDP is integrated across web, CRM, and commerce, supporting real-time segmentation. |
| 5 — Leading | The CDP is the backbone of personalization and measurement, with governed identity resolution and proven activation ROI. |
| 1 — Absent | No consistent planning cadence. Work gets prioritized ad hoc, often by whoever's loudest in the room. |
| 2 — Emerging | Some teams run sprints, but backlog discipline and definition of done vary widely across the org. |
| 3 — Developing | A standard cadence and tooling are in place, but capacity planning and cross-team coordination are inconsistent. |
| 4 — Advanced | Consistent planning, backlog, and reporting practices across teams, with reliable delivery predictability. |
| 5 — Leading | Ways of working are self-improving — retrospectives actually change practice, and delivery data feeds back into planning. |
Every gap scored on effort, dependency, and value, then plotted so the room can see, in one glance, what to act on this quarter versus what to sequence for later. This ranking is directional until anything flagged uncertain has been through Audit.
High value, low effort — act on these immediately.
High value, high effort — sequence deliberately, often the unlocking decision.
Low value, low effort — do opportunistically, never lead with these.
Low value, high effort — question whether this belongs on the roadmap at all.
Audit doesn't run on everything, every time. It runs wherever Assessment's evidence is too thin, too contradictory, or too high-stakes to hand to Strategy as a guess. Two levels, chosen by what triggered them.
On a recent discovery engagement, nobody reviewed the mobile app or the analytics implementation directly — the assessment relied on what stakeholders said was there. A Targeted Audit against those two areas alone would have caught the gap before Strategy started building on an assumption.
Some audits aren't optional regardless of what the customer's problem statement scopes in. A security review is a must-have the moment real infrastructure is in play, whether or not security was the stated reason for the engagement. Which audits are must-have, per pillar, gets defined once — not re-litigated on every engagement.
Every backlog closes with a single named decision — framed as a clear fork in the road, in front of the sponsor, in the readout, not buried in an appendix.
Whether the CMS gets replatformed within the next two quarters, or the organization keeps absorbing the compounding cost of patching it, is a fork already visible in the evidence.
Sequencing a CDP ahead of the personalization roadmap, rather than after it, is what determines whether personalization has a real data foundation to build on.
The absence of a Head of Product rarely blocks this quarter's work — but it quietly decides whether next year's roadmap has anyone accountable for it.
The scorecard fixes a point in time. The roadmap plots the path forward — a twelve-month target built from the quick wins already identified, then four more years of iterative movement toward the position the business actually needs. Short-term and long-term sit on the same chart, deliberately, so neither gets planned in isolation.
The quick-wins quadrant plus whatever the named decision requires. This is what Roadmap & Sequencing takes and turns directly into sprints.
The target position on the maturity chart, and the operating-model shape needed to sustain it without Axelerant in the room every quarter.
Axelerant's upcoming Strategy layer names eight practices — this assessment is the first. Every other practice draws directly from its scorecard, backlog, and named decision, rather than starting its own diagnostic from zero. That's what makes this a long-term partnership model, not a single deliverable.
The platform, architecture, and infrastructure direction, chosen against your scenario rather than our preference. Technology as the enabler, never the point.
How your data is modeled, governed, and put to work, so it becomes an asset the rest of the build can rely on.
Where AI actually earns its keep in the business, and the architecture, governance, and cadence to move it from pilot to production.
How content is planned, modeled, and governed, so it can be reused across regions and channels, and published without waiting on a developer.
The positioning and brand principles that keep the work coherent across every surface a customer touches.
The revenue operating model behind the platform — demand generation, pipeline management, and how CRM, marketing automation, and analytics compound outcomes after launch.
Priorities ordered into a build plan the team can execute from, so the strategy turns into shipped work, not a document.
Three different kinds of input, each used differently: one delivered engagement reviewed as a real-world reference point, five boutique practitioners competing for similar work (AIT among them), and six research-firm frameworks that have shaped how "digital maturity" is understood as a category.
A real, delivered four-function assessment (Product, Technology, Data & Analytics, Human Capital Management), built on 36 stakeholder interviews, a four-level scorecard, and a two-axis maturity chart. Reviewed here alongside the other entries in this landscape as one example of how this category of work gets delivered in practice.
AIT assesses as a one-time engagement rather than an ongoing relationship. Crosslake and Beckway assess for a deal. Dyopath assesses to sell a support contract. Strategex isn't a technology assessment at all. Every one of them hands off to somewhere else when the scoring stops.
| Firm | What they assess | Method | Buyer |
|---|---|---|---|
| AIT | Technology (architecture, systems, security, DR), Business Intelligence, Human Capital Management, and Product Management — four centers of excellence | Practitioner-led assessment feeding a prioritized strategic roadmap; for the PADI engagement specifically, 36 stakeholder interviews and a four-level scorecard | PE firms and portfolio companies, interim management engagements, public/private companies (often ahead of an exit or carve-out) |
| Crosslake | Full-stack tech due diligence — infra, SDLC, infosec, architecture | Practitioner-led, benchmarked vs. 4,000+ prior M&A deals | PE firms, at deal speed |
| Dyopath | IT maturity across people/process/tools (DYOSPHERE) | Entry point into an ongoing managed-services contract | Mid-market IT leaders, portfolio companies |
| Beckway | Tech due diligence + ERP/cloud, inside a broader ops practice | Interim operators embedded hands-on in the business | PE sponsors, portfolio management |
| Strategex | Not a tech assessment — 80/20 profit & growth, Voice-of-Customer | Interview and survey-driven commercial diligence | PE operating partners, B2B manufacturers |
Six frameworks, each emphasizing a different lever — the differences are emphasis, not quality. McKinsey leans on culture and talent, Gartner on operational systematization, MIT CISR on the business outcome itself.
| Framework | Dimensions | Maturity scale | Known for |
|---|---|---|---|
| McKinsey Digital Quotient | Strategy, organization & talent, agile delivery & culture, capabilities, adoption & scaling — 32 practices | 1–5 per practice, converted to a 0–100 score | Linking DQ score directly to 5-year shareholder return and revenue growth1,2 |
| MIT CISR Future-Ready | Customer experience × operational efficiency — a 2×2, not a checklist | Four quadrants: Silos & Spaghetti → Future-Ready | Quantifying the cost of staying put — Silos & Spaghetti firms ran 5pp margin below industry average; Future-Ready firms ran 16pp above3 |
| Westerman / MIT + Capgemini "Digirati" | Digital intensity × transformation management intensity | Four quadrants: Beginners, Fashionistas, Conservatives, Digirati | The original 2x2 that named the failure mode of investing in digital without governance ("Fashionistas")4 |
| Forrester Digital Maturity Model | Culture, technology, organization, insights — 28 questions | Four segments: Skeptics, Adopters, Collaborators, Differentiators | Embedding the questions directly into an annual Business Technographics survey, so scores are always benchmarked against a live global sample5,6 |
| Gartner ITScore / AI Maturity Model | Applied per functional domain — IT, Data & Analytics, Enterprise Architecture, AI | Five levels: Basic → Opportunistic → Systematic → Differentiating → Transformational | A subscription diagnostic with 2,000+ benchmarks, reusable across functions rather than a one-off engagement7,8 |
| BCG Digital Acceleration Index | 41 dimensions across strategy, operating model, and technology | Continuous index score benchmarked to peers and "digital leaders" | The largest longitudinal dataset in this list — over a decade of data, 10,000+ companies9 |
Two design choices in this framework draw directly on what's below: a five-level scale rather than a four-segment one, giving room for a genuine mid-point between early and mature states, and a 2×2 rather than a flat checklist for the headline visual, since a single number hides more than a plotted position does. What sets this framework apart from every entry in this landscape is what happens after the score: it hands off directly into a build team, rather than closing out as a standalone report.
Axelerant's Digital Maturity Assessment is the only one in this set that scores you and then builds with you — same team, same metric, straight from scorecard into every other Strategy practice, Design, and Engineering.
PADI is the obvious pilot — the raw material already exists to pressure-test the scoring rollup and the two-axis chart.
McKinsey's DQ and BCG's DAI both refresh their datasets periodically — worth revisiting yearly so Axelerant's scoring calibration doesn't drift from what "leading" actually means in the market.
So the client-agreed weighting step doesn't get skipped under deadline pressure.
So the handoff is one shared backlog, not two teams rebuilding the same thing in different tools.
Deloitte's, KPMG's, PwC's, and Capgemini's own models were reviewed via secondary synthesis (Technoforte, StartUs Insights) rather than fetched from primary sources directly, and are referenced in the framework's supporting notes accordingly rather than scored in the table above.