[Build] [result one] & [result two] [that run] [their areas of life]

[Name the reader's habit: the thing they keep doing instead of using what they learn.] [One line that ends the habit.] [Your member count, bolded inside the sentence], [then the concrete things they'll build for each part of their life.]

[Join the program] →

[Doors close soon · We start Month D]

[Portrait: warm light, eye contact]

1 · Hero: identification before instruction

What: A three-line display headline with the key words in red, a sub that opens with the reader's habit and bolds the member count, one full-width button, the deadline line, and a full-height portrait (photo first on mobile).
Why: The sub names the reader before it names the product, and proof arrives in the first breath. The face does the trust work that a page with no video has to get from somewhere. No price, no schedule.
Tech: Grid 1.08fr / .92fr; H1 clamp(2.2rem, 3.6vw, 3.5rem), line-height .94; the photo's left edge is feathered with a mask; on mobile the photo moves above the copy (order: -1).

Stat marquee: the format in five words

What: Five red cards scrolling left: length, format, hands-on, people, access.
Why: The "what kind of thing is this?" questions answered before any prose, two words each, in motion.
Tech: One duplicated track, translateX to -50% over 30s; pauses on hover; stops under reduced motion.

[Length]: [the duration, at their pace]
[Format]: [how it is taught]
[Hands-on]: [what they install]
[People]: [who they meet]
[Access]: [how long it is theirs]

2 · What this is: the overview in three paragraphs

What: Three centered paragraphs: your proof of practice, the format, the audience.
Why: It turns the promise into a mechanism (watch, install, keep) and widens the audience so nobody rules themselves out.
Tech: A 780px column, centered lead text at line-height 1.82.

