Executive Summary
The website program in one screen — where we are, what to know before reviewing, what happens next, and the whole site one click deep.
Where we are now
Delivering scope: the project brief, the full template and page scope, and the v1 mock-up website experience — the complete architecture, navigable end to end from the sitemap below.
Presented and endorsed. Claudia + Allison (Aug 31): direction endorsed, Figma handoff and Storybook versioning agreed. Shafiq (Sep 1): "important project, do it 100%" — progress over perfection, don't mess up what we have. Nav order updated to Platform → Build → Deploy → Solutions; head-to-head comparisons added to the product-page spec.
Read this first
No color, no design — just content and alignment on "how we do web" moving forward. The mock is deliberately unstyled: it exists to lock structure, templates, and the operating model before any design investment.
Content is directionally accurate but is NOT updated to reflect the latest detail from product and C-level — it needs a full and complete review. Treat copy as placeholder-grade until that review clears; the gates are tracked on the copy registry.
Expected next steps
- Move to v1.2 — discussing the strategy for all pages and templates.
- Define design system versions — stay with the current system vs. enhancements → then move to template design.
- Build the content & keyword map — a clean Sanity export of every live URL, merged with Ahrefs + GSC + paid keyword data, mapped keyword-to-content across every page and section, head terms assigned to all new pages, then the deep directories (blog, resources) reviewed against it.
- Stand up the campaign directory — a hidden noindex home (`/c/`) for paid search, paid social, newsletter, email, and Redis500 ABM pages, plus the first influencer and partner referral campaigns.
- Lock starting-point benchmarks with Reet — the numbers this program will be graded on, before lift claims.
- One naming meeting — Build vs. Solutions vs. "use cases" (Nash + Shafiq + Jeff + Allison); blog surface naming rides along.
- Socialize beyond marketing — keep the wider org informed as waterfall changes land (the blog is a known hot-button).
- Run the five phases against the October window, below.
Decision log
- Sep 1 — Nav order decided: Platform → Build → Deploy → Solutions (ratified with Shafiq; Jeff read-back pending). Mock updates on the next design export.
- Sep 1 — Head-to-head comparison modules added to every product page; Compare rebuilds on the "Redis versus" pattern.
- Sep 1 — Benchmarks gate set: starting-point baselines locked with Reet before any lift claims.
- Sep 1 — Growth Sr Manager backfill JD approved — high-priority req; the seat owns the 6sense MQA/orchestration playbook.
- Aug 31 — Direction endorsed by Claudia + Allison: Figma is the design repository, Storybook is the point of design, waterfall releases over a big launch, human copy on high-visibility pages.
- Open — chapter naming (Build vs. Solutions vs. use cases) and blog surface naming: one meeting, Nash + Shafiq + Jeff + Allison.
The full running log across the whole program lives on Decisions.
The five phases
- Phase 0 · The template system — the 16-template build that carries everything after it.
- Phase 01 · Product & platform — product and platform pages rebuilt show-first, with conversion impossible to miss.
- Phase 02 · Offers & flows — four new offer pages, four existing flows optimized.
- Phase 03 · Destinations — the six traffic-carrying pages rebuilt to convert.
- Phase 04 · Foundations & measurement — redirects, GA4, tracking standards, the LP system, and the build workflow.
The sitemap at a glance
Every page, one click deep — each opens its live mock in a new tab. Full detail on the Sitemap.