Coach’s Compass relaunch

Why

The Coach’s Compass was Kevin’s most-claimed free product: a 7-day team transformation system for new coaches, built July 2025 as seven GitHub Pages repos under the 360tft org (Day 1 diagnostic through Day 7 transformation plan). Evidence of demand: 210 claims on the Gumroad gate, 157 claimants in hub contacts tagged gumroad:the-coach-s-compass-free, real named testimonials in the FCA Skool thread, and repeat promotion through 2025.

It was pulled from promotion because its CTAs sell the 2025 Gumroad-products world (Game Model, Mastery System, session packs, linktr.ee). But its core message (“Drowning in information and need some concentrated help?”) is the proto-version of the locked brand stance. The content fits TODAY’S strategy better than the funnel it was built for. Full investigation: session 2026-07-25, summarised in memory project_coaches_compass_7day_product_relaunch.md.

What

Domain rule (Kevin, 2026-07-25): hub.360tft.com is NEVER a public-facing URL. Public surfaces live on 360tft.com or 360tft.co.uk, one or the other. 360tft.com apex/www is Gumroad’s custom domain (paths not controllable), so the practical homes are the 360tft.co.uk site (repo 360tft/360tft, GitHub Pages, actively maintained) or a new subdomain of 360tft.com (needs DNS plus hosting, Gate 2.5 impact map first).

Relaunch as ONE consolidated build at 360tft.co.uk/coaches-compass/ (recommended: the product page already lives at that path, day pages nest under it, zero DNS work, established domain already indexed):

• Keep the 7-day structure and the Day 1 interactive team diagnostic (the hook: rating buttons plus deterministic calculateResults scoring, no backend, no runtime LLM). The diagnostic result is the peak moment.
• Restructure the arc so each day still gives standalone value (the compass standard) but routes to the CURRENT lane where a reader would naturally go deeper: FootballGPT signup, the book, free FCA community, The Agentic Coach Substack. One primary CTA per day, no legacy Gumroad packs, no linktr.ee.
• Email capture on Day 1 (after the diagnostic result, not gating it), the form POSTing to a hub API endpoint (backend only, the visitor never sees a hub URL), feeding a hub 7-day drip sequence that delivers one day per email. The seven pages stay directly linkable; the drip is the reason to hand over an email, not a wall.
• Full voice pass to current rules: British English, no emojis in UI, no em dashes, anti-slop, no hype claims (“transform any team in 7 days” goes).
• Analytics on every page (the originals had none, so popularity was never measurable).
• Old GitHub Pages: add a prominent “this has moved” banner linking the new home. Do NOT delete the repos (Kevin decision only).

Scope

In scope: new pages in the 360tft/360tft site repo (public surface); capture API endpoint + drip sequence in the hub (backend only); content rewrite of all 7 days; banner commit to the seven old repos.

Out of scope: deleting or archiving the old repos or the Gumroad listing; any email to the 157 existing tagged contacts (external send needs Kevin’s explicit say, see Open questions); any Stripe/pricing surface; any ACM enrollment/price copy or Summit reference (campaign pause rules); DNS changes (a vanity subdomain would need a Gate 2.5 impact map first).

Open questions (Gate 0)

1. Final home: 360tft.co.uk/coaches-compass/ (recommended, zero DNS) or a new 360tft.com subdomain such as compass.360tft.com (needs DNS + hosting
   • Gate 2.5 impact map)?
2. Old pages: banner only, or hard redirect once the new home is live?
3. Do the 157 existing compass contacts get a relaunch email? (Kevin explicit yes required before any send.)
4. Does the seeded Compass to CoachReflect upsell sequence get repointed at the new funnel or retired?

Expected Experience

• Job: an overwhelmed new coach diagnoses their team’s biggest weakness in 5 minutes and leaves each day with something they can run at training.
• Copy bar: helpful peer voice, value first, product enters only as the means or source (sell without selling).
• Never-list: no fabricated stories or counts, no legacy product CTAs, no off-brand hype, no emojis.
• Proof before Shipped: live 200 on the new URL, a real capture written to contacts, drip sequence firing on a test contact, Kevin review of the rewritten copy (brand-voice surface).

