A Public Page for an Idea You Have Not Shipped

A public page can exist before the product does. It teaches you something only when a stranger can tell what is real. "Join the waitlist" on a page that looks like a finished app is a different offer from "the app is live, create an account." Mixing those two offers wastes the only signal the page can give you.

A free launch scan needs a public URL. It can review what a cold visitor sees; it does not build the app, inspect a private prototype or validate demand. Publish an honest page on a host you control, and keep your accounts and customer data under your authority.

Write the status before the layout

Finish this sentence before you pick fonts:

For [a specific person], this helps with [a job they already have]. It is not available yet. Leaving an email means [one concrete follow-up], and it does not mean they can use the product today.

If the person and the job are still fuzzy, more visual polish will not make the page clearer. How to Validate a Product Idea Before You Build More is a separate, harder test. A pretty waitlist is not that test.

On the first screen, include:

• The job, in ordinary language.
• A status the reader cannot miss: "Not available yet" or "Prototype only."
• What the email is for, and what it is not for. A fair example is: "One note when a test version exists. No charge."
• Three short steps. If you have no product screens, label the steps as the plan.
• A small FAQ for timing, price, and what happens to the address. If you do not know, say you do not know.

Leave out quotes, user counts, and logos you do not have. An empty proof section is more trustworthy than a made-up one. Waitlist page examples are useful for structure. Copy the structure only where it still lets you tell the truth about your status.

George's post on X argues for questions about past behavior and workarounds people already use. The story in that post is secondhand. The useful piece for this page is a single optional field under the form: "What do you do today when this problem shows up?" The answers are language for the next draft. They are not a demand statistic, and a handful of replies is not a market study.

A test you can score without a fake rate

Write the pass rule before you share the link. A conversion percentage on twelve friends is noise, so keep the rule qualitative and specific.

A usable rule looks like this: "I will show the page to eight people who already do this job. I will keep going for another build week only if at least three leave an email without me on the call, and at least three describe a current workaround in their own words. 'Cool idea' does not count."

Then do the work in order:

1. Publish the page and read it on a phone. The status line has to be visible without hunting.
2. Take it to those eight people in a place they already are. Ask them to criticize the promise, not to encourage you.
3. Do not spend money until those conversations exist, unless you already know a precise way to reach that job and you choose to approve a small test. Spending and sending stay your decisions.
4. For each person, note: saw the status, left an email, described a workaround, asked whether it was live.

If people who do the job lose interest, change the sentence and the status before you add features. If you cannot get the page in front of anyone who does the job, you learned something about reaching them, not about the idea.

Hypothetical example

**Hypothetical.** You want a tool that turns client voice notes into a one-page brief for freelance designers. You have a clickable mock and no accounts. The page says, "Not available yet. Designers can ask for a prototype invite." Five working designers visit. Two leave an email, and both say they currently paste notes into a doc late at night. Three say they would not send an automated brief to a client. You keep the list and change the promise to "a draft I edit," and you do not start building invoicing.

Copyable agent prompt

Draft a one-page waitlist for an idea that is not a shipped product. Do not invent customers, quotes, logos, or usage numbers. Do not imply someone can use the product today.

I will paste: who it is for, the job, what is actually built, and what the email is for.

Write:
- A headline that states the job.
- A status line, "Not available yet" or "Prototype only," that matches my input.
- What the person gets by leaving an email, and what they do not get.
- Three short steps labeled as the plan when screens do not exist.
- Four FAQ answers I can stand behind. If price or date is unknown, say so.
- One optional question about what they do today when the problem happens.

Plain language. No slogan voice. Output Markdown and the exact button label.

Finish rule

You are done with this stage when the public page shows a true status, the form stores addresses you can export, and you have notes from the people named in the rule you wrote down. You are not done if the only visitors are friends who have never done the job.

Once a URL is public, scan it for a static read of clarity. The score is not evidence that anyone wants what you described. Save the product launch checklist for the point when there is a product to launch.