Owns narrative, sequencing, and client sign-off. Written recommendations and workbook materials are supplied outside this dashboard.
Runs the P0 priorities track: dates, owners, dependencies, and client approvals.
Executes the Personalization + HubSpot tab (properties, workflows, CMS, Operations Hub where relevant), plus QA and rollback.
Summary
Strong full-stack positioning, flywheel narrative, and credible proof (including at least one strong HTML case study). The sharpest gap vs what you sell: the same homepage and primary CTA for every visitor while you help clients use HubSpot for segmented, personalized experiences—reflected as high priority on personalization and conversion in the Scorecard. Supporting levers: HTML case studies (AEO) vs PDF-only for key wins, plus a deliberate two-path conversion design once you are ready to operationalize it.
Current scores vs target band
Radar uses scored categories only (same set as the bar chart). Dashed ring = illustrative 4.0 “strong” band. “Not assessed” rows are intentionally omitted.
Scores today vs a 4.0 “strong” bar
This chart only includes rows that received a numeric score in this audit. Performance & mobile is listed on the Scorecard as not assessed because we did not run a dedicated speed / Core Web Vitals pass here.
How to read it: for each scored area, the blue bar is the current score; the gray bar is the same 4.0 “strong” benchmark used on the radar. The space between the two is how much lift is still available on that axis.
We are not using “RAG” here. Status is plain language tied to the 1–5 score in each row.
| Category | Score | Status | What we observed |
|---|
Numbers are qualitative from this audit (structured review of the public site and stated funnel patterns), not an automated benchmark suite. They are meant to prioritize discussion and implementation — not to imply lab-grade measurement.
P0 — first sprint focus
These are the four workstreams we recommend starting first. In practice, your project manager keeps a simple tracker: who owns each item, when it is due, and what must be finished before the next step begins. Use whatever you already use—Asana, Monday, Notion, or a shared spreadsheet. There is no special jargon required; the table below is the scope list.
| Workstream | Priority | What “done” looks like |
|---|---|---|
| 1 · Segment entry (homepage + vertical landings) | P0 | Visitors can self-identify or arrive via UTM and see a hero, proof, and CTA that match that audience—not one generic path for everyone. |
| 2 · Clear conversion paths (two ways to raise a hand) | P0 | At least two intentional paths—for example a short calendar booking for a fit conversation and a separate, longer form for a scoped inquiry—with each tagged in CRM so follow-up matches intent. |
| 3 · Case studies in HTML (AEO-friendly proof) | P0 | Key stories live on the site as proper pages (search- and snippet-friendly), with one canonical URL per story; PDFs only if you still want a download, not as the only home for the story. |
| 4 · CRM segments that power the site | P0 | Reliable segment fields and lists in HubSpot so marketing and the site can show the right message to the right person—including data cleanup where needed. |
Fix Your Personalization Deficit with HubSpot
This tab is the remediation spine: who sees what on the site (lists + smart content), how visitors convert (intent-matched CTAs and meetings vs forms), and proof in HTML for search and AEO — on the HubSpot stack you already run. Operations Hub keeps CRM data and routing trustworthy for personalization; Marketing Hub and CMS deliver forms, meetings, smart modules, and journeys. Confirm subscription tiers before enabling advanced Operations Hub features (for example programmable automation).
| ID | Surface | What to build | Acceptance (short) |
|---|---|---|---|
| T-01 | Ops + CRM | Properties primary_segment, intent_type; workflow on submit. | 100% new site leads have values populated. |
| T-02 | Marketing | Active lists per segment + unassigned bucket. | No duplicate segment membership without rule. |
| T-03 | CMS + Marketing | Smart rules: hero + proof strip by list membership. | Known contact sees variant; incognito sees default. |
| T-04 | Marketing | Meetings link + inquiry form; hidden intent field. | CRM timeline shows correct source + intent. |
| T-05 | Ops (optional) | Data quality / title bucket → persona (if justified). | Tier confirmed; test matrix passes. |
| T-06 | CMS | Case study HTML template + FAQ/schema module. | Pilots live; one canonical URL per story. |
| T-07 | Marketing | Post-submit journeys by intent_type. | Branches enroll correctly; unsubscribe compliant. |