Assumed audience
- Reading level: comfortable writing prose; new to writing copy that sells.
- Background: understands audience, tone, and voice as general writing concepts.
- Goal: learn to write headlines and value propositions that earn readers’ attention and give them a reason to act.
The headline’s job
A headline has one job: earn the reader’s next second of attention. Not their commitment, not their money, not their email address — just one more second. Everything else in the copy depends on that second.
David Ogilvy put the stakes simply: on average, five times as many people read the headline as read the body copy [@ogilvy1983]. This means that when you’ve written your headline, you’ve spent eighty cents of your dollar. If the headline fails, nothing else matters — the reader is gone.
This is true on landing pages, in email subject lines, in blog post titles, in social media posts, and in ad copy. The format changes; the principle doesn’t.
Features versus benefits
The most important distinction in copywriting is between features and benefits:
- A feature describes the product. “256GB solid-state drive.” “24/7 customer support.” “Built with React.”
- A benefit describes what the product does for the reader. “Your laptop starts in 3 seconds.” “Get help whenever you need it.” “Pages load instantly.”
Features are about the product. Benefits are about the reader. Headlines that state features attract the reader’s intellect; headlines that state benefits attract their self-interest. Self-interest wins.
The translation from feature to benefit follows a simple structure: take the feature, ask “so what?” and answer from the reader’s perspective.
| Feature | ”So what?” | Benefit |
|---|---|---|
| 500GB cloud storage | The reader never runs out of space | ”Never lose a file again” |
| Same-day delivery | The reader gets what they need now | ”Order by noon, have it tonight” |
| End-to-end encryption | The reader’s data is private | ”Your conversations stay between you” |
Not every feature has a compelling benefit. Features that don’t translate into something the reader cares about should stay in the spec sheet, not the headline.
Four headline structures
Most effective headlines follow one of four patterns:
1. The benefit headline. States what the reader gets. “Save 3 hours a week on email.” This is the most direct form and often the most effective. It works when the benefit is concrete and the reader recognizes the problem.
2. The curiosity headline. Opens a question the reader wants answered. “The mistake 90% of startups make with their pricing page.” This works when the reader’s curiosity is genuine — when they actually want to know the answer. It fails when the curiosity is manufactured and the body doesn’t deliver (the “clickbait” failure).
3. The how-to headline. Promises instruction. “How to write a landing page that converts at 5%.” This works for educational content and products that solve skill gaps. It combines benefit (the result) with method (how to get there).
4. The proof headline. Leads with evidence. “10,000 teams switched to [Product] last year.” This works when the proof is striking enough to imply the benefit — if 10,000 teams switched, there must be a reason worth knowing.
The value proposition
The value proposition is the headline expanded into a promise: what the reader gets, why it matters, and why this offer rather than alternatives.
A value proposition has three components:
- What — the concrete thing the reader receives.
- Why it matters — the problem it solves or the improvement it creates.
- Why this — the differentiation from alternatives.
Test your value proposition with the “so what?” and “says who?” challenges. If a reader can respond “so what?” the value proposition isn’t relevant enough. If they can respond “says who?” it isn’t credible enough.
Worked example
Product: A project management tool for small teams.
Weak value proposition: “The best project management tool for teams.” (No specificity, no differentiation, no credibility.)
Better: “See who’s doing what, in one place. Stop chasing updates across email, chat, and spreadsheets — [Product] puts your team’s work in a single board that updates in real time.”
The better version names the problem (chasing updates), offers a specific solution (single board, real time), and differentiates (one place vs. scattered tools).
Guidance
- Write ten headlines before choosing one. The first headline is rarely the best — it’s the most obvious. Push past obvious.
- Read your headline without the body copy. If the reader would scroll past it, it’s not doing its job.
- Check every headline for specificity. Replace vague words (“better,” “fast,” “easy”) with concrete ones (“3x faster,” “in under 2 minutes,” “without writing code”).
- Test headlines against each other whenever the platform allows B testing. What the writer thinks will work and what actually works are often different.