Write Your Landing Page Copy

Build a high-converting landing page using a proven structure. Use AI to draft each section, then edit for voice and clarity.

Why This Matters

Your landing page is the only piece of marketing that every potential customer will see. Traffic from SEO, social, cold outreach, and word of mouth all converge here. It either converts or it doesn't.

Most landing pages fail for one of three reasons:

They talk about features instead of outcomes
They're written for the founder, not the buyer
They try to say too much

A good landing page has one job: get the right visitor to take the next step. Everything on the page should serve that job or be cut.

You're not designing the page today (that's the CTO's job). You're writing the copy. Clean copy is the foundation — design enhances it, but design cannot save bad copy.

The 7-Section Landing Page Structure

This is the battle-tested structure for a conversion-optimized SaaS landing page:

Hero — headline, subheadline, CTA, optional hero image
Problem — articulate the pain in the buyer's language
Solution — how you solve it (not what the product does — what the customer gets)
Social Proof — testimonials, logos, metrics
Features — the specific capabilities, framed as outcomes
Pricing — clear, simple, 3 tiers
CTA — final push + risk reversal (free trial, money-back guarantee)

This isn't the only structure that works, but it's where you should start. You can iterate from here.

Section 1: Hero

The hero is the most important section. Visitors decide in 3 seconds whether to keep reading.

What the hero must do:

Answer "what is this?" immediately
Tell the visitor if it's for them
Give them a reason to keep reading

Structure:

Headline: 6-12 words, outcome-focused
Subheadline: 20-30 words, who it's for and how it works
CTA: 2-5 words, tells them exactly what to do
Optional: Hero image / product screenshot

Use Pixola.ai to generate your hero image or product visualization if you don't have screenshots ready.

Write 5 hero sections for [product].

Target buyer: [ICP description]
Value proposition: [your value prop]
Key differentiator: [what makes you different]
Primary CTA action: [free trial / get access / see demo]

For each hero section:
- Headline (6-12 words, outcome-focused, buyer's language)
- Subheadline (20-30 words, who it's for + how it works)
- CTA button text (2-5 words)
- CTA supporting line (10-15 words, risk reversal or reinforcement)

Avoid: "revolutionary," "game-changing," "AI-powered," vague benefits, jargon.

Pick the one that best matches your ICP research and positioning.

Section 2: Problem

Most landing pages skip the problem section. This is a mistake — buyers need to feel understood before they'll believe you can help them.

The problem section creates emotional resonance: "They get it. They understand what I'm dealing with."

What to include:

The specific, named frustration (not "marketing is hard")
The hidden cost of the status quo (what are they losing by not solving this?)
The faulty assumption that created the problem ("You were told that X would work, but...")

Write a problem section for [product]'s landing page.

The specific problem: [describe it precisely]
The status quo they're using: [what do they do today?]
What that costs them: [time, money, stress, missed opportunity]
The false promise they've been given: [what did they try that didn't work?]

Write this in second person ("You've probably tried..."). 150-200 words.
Mirror the language my ICP uses: [paste 5-10 phrases from community research]

Section 3: Solution

The solution section is not a feature list. It's the transformation — where the buyer is now vs. where they'll be with your product.

Format that works:

Before: [their current state — frustrating, inefficient, expensive] After: [their future state — the outcome your product delivers]

Then: how do you get them there? (3-5 high-level points, each framed as an outcome)

Write a solution section for [product]'s landing page.

Current state (before): [describe their painful reality]
Future state (after): [describe life with your product working]

The 3-5 key things we do to get them from before to after:
1. [step/capability + what it means for them]
2. [step/capability + what it means for them]
3. [step/capability + what it means for them]

Write this in 200-250 words. Lead with the transformation, not the product.

Section 4: Social Proof

Buyers don't trust companies. They trust other buyers. Social proof is the bridge between your claims and their belief.

Types of proof, in order of strength:

Specific outcome testimonials — "We cut our content production time by 60%"
Named testimonials with photo and role — more credible than anonymous
Company logos — "Trusted by X, Y, Z"
Metrics — "X customers / Y articles published / Z% average improvement"

If you don't have testimonials yet:

Ask your beta users / early access people for a quote
Use usage statistics instead ("X articles generated in beta")
Use the logos of companies your users work at (with permission)

I don't have testimonials yet, but I have these beta users:
[describe who's used your product, what they said informally]

Help me:
1. Write 3 testimonial request emails to send to beta users
2. Draft 2 "placeholder proof" concepts using the data I do have
3. Write a social proof section that uses metrics instead of testimonials until I have real ones

Available metrics: [whatever you have — signups, usage stats, beta feedback]

Section 5: Features

This is where you get specific. Features should be framed as what the buyer can do, not what the product has.

Feature framing:

Bad: "AI-powered content generation"
Good: "Go from keyword to published post in under an hour — with SEO scoring built in"

Each feature point should answer: "So what? What does this let me do that I couldn't before?"

Write a features section for [product]'s landing page.

My product's key capabilities:
[list features]

For each capability, write:
- Feature name (3-5 words, benefit-framed)
- Feature description (20-30 words, outcome-focused)
- Optional: proof point or example

Target buyer: [ICP]
Tone: direct, specific, no marketing fluff.

Avoid: "powerful," "robust," "seamless," "cutting-edge," "best-in-class"

Section 6: Pricing (Summary on Landing Page)

Your full pricing page is separate, but your landing page should include a condensed pricing section with your 3 tiers and CTAs.

Use the copy you wrote in the Pricing Strategy guide. Add:

A headline for the pricing section (not just "Pricing")
Emphasis on the Pro tier (your target)
Annual discount call-out
FAQ link or top 1-2 FAQ answers inline

Section 7: Final CTA

The final CTA section is your closing argument. Buyers who've read this far are interested — help them take the step.

What to include:

Restate the primary promise (echo the hero)
Risk reversal (free trial, money-back guarantee, no credit card)
Urgency if you have it (launch pricing, limited beta spots)
The CTA

Write a closing CTA section for [product]'s landing page.

Primary promise: [value prop]
Risk reversal: [free trial / money-back / no credit card]
CTA: [primary action]

Write 3 versions:
1. Urgency-focused (for launch period)
2. Confidence-focused (long-term default)
3. Question-focused (starts with a question that primes the CTA)

Each version: 50-75 words + headline + CTA button.

Assembling the Full Page

Once you have all sections drafted, assemble them and review the flow. Use FastWrite to run a brand voice check across the full page copy — your hero shouldn't sound corporate if your problem section sounds conversational.

Final check:

Does the page answer "what is this?" in 3 seconds?
Is it clear who it's for?
Is every benefit specific and outcome-focused?
Is social proof present?
Are there CTAs at hero, after features, and at the bottom?
Does the copy sound like a human founder, not a marketing robot?

Deliverable

One markdown file: landing-page-copy.md

Structured with all 7 sections, each labeled. This is your copy brief for the engineer building the page.

What's Next

With your landing page copy drafted, move to Define Your Brand Voice — so every subsequent piece of content sounds like you.