How to Write a Landing Page That Converts Before You've Built Anything
Learn how to write a landing page that converts using a pre-launch landing page, before writing a line of product code. Validate your idea in one weekend.
Can You Answer "Yes" To Any of These?
You've been sketching the same product idea in your notes app for three weeks.
You're tempted to spend the next two weekends building it before telling a single stranger about it.
You've built something before, launched it quietly, and heard nothing back. Not even crickets — just silence.
You keep asking "should I build this?" when the real question is "would anyone sign up for this?"
If any of that sounds familiar, this is for you. You're going to write a landing page before you write a single line of product code, and use it to find out if anyone actually wants what you're planning to build.
The Old Way Doesn't Work Anymore
Here's the sequence most people follow: have an idea, build the thing, then go looking for users. It feels productive — code is progress you can see, and a landing page with an email form feels like nothing by comparison.
But building first is backwards. You're spending the most expensive resource you have, weeks of your time, on the least certain part of the process: whether anyone wants this at all.
A landing page flips the order. You describe the product as if it already exists, put a single action in front of visitors, and count who takes it. The median landing page across industries converts at 6.6%, based on an analysis of 41,000 pages and 464 million visitors — now you have a real number to compare yourself against before writing a single database schema.
Ready to see what a validated idea actually looks like before you start? Browse validated startup ideas with the market research already done.
Why a Landing Page Beats Building First
A landing page is a "fake door" test. You put up a page describing an offer, add a button that suggests the thing exists, and see who tries to walk through it. The door usually leads to an honest waitlist or "coming soon" page instead of a working product — you're not tricking anyone into paying for something that doesn't exist, you're measuring interest.
The advantage is speed. A fake door test needs almost no engineering, so you can run one in days and have a read on demand within a week. A full validation sprint, page plus a small amount of traffic, can cost under $200 — compare that to spending six weekends building the full product only to find out nobody wanted it.
Dropbox is the classic example: instead of building the full sync product first, they made an explainer video and a signup page. Overnight, signups went from 5,000 to 75,000 — no product existed yet, just a page and a clear pitch.
What You Actually Need
You don't need much. That's the point.
- A page builder. Carrd is the fastest option for a single prelaunch page — Pro is $19/year and you can have something live in under an hour. Framer gives more design control and a CMS if the page needs to grow later. Unicorn Platform is built specifically for SaaS-style pages with pricing and feature blocks already done for you. Comfortable with Next.js? A single static page works fine too.
- A waitlist or form tool. Anything that captures an email and timestamps it. Keep the form to one field if you can — three-field forms convert at roughly 10.1%, nine-field forms drop to 3.6%.
- A headline you can write in one sentence. Can't describe the product in one line? You're not ready to write the page yet — go define the problem more narrowly first.
- Somewhere to send traffic. A relevant subreddit, a founder community, a few DMs to people who've complained about the problem, or a small ad budget. You don't need thousands of visitors. You need the right dozens.
That's the entire toolkit. No backend, no auth, no database.
The Step-by-Step Framework
Step 1: Write a headline that states the outcome, not the feature
"AI-powered meeting transcription platform" describes a feature. "Never write meeting notes again" describes an outcome. Visitors decide whether to keep reading in about five seconds — a feature name makes them do the translation work themselves, an outcome does it for them. Use plain language, skip the adjectives.
Step 2: Write a subhead that removes the obvious objection
The subhead answers the question your headline just raised: "how" or "for who." Headline: "Never write meeting notes again." Subhead: "Paste your messy transcript, get back clean action items and decisions in under a minute." This is also where you name your audience if the product isn't for everyone — "for sales teams" or "for solo consultants" filters out the wrong visitors before they waste your form's time.
Step 3: One call-to-action. Not three.
Every additional choice on the page reduces the odds any single one gets taken. Don't put "Join the waitlist," "Learn more," and "Follow us on X" all above the fold competing for attention. Pick one action — for a pre-launch page, that's almost always "join the waitlist" or "get early access" — and repeat that same button copy and destination everywhere on the page.
Step 4: Add a placeholder for social proof
Even before launch, social proof reduces hesitation. "Join 340 people already on the list" works once you have real numbers. Before that, a line like "Built after talking to 20+ people who deal with this weekly" does the job. Put it near the signup form specifically, not buried at the bottom — and don't fabricate numbers. An honest small number beats an invented big one.
Step 5: Structure everything above the fold around the decision
The visitor should be able to decide to sign up without scrolling: headline, subhead, one CTA button, one line of social proof, all visible on a phone screen. Mobile now accounts for the majority of landing page traffic but converts at roughly 58% of the desktop rate — if your above-the-fold section doesn't work on a phone, you're losing most visitors before they see your CTA.
Step 6: Set up the fake-door mechanic honestly
The button should lead somewhere real, even if the product doesn't exist yet. Clicking "Get early access" takes the visitor to a form that says plainly: "We're building this. Leave your email and we'll let you know the moment it's ready." Never take payment for something that doesn't exist, and never claim the product is live when it isn't. Set a clear hypothesis before you start — for example, "if we get above 10% signup conversion from 100 targeted visitors, we build it."
Once you've got a working page structure, this is a good point to check what tools others are using to actually build the thing after validation — see the startup idea library for prompts and scope already mapped out.
A Real Walkthrough
Say the idea is a tool that turns messy meeting transcripts into clean summaries.
Headline: "Never write meeting notes again." Subhead: "Paste your transcript, get clean action items and decisions back in under a minute. Built for consultants and small teams." CTA: "Get early access" — one button, repeated twice on the page. Social proof line: "Built after 15 conversations with people who dread this exact task every week."
Below the fold: three short sections — the problem (messy transcripts eat 15 to 30 minutes after every call), the fix (paste, click, done), and a simple three-step visual of the flow. The form is a single email field behind the CTA, landing on an honest "we're building this" confirmation.
Traffic: 40 people from a relevant Slack community, 60 from a small LinkedIn post. If 10 of those 100 sign up, that's a 10% conversion rate — well above the typical 2 to 5% range for a cold-traffic waitlist. That's your green light to start building.
What to Do If You're Stuck
Can't write the headline? You don't understand the problem well enough yet — go talk to five people who have it before touching the page again.
Getting zero traffic? Don't blame the page yet. You likely haven't found the right dozen people. One well-placed post in a niche community beats a hundred visitors from nowhere in particular.
Getting traffic but no signups? That's useful data too — it usually means the headline describes a feature instead of an outcome, or the CTA is competing with too many other choices. Fix one variable at a time and resend to a fresh batch of people.
Want help building whatever the page validates? Book a Weekend MVP Sprint and go from validated idea to working demo alongside someone who's done it before.
Quick Questions
What's a good conversion rate for a pre-launch landing page?
Waitlist pages average around 15% signup conversion, with good pages landing in the 20 to 30% range. Anything meaningfully above your traffic source's typical range (2 to 5% for cold traffic) is a real signal worth building on.
Do I need to build the actual product to test the landing page?
No — that's the entire point. The page describes the outcome, the form captures interest, and you only start building once the numbers say it's worth it.
What if I get very few signups?
That's a valid, cheap result. You just saved yourself weeks of building something nobody wanted. Change the headline, change who you're showing it to, or move to a different idea entirely.
Is it dishonest to advertise something that doesn't exist yet?
Not if you're upfront about it. The line between a fake door test and deception is honesty at the point of signup — tell people plainly you're validating demand before building.
TL;DR
- Write the landing page before the product. It's the cheapest way to test whether anyone wants what you're planning to build.
- One headline stating the outcome, one subhead removing the obvious objection, one CTA — repeated, not diversified.
- Keep forms to a single field and put social proof right next to the button.
- Send the page to the right dozen people, not the widest audience you can find.
- A 10%+ signup rate from targeted traffic is a real green light. Now go check the startup idea library for a validated idea to start with, or take the one you just tested and start building this weekend.