Skip to content

Prototype alt redesign: FAQ debunks, 3-tier pricing, engagement path#1

Draft
ZylkaGreger wants to merge 1 commit into
mainfrom
alt/redesign-2026
Draft

Prototype alt redesign: FAQ debunks, 3-tier pricing, engagement path#1
ZylkaGreger wants to merge 1 commit into
mainfrom
alt/redesign-2026

Conversation

@ZylkaGreger
Copy link
Copy Markdown
Collaborator

Draft / for review only — not for merge yet.

Alternative version of the site for comparison against main. Builds locally with npm run dev.

What's in here

  1. New FAQ on the Lighthouse page (after testimonials) — nine assumption-debunk pairs covering the objections we hear most: "I need lots of data", "IT will block it", "I'm just an SM", "tried it before", etc. — plus an honest "Is this even for me?" section that calls out who Lighthouse is not for.

  2. New 3-tier Lighthouse pricing reflecting the 2026-05-22 decision:

    • Community (free, capped, unchanged)
    • Self-Service — CHF 2,000/yr (full product, community Slack, ideas.letpeople.work, best-effort help)
    • Enterprise — CHF 10,000/yr (prioritised support, 24h ack, 2×60-min onboarding, named contacts, 10% workshop discount)
    • Pre-launch bridge notice for existing CHF 999 customers above the cards
    • Feature comparison rebuilt as a 4-column data-driven table (also fixes a pre-existing nested <tr> bug for Blackout Days)
    • Self-Service framing is positive (no "what you don't get" list)
  3. Services restructured as a 3-tier engagement path (Assess → Implement → Transform) inspired by nwave.ai/solutions#how-we-help. Implement carries the "Recommended" badge. Full training catalogue retained below.

  4. Apple-style visual direction — bigger display typography, restrained colour (teal as accent, not background fill), full-bleed sections, scroll-driven reveals via a new useScrollReveal hook. Teal palette retained; no new design tokens.

What I need from Benjamin specifically

  • Sign-off on the 10% workshop discount as an Enterprise perk (your proposal from 2026-05-25)
  • Sanity-check the Enterprise framing — you're listed as the technical named contact alongside Peter on coaching/flow
  • Confirm the DPA wording for self-hosted is sufficient as written, or send a corrected version
  • Flag anything that feels off about the Self-Service framing — we deliberately avoided a "what you don't get" list

Open items deferred

  • Final tier headline wording on EngagementPath (placeholder + TODO(peter) comment in code — Peter to draft 3–5 candidates)
  • Substack channel viability for the essay — not blocking this branch
  • JLP (#60) outreach window — operational
  • Stripe price update (server-side in supabase function create-payment) — out of scope for this branch; display-only changes here

Test plan

  • npm install && npm run dev — visit / and /lighthouse
  • Walk through Hero → HowItWorks → EngagementPath → full catalogue → Lighthouse pricing → Lighthouse license sections
  • Open the FAQ accordions on the Lighthouse page — verify all nine read well
  • Check mobile (≤640px) rendering of the 3-tier pricing cards and engagement path
  • Compare against main deployed at letpeople.work to evaluate visual direction

Alternative branch (not for merge yet) for stakeholder review against main.

- Add 9-question FAQ on Lighthouse page that debunks adoption objections
  (data volume, IT blocking, maturity, management buy-in, etc.) including
  honest "not for you" entry
- Restructure Lighthouse pricing to 3 tiers reflecting 2026-05-22 decision:
  Community (free) / Self-Service (CHF 2,000) / Enterprise (CHF 10,000),
  with pre-launch bridge notice for existing CHF 999 customers
- Replace flat services menu with 3-tier engagement path (Assess → Implement
  → Transform), inspired by nwave.ai. Full training catalogue retained below.
- Apple-style polish pass: larger display typography, restrained colour,
  full-bleed sections, scroll-driven reveals via useScrollReveal hook
- Fix pre-existing nested <tr> bug in feature comparison table; rebuild
  table as data-driven 4-column comparison
- Update JSON-LD structured data on Index + Lighthouse pages to reflect
  the new tiering
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.

1 participant