Source: frameworks/kit-offer-page/01-offer-page-context.md

Context — Offer Page Inputs and Validation

Required Inputs

Every offer page requires a complete inputs set before building. Missing inputs produce pages that don't convert — because the builder has to guess at positioning, proof, or objection handling.

Required Inputs by Category

1. Offer Architecture

Input	Required	Notes
Offer name	Yes	The name that appears on the page
Price point	Yes	Specific dollar amount
Timeline/duration	Yes	How long it takes (for services) or how long to use (for tools)
What's included	Yes	Deliverables, assets, sessions, artifacts
What it's NOT	Yes	Minimum 3 disqualifiers (not coaching, not a course, etc.)

2. Positioning

Input	Required	Notes
Who it's for	Yes	Specific criteria, minimum 3
Who it's NOT for	Yes	Disqualifiers, minimum 3
Primary objections	Yes	Minimum 3 — these become FAQ answers
Key distinction	Yes	What justifies this price vs. cheaper alternatives

3. Transformation Framework

Input	Required	Notes
Symptom	Yes	What they come in with — the surface-level problem
Upstream constraint	Yes	Root cause — why the symptom persists
System/asset built	Yes	What solves it — the thing that gets deployed
Outcome	Yes	Measurable change — what's different after

4. Proof

Input	Required	Notes
At least one testimonial with specific outcome	Yes	Must show transformation, not generic praise
Pull-quote identified	Yes	Strongest single line from any testimonial
Case study or anonymized example	Preferred	Shows the full arc: before → intervention → after

If proof comes from a different product/engagement than the one being sold, include an honest disclaimer. Never imply results came from the product being sold if they didn't.

5. Funnel Context

Input	Required	Notes
Where page sits in buyer journey	Yes	Cold traffic, warm from article, post-audit, etc.
What visitors already know	Yes	What content they've consumed before arriving
Primary CTA + destination URL	Yes	Checkout link or Calendly URL
CTA subtext	Yes	Lowers commitment anxiety (e.g., "60 minutes. No obligation.")

6. Brand & Voice

Input	Required	Notes
Design system	Yes	Default: AOS (charcoal/cream/gold)
Voice/tone constraints	Yes	Direct, pattern-revealing, grounded
Words to avoid	Yes	See vocabulary in terminology file
Do NOT mention items	Conditional	Things that should never appear on this page

7. Technical

Input	Required	Notes
Target platform	Yes	Convertri, standalone HTML, other
CTA destination URL	Yes	The link the button goes to
Analytics/tracking needs	Conditional	Pixel, UTM parameters, etc.

Validation Checklist

Before building, confirm every item below. Any gap stops the build.

[ ] Offer name defined
[ ] Price point confirmed
[ ] At least 3 "who it's for" criteria
[ ] At least 3 "who it's NOT for" criteria
[ ] At least 3 primary objections identified
[ ] Key distinction articulated (what justifies this vs. cheaper)
[ ] Transformation framework complete (symptom → constraint → system → outcome)
[ ] At least 1 testimonial with specific outcome
[ ] Pull-quote selected
[ ] CTA text and destination URL confirmed
[ ] CTA subtext written
[ ] Voice/tone confirmed (default: AOS voice.md)

What the Golden Example Provides

The golden example (File 03) is a styling and structure reference only.

Use it for:

Exact CSS values, spacing, typography
Section order and visual hierarchy
Interactive element patterns (tabs, click-to-reveal, hover states)
Component structure (distinction cards, proof cards, FAQ grid)

Do not use it for:

Copy or content (those come from inputs)
Testimonial text
Offer-specific positioning
Any content that should come from the inputs template