One page. A headline that makes one promise, a line saying what it is, a price, and a single email field. That is the entire website, and it should take you a day.
The page is not a product and it is not a brand. It is a measuring instrument, and the only thing it measures is one sentence. Every extra hour you put into it adds a variable to the experiment and takes something away from your ability to hear the answer — which is why the most common way to fail at this is not building a bad page, but building a good one slowly.
This is the middle step of a larger sequence: define the promise, put it on a page, buy traffic, read the result. What follows is only the page.
1. Write the sentence before you open the builder
The page is scaffolding around a single claim, so the claim comes first — on paper, before any tool is involved.
You need four things settled: what changes for the customer, who they are, what it costs, and what they do today instead. The pillar covers how to pin those down; the point here is that a page builder will not tell you when they are missing. It will produce something handsome around a claim nobody can parse, and the vagueness will survive all the way to the ad campaign, where it will come back as a number you cannot interpret.
The test: write the promise as one sentence and read it to somebody who does not know what you are working on. If they ask what it does, you have written a category rather than a promise, and you are not ready to build anything yet.
2. Give the page a day
Not a rough guess at a day. A rule. If the page is not live at the end of the day, publish whatever you have and start sending people to it.
The reason to be strict about this is not speed for its own sake. It is that a page you have spent weeks on stops being an instrument and turns into something you own. One founder writing on Indie Hackers in January 2026 laid the pattern out plainly: two months building the core product, then three months on the landing page and payment logic, because he had heard that landing pages were crucial for conversion. "I obsessed over every pixel," he wrote. "I scrapped and redid it countless times until I was finally satisfied." He launched in month nine to fifty signups and no paying customers, by which point the platform he was building on had shipped the same feature for free.
The three months did not cause the failure. They just made sure it arrived too late to be useful.
A day is realistic because the tools are now built for exactly this. Lovable will generate and deploy a page from a description of what you want. Carrd and Framer will get a single page to a live URL in an afternoon. Draper will generate the page on-brand and run traffic to it, which collapses the page and the traffic into the same afternoon. Any of them are sufficient. None of them are the reason the test works or fails.
3. Put five things on the page and nothing else
- A headline carrying the promise. It must match the ad or the post that brought the visitor. If they disagree, you have measured your ad, not your idea.
- One line explaining what it is. Plain words, no category language.
- The price, visible without scrolling.
- One action. Not a signup form and a demo booking and a newsletter box. One.
- What actually exists today. "Not built yet — join the early access list" is a perfectly good sentence.
That is the page. Not on it: an About page, a logo you paid for, a founder story, an FAQ, a feature grid, a roadmap, a Discord badge, or testimonials — you do not have any, and writing fictional ones is not a shortcut, it is a lie your first real customer will eventually read.
Buffer is the worked example of exactly this page. Its first version was two pages: one describing the product with a "Plans and Pricing" button, and behind the button a page admitting there was nothing built yet, with a field for an email address. Joel Gascoigne's stated aim was deliberately narrow — to check whether people would even consider using the app. Seven weeks after that page went up, Buffer had a paying customer.
Founders resist building something this plain, because the missing pieces feel like the difference between a real business and a placeholder. They are not, and the ordering of what actually moves your result is not the ordering most people assume.
influence on the result
- Which promise is in the headline
The same product under a different promise is a different test.
- Whether there is a price on the page
Changes who signs up, not only how many.
- Whether the page matches the ad
A mismatch measures the ad instead of the idea.
- How the page looks
Above the threshold where it looks broken or fake, very little.
The first three are decisions you make in a sentence each. The fourth is where the month goes.
Design matters below a threshold and barely above it. A page that looks broken, or looks like a scam, will cost you signups. A page that looks clean and plain will not cost you any, and no amount of polish past that point buys information.
One thing worth doing before the traffic starts is working out what this particular page will entitle you to say. An email address is a perfectly good thing to collect — it is the fastest signal there is — but knowing its limits in advance is what stops a decent result being oversold and a soft one being read as a verdict.
What will your page actually prove?
Pick what your page asks for and what it shows, and read the sentence you will honestly be able to say when the test finishes — along with the one you will not.
You will be able to say
That your headline was interesting enough to be worth an email address.
You still will not be able to say
That anyone would pay. Nobody who signed up has been shown a number.
They reacted to a sentence, so some of what you measured is their imagination filling in the rest. Expect the response to soften when they see the real thing.
4. If the product doesn't exist, show it anyway
The hardest page to write is the one for a product with nothing behind it, and the instinct is to compensate with adjectives. Do the opposite: give the visitor something concrete to react to, and be explicit that it is not finished.
Concrete means a screenshot of the interface even if the interface is a mockup, a short screencast of a clickable prototype, or a plain before-and-after of the work the product removes. Any of these produce a sharper reaction than three paragraphs of description, because the visitor is responding to a thing rather than to your vocabulary.
Dropbox is the standing example. Drew Houston put a screencast of an unfinished product in front of the communities his early users were in, and the waiting list went from a few thousand to around 75,000. The video did the work the product could not do yet — it made something abstract legible in a couple of minutes.
Saying it is a mockup costs you almost nothing and protects the number. People who sign up expecting something usable behave differently from people who know they are early, and a page that implies a working product quietly mixes the two groups together in your results.
5. Run one promise at a time
One page carries one promise. If it underperforms, what you have learned is that that promise underperformed — which is not the same thing as learning that nobody wants the idea, though it is routinely read that way, and that misreading is the most expensive one in the whole exercise.
"Know whether your idea has customers before you build it" and "See what your competitors are doing" can describe one identical product and attract completely different people at completely different costs. Draper's own paid test found a roughly fivefold spread in cost per signup across three framings of the same product, with nothing else changed.
The temptation is to run all of them at once. Resist it: a few hundred dollars split three ways returns three numbers, each too small to compare with the other two, and you end up with less certainty than you started with rather than more.
Run one. Decide in advance what a soft result will mean — and let it mean rewrite the headline, not abandon the idea. Then change the promise to a genuinely different claim about what the product is for, put it on the same page, and run it again. Nothing else on the page has to move.
That is the other reason step 2 matters. A page you built in a day is a page you can rewrite on Thursday.
6. Instrument it so a no is unambiguous
You need two numbers and no others: how many people arrived, and how many acted.
Every page builder and every analytics tool will give you those without configuration. Resist the urge to add heatmaps, session recordings and scroll-depth tracking on top. At the sample size a few hundred dollars buys, none of it will be interpretable, and all of it will give you something to study instead of a decision to make.
Then leave the page alone while it runs. Editing the headline on day three because the early numbers look soft blends two tests into one unreadable number — if you want to try a different promise, let the first one finish. A week is not long.
Ready to send traffic
What comes next is traffic, and that is a separate craft. Paid is the faster route, because you control the volume and the timing. Posting where your customers already gather is slower and costs nothing but standing — the same rooms you would use to find your first hundred customers.
When a page isn't the right instrument
A page is one way of asking the question, not the only one. None of what follows is a reason to skip ahead and start building — the point of each is that you can get a better answer a different way, and the answer still comes before the build.
When your market is ten named companies. Enterprise buyers do not evaluate anything by filling in a form. Write to the ten. A landing page is a tool for reaching strangers at volume, and you do not have volume — you have names, which is better.
When you already have the right people's attention. If you have a list, or you are a genuine member of a community your customers are in, ask them directly before you build anything at all. At that scale a conversation tells you more than a conversion rate, because you get to hear the reason behind the answer. Put the page up afterwards, with what they told you in the headline.
When you have no way to get anyone onto it. The page is the cheap half of this exercise; the traffic is the half that costs money or standing. If you cannot buy visitors and you have no room to post in, a live page will sit at zero and you will read that as a verdict on the idea when it is a verdict on your distribution. Settle where your customers actually gather first.
Related questions
Before you build anything, it is worth knowing whether the group you are aiming at genuinely coheres: how to tell whether your target market is real. Once the page is live it needs traffic and a way to read what comes back, which is the demand test end to end. And if the answer is yes, the acquisition problem starts over from scratch: how solo founders find their first 100 customers.
Want the page and the traffic handled in one go? Try Draper free →
