← Vault Index
Source: frameworks/kit-thank-you-page/01-thank-you-page-context.md

01 — CONTEXT: Thank-You Page

Input definitions, validation rules, and what each mode requires.


Mode 1 Inputs — Create Thank-You Page

InputRequiredExampleUsed For
Lead magnet nameYes"Client Intelligence Brief"Confirmation headline, body copy
Lead magnet delivery methodYes"Email with download link" or "Instant download"Confirmation copy — tells them where to find it
Lead magnet one-line descriptionYes"AI skill file + quick-start guide for client call prep"Confirmation section context
Next offer nameYes"The Build"Pitch section headline and body
Next offer one-line pitchYes"3-session live event where you install three AI skills on your computer"Pitch section lead copy
Next offer detailsYesSessions/modules, what they walk away with, dates, price, formatPitch section content — sessions list, deliverables, details card
Next offer CTA URLYeshttps://thepracticebuilders.ai/the-buildCTA button destination
Next offer CTA textYes"Learn More About The Build"CTA button label
Next offer priceYes"$47"Details card
Next offer pricing contextNo"Launch pricing (returns to $97 after April 22)"Details card subtext. Use "Launch pricing" — not "founding cohort," "early bird," or "beta."
Brand variantYes"CYP" or "AOS"Determines color palette, fonts, logo, footer entity
Header CTA URLNoSame as next offer CTA URLHeader button link (defaults to next offer CTA URL)
Header CTA textNo"Join The Build"Header button label
Reassurance lineNo"You keep everything you build. No subscription. No platform lock-in."Below CTA — addresses hesitation
Bottom noteNo"Works with any large language model."Below reassurance, separated by rule

Validation Rules — Mode 1

  1. Lead magnet name must be spelled out in full. No acronyms in customer-facing copy. "Client Intelligence Brief" — not "CIB."
  2. Next offer must have a live URL. The CTA button links to an existing page. Do not build a thank-you page for an offer that has no destination.
  3. Brand variant must be specified. CYP uses Fraunces + Montserrat, deep teal palette, Practice Builders branding. AOS uses Cormorant Garamond + Inter, charcoal palette, Advisory OS branding. No hybrid.
  4. Price must be a real number. No "TBD" or "coming soon" — the price appears on the page.
  5. "Launch pricing" is the only acceptable urgency framing. Not "founding cohort," "early bird," "beta pricing," or "introductory rate."
  6. No scroll-reveal animations. Pages are static HTML with hover states only.
  7. No CSS var() in final output. Every color value hardcoded as hex. Inline styles throughout.

Mode 2 Inputs — Improve This Kit

InputRequiredSourceUsed For
Kit locationYescontent/frameworks/kit-thank-you-page/Which kit to improve
TriggerYesOne of: QC failure, manual output changes, system suggestionDetermines which files to update
Updated outputIf applicableThe corrected or improved HTML fileReplaces file 03 (golden example)
QC findingsIf applicableSpecific checklist items that failed or were missingUpdates file 04 (quality)
Process changesIf applicableSteps that were wrong, missing, or in wrong orderUpdates file 05 (output skill)

Validation Rules — Mode 2

  1. Always read the current kit files before making changes. Never update blindly.
  2. Changes propagate. If you update the golden example, check whether the output skill and quality checklist still match.
  3. Never remove a quality check without a reason. Quality checks accumulate — they represent lessons learned.
  4. Document what changed and why. Add at the bottom of HTML files, or a ## Change Log section for markdown files.

Input Priority Hierarchy

When inputs conflict or are ambiguous:

  1. The golden example wins for structure, format, and visual patterns
  2. Kathryn's description wins for audience, purpose, and content
  3. Brand reference files win for colors, fonts, and design tokens
  4. Voice reference wins for tone, vocabulary, and copy patterns
  5. Compliance files win for footer disclaimers and FTC/Meta language

Brand Variant Reference

CYP (Creating Your Plan / Practice Builders)

ElementValue
Primary background#0f2d3e (Deep Teal)
Gradient#0f2d3e → #3e666e (Deep Teal → Slate Teal)
Light background#f1ede6 (Cream)
Text on dark#f1ede6 (Cream)
Text on light#334155 (Slate)
Muted text#64748b (Muted Slate)
Gold accent#b79d64
Heading fontFraunces, serif
Body fontMontserrat, sans-serif
LogoPractice Builders icon (white)
Footer entity"Practice Builders is a brand of Creating Your Plan"
Emailkathryn@creatingyourplan.com
Domainthepracticebuilders.ai

AOS (Advisory OS)

ElementValue
Primary background#1a1a1a (Charcoal)
Gradient#1a1a1a → #0f0f0f (Charcoal → Deep Black)
Light background#f5f4f0 (Cream)
Text on dark#f5f4f0 (Cream)
Text on light#4a5a6a (Slate Blue)
Muted text#8a8680 (Stone)
Gold accent#b79d64
Heading fontCormorant Garamond, serif
Body fontInter, sans-serif
LogoAdvisory OS
Footer entity"Advisory OS"
Emailkathryn@advisoryos.ai
Domainadvisoryos.ai

Gold (#b79d64) is shared across both brands. It is the one constant.


External QC Dependencies

FileWhen to RunWhat It Catches
business-aos/reference/brand/copy-qc.mdAfter writing all copy, before final buildAI-generated language patterns (twinning, three-beat lists, mirror reversals, etc.)
business-aos/reference/core/voice.mdWhile writing copyVocabulary, tone, cadence — the "would Kathryn say this?" test
vip/.claude/lenses/ftc-compliance.mdAfter writing pitch sectionIncome claims, false scarcity, endorsement rules
vip/.claude/lenses/meta-policy.mdAfter final buildMeta ad policy compliance for pages that receive paid traffic