Skip to content

feat(marketing): /validation page (Track 3) - buyer-readable benchmark memo#20

Merged
ptengelmann merged 1 commit into
mainfrom
feat/marketing-validation-page
Jun 27, 2026
Merged

feat(marketing): /validation page (Track 3) - buyer-readable benchmark memo#20
ptengelmann merged 1 commit into
mainfrom
feat/marketing-validation-page

Conversation

@ptengelmann

Copy link
Copy Markdown
Owner

Summary

Track 3 of the GPT review: a single-page validation memo for partners and COLPs evaluating Interfluo. Pulls the BASELINES.md summary into buyer-readable form with the caveats prominent rather than buried. The asset GPT recommended for booking the first real review session.

Page structure (apps/marketing/src/app/validation/page.tsx)

  1. Hero claim + caveat line: "Internal validation. Not a substitute for fee-earner review."
  2. What we tested - one paragraph on the methodology.
  3. Headline numbers - 5 stat cards (9/9 scenarios, 40/40 signals, 33/33 codes, 0/8 over-flags, 98/100 average).
  4. Per-scenario results - all 9 scenarios with humanised names, one-line description, score, EXCELLENT verdict pill, regression note. Editorial numbered layout matching the FAQ section.
  5. What the Matter Quality Score measures - the 4 weighted components with explanations.
  6. What we do not claim - explicit caveat block in a callout style. Four caveats: not legal advice, internal corpus not market data, fee-earner remains responsible, citation grounding does not replace reading the source.
  7. Next step - section pivoting to the real ask. CTA: "Book a review session" linking to /pilot.
  8. Footnote - link to BASELINES.md for methodology + last validated date.

Linking

  • Validation entry added to the footer's Product nav group.
  • Trust section gains a discreet "see the validation memo" link under the four trust cards.
  • NOT added to the primary nav (keeps the site restrained; the page is for evaluators, not casual visitors).

Design decisions (per the two judgement calls confirmed)

  • Tone: memo-formal. Matches the rest of the brand (Hanken Grotesk body, Instrument Serif display, Ink on Paper).
  • Scenario names: humanised. "Active enforcement notice + undisclosed occupier" rather than freehold-enforcement-and-undisclosed-occupier. Better for the partner reader; the raw scenario IDs remain in BASELINES.md for engineers.

What this PR does NOT do

  • No new marketing claims beyond what BASELINES.md already supports. Every number on the page (9/9, 40/40, 33/33, 0/8, 98/100) is grep-verifiable.
  • No shareable matter links / external reviewer workflow. Per the GPT note: "Do not overbuild the review workflow before one human has reacted to the product. For the first conveyancer review, just do screen share + controlled walkthrough." This page is the front door for that conversation, nothing more.
  • No new bench scenarios. Track 2 deferred until after the first real review tells us what to build next.

Test plan

  • pnpm typecheck - 9/9 workspaces pass
  • pnpm check - 0 errors, 3 pre-existing warnings (2 files auto-fixed for import ordering)
  • pnpm build - 3/3 tasks pass
  • Dev server returns 200 on /validation
  • Footer "Validation" link navigates correctly
  • Trust section "see the validation memo" link navigates correctly
  • No em-dashes; no §; UK English throughout
  • CTA to /pilot uses the standard h-10 pill + chip button pattern

Brand and liability check

  • Uses brand tokens, UK English, no emoji, no hype
  • Caveats prominent in their own callout section, not buried in fine print
  • "Internal validation. Not a substitute for fee-earner review." appears in the hero AND in the dedicated caveats section
  • CTA is to book a review session, not "try the product" - matches the GPT framing of the next milestone

Moat level

L7 - the validation memo is the artefact you send a prospect before booking a review. Without it, the moat work is invisible to buyers. With it, the proprietary calibration / taxonomy / scorer work has a single URL that summarises the position honestly.

…k memo

A single-page validation memo for partners and COLPs evaluating Interfluo.
Pulls the BASELINES.md summary into buyer-readable form with the
caveats prominent rather than buried.

Page structure (apps/marketing/src/app/validation/page.tsx):

  1. Hero claim + caveat line: "Internal validation. Not a substitute
     for fee-earner review."
  2. What we tested - one paragraph on the methodology.
  3. Headline numbers - 5 stat cards (9/9 scenarios, 40/40 signals,
     33/33 codes, 0/8 over-flags, 98/100 average).
  4. Per-scenario results - all 9 scenarios with humanised names,
     one-line description, score, EXCELLENT verdict pill, regression
     note. Editorial numbered layout matching the FAQ section.
  5. What the Matter Quality Score measures - the 4 weighted components
     with explanations.
  6. What we do not claim - explicit caveat block in a callout style.
  7. Next step - section pivoting to the real ask: "the benchmark is
     internal. The next validation is one fee-earner." CTA links to
     /pilot.
  8. Footnote: link to BASELINES.md for full methodology + last
     validated date.

Tone: memo-formal (matches the rest of the brand). Names: humanised
(matches buyer-readability goal). Brand tokens unchanged.

Linking:
- Added "Validation" entry in the footer's Product nav group.
- Trust section gains a discreet "see the validation memo" link under
  the four trust cards.
- NOT added to the primary nav (keeps the brand restrained).

Per the GPT review's strategic framing: this page is the asset that
turns "we have benched it internally" into "we have a memo to send a
prospect before booking a 30-minute review session". The page itself
makes no claim that is not already in BASELINES.md.

Cost: zero API calls. Pure marketing surface.

Refs: GPT external review of v3 bench, Track 3.
@ptengelmann
ptengelmann merged commit 3d6f392 into main Jun 27, 2026
1 check passed
@ptengelmann
ptengelmann deleted the feat/marketing-validation-page branch June 27, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants