In this guide
Interviews tell you a problem exists. A page tells you whether strangers care enough to leave an email address for a solution. It's the cheapest test of your promise, your audience and your words, and it gives you something you'll need anyway: a list of people to launch to.
This guide covers what goes on the page, how to write it from your interview notes, how to build it for nothing, where to share it, and how to read what happens.
What goes on the page
- A headline that names the problem the way your interviewees did: "Stop chasing receipts on Friday afternoons", not "AI-powered document collection".
- One sentence on how it works.
- Three short points on what changes for them: time saved, a task that disappears, a worry removed.
- One email box, and a button that says what happens: "Tell me when it's ready".
- Optional: a planned price. It filters for people who'd pay, and tells you whether the number scares them.
- A line about you: who's building this and why. A real person is more trustworthy than a logo.
Writing it in their words
Open your interview notes and highlight every phrase people used to describe the problem. You're looking for repeated words.
Hypothetical example
| What interviewees said | Times heard | Use it for |
|---|---|---|
| "chasing receipts" | 7 | Headline |
| "every Friday" | 5 | Headline |
| "the same three clients" | 4 | Point 1 |
| "blurry photos" | 3 | Point 2 |
| "I feel like a nag" | 3 | Point 3 |
Result: "Stop chasing receipts every Friday." Points: "Your clients get a friendly reminder, not a nag from you." "Clear photos, straight from their phone." "See at a glance which clients are still missing receipts."
People who see the page will recognise their own words. It reads as "this person understands my problem", not as marketing.
Building it for $0
A single HTML page fits easily inside free hosting limits: Netlify's free plan includes 300 credits a month[1], and Cloudflare Pages' free plan allows 500 builds a month[2]. A static page that's deployed a few times uses a tiny fraction of either.
For the email box, use a simple form service, your host's built-in form handling if it has one, or your email tool's sign-up form. The page doesn't need a database. If you send a confirmation email, a free transactional email plan covers it: 3,000 a month and 100 a day is plenty for a test[3].
Before you share it
- It loads quickly on a phone, on mobile data.
- The sign-up works, and you receive the email address.
- There's a one-line privacy note: what you'll do with their email.
- It's on your own domain if you have one; you'll keep it for the real product.
Where to share it
- Your interviewees first. Ask if they'd like to be told when it's ready, and whether they know two others with the same problem.
- Two communities where your audience already talks. A short, honest note: what you noticed, what you're building, a link. Read each group's rules and follow them.
- Not everywhere. Fifty visitors from the right group tell you more than 5,000 from a general tech forum.
Hypothetical example post
I talked to ten bookkeepers last month and eight of them spend Friday afternoons chasing clients for receipts. I'm building a small tool that sends the reminders for you. If that's you, there's a sign-up here; I'll email once when it's ready. Happy to hear how you handle it today, too.
Reading the numbers honestly
| What you see | What it probably means | Next step |
|---|---|---|
| Strong sign-up rate from targeted visitors, and people replying with questions | The promise lands | Build the smallest version that keeps the promise |
| Visitors, but few sign-ups | The promise or the words miss | Rewrite the headline with different interview phrases and share again |
| Few visitors | You haven't reached the audience yet | Find where they really gather; ask interviewees |
| Sign-ups from outside your audience | Interesting, but not your test | Note it; don't change direction on it alone |
The strongest signal is people writing back: "When will this be ready?", "Can I pay now?", "Does it work with my setup?" Reply to every one personally. Those people are your first customers and your best testers.
Should you show a price?
Leave it off when
- You're still unsure who the customer is
- You want the widest first list
Show it when
- You want to know if people would pay, not just if they're interested
- You've seen what they pay for related tools in interviews
Ways the test can mislead you
- Writing in your words instead of theirs. Your feature name means nothing to them yet.
- Buying traffic. Paid clicks from a broad audience tell you about the ad, not the problem.
- Waiting for a perfect page. A plain page that ships today beats a beautiful one next month.
- Not following up. A list you never email goes cold within weeks.
Questions
Is it dishonest to collect sign-ups for something that doesn't exist?
Not if you're clear. Say it's coming, invite people to be told when it's ready, and don't take money for something you might not build.
How long should the test run?
One to two weeks of active sharing is usually enough. If nothing happens after that, the words or the audience need to change, not the timeframe.
What if a competitor sees it?
At this stage, the risk is building something nobody wants, not someone copying an idea that isn't built.
If it works, you have a headline, a list and a promise to keep. Build only what the promise needs, check which free limits will matter, and follow the launch week plan.
Sources
Checked 14 November 2026. Numbers in brackets in the text point to these sources.
