digital-maturity-benchmark
Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V. ✓ Copied. Switch to Claude and paste — ⌘/Ctrl+V.
Digital Maturity Benchmark
Score a client's or competitor's digital maturity across six dimensions and produce a benchmark report with evidence, quartile positioning, and a prioritized improvement roadmap.
When this skill applies
- User asks for a "digital maturity assessment," "maturity score," "benchmark vs. sector peers," or "where do we sit digitally?"
- Pre-envision or platform-selection context: establishing a current-state baseline before recommending a roadmap
- RFP or BD: demonstrating RBA's diagnostic capability with a structured current-state read
- Companion to
competitor-teardown: use that skill first for a competitor, then this skill to score the client head-to-head
Skip for: full competitor teardown → competitor-teardown; SEO/content gap only → seo-content-gap; market structure → five-forces-analysis.
Inputs
| Parameter | Required | Default |
|---|---|---|
client-domain-or-name |
Yes | — |
--sector |
No | auto-infer |
--compare |
No | — |
--output |
No | scorecard |
Workflow
Step 1 — Scope and baseline
Confirm:
- Client domain or organization being scored
- Industry sector (used to contextualize the score against sector norms)
- Competitor domains for comparison (if any)
- Intended output format
Collect initial signals: stack detection (see competitor-teardown reference § Stack Taxonomy), organic traffic estimate, Core Web Vitals from PageSpeed Insights.
Step 2 — Score each dimension
Score each dimension 1–5 using the anchors in reference.md § Maturity Dimension Anchors. For every score:
- Cite at least one piece of observable evidence (page URL, HTTP header, tool output, published document)
- Note confidence: High (direct evidence), Medium (indirect signal), Low (inferred from absence of signals)
- Flag dimensions where evidence was insufficient to score reliably (mark N/A or score with a confidence caveat)
The six dimensions:
1. Experience Design Observable signals: visual consistency, navigation clarity, heuristic review (run 5 of Nielsen's 10 heuristics minimum), mobile responsiveness, design system evidence, Core Web Vitals performance.
2. Content Operations Observable signals: content types present, publishing cadence (date stamps on 5+ pieces), topic depth and consistency, content freshness, editorial standards evidence (author bios, bylines, fact-check notices), content hub or resource center presence.
3. Data / Personalization Observable signals: tag management tool (GTM, Adobe Launch), analytics platform detected, A/B testing tool detected, gated content or progressive profiling, recommendation widgets, region/industry selectors, CDP signals (Segment, Tealium).
4. Commerce Capability Observable signals: commerce platform detected in stack, product catalog, cart/checkout flow, B2B pricing/quoting, subscription or marketplace signals, multi-currency or multi-region commerce. Score N/A for organizations with no commerce mandate.
5. Cloud / Infrastructure Observable signals: CDN detected (type and tier), Core Web Vitals performance (PageSpeed Insights — mobile and desktop), hosting provider signals (Azure, AWS, GCP, Vercel, Netlify), SSL and HTTP/2 or HTTP/3 presence, evidence of edge delivery or DDoS protection.
6. Accessibility
Observable signals: run WAVE Web Accessibility Evaluation (public view at https://wave.webaim.org/report#/[domain]) for the homepage; check for skip navigation link, visible focus indicators, alt text on primary images, color contrast on body text (visual check), published accessibility statement or VPAT, compliance target statement.
Step 3 — Maturity band and quartile positioning
Overall maturity score = sum of six dimension scores (max 30; commerce N/A = max 25).
| Band | Score range (6 dimensions) | Score range (5 dimensions, commerce N/A) |
|---|---|---|
| Emerging | 6–12 | 5–10 |
| Developing | 13–18 | 11–15 |
| Advancing | 19–24 | 16–20 |
| Leading | 25–30 | 21–25 |
Sector quartile positioning:
Use the sector benchmarks in reference.md § Sector Quartile Benchmarks to position the client's score:
- Bottom quartile (Q1) — Emerging band or low Developing
- Lower-middle (Q2) — Developing band
- Upper-middle (Q3) — Advancing band
- Top quartile (Q4) — Leading band
State the quartile and note that sector benchmarks are derived from RBA's observed assessment range, not a statistically representative sample.
Step 4 — Head-to-head comparison (if competitors provided)
Score each competitor on the same six dimensions using the same methodology. Present as a comparison table:
| Dimension | [Client] | [Competitor 1] | [Competitor 2] | Delta (client vs. best) |
|---|---|---|---|---|
| Experience design | ||||
| Content operations | ||||
| Data / personalization | ||||
| Commerce capability | ||||
| Cloud / infrastructure | ||||
| Accessibility | ||||
| Total |
Highlight the dimensions where the client is ahead (competitive advantages) and behind (priority improvement areas).
Step 5 — Roadmap (if --output roadmap)
For each dimension scoring ≤ 3, produce a prioritized improvement recommendation:
| Dimension | Current score | Target score | Priority | Recommended action | Estimated effort | RBA-addressable? |
|---|---|---|---|---|---|---|
| [Dimension] | [1–5] | [target] | High/Med/Low | [specific action] | Low/Med/High | Yes/No/Partial |
Priority = combination of gap severity (how far below 5?) and strategic importance to the client's goals.
RBA-addressable flags which items RBA can help deliver directly vs. which require client-side organizational change (e.g., RBA can improve UX and accessibility; RBA cannot change the client's content governance culture unilaterally, but can recommend and model it).
Step 6 — Self-check before returning
- Every score has at least one cited evidence item (URL, tool output, or named document)
- N/A dimensions are flagged explicitly — not left as blanks
- Sector quartile claims are labeled as RBA-observed benchmarks, not authoritative industry statistics
- Roadmap items distinguish RBA-deliverable from client-organizational actions
- Accessibility scoring uses at least one tool-supported check (WAVE public view), not visual impression only
Return the benchmark report as markdown. Offer to run market-research-reviewer for independent quality check.
Reference file
reference.md— Maturity Dimension Anchors (detailed scoring), Sector Quartile Benchmarks, Evidence collection checklist per dimension
Technical details
- Plugin
- market-research-agent
- Author
- Dakota Smith
- Skill name
digital-maturity-benchmark- Maturity
- experimental
- Security review
- No security review
- Owners
-
- strategy
- Argument hint
<client-domain-or-name> [--sector <industry-vertical>] [--compare <competitor1,competitor2>] [--output scorecard|roadmap|executive-summary]- Allowed tools
-
ReadWriteWebFetch(domain:pagespeed.web.dev)WebFetch(domain:wave.webaim.org)WebFetch(domain:www.wappalyzer.com)WebFetch(domain:builtwith.com)WebFetch(domain:similarweb.com)WebFetch(domain:www.w3.org)
- Source
plugins/market-research-agent/skills/digital-maturity-benchmark/SKILL.md
Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.