[Your proof of practice: what you run on this yourself, in one sentence.] [Three or four concrete jobs it does for you.] [Over the next N days, you'll show how you built it and hand them what they need to build their own.] [The member count, as proof of the method.]

[The format in one paragraph: the pace, what comes with every lesson, and that they keep what they build.]

[Who it's for, named as the parts of their life it touches.]

3 · The thesis: stakes without pain

What: The big idea in two lines (black caps, then a red italic payoff), the usual failed attempt, and an extra-large condensed promise.
Why: This is the negative-stakes section told as a thesis: the loss is falling behind, and the product is the bridge across the gap.
Tech: A radial red glow at 16% behind the section; the kicker line is Anton caps, clamp(1.9rem, 4.4vw, 3.4rem).

[The thesis, in caps,] [and why it matters now.]

[The usual failed attempt, in their words: the random question, the saved tip, the tool tried for a week, then back to doing it by hand.] [One line that names the gap your program closes.]

[Your one-line promise in condensed caps, ending on the] [payoff words.]

4 · The honest part: permission

What: What you are NOT going to turn them into, why you aren't that either, what they'll build anyway, and a three-beat kicker.
Why: The first objection is "I'm not technical." Lower yourself before you raise the promise.
Tech: Tan band #f6eed2 marks a practical "room"; the italic serif carries the scary word.

[What you won't turn them into:] [the scary word.]

[Lower yourself first: why you are not the expert they fear.] [What they'll build anyway, as four short things.]

[The benefits across career, income and time, in one sentence.]

[Three short beats that hand it to them,] [ending on them.]

5 · The founder story: the teacher's before and after is the demo

What: A sticky portrait beside four paragraphs: where you started, the first fast win, what it runs now (numbers you can prove), the "I'm not a guru" paragraph, and why you built this.
Why: "If they could, I can." The sticky photo keeps a face on screen through a long stretch of text.
Tech: Grid 410px / 1fr, gap 65px; the photo is position: sticky (desktop only).

[Hello line,] [your name.]

[A year ago: where you started, and the part that felt too technical.]

[The first fast win: the job that took days and then took minutes.] [The moment it clicked.] [What it runs for you now, with the numbers you can prove.]

[The part you need them to hear:] [you're not a guru, you learned simple systems, and there's no reason they can't.]

[Why you built this: the messages you kept getting.] [What they walk away with.]

6 · Proof: outcome first, evidence under it

What: The member count in the headline; four result cards (a big red outcome, a one-line caption, a screenshot of the member's own post with the surname blurred); a snap rail of six more; tap to enlarge; the button.
Why: The eye reads the result in display type and the screenshot backs it. Community posts read as unscripted and prove the community exists.
Tech: 2-column grid; a horizontal scroll-snap rail (78vw cards on mobile); the lightbox clones the post at reading size; Esc closes.

[Member count] [members started where they are] [and built the result.]

[Who they were when they started, and what they built inside.] [A line that says the doors are open, with the start date.]

[30+ things built][One sentence: who, what they built, what it changed.]

MA[Member] 2d

[A different kind of result][One sentence: the unexpected use that makes a new reader think "me too."]

FO[Member] 3h

[N tasks in N minutes][One sentence: speed, with the list of what got done.]

ST[Member] 2d

[A surprising use case][One sentence: a profession nobody expects, getting a real result.]

SI[Member] 2d

[More from inside]

ED[Member] 3d

CH[Member] 4h

DE[Member] 1d

KH[Member] 5h

CR[Member] 2d

AL[Member] 6h

[Join the program] →

[Doors close soon · We start Month D]

7 · The package: tangibility and sequence

What: Three numbered cards (the first day, the foundation, the daily builds), each with a kicker, a title, a format line, a body, an arrow list and an outcome line on a red rule.
Why: A month becomes three steps, and each card ends on the result of the step, not its contents. The format line (hours of video) turns effort into value.
Tech: Card grid 120px / 1fr; the number is Anton at clamp(2.8rem, 5vw, 4.4rem); the outcome line is a 3px red left rule.

[What's] [inside.]

[Day 1 · Orientation]

[What they get the moment they join]

[Format · replay]

[What the first video or session covers, and how it sets up a first win early.]

[Covering]

[Topic 1: the roadmap]
[Topic 2: your own use, shown]
[Topic 3: the tools]
[Topic 4: the path from zero]
[Topic 5: using the community]

[You'll leave knowing] [the outcome of this step, in one sentence.]

[Week 1 · the foundation]

[The foundation that makes the rest work]

[5 trainings · 5+ hours]

[Why the foundation matters for beginners and for people who already use the tools.]

[We go deep on]

[Skill 1]
[Skill 2: the tools, named]
[Skill 3]
[Skill 4: the first build]
[Skill 5: checking the work]

[When the week ends] [what they can do now, and the three things they have.]

[Weeks 2 to 4 · the builds]

[The system they build for life, work and business]

[Daily builds · hours of video]

[The daily build: one thing they keep, every day. Name the areas.]

[You will build]

[Build 1]
[Build 2: your own versions of the tools you use]
[Build 3: a personal-life system]
[Build 4: workflows for their job]
[Build 5: the content engine]
[Build 6: new income ideas]
[Build 7: something they ship, like a site or an app]
[Build 8: a live teardown of a real business]

[On the last day] [what they built, and what they can now tackle alone.]

[Join the program] →

[Doors close soon · We start Month D]

8 · How it works: the logistics

What: Four numbered cards: where it lives, the daily rhythm, the build (and the computer they need), the support.
Why: The formula's "how it works," used to pre-answer access, pace, equipment and help. Hers is the one content section with no button.
Tech: 2 x 2 grid of white cards, 14px radius, soft shadow.

[How the days] [actually run]

[Where it lives]

[One place for every lesson, file and the community; any device; theirs to keep.]

[The daily rhythm]

[What unlocks each day, and what comes with it so they build alongside you.]

[The build]

[Every lesson becomes something they use. The equipment they'll need.]

[The support]

[Who answers questions, where, and who else they'll meet.]

9 · The bonuses: value stacking with specifics

What: Ten cards: a badge, a title, a one-line promise, a body, a struck-through value and "included."
Why: Each bonus is a named thing with a price, so the stack feels countable. Tie at least one value to something you really sell and the anchor becomes real.
Tech: Tan band; 2-column grid; the value line is Anton caps with the old price struck.

[The] [bonuses.]

[Why the bonuses exist: they get from a lesson to a finished system faster.]

10 · Add it all up: anchor and choice

What: The value table (core plus bonuses, a total) beside a red price card: pay in full, or split it, two buttons, the deadline. Then a payback line, the refund line and the fine print.
Why: The total sits at the same eye height as the price; two choices make the decision "how," not "whether"; the payback line turns price into one saved afternoon. The price first appears here, 64% of the way down.
Tech: Grid 1.1fr / 1fr; values are data-sample; the buttons read CONFIG.checkoutUrl.

[Add up] [the value.]

[Pay in full]

$297

[One payment, full access, set against the total value.]

[Join the program]

[Or split it]

$160 x 2

[Split in two; identical access.]

[Join the program]

[Doors close soon · We start Month D]

[The payback line: the price, set against one concrete saving they'll feel.]

[Your risk reversal, in one plain sentence, with the date it runs to.]

[Price in full, or N payments of $Y. Subscription or not. What's included, and when they can start.]

11 · The expectation reset: inoculation after the price

What: A "this is not the hype version" headline, a paragraph that predicts early confusion and refuses the big promise, then makes the one promise you will keep.
Why: It pre-empts the week-one wobble that drives refunds, and refusing the big promises makes the small one believable.
Tech: Centered narrow column, kicker line, button.

[This is not a] [hype-version] [program.]

[Predict the early struggle in their words. Refuse the big promise. Then the one promise you will make, if they put in the work.]

[What you give them,] [and what they'll see.]

[Join the program] →

[Doors close soon · We start Month D]

12 · The fit check: qualification as persuasion

What: Two cards: seven "for you if" with red checks and six "not for you if" with grey crosses.
Why: Readers who see themselves in the checks self-select; the crosses push out refund risks and make it feel selective.
Tech: 2-column grid; the "no" card sits on the band color so the "yes" card reads brighter.

[Is this] [for you?]

// [For you if]

[Reader 1: they know it matters but haven't built anything.]
[Reader 2: the parts of life they want it for.]
[Reader 3: they use it, but only one-off.]
[Reader 4: the business owner.]
[Reader 5: the professional who won't get technical.]
[Reader 6: wants step-by-step, not tips.]
[Reader 7: willing to sit at a computer and make things.]

// [Not for you if]

[Not 1: wants a get-rich shortcut.]
[Not 2: wants to watch and never do.]
[Not 3: won't use a computer.]
[Not 4: wants it built for them.]
[Not 5: expects perfection without practice.]
[Not 6: won't practice.]

[Join the program] →

[Doors close soon · We start Month D]

13 · Questions: objections in the buyer's words, after price

What: Eighteen accordions in condensed caps; the "+" turns to an "x."
Why: After the price, the questions are the real ones. Hers carries the refund conditions here, where only a serious reader goes; put yours beside the price instead.
Tech: Native <details> (no JS, keyboard and screen-reader ready); max-width 920px.

[Questions]

14 · The final call: two futures

What: The only red ground: "keep doing it the old way, or start the new way," a two-futures paragraph (the same days either way), a cream button.
Why: The choice is framed as two versions of the same month; the color change makes the close feel like a new room.
Tech: Red ground, cream display caps, the italic payoff word in ink.

[Keep doing it the old way.] [Or start building] [the new way.]

[Two futures, the same N days: where they'll be if nothing changes, and where they'll be if they do this. End with the people who already crossed.]

[Join the program] →

[Doors close soon · We start Month D]

15 · The P.S.: the letter convention

What: Three short paragraphs in your voice, your name, one button and the deadline.
Why: Skimmers read the P.S. It restates the thesis personally and ends on a name and one button.
Tech: Centered 760px column; the sign-off in spaced caps.

// [P.S.]

[The feeling they have right now, named with empathy.]

[What actually separates those who pull ahead: practice, not tools.]

[What you'll do together, and the invitation.]

[YOUR NAME]

[Join the program] →

[Doors close soon · We start Month D]

[BRAND] WITH[NAME]← [Back to details]

Checkout: her own page, email before card

What: Plan cards, then name, then email, then the card, on her domain in her brand, with the countdown on top. The right column keeps selling: the full stack and a price block that follows the plan.
Why: The email is captured before any card is typed, which is what starts the follow-up for anyone who stops. The decision moment still sees the value and the proof.
Tech: Hers: Stripe Elements, deferred intent (the payment field mounts on load; the charge is created on Pay); a Link Authentication Element for the email; a server function fires "Started Checkout." Here: plain inputs and a placeholder, nothing sent.

// [The program]

[Claim your] [seat.]

[Pay in full]$297[One payment, full access.] [Or split it]$160[today, then $160 in 7 days]

[Trust line: encrypted, processed by Stripe, the card never touches your server]

[Your guarantee, in one line.] [The terms, plainly, with the date.]

Event log (teardown only)
[Type a name and a valid email: the started-checkout event fires once, the way hers does.]

[Here's] [everything] [you get.]

[One line: the access, and the total value it sits against.]

[Your price today]

$297

[vs the total value]

[One-line reason to act today]

Checkout proof: three fast credibility signals

What: Three result cards under the form, then a one-line close, then a full proof wall.
Why: Doubt peaks at the card field; the proof sits exactly there.
Tech: 3-column grid; the wall is CSS columns; every post opens in the lightbox.

// [N people · the transformation]

[Proof headline,] [the result half.]

[One line: how many have been through it, and what they came out doing.]

// [one-line motto]

[Closing promise with one] [hot word.]

[Two sentences: the reps, the pace, the result.]

// [real people · real builds]

[Wall headline,] [the payoff.]

[One line: these are members' own posts.]

Success: confirm, never grant

What: "You're in," a celebration image, what's ready now, which inbox to watch, and a state line. Three states: paid, processing, not completed.
Why: The buyer's first worry is "did it work, and where do I go?" Access is provisioned by a verified webhook, never by visiting this page.
Tech: Hers echoes the email from the URL (and Stripe appends the payment secret beside it). Ours reads the email from this browser session, so no URL ever holds it.

[The program]

[You're in.]

[Celebration image]

[Payment confirmed. What is ready for them right now.]

[Band eyebrow]

[What starts now]

[Watch for the community invitation, then begin.]

What happens next: name the sender, warn about spam

What: Two lines (the email that's coming and who sends it; the support address) and a boxed spam warning. A note for the two-payment plan.
Why: A buyer who can't find the access email becomes a refund or a support ticket.
Tech: Hers keeps the countdown and a Join button on this page: set CONFIG.salesChromeOnSuccess to false in a real build. Add a calendar link for the first live session.

[What happens next]

[Email 1: what arrives, from whom, and when.]
[Questions: the support address.]

⚠ [Check the other folders first][Where the access email tends to land, and the one step that keeps the next one out of there.]