Note (mirrored into this repo 2026-07-25): this PRD is owned and tracked canonically in 360tft-hub/docs/prd/, per the Hub_ prefix and the PRD Naming & Per-Product Queues convention in that repo’s CLAUDE.md. It is copied here only so this repo’s pre-commit Gate 1-3 PRD check has a local artefact to point at, since the implementation (the seven day pages) lives in this repo (360tft/360tft) while the PRD process lives in the hub. Treat the hub copy as the source of truth for status changes.

Honesty artifact

Stated assumptions (decided during implementation, not spelled out in the PRD body above):

• Final home: went with 360tft.co.uk/coaches-compass/day-1/ through /day-7/ (recommended option in “Open questions” #1), zero DNS work.
• CTA mapping per day (PRD says “map naturally,” left to the implementer): Days 1, 2, 4, 5, 7 (diagnostic, emergency sessions, SSG mastery, formation fix, closing day) lead with FootballGPT since they’re session/planning content. Days 3 and 6 (mindset reset, match day confidence) lead with the free Football Coaching Academy community since they’re mindset/community content. Kevin’s X profile appears in the footer of every page. Day 7 closes the loop with all three CTAs plus a link back to the product page.
• Dropped the original drill-diagram images and image-enlarge modal on Days 2, 4, 5, 6 (Day 1 had none). The images lived on 360tft.github.io, a domain this PRD does not authorise editing beyond a “moved” banner, and hotlinking them into the new permanent home felt fragile. The written coaching content (setup, key coaching points, why it works) is preserved in full; only the illustrative photos of hand-drawn diagrams are gone.
• Logo swapped from the old hotlinked 360tft.github.io JPG to the existing local asset /assets/images/logo-360tft.png already used by this site’s header include.
• Reworded three phrases that used “guarantee” or “unlock” in a literal, non-marketing sense (a finishing drill players “can’t fail at,” a winger who “breaks down” defences) to avoid ambiguity against the anti-hype banned-word list, even though the original usage wasn’t a marketing claim.

Known gaps (explicitly out of scope for this PR, per the parent task’s instructions, which override the PRD’s own “in scope” list where they conflict):

• No email capture form on Day 1 and no hub drip-sequence endpoint. The PRD describes this as the intended next step; the hub API decision is still pending, so this PR ships the seven pages only.
• No “this has moved” banner committed to the seven old 360tft/<day-repo> GitHub Pages repos. Those repos are untouched.
• The 157 existing gumroad:the-coach-s-compass-free contacts have not been emailed about the relaunch (needs Kevin’s explicit yes per the PRD’s open question #3).
• No local Jekyll build was run (no ruby/bundle/jekyll on this machine). Verified instead with this repo’s own node scripts/manual-html-validator.js (0 errors, only pre-existing-style warnings shared with the rest of the site) and manual front-matter/ permalink comparison against working pages (first-agent.html, ai-coaching-mastery.html).
• Analytics: checked whether any layout wires up the google_analytics: G-L6CXTTSPV2 value from _config.yml into an actual gtag.js loader script. It does not, anywhere in _includes/ or _layouts/, on ANY page of this site, not just these seven (confirmed by grepping for site.google_analytics and gtag( across every include and layout). This is a pre-existing, site-wide gap that predates this PR, not something specific to the layout: null choice made here (the two other layout: null pages, first-agent.html and ai-coaching-mastery.html, have the same gap). Wiring up analytics correctly means editing a shared include or layout, which this task was explicitly told not to do (“Do not modify the homepage, nav includes, or _config.yml”). Flagging for Kevin rather than silently fixing it: the PRD explicitly calls out “Analytics on every page” as a requirement, and that requirement is currently unmet for the whole site, not just this feature.