Sample report — illustrative data
The Digital Performance Benchmark
This is an anonymized, illustrative example of the benchmark we run during discovery — the assessment that tells a leadership team where its digital operation actually stands. It is written for CEOs, boards, and investors, and it supports one decision: where the next quarter's effort and budget produce the most return.
How to read this report
We analyzed the company's public website, analytics, field performance data, and search and AI-answer coverage. The method:
- Nine-dimension maturity scoring. Each dimension is scored 0–5 against a defined rubric, then benchmarked against the company's category.
- Evidence over opinion. Scores draw on analytics, real-user performance data, and measured search and AI-answer coverage — not stakeholder interviews alone.
- The gap is the roadmap. Low scores are not criticism; they locate the highest-leverage fixes.
- Every figure on this page is illustrative. It shows the shape of the deliverable, not any real client's data.
The scorecard
Nine dimensions, scored 0–5 and benchmarked against the category. Illustrative scores for an anonymized mid-market B2B company.
AI discoverability scores 1 of 5 and accessibility 2 of 5 — the two lowest marks, and the two highest-leverage fixes. Brand consistency and search visibility are strongest at 4 of 5.
| Dimension | Score (of 5) |
|---|---|
| Brand consistency | 4 |
| UX clarity | 3 |
| Accessibility | 2 |
| Mobile performance | 3 |
| Conversion readiness | 2 |
| Search visibility | 4 |
| AI discoverability | 1 |
| Analytics maturity | 3 |
| Automation maturity | 2 |
Read the bars as a map, not a verdict. The company is good at being found in classic search and looks coherent doing it — and it is nearly absent where buyers increasingly start, while excluding users it has already paid to reach. The two lowest scores are where the next quarter goes.
Qualified demand, twelve months
Indexed qualified demand — enquiries that matched the company's buyer profile — across the benchmark period. Illustrative data, January = 100.
Jun — Technical and accessibility fixes ship — qualified demand turns upward
Qualified demand rises 38 points over the year, from 100 in January to 138 in December, with the sustained inflection following the technical and accessibility fixes shipped in June.
| Period | index |
|---|---|
| Jan | 100 |
| Feb | 103 |
| Mar | 108 |
| Apr | 106 |
| May | 112 |
| Jun | 118 |
| Jul | 115 |
| Aug | 121 |
| Sep | 119 |
| Oct | 127 |
| Nov | 133 |
| Dec | 138 |
The point of the chart is the inflection, not the slope: demand did not respond to more content or more spend — it responded when the site stopped blocking the demand already arriving. That is typical of benchmarked companies in this score band.
Findings
-
Invisible in AI answers while competitors are cited
AI discoverability scores 1 of 5. Running the category's core buying questions through the major answer engines, this company appeared in none of them; three competitors appeared in most. That matters commercially because first-pass vendor research is increasingly an answer-engine query, and an absent brand is not a runner-up — it is not considered. First move: define the 20–40 questions buyers actually ask, measure the current citation footprint, and rebuild core pages so answers can be retrieved, lifted, and corroborated.
-
Accessibility gaps cost users and contracts
Accessibility scores 2 of 5: insufficient contrast on key templates, forms that fail keyboard navigation, and no stated conformance level. Beyond the users this excludes today, it limits procurement eligibility — enterprise and public-sector buyers increasingly require an accessibility standard in vendor assessments, and this company cannot currently state one. First move: audit the core templates and forms against WCAG 2.2 AA, fix what fails, and publish a conformance statement sales can hand to procurement.
-
Demand exists; the conversion path leaks it
Search visibility scores 4 of 5 while conversion readiness scores 2 of 5. The company earns qualified visits, then loses them: the primary contact form abandons at a high rate on mobile, and the highest-traffic pages carry no clear next step. Commercially, this is the most expensive kind of problem — money already spent on demand that the site then wastes. First move: rebuild the top three entry pages and the enquiry flow before any new demand spend.
-
Reporting describes traffic, not the business
Analytics maturity scores 3 of 5: events fire and dashboards exist, but leadership cannot answer "which channel produced this quarter's pipeline" without a manual exercise. Decisions about budget follow opinion because the numbers do not connect to revenue. First move: define the handful of questions the leadership team actually asks, and rebuild reporting around those — channel to qualified enquiry to pipeline, one view.
Recommended sequence
Ninety days, three moves, in this order — each one makes the next cheaper.
-
Days 1–30 — Foundation: accessibility and conversion-path fixes
Fix the failing templates, forms, and mobile enquiry flow identified in the scorecard.
Expected effect: The site stops excluding users and losing existing demand; procurement can be answered honestly.
-
Days 31–60 — Answer-engine readiness
Restructure core pages, add structured data, and rewrite key passages so they can be lifted and cited; start monthly citation tracking.
Expected effect: AI discoverability moves off 1 of 5 with a measured baseline, and first citations appear on tracked questions.
-
Days 61–90 — Reporting the business reads
Rebuild measurement around channel-to-pipeline questions and deliver the first monthly report in the new format.
Expected effect: Budget decisions run on evidence; the benchmark re-scores at day 90 to show movement.