| Example | Hypothesis | Traffic source | Signal to measure | False positive risk | Next decision |
| Landing page with early access request | A specific segment understands the problem and wants the promised outcome enough to request access. | Search ads, founder-led community posts, partner newsletter, or direct outreach to a narrow list. If using paid traffic, keep the page aligned with one search intent and one offer; a focused landing page for paid ads is easier to interpret [https://dowhatmatter.com/guides/landing-page-for-paid-ads]. | Qualified email submissions, role/company fit, completion of an optional problem question, and willingness to be contacted. | Broad copy can attract people who like the idea but do not have the problem now. Incentives can also inflate signups. | Interview qualified leads. If they describe the problem in their own words and accept a follow-up, test a manual or concierge version. |
| Waitlist with segmentation questions | The target buyer will identify themselves and share enough context to justify follow-up. | Founder audience, niche communities where promotion is allowed, LinkedIn posts, or an existing customer network. | Waitlist completion plus useful answers about role, urgency, current workaround, and desired outcome. | A waitlist is low commitment. People may join because it is free, interesting, or socially easy. | Prioritize interviews with high-urgency respondents. Do not count raw waitlist size as validation unless the audience is qualified. |
| Pricing click test | Prospects are willing to explore a paid path, not just read about the solution. | Landing page visitors from a defined campaign, existing email list, or product-marketing page. | Clicks on pricing tier, request-to-buy button, booked sales call, or completed notify-me form after pricing is shown. | Pricing curiosity is not the same as payment intent. A user may click only to understand the model. | Follow up with people who clicked and ask what they expected to happen next. If qualified prospects discuss budget or procurement, move toward a sales conversation or pilot offer. |
| Feature gate inside an existing product | Existing users want a specific capability strongly enough to try to access it during their workflow. | Current product users, beta cohort, or controlled in-app segment. | Clicks on locked feature, repeated attempts, workflow context, and opt-in to be notified or interviewed.
| Users may click new UI elements because they are visible, not because the feature is essential. Placement can manufacture attention. | Compare clicks with account type, workflow stage, and follow-up responses. Build only if the need shows up repeatedly in valuable workflows. |
| Sales outreach fake door | A buyer segment is willing to engage around a promised outcome before the product exists. | Cold email, warm intros, LinkedIn outreach, or founder-led account targeting. | Replies that mention the problem, accepted discovery calls, forwarded messages to a decision-maker, or requests for details. | Polite replies and sounds-interesting responses are weak. Friendly network feedback can overstate demand. | Ask for a concrete next step: problem interview, workflow walkthrough, pilot scoping call, or permission to send a proposal when ready. |