Waitlists are used to gauge demand before a product exists. The number they produce measures something real, but rarely the thing it is taken to measure.
Signing up costs nothing
Entering an email address requires no money, no time commitment and no decision. The action reflects curiosity rather than intent to purchase.
Conversion from a free list to a paid product is consequently low, and treating list size as a forecast of early revenue overstates it substantially.
The gap widens with how the list was promoted. Names gathered from a viral campaign convert far less than names gathered from a problem-focused description.
Friction filters for seriousness
Requiring more from a signup, such as answering questions about current tools or committing a refundable deposit, reduces list size and raises its predictive value.
A smaller list of people who described a specific problem is more informative than a large one collected behind a single button.
Deposits change the signal most sharply because they convert an expression of interest into a financial decision, though they also introduce refund obligations.
Delay decays whatever intent existed
The need that prompted a signup does not wait. If the wait is long, people solve the problem another way and forget the list entirely.
Lists built far ahead of availability therefore contain a growing proportion of names whose relevance has expired.
Periodic contact slows this by keeping the product present, at the cost of unsubscribes that reveal the decay that had already happened.
Scarcity framing changes who joins
Presenting access as limited raises signups by adding urgency, and it attracts people motivated by access rather than by the product.
Those users behave differently after launch, with lower engagement and higher churn than users who arrived because they needed the thing.
Invitation mechanics compound this when they reward referral volume, since the incentive selects for people who will forward a link rather than use a product.
Sequenced release is the operational use
The defensible reason for a list is capacity management. Releasing access in batches lets support, infrastructure and onboarding absorb load progressively.
It also allows early cohorts to be observed before the product meets a wider audience, which is more valuable than the aggregate number.
Reading the list as a demand estimate is where it misleads. Reading it as a queue to be worked through, with conversion measured per batch, produces information the business can act on.