Price your waitlist before you build

You have an idea, a rough sketch, and a folder full of screenshots. Before you spend months building, put a real price on a waitlist page and watch who asks to pay. A priced waitlist is a small, honest test.

Treat it as a willingness-to-pay check, not a favor request. Someone who sees the price and still asks how to reserve a spot is a signal. Polite silence is a cheaper lesson than a failed build.

Dropbox used a pre-product explainer video to collect signups, and those registrations served as demand evidence before the product existed. DoorDash's founders built a one-afternoon landing page called Palo Alto Delivery, listing local restaurant menus with personal cell phone numbers. Both moves are small, concrete, and cheap to fail.

The price is the first question

A free waitlist can feel generous, but it often measures curiosity, not demand. A real price forces the page to answer a harder question: what is this worth to the person who would use it? You can start with a number you would actually charge, not a placeholder.

Superhuman sold lifetime access at $30 per month to its first 3,000 users, creating advocates who supported its premium pricing.

Early-bird pricing can lift conversion by 20 to 30 percent when the discount sits around 10 to 20 percent off regular price. It gives a reason to act now.

Run the five-step test this week

Put a real price on the page. Do not hide it behind free or coming soon.
Ask what they do and what they expect. One short question beats a long survey.
Recruit design partners. Invite a few people to help shape the product before it exists.
Promise a delivery date you can meet. Say what happens if it slips.
Treat first orders as a fulfilment test. Make, ship, and support the first few carefully.

Start with one page, one price, one question, and one date. You do not need a full product or a launch plan. You need a small set of people who will tell you whether the offer is real. Put the price in the headline, not in a footnote.

When you ask what they do, you want the way they handle it now, not compliments. Note what they pay for a similar tool, or what they tried before. If they cannot name the task, the price may be too high or the buyer may be wrong.

A small set of five paying customers can be more informative than hundreds of free signups that never return. Notion collected 1 million signups in 5 weeks on its AI waitlist and learned that users preferred AI for content revision over generation, which pushed it from usage-based pricing to flat monthly pricing. Use the waitlist as a research instrument, not a trophy shelf.

Make the date a promise, not a poster

A waitlist without a date can become a waiting room. A date gives the buyer a reason to believe the product is real. It also gives you a deadline that forces decisions.

A date helps you choose the first offer. When you can deliver quickly, say so. When the first units must be hand-built or the first batch is limited, say that too. The buyer should know what they are getting and when.

Temple set the opening of public pre-orders for its wearable for November 1, 2026. Its early-access waitlist showed applicants a price of Rs 85,000 for the device. Temple said its first consumer units would be produced by hand in small batches, with buyers told to expect about three months for delivery, so some November 2026 orders could arrive in early 2027.

The limited launch edition was slated to ship before 2026 ended. Temple appeared to be treating early orders as a partial test of manufacturing, fulfilment, and customer support before widening availability. Temple would personally choose waitlist applicants who could provide meaningful feedback.

Access timing matters. When admitted within a month, about half of waitlisted users make a free sign-up; after three months, fewer than 20 percent do. A date you can give is better than none. If you cannot, say so plainly.

Then you know whether the next step is building, changing the offer, or finding a different buyer. When the answer is not clear, change the page and run the test again.