Does the website scope match what Matthew is actually building?
Read both source documents Matthew sent on Mon 11 May 2026 — the Business Plan v2.0 and the Marketing Brief v1.0. Walked them line-by-line against the website Scope of Work (12 May 2026 v2.0) and the live Squarespace site. This is the gap analysis.
What was reviewed
Three sources cross-walked. Quotes are direct from the named document.
Business Plan v2.0
Sent by Matthew Mon 11 May 2026. 1,881 lines. 17 sections + 2 appendices. Contents: Strategic positioning, 5-phase roadmap, customer segmentation, 11-SKU catalogue, 4 moats, tech ecosystem, 121 Group division of labour, KPIs, 5-year financials.
Marketing Brief v1.0
Sent same email. 591 lines. 9 sections. Contents: Strategic frame, brand architecture & voice, 3 audience tiers, 4 content pillars, quarterly campaign roadmap, 121 Group division of labour, named KPIs, what’s expected from 121 Group.
Live Squarespace site
Crawled 12 May 2026. 196 URLs · 38 top-level pages · 32 articles. Existing service mix: AI Workshop, Legal-Tech Strategy & Advisory, Legal Consultant, Fractional Growth Officer, Transformation Partner. Structured by audience (in-house vs law firms).
What’s already aligned · 10 items
Where the scope-of-work already reflects the plan correctly. No change needed.
WordPress as the platform — aligns with plan’s tech ecosystem
Plan \u00a78 lists Layer 5 (cert + community platform) as “Maven for cohorts · Circle/Slack for community” and the public site as “the firm’s brand”. WordPress is the right substrate to host that brand & integrate with downstream tools. No rework.
AU hosting & data sovereignty
Plan emphasises Australia-first GTM and ASX 200 / large enterprise audience. AU-hosted Synergy stack we proposed is on-message. No change.
HubSpot as the CRM of record
Marketing Brief \u00a76: “HubSpot operations, lead capture forms, scoring, routing into pipeline. Dashboard reporting.” Our scope already wires HubSpot natively into Phase 1. No change.
SEO & programmatic content readiness
Plan KPIs: 1,500 newsletter subs FY26 \u2192 100K+ FY30. Marketing Brief Pillar 1\u20134 cadence: 4 whitepapers/qtr, podcast bi-weekly, weekly LinkedIn long-form. WordPress + REST API + Rank Math is the right substrate to support that volume. Phase 1 deliverable.
121 Group as marketing partner — division of labour ratified
Marketing Brief \u00a76 explicitly assigns substance origination to Everingham, distribution & amplification to 121 Group. Our scope respects this: we build the substrate, we don’t author opinions on Matthew’s behalf. Operating principle confirmed.
Phase 1 timing aligned — both run May\u2013August 2026
Plan Phase 1 (Foundations): now to August 2026. Our website Phase 1: signed 4 May, go-live target Week 8 (~end June 2026), with content tuning into July\u2013August. Calendar fits.
Stage-gate discipline matches plan’s sequencing
Plan \u00a74: “Resist the temptation to run [phases] in parallel — that is the founder-bottleneck failure mode that destroys most ventures of this shape.” Our scope’s explicit Phase 1 \u2192 2a \u2192 2b \u2192 3 \u2192 4 gates with named triggers honour this principle. Fully aligned.
Lead-magnet pages preserved — protect the publication funnel
Plan KPIs include MQLs delivered to pipeline (80 FY26, 250 FY27, 600 FY28). The 8 existing campaign / lead-magnet pages (/ai-readiness-pack, /ebook, /legal-ops-tech-scorecard etc.) are explicit MQL sources. Our scope keeps every URL working. Plan-protective.
Phase 2b portal as “not a custom build until needed”
Plan \u00a78: “Client portal — for active engagements, a Notion-based client space or a structured Google Drive sub-folder per engagement; not a custom portal until Year 3.” Our Phase 2a is exactly that (Drive + login, ~$0). Phase 2b ($2.5k indicative) is contingent on cohort 1 signal. Discipline preserved.
Existing 4 content collections survive as Pillars 1\u20133
Marketing Brief \u00a74 names 4 content pillars: (1) legal-tech decision-making, (2) legal ops maturity, (3) AI in legal, (4) the category & profession. Existing collections /legal-technology, /legal-process, /legal-skills-and-coaching, /law-firms-marketing-growth already map to the first three pillars. Pillar 4 is a future addition. No structural rework needed.
Where the scope conflicts with the plan · 6 items (1 resolved 13 May)
These need a decision before Phase 1 build crosses Week 4 (information architecture lock). C2 has had its direction set; remaining items are flagged in red on the Scope of Works §1.1 or resolved internally below.
Naming: “Three services” vs plan’s “four-layer ecosystem”
| Plan says | Layer 1 Insights (free) · Layer 2 Community ($3\u20135k p.a.) · Layer 3 Education & Certification ($6\u201312k/seat) · Layer 4 Advisory & Managed Services ($25k\u2013$2M+). |
| Scope says | Three named services: Consulting · Education · Membership. Insights folded into the blog; the “Membership” tab maps to plan’s Community. |
| Risk | “Consulting” isn’t the plan’s name — the plan calls it Advisory & Managed Services. “Membership” isn’t the plan’s name either — the plan calls it Community. Inconsistent vocabulary across website, sales, contracts, marketing collateral. |
| Recommend | Adopt plan’s vocabulary verbatim: Insights · Community · Education · Advisory & Managed Services. The website nav can still consolidate, but the published service names should match the business plan. |
Education positioning — “premium $10k+ certs, live/in-person” vs plan’s cohort SKUs ✓ Direction set 13 May
| Plan says | Three named programmes: Maturity Programme ($6\u20138k/seat), Procurement Mastery ($8\u201312k/seat), AI for Legal Leaders ($6\u20139k/seat). Cohort-based. 20\u201325 seats per cohort. Maven as delivery platform. Co-credentialed with university or association by Cohort 2. |
| Scope says | Phase 3: “premium $10k+ certs, live or in-person”. Doesn’t name the three programmes. Implies 121 Group builds the LMS / education platform. |
| Risk | Wrong delivery model assumed. Plan uses Maven (purpose-built for cohort education); we implied a custom build. Custom LMS would be 5\u201310\u00d7 the cost and duplicate Maven’s functionality. Three programme names are also missing — the website’s Education page can’t convert without them. |
| Recommend | (1) Education page in Phase 1 = marketing surface that lists the three named programmes + waitlist signup — no commerce, no LMS. (2) Cohort recruitment runs through Maven embed + HubSpot forms in Phase 2a (no website build). (3) Strike “custom education platform” from Phase 3 scope — replace with “Maven integration + cert-verify page”. |
| Resolved 13 May | Direction adopted. Phase 3 of the website Scope of Works updated: now reads “Maven-style education portal integration (Layer 3)”. Replaces earlier “custom WP admin extension” framing. Indicative scope: Maven (or equivalent — Circle, Disco, Mighty Networks) account + brand theming, enrol button hand-off, public cert-verify page /verify/{cert-id}, HubSpot bi-directional sync, alumni surface. Specific platform choice remains Matthew’s call. |
Membership / Community timing — Phase 2b (M4\u20136) vs plan’s Phase 3 (Apr\u2013Aug 2027)
| Plan says | Phase 3 (April\u2013August 2027): “Community paid tier opens with founding members invited from existing client base and content audience.” Price band $3\u20135k p.a. Conversion layer; not primary revenue. |
| Scope says | Phase 2b (Month 4\u20136 from Phase 1 launch \u2248 Oct\u2013Dec 2026) builds the member portal at $2.5k indicative. |
| Risk | We’d ship a paid-membership commerce flow ~6 months before the plan opens the paid tier. Either: (a) we waste the $2.5k build because no members exist yet to use it, or (b) we accidentally pull the plan’s Phase 3 commitment forward without a curriculum + community roster to fill it. |
| Recommend | Push the website Phase 2b portal build to align with plan’s Phase 3 (Q2 FY27 = Dec 2026\u2013Feb 2027 onwards). Until then, the “Membership” surface is a waitlist-only landing page. The $2.5k indicative number stays valid; the trigger moves. |
Phase numbering misalignment between scope and business plan
Both documents use “Phase 1\u2026Phase 5” numbering but they don’t mean the same things. Easy to confuse internally and in any client-facing artefact.
| Period | Business plan phase | Website scope phase |
|---|---|---|
| May\u2013Aug 2026 | Phase 1 — Foundations (Drive taxonomy, content cadence, hire senior consultant) | Phase 1 — WP migration + 2 new pages |
| Sep 2026\u2013Mar 2027 | Phase 2 — Productisation (SKUs formalised, Telstra implementation, Maturity curriculum, waitlist opens) | Phase 2a — cohort 1 recruitment (Drive + login) |
| Apr\u2013Aug 2027 | Phase 3 — Ecosystem (first cohort runs, community opens, first international engagement) | Phase 2b — member portal build |
| Sep 2027\u2013Aug 2028 | Phase 4 — Scale (UK principal, Procurement Mastery + AI for Legal Leaders cohorts, managed services) | Phase 3 — education platform |
| Y4\u20135 | Phase 5 — Category leadership (Singapore, US, multi-cohort) | Phase 4 — Layer 4 capture surface (advisory & managed services pages) |
Recommend: rename the website scope’s phases to mirror the plan: Migration (P1) · Cohort Surface (mirrors plan P2) · Member & Cohort Live (mirrors plan P3) · Education-Platform Integration (mirrors plan P4) · Geographic Expansion (mirrors plan P5). One numbering scheme across all artefacts.
Audience-led IA vs plan’s tier-led targeting
| Plan says | “Lead with in-house through Year 2; pursue law firms opportunistically; add law firms as a deliberate second segment from Year 3 with a partner-level hire.” Tier 1 = GC/CLO/Head of Legal Ops at $500M+ revenue. AL&A is the only firm-side reference. |
| Live site says | Top-level nav has both “In-House Legal Teams” and “Law Firms” given equal weight. Services page has separate sections for each. Fractional Growth Officer (firm-side service) is the lead capability on the homepage today. |
| Scope says | Migration ports both audience hubs as-is. Doesn’t address whether to demote law-firm prominence. |
| Risk | The current site dilutes the in-house pitch by giving law-firms equal real-estate. The plan’s 23/25 segment-fit score for in-house is undermined by the website’s 50/50 framing. |
| Recommend | Decide before Phase 1 IA lock (Week 4): does the migrated site keep audience parity, or do we demote “Law Firms” to a sub-page under About / Services and lead the homepage with in-house? This is a Matthew decision, not a 121 Group decision. If parity is kept (faithful migration), flag it as a known divergence from the plan’s positioning; revisit at the plan’s Year 3 GTM expansion. |
Sub-brand decision deferred — affects /education routing
| Plan says | “The certification arm may operate under a sub-brand (decision deferred to programme launch) — likely ‘The Legal Operations Institute by Everingham Legal’ or equivalent.” |
| Scope says | Education lives at /education on the main domain, treated as just another service. |
| Risk | If the Institute sub-brand activates at Cohort 2 (plan suggests this), we’ll need to decide whether the Education routes migrate to a sister domain (legaloperationsinstitute.com.au) or stay on Everingham Legal with co-branded treatment. Cheaper to plan for it now than retrofit. |
| Recommend | Phase 1 builds Education routes on the main domain. Add to the scope’s “assumptions” that if the sub-brand activates pre-Cohort 2, a domain split adds 2\u20133 days of work (cert-verify URLs, redirect map, brand asset swap). No price impact for Phase 1. |
Gaps in the scope · 4 items
Things the business plan calls out that the scope hasn’t addressed at all yet.
No publication-engine surface — podcast, newsletter, vendor benchmark, maturity self-assessment
Marketing Brief Pillar 1\u20134 specifies a heavy publication cadence: 1 whitepaper / quarter / pillar (= 16/yr at maturity), bi-weekly podcast, weekly LinkedIn long-form, weekly newsletter, annual State of Legal Tech report, annual vendor benchmark report, public maturity self-assessment. The KPI table runs to 100K+ newsletter subs by FY30.
Our scope: a unified /insights blog (good), but no dedicated podcast page, no podcast-platform embed (Sounder/Transistor), no public maturity self-assessment tool, no vendor-benchmark commerce, no State of Legal Tech landing page.
Recommend: add to Phase 1 deliverables: (1) /podcast route with episode template & transcript pages, (2) Substack/Beehiiv newsletter signup embed across the site, (3) placeholder /maturity-assessment route reserved for the public scorecard tool (build deferred to Phase 2). State of Legal Tech is a Phase 4 marketing-engagement deliverable, not a website build.
Vendor-benchmark licensing surface ($50k\u2013$250k p.a. SKU) not scoped
Plan \u00a76 includes “Vendor benchmark licensing · $50k\u2013$250k p.a. · 85%+ gross margin” as a Phase 4 SKU, sold to vendors. Plan \u00a73 also calls vendor-side revenue out as capped at \u226415% of total revenue under the firm’s independence policy.
This needs: (a) a buyer-facing “benchmark report” landing page with gated download for the executive summary & paid-tier purchase for the full data; (b) a public independence policy page; (c) a vendor-side intake page distinct from the buyer-side contact form.
Recommend: add a placeholder /independence-policy page in Phase 1 (footer link, statutory-style copy authored by Matthew). Vendor-side intake + benchmark commerce flow is a Phase 4 add (mirrors plan’s Phase 4 SKU launch). Note this against the Phase 4 scope row in the website document.
Geographic / multi-region readiness
Plan \u00a73 + \u00a74: UK presence Year 3 (named principal), Singapore Year 4, US Year 4\u20135. Cohort pricing varies by region; case-study and audience pages plausibly want regional variants.
Our scope is silent on this. WordPress can handle multi-region (Polylang or WPML or native ‘regions’ CPT), but the IA decision needs to be made before Phase 1 IA lock or it’s a costly retrofit.
Recommend: Phase 1 stays Australia-only (matches plan’s Year 1\u20132). Add “regional architecture” as an explicit Phase 4 deliverable in the scope: regional landing pages under /uk/, /sg/, /us/ with currency & legal-locale variants. Hreflang plumbing & the regional-router is a one-week build at Phase 4 timing.
Marketing stack integrations not enumerated
Plan \u00a78 enumerates the firm’s tech stack: Granola/Otter/Fireflies (capture) · Google Drive (storage) · Claude Projects (retrieval & drafting) · Substack/Beehiiv (newsletter) · Sounder/Transistor (podcast) · Buffer/Sprout (social ops) · Maven (cohorts) · HubSpot (CRM).
Our scope mentions HubSpot. The other 6\u20137 platforms each have a website touch-point: newsletter embed (Substack/Beehiiv), podcast embed (Sounder/Transistor), social feed widget (Buffer), cohort cart (Maven). None are explicitly scoped.
Recommend: add a “Phase 1 integrations” sub-list to the website scope: HubSpot (forms + tracking), Substack/Beehiiv (newsletter signup), podcast platform embed (deferred until podcast goes live but reserved). Maven embed and Buffer feed are Phase 2 / 4 respectively.
Decisions needed before Phase 1 IA lock (Week 4)
Six questions for Matthew. Each one is a pre-build decision; answers reshape the IA workshop deliverable.
/podcast, newsletter signup, placeholder /maturity-assessment?Two questions carry forward to Matthew
Q1 (vocabulary) and Q2 (cohort platform — Maven or equivalent) are now flagged in red on the Scope of Works at §1.1 and will be raised with Matthew by email. Q1 reshapes Phase 1 service-page copy. Q2’s direction is set internally (Phase 3 = Maven-style integration, not custom LMS) — Matthew’s confirmation locks the specific platform choice. The signed Phase 1 fee is unaffected by either answer.