git:20260705.acb5571 to git:20260705.a28c4ce

19 added, 19 removed. Audit A to A.

---

name: course-sales-page

- description: Writes the long-form sales page for a paid online course — above-the-fold promise, PAS-to-proof-to-program-to-price section order, value-stack price anchoring, an action-based guarantee, and an FAQ mapped to real objections. Use when a creator says "write my course sales page", "why isn't my course page converting", "how do I present the price", or "what goes in the FAQ". Do NOT use for a general product or SaaS landing page — use landing-page-copy instead — or for the emails that drive traffic to this page — use launch-email-sequence instead.

+ description: Writes the long-form sales page for a paid online course - above-the-fold promise, PAS-to-proof-to-program-to-price section order, value-stack price anchoring, an action-based guarantee, and an FAQ mapped to real objections. Use when a creator says "write my course sales page", "why isn't my course page converting", "how do I present the price", or "what goes in the FAQ". Do NOT use for a general product or SaaS landing page - use landing-page-copy instead - or for the emails that drive traffic to this page - use launch-email-sequence instead.

---

# Course Sales Page

- A course sales page fails one way above all others: it sells the course instead of the transformation — modules, hours of video, and features, when the buyer only cares what their life looks like after. This skill produces the long-form page in the section order that converts cold-to-warm readers, anchors the price with a value stack, and answers objections before the buyer bounces to "maybe later" — which for course launches means never.

+ A course sales page fails one way above all others: it sells the course instead of the transformation - modules, hours of video, and features, when the buyer only cares what their life looks like after. This skill produces the long-form page in the section order that converts cold-to-warm readers, anchors the price with a value stack, and answers objections before the buyer bounces to "maybe later" - which for course launches means never.

This skill runs after course-outline-architect, which supplies the transformation statement and the cut-list bonuses, and alongside launch-email-sequence, which drives the traffic and must quote this page's promise, stack, and guarantee word-for-word. Testimonials arrive over time from community-engagement-playbook; the page ships with what proof exists today and gets stronger every cohort.

Worked example throughout: Dana, a productivity consultant with an 8,000-subscriber list, selling "Notion OS for Consultants" at $297.

## Operating procedure

### Step 1: Collect the inputs

- 1. The transformation statement from course-outline-architect. If it does not exist, stop and build the outline first — a sales page for an undefined transformation is decoration.

+ 1. The transformation statement from course-outline-architect. If it does not exist, stop and build the outline first - a sales page for an undefined transformation is decoration.

2. The module list with milestone names, and the cut-list items destined for the bonus vault.

3. All available proof: student results, client results, the creator's own numbers, screenshots. Label anything unverified as unverified and do not use it.

4. Price, and any payment plan.

5. The top 5 to 7 objections. If unknown, mine replies from the pre-launch runway emails (launch-email-sequence collects these) or ask 5 audience members directly.

### Step 2: Write above the fold

The formula: outcome + timeframe + differentiator, then one subhead of specificity, then the primary call to action. The headline states the after, never the mechanism.

Good/bad pair for Dana:

```

- BAD: "Notion OS for Consultants — 6 modules and 28 video lessons

+ BAD: "Notion OS for Consultants - 6 modules and 28 video lessons

on building your consulting workspace in Notion"

(sells the course: features, format, effort)

- GOOD: "Run your entire consulting practice from one Notion system —

+ GOOD: "Run your entire consulting practice from one Notion system -

and onboard your next client in under a day"

Subhead: "The exact operating system Dana built running a

- productivity consultancy — installed in 6 milestones, about

+ productivity consultancy - installed in 6 milestones, about

4 hours of lessons, working from module one."

(sells the after; the course is just the vehicle)

```

- ### Step 3: Write the body in this order — PAS, proof, program, price, guarantee, FAQ

+ ### Step 3: Write the body in this order - PAS, proof, program, price, guarantee, FAQ

The order is the argument. Do not rearrange it.

1. **Problem.** The before state in the reader's own words: six tools, docs rebuilt from scratch, roughly 5 hours a week lost to admin.

- 2. **Agitate.** The cost of staying: 5 hours a week is over 250 billable hours a year; at Dana's students' typical $150/hour, about $37,500 of unbilled time — plus the client who churned because onboarding felt chaotic. Use real math from the reader's world, never manufactured doom.

+ 2. **Agitate.** The cost of staying: 5 hours a week is over 250 billable hours a year; at Dana's students' typical $150/hour, about $37,500 of unbilled time - plus the client who churned because onboarding felt chaotic. Use real math from the reader's world, never manufactured doom.

3. **Solve.** Introduce the transformation statement from course-outline-architect, near verbatim. Name the mechanism once, then return to outcomes.

4. **Proof.** Results before credentials: student and client outcomes with names and specifics, then Dana's own numbers, then credentials last. Only verified claims.

- 5. **Program.** The modules as milestones — "by the end of Module 2, every lead and proposal lives in one view" — never as a table of contents. One line per module, outcome-phrased.

+ 5. **Program.** The modules as milestones - "by the end of Module 2, every lead and proposal lives in one view" - never as a table of contents. One line per module, outcome-phrased.

6. **Price** with the value stack (Step 4).

7. **Guarantee** (Step 5).

8. **FAQ** (Step 6), then a final call to action restating the promise and the deadline.

### Step 4: Present the price with a value stack

- Never let the price appear before value has been stacked. List each component with an honest standalone value, total it, then present the price against the total. Dana's stack — shared verbatim with launch-email-sequence:

+ Never let the price appear before value has been stacked. List each component with an honest standalone value, total it, then present the price against the total. Dana's stack - shared verbatim with launch-email-sequence:

```

The full Notion OS for Consultants curriculum (6 modules) $997

12 client-ready Notion templates, yours to rebrand $297

Bonus: Notion API automations mini-course $197

Private student community + weekly office hours (1 year) $197

Total value $1,688

Your price $297

```

- Value-stack rules: every line must be defensible (the templates sell separately at $297 — that is a real number, not an invention); total value between 3x and 7x price — under 3x the anchor is weak, over about 7x it reads as fake; 3 to 6 lines, because stacks of ten junk bonuses signal desperation.

+ Value-stack rules: every line must be defensible (the templates sell separately at $297 - that is a real number, not an invention); total value between 3x and 7x price - under 3x the anchor is weak, over about 7x it reads as fake; 3 to 6 lines, because stacks of ten junk bonuses signal desperation.

- ### Step 5: Design the guarantee — 30 days, action-based

+ ### Step 5: Design the guarantee - 30 days, action-based

- The default: a 30-day action-based guarantee. Dana's: "Complete Modules 1 and 2 and build your dashboard. If it hasn't saved you real time within 30 days, email your workspace link for a full refund." Action-based beats no-questions-asked for courses because it filters refund-seeking browsers, pushes buyers into the material (which drives the completion rate this pack designs for — 35 percent or better, against the 10 to 15 percent industry average), and is stronger copy: the creator is betting on the student doing the work. State it plainly; a guarantee buried in small print removes no risk.

+ The default: a 30-day action-based guarantee. Dana's: "Complete Modules 1 and 2 and build your dashboard. If it hasn't saved you real time within 30 days, email your workspace link for a full refund." Action-based beats no-questions-asked for courses because it filters refund-seeking browsers, pushes buyers into the material (which drives the completion rate this pack designs for - 35 percent or better, against the 10 to 15 percent industry average), and is stronger copy: the creator is betting on the student doing the work. State it plainly; a guarantee buried in small print removes no risk.

### Step 6: Map the FAQ to objections

- Each FAQ entry is a named objection wearing a question mask. Cover at minimum: time ("I'm too busy" — cite the 5-12 minute lessons and the 20-minute module-1 quick win), fit ("Will this work for MY niche"), skill ("I'm not technical"), timing ("Can I buy later" — answer honestly with the deadline and what lapses), price ("Why $297"), and access/logistics. 6 to 9 entries; answer each in under 100 words, restating a benefit.

+ Each FAQ entry is a named objection wearing a question mask. Cover at minimum: time ("I'm too busy" - cite the 5-12 minute lessons and the 20-minute module-1 quick win), fit ("Will this work for MY niche"), skill ("I'm not technical"), timing ("Can I buy later" - answer honestly with the deadline and what lapses), price ("Why $297"), and access/logistics. 6 to 9 entries; answer each in under 100 words, restating a benefit.

### Step 7: Assemble from the skeleton

```

- [FILL: HEADLINE — outcome + timeframe + differentiator]

- [FILL: subhead — one line of specificity] [CTA button]

+ [FILL: HEADLINE - outcome + timeframe + differentiator]

+ [FILL: subhead - one line of specificity] [CTA button]

PROBLEM [FILL: before state, reader's words, 2-3 paragraphs]

AGITATE [FILL: cost of staying, real math]

SOLVE [FILL: transformation statement + mechanism, once]

PROOF [FILL: results w/ names -> creator numbers -> credentials]

PROGRAM M1-M[N]: [FILL: one outcome line per module] [CTA]

PRICE [FILL: value stack, 3-6 lines, total 3-7x price]

[FILL: price + payment plan if any]

GUARANTEE [FILL: 30-day action-based, plainly worded]

FAQ [FILL: 6-9 objection-mapped entries]

CLOSE [FILL: restate promise + deadline] [CTA]

```

## Deliverable

- A complete long-form sales page: above-the-fold promise block, PAS opening, proof section using only verified claims, milestone-phrased program section, value-stacked price presentation, a plainly worded 30-day action-based guarantee, and a 6-to-9-entry objection-mapped FAQ — with the promise, stack, and guarantee phrased identically to what launch-email-sequence will quote.

+ A complete long-form sales page: above-the-fold promise block, PAS opening, proof section using only verified claims, milestone-phrased program section, value-stacked price presentation, a plainly worded 30-day action-based guarantee, and a 6-to-9-entry objection-mapped FAQ - with the promise, stack, and guarantee phrased identically to what launch-email-sequence will quote.

## Do NOT

- Do not lead with modules, lesson counts, or hours of video. Features are the vehicle; the reader buys the destination.

- Do not show the price before the value stack. An unanchored $297 is expensive; against a defensible $1,688 it is obvious.

- - Do not inflate stack values past roughly 7x price or pad with junk bonuses — readers smell it and the whole page loses credibility.

+ - Do not inflate stack values past roughly 7x price or pad with junk bonuses - readers smell it and the whole page loses credibility.

- Do not use unverified or composite testimonials, ever. Thin real proof beats thick fake proof, and community-engagement-playbook will supply more each cohort.

- Do not bury the guarantee or hedge it with dense conditions. One action condition, 30 days, full refund.

- Do not write FAQ entries for questions nobody asked while skipping the price and time objections everyone has.

## Quality bar

- The headline passes the "after, not vehicle" test: it would still make sense if the course were delivered by carrier pigeon.

- Sections appear in PAS → proof → program → price → guarantee → FAQ order with a CTA at minimum after the fold, after the program, and at the close.

- Every proof claim is verifiable; every stack line defensible; stack total 3-7x price.

- The guarantee names one action, one window (30 days), one outcome.

- Promise, stack, and guarantee wording matches launch-email-sequence exactly.

## Escalation and routing

- Traffic and the open-cart sequence: launch-email-sequence. A webinar-driven pitch instead of a page-first launch: webinar-funnel-builder. Non-course landing pages: landing-page-copy. Collecting the testimonials this page needs: testimonial-capture-interview, prompted at the harvest moments community-engagement-playbook defines. Income-claim marketing has legal exposure in many jurisdictions — if results claims imply earnings, have counsel review; this is not legal advice.

+ Traffic and the open-cart sequence: launch-email-sequence. A webinar-driven pitch instead of a page-first launch: webinar-funnel-builder. Non-course landing pages: landing-page-copy. Collecting the testimonials this page needs: testimonial-capture-interview, prompted at the harvest moments community-engagement-playbook defines. Income-claim marketing has legal exposure in many jurisdictions - if results claims imply earnings, have counsel review; this is not legal advice.