Landing Page Copy That Converts: Write for the Reader, Not the Product
Two therapists. Same city. Same qualifications. Same service.
One has been practicing for 2.5 years, has 7 reviews, and a website that says: "Experienced therapist offering sessions online."
The other launched less than a year ago, has 49 reviews, and a landing page that opens with: "Struggling with anxiety? Get practical tools you can use today."
The second converts at nearly 7x the rate of the first.
This isn't about credentials or experience. It's about the first thing the page communicates. One describes the provider. The other describes the visitor's problem. The gap between those two approaches is most of the difference in conversion rate on most landing pages.
Why the default approach fails
When founders write landing pages, they write about what they built. Features, functionality, what the product does. This is understandable — they spent months building it and they know it deeply.
The problem: visitors land on a page thinking about themselves, not about the product. Their implicit question is "can this help me?" And a features list doesn't answer that question directly. It makes the visitor do the work of inferring whether their problem maps to your solution.
Most visitors won't do that work. They'll leave.
The alternative: write the page so the visitor's problem is visible before the product is introduced. By the time they reach your description, they already know you understand their situation.
The structure that works
This isn't a formula to follow mechanically — it's a logical sequence that mirrors how people actually decide to buy something.
1. Headline that names the outcome, not the product
The question a headline has to answer in three seconds: "What's in this for me?"
Compare:
| Weak | Strong |
|---|---|
| "The all-in-one project tool" | "Your team ships features without weekly status meetings" |
| "Advanced HR software" | "Stop spending Fridays on payroll" |
| "Our platform helps you grow" | "First 50 paying customers in 90 days — or we help you figure out why not" |
The strong versions name a specific outcome. Visitors who want that outcome self-identify. Visitors who don't, leave — which is fine. Your conversion rate improves because you're measuring qualified visitors, not all visitors.
2. Mirror the reader's situation
After the headline, the first paragraph should describe what the visitor's life looks like before your product. Not as a sob story — as a recognition.
"You're losing track of client feedback. Projects have multiple Slack threads, three email chains, and nobody's sure which version is current."
When someone reads that and thinks "yes, that's exactly what's happening" — they're already paying attention differently. You've demonstrated understanding before asking for anything.
3. Name the consequence of staying where they are
This step makes the cost of inaction concrete. It doesn't need to be dramatic. It just needs to be real.
"Every missed feedback cycle extends the timeline. Every version confusion means rework. The average team loses 4–6 hours per project to this kind of coordination overhead."
According to McKinsey research on knowledge worker productivity, knowledge workers spend 28% of their time on email and coordination tasks. Making that visible gives visitors a frame for understanding what your solution is actually worth.
4. Introduce the product in terms of what it prevents or enables
Now, and only now, introduce what you built. But introduce it in outcome language, not feature language.
Not: "Our platform has task tracking, comment threading, and file versioning."
Yes: "One place for client feedback. Everyone sees the same version. Projects move on the first pass."
5. Social proof that sounds like a person, not a testimonial
Generic: "Great product. Would recommend."
Specific: "We used to spend Monday mornings reconstructing what happened the previous week. Now the whole team knows by Friday afternoon."
The specific version works because it describes a recognizable situation. Visitors who've experienced Monday morning reconstruction know immediately that this review is real.
6. One CTA, stated simply
One action. Not three options. The copy should set up what happens next so the button doesn't need to work hard.
"Start with a free account — no card required. Most teams are running by end of day."
The last sentence removes the fear of setup complexity, which is a real conversion barrier for productivity tools.
What a small copy change actually moves
Before revision: "Our tool helps with team communication. We offer a variety of solutions to improve workflows." Conversion rate: 1.2%
After revision: "Struggling with miscommunications? Our tool helps teams respond 50% faster — saving hours weekly." Conversion rate: 4.8%
Same product. Same price. Same traffic. Four times the conversion from changing what the page says about the visitor's situation versus what it says about the product.
CXL Institute's landing page research consistently finds that headline and value proposition changes produce the largest conversion lifts — significantly larger than design, button color, or layout changes.
Common mistakes worth naming
| Mistake | Why it costs conversions | Fix |
|---|---|---|
| Features before benefits | Requires visitor to infer value | Lead with outcome, follow with feature |
| No mention of the problem being solved | Page feels irrelevant | Name the situation in the first 100 words |
| "We" language throughout | Feels self-centered | Rewrite with "you" as the subject |
| Multiple CTAs | Creates decision paralysis | One action per page |
| Vague social proof | Doesn't feel real | Replace ratings with specific stories |
A landing page that describes a product rarely converts as well as one that describes a customer.
If your page traffic is decent but the conversion rate isn't moving, the copy is usually the first thing to look at — before the design, before the pricing, before anything else.
We've fixed this for a lot of clients. Happy to look at yours →
