Module 5: The sales page
Your sales page does the selling while you sleep. This module covers the structure that converts browsers into buyers.
The anatomy of a converting sales page
Follow this order: headline (the outcome, specific), subheadline (who it's for + the mechanism), the problem (agitate the pain in their words — from your Module 2 conversations), the solution (your product as the bridge), what's inside (module-by-module breakdown with benefit bullets), testimonials and proof, the offer stack (everything they get, with values), price with guarantee, FAQ (every objection answered), final call to action. This structure is battle-tested because it mirrors how buyers decide.
One page, one job: the buy button. Remove navigation menus, sidebar links, and anything that leads away. Every element either builds desire or removes friction; everything else is clutter. Read the page on your phone before launch — most buyers will.
Write the headline last, not first. Once the whole page exists, the sharpest promise usually reveals itself — and it's often a buyer's phrase from your conversations, not your cleverest line. Test two headlines if you can: the specific-outcome version vs. the pain-agitation version. The winner usually surprises you, which is exactly why you test.
Where should your strongest testimonial go?
SALES PAGE OUTLINE
HEADLINE: [outcome] for [who] — without [pain]
SUBHEAD: How it works in one sentence
PROOF: 3 testimonials with specific results
WHAT'S INSIDE: module-by-module, outcome per module
WHO IT'S FOR / NOT FOR: be honest, it builds trust
PRICE + GUARANTEE: tiers, then risk reversal
FAQ: answer the 5 objections that kill sales
CTA: one button, repeated 3x
Leading with features ("12 modules, 8 hours of video, 40 worksheets"). Nobody buys features — they buy the outcome. "12 modules" is inventory; "book your first 3 clients in 30 days" is a reason to pay. Translate every feature into the result it produces before it earns a spot on the page.
The anatomy of a converting sales page
Headline
The outcome, specific.
Subheadline
Who it's for + the mechanism.
The problem
Agitate the pain in their words.
The solution
Your product as the bridge.
What's inside
Module-by-module breakdown with benefit bullets.
Testimonials and proof
Buyers don't trust promises; they trust proof.
The offer stack
Everything they get, with values.
Price with guarantee
The last thing a buyer reads should be risk reversal, not risk.
FAQ
Answer every objection explicitly.
Final call to action
One page, one job: the buy button.
Build brief
Write the painful problem your buyer has in their own words — what would they type into Google at 11pm?
Saved
Proof: testimonials, numbers, and your story
Buyers don't trust promises; they trust proof. Collect testimonials from beta users with this format: their situation before, what they did, the specific result after. "I was stuck at $3k months; after the pricing module I raised rates and closed two $8k projects in six weeks" outsells ten "great course!" quotes. Ask for specifics — vague praise is decoration.
No buyers yet? Use your own results and client results (with permission): "I've used this exact process with 40 clients." Screenshots of real outcomes — revenue dashboards, before/after work, completed projects — beat adjectives. And tell your story briefly: why you're the person to teach this. Credentials matter less than relevance — "I solved this problem 200 times" beats any certificate.
Place the strongest proof near the price, where doubt peaks. Testimonials scattered through the page keep belief high all the way down; a single testimonial section at the bottom gets skipped.
Video testimonials outperform text when you can get them — even 30 seconds on a phone. But a text testimonial with a full name, photo, and specific numbers beats an anonymous video every time. Specificity is the currency of belief: "I made $4,200 in my first month" persuades; "this changed my life!" doesn't. Always ask permission before publishing, and make it easy by drafting the testimonial from their results for their approval.
Maya's sales page gets 2,000 visitors a month and zero sales. Her $297 product page lists features for three paragraphs, shows no testimonials, and never mentions a guarantee. What should she fix first?
Build brief
What proof do you have — or could you gather in the next 30 days — that your method works? Think results, testimonials, or your own story.
Saved
FAQs that close the sale
Your FAQ isn't an afterthought — it's where fence-sitters decide. Answer every objection explicitly: "How much time does it take?" "What if I'm a beginner?" "How is this different from [competitor/free YouTube]?" "What if it doesn't work for me?" (→ the guarantee). "How do I access it?" "How long do I have access?" Write each answer to dissolve the specific fear behind the question.
The "different from free content" question deserves care: free content is scattered, unorganized, and unaccountable; your product is a sequenced path with support and a proven outcome. Say so plainly. People pay for curation, sequence, and accountability — not just information.
After launch, your FAQ becomes a living document: every support question that starts with "does it cover..." or "what if I..." is a missing FAQ entry. Update it monthly. A FAQ that answers real buyer questions — in their words — quietly lifts conversion for every future visitor without you touching anything else on the page.
Draft 10 headlines that promise a specific outcome for a specific person. Don't write the page yet — the headline is the page. Pick the one you'd click.
Your turn: Draft your headline and subheadline using your buyers' exact words from validation conversations — outcome first, no jargon.
Saved.