Different Hunger

Canonical Components (v18)

L1 · 02 Lead Generation

The Lead Magnet Bundle (Landing + Quiz + Access + LM Content + Delivery Email) + Marketing Website + Dynamic Retargeting + Share to Unlock.

L1 · 02 Lead Generation

Purpose: Build trust and convert attention into leads.

Locked sub-deliverables:

SlugNameKind
l1.lead-gen.lm-bundleLead Magnet Bundlebundle (5 sub-pieces)
l1.lead-gen.marketing-websiteMarketing Websitepage
l1.lead-gen.dynamic-retargetingDynamic Retargetingbundle
l1.lead-gen.share-to-unlockShare to Unlock Reward ↻process

l1.lead-gen.lm-bundle — Lead Magnet Bundle

The most important deliverable. ONE generation call produces 5 coherent sub-pieces:

Sub-pieceWhat it isRenders at
landingOpt-in page · hero + form + trust + preview/<lm-slug>
quizPre-qualification questions · feeds dynamic LM geninline on landing
accessPost-opt-in resources page · embedded LM + conversion CTA/<lm-slug>/access
lm-contentThe deliverable PDF/booklet itself (or dynamic page)Resend attachment / Access embed
lm-delivery-emailResend template that delivers the LMinbox

Bundle instances per brand: one per LM. MCM today has 3:

  • wellness-plan (primary · 9.5/10 locked)
  • resource-guide (warm-traffic variant · just generated)
  • chapter-17 (warm-traffic variant · just generated)

Why a bundle vs. 5 separate deliverables:

  • Shared magnet name, voice, audience, trust signals → coherence guaranteed
  • Drift problem (regenerate one piece, forget the others) → eliminated
  • Two-stage lock applies to the whole bundle at once (copy_locked → hifi_locked)

Quiz placement ([[project_quiz_is_core_to_install]]):

Quiz lives ON the landing page for every brand. Pre-qualifies + fuels flywheel + feeds dynamic LM content gen.

Headline rules per traffic source:

  • cold (paid ad / SEO) → full hook + offer pattern (per canonical landing.md)
  • warm (downstream of About/Resources/email) → simple offer-only with optional credential anchor

Generation flow:

1. Operator/API picks bundle instance (e.g. mcm + resource-guide)
2. lib/install/components.ts → generateLandingVariant({ brand_slug, variant_slug, magnet_name, audience_pain, lm_excerpt, traffic_source, credential_anchor })
3. Loads canonical landing prompt + 2-4 library refs (rated 4-5/5)
4. Extracts patterns from each ref via Claude
5. Fires Claude with shared context + variant override
6. Output writes to brand.config.engine.components[`landing-<variant>`].content_json
   (TODO: migrate to brand.config.engine.bundles.lm-bundle[<variant>])

HIFI rendering (per [[feedback_no_custom_hifi_dev]]):

  • All 5 sub-pieces render through MasterLanding + MasterAccess + MasterDeliveryEmail templates
  • Templates use Aceternity components or approved templates only (no hand-rolled Tailwind)
  • Theme/copy/assets all swap via brand.config.brand_os.theme + content_json — zero hardcoded

l1.lead-gen.marketing-website

Site Architecture (SEO/AEO) · Trust Center (UGC/Press/Case Studies) · Distribution Hooks · Tracking & Pixels.

Refs: [[project_multi_tenant_hostname_routing]] · [[project_staging_domain_pattern]]

Status: spec lock pending. SEO infra checklist exists at root CLAUDE.md Step 0.5 — bring forward to v18.


l1.lead-gen.dynamic-retargeting (bundle)

Nurture 7-Email + Retargeting Ads. Wins back warm visitors who didn't convert.

Sub-pieces: nurture-7-email · retargeting-ads


l1.lead-gen.share-to-unlock

Referral mechanic baked into LM delivery + Resources page. Refer N friends → unlock extended LM access or bonus asset (e.g. full book free).

Refs: [[project_referral_flywheel_first_step]]


Reference rule

Min 2 / Max 4 reviewer-rated 4-5/5 library refs per sub-deliverable. Below 2 = portal flags "needs curation".