Skip to content

Demand Validation Experiments

First PublishedLast UpdatedByAtif Alam

The decision this page enables: will real people give real signal — a click, an email, a credit card — at a price you can build a business on?

A demand validation experiment is a small, time-boxed test designed to show whether real customers will take a real action — sign up, leave a credit card, pre-order, sit through a manual delivery — for a thing that’s only partly built (or not built at all). The output is behavioral data, not stated-intent data.

Stated intent is famously unreliable. “Yes, I would totally use that” is one of the most common false positives in early-stage research. Demand validation replaces the question “would you use this?” with the question “did you click, type, or pay?” — questions with binary, falsifiable answers.

It pairs with trends and demand, which scans the macro signals. Demand validation tests the micro signal: is your specific offer, at your specific price, attractive enough to get a real customer to act?

  • It’s the cheapest way to kill a bad idea before building it. A two-week, $500 experiment that disconfirms a hypothesis saves six months and $100K of build.
  • It produces the first real conversion-rate benchmark that grounds the rest of Workbook → KPI baseline.
  • It generates the first qualified user list — the people who clicked or signed up are your warmest leads.
  • It de-risks pricing — putting a price in front of a customer (even fake) is the only way to learn whether the price is workable.

The experiment types (smallest to largest commitment)

Section titled “The experiment types (smallest to largest commitment)”
TypeWhat it testsEffortRisk if it backfires
Ad-only smoke testDoes the message earn a click?1-3 days; ~$300-1,000Minimal
Fake / coming-soon landing pageDoes the message earn an email?3-7 days; ~$500-2,000Brand drag if discovered
Waitlist with positioningDoes the offer earn an email + sustained patience?1-2 weeks; ~$1-3KSame
Concierge MVP (manual delivery)Will customers use the outcome if delivered by hand?2-6 weeks; ~$5-20KCost of doing manual work
Pre-order with real billingWill they put a card down on a future product?2-4 weeks; ~$2-10KRefund obligation; reputation if cancelled
Crowdfunding (B2C)Public, all-or-nothing, with a delivery commitment4-8 weeks campaign + months of fulfillmentMulti-month delivery exposure

Pick the smallest experiment that can answer your hypothesis. Most teams over-build; a fake landing page can disprove a bad idea in a week.

A 6-step process per experiment:

  1. Write the hypothesis as falsifiable. “I believe that [target segment] will [specific action] at a rate of at least X%, when shown [offer], on [channel].” If “X%” or “at least” is missing, the experiment is unfalsifiable and won’t kill anything.
  2. Define success and failure thresholds before running. Success threshold (the action rate above which you commit to building) and kill threshold (the rate below which you stop). Pre-commit to both — it’s the discipline that makes the experiment useful.
  3. Pick the smallest experiment that can answer the hypothesis. Resist scope creep.
  4. Define the audience and channel. Where will real prospects see this? Don’t test on internal lists or warm networks — those skew positive.
  5. Run for a defined window. 1-2 weeks for ad/landing-page tests; 4-6 weeks for concierge / pre-order. Don’t keep running until you “get the result you want.”
  6. Decide and document. Compare to the pre-set thresholds. Write down: hypothesis, design, result, decision, lessons. Even kills are valuable — they tell you where not to spend the next six months.

Fill in before running:

EXPERIMENT NAME: [short label]
HYPOTHESIS: I believe [target audience] will [specific action] at a
rate of at least [X%] when shown [offer] on [channel].
AUDIENCE: [where the audience lives + the recruit / ad spec]
CHANNEL: [paid ad on which platform | content / SEO landing |
community post | etc.]
OFFER: [one-line description of the value the user sees]
PRICE / ACTION: [the action you're measuring — click / email / pre-order / etc.
+ price displayed if applicable]
WINDOW: [start date — end date; minimum spend / impressions / traffic]
BUDGET: $______ (cap; do not exceed)
SUCCESS THRESHOLD: ≥ [X%] action rate ⇒ commit to building [next step]
KILL THRESHOLD: < [Y%] action rate ⇒ stop / pivot / re-scope
WHAT WE'LL LEARN BY KILLING IT:
- [the specific learning a negative result gives you]

Fill in after running:

EXPERIMENT: [name]
RAN: [start — end]
TRAFFIC: [impressions / sessions / qualified visitors]
SPEND: $______
OBSERVED:
- Action rate: ____%
- Cost per action: $____
- Quality of action: [for emails, what fraction had real domain / role match?]
DECISION:
☐ Commit to next step: [what we'll build / test next]
☐ Run a follow-up test: [what we'll change]
☐ Kill / pivot: [what we now believe is not true]
QUOTES FROM RESPONDENTS: [paste 2-3 in their own words]
LESSONS / SURPRISES:
- ...

Pre-order page template (high-commitment version)

Section titled “Pre-order page template (high-commitment version)”
HEADLINE: [the outcome they want, framed as a promise]
SUBHEAD: [one-line "without the pain they expect"]
PROOF / SOCIAL: [logos / quotes / waitlist count if any]
PRICE: $____ (anchor; either "launch price" or "founders price")
DELIVERY DATE: [realistic — refundable until delivery]
GUARANTEE: 100% refund anytime before delivery + N days after.
CTA: Reserve your spot — $____ down today
TRUST SIGNALS: [your name + face + a way to contact you]

These are rough — variance is enormous by channel, message, and audience quality. Use as a sanity check, not a target.

  • Click-through rate on a category-relevant paid ad: 0.5-2% (paid social) up to 3-5% (paid search on intent keywords).
  • Email-capture rate on a landing page from cold traffic: 1-3% is typical; >5% means the message is exceptional, <1% means it’s off.
  • Email-capture rate on a landing page from warm traffic: 8-20%.
  • Pre-order rate (credit card down) on a landing page: 0.5-3% from warm traffic; <0.5% from cold is normal. >2% from cold is excellent.
  • Crowdfunding pledge rate from campaign-page traffic: 1-5%.

A real signal is typically 2-3× the floor of the relevant prior, not the floor itself. A 1.2% email rate from cold traffic is not signal; a 6% email rate is.

  • Action rate (CTR, email rate, pre-order rate) — primary signal, compared against your pre-set threshold.
  • Cost per qualified action — total spend ÷ qualified responses. Used to project CAC at scale.
  • Quality of the action — for email signups, are the addresses from real domains and target-segment roles? Floor: 60% qualified.
  • Time-to-action — average time on landing page before action. Very short times (<10s) suggest accidental clicks; very long (>5min) suggest confusion.
  • Subsequent engagement — fraction of signups who open the welcome email, click the follow-up, take a second action. The strongest signal of real intent.

Before building the unified-workspace product, the founder ran a fake-landing-page test:

  • Hypothesis: team leads at small SaaS teams will leave their email at ≥4% rate when shown “ship the whole workflow from one tool” against the do-nothing alternative.
  • Channel: 3 days of paid X ads ($800 budget) + 2 niche subreddit posts (free).
  • Offer: a one-page landing site with the headline, three feature mocks, and a “Get on the early access list” form. Price not yet shown.
  • Result: 1,200 visitors, 102 email signups (8.5% rate). 71 of 102 (70%) from real-looking team-lead emails at small SaaS companies. 18 of those replied to the follow-up with substantive answers.
  • Decision: commit to building. The signup rate was 2× the cold-traffic prior, and the quality of follow-up replies converted directly into the first 8 design-partner conversations.

Six weeks of build was de-risked by one week and $800 of experiment.

Before adding a “rest week” feature to the app, the team tested whether users would actually opt into it:

  • Hypothesis: churn-prone users will opt into a “rest week” toggle at ≥20% rate when prompted after missing 2 consecutive workout days.
  • Channel: in-app prompt to 1,500 users who’d just hit the 2-missed-days trigger.
  • Offer: “Take a 7-day break? Your streak keeps going. We’ll check in on day 7.”
  • Result: 31% opt-in (above the 20% success threshold). 7-day retention for opters: 78%, vs. 41% for the matched cohort that didn’t opt in.
  • Decision: ship the feature broadly. The behavioral signal was strong enough that the team skipped a more elaborate A/B test.

The B2C lesson: in-product experiments are the consumer equivalent of fake landing pages — they cost almost nothing and produce the cleanest signal because the action is the behavior.

  • Vague hypotheses. “I want to see if people are interested” is not a hypothesis. Specific audience, specific action, specific threshold — or you can’t fail.
  • No pre-set kill threshold. Without it, every result becomes “directionally encouraging.” Pre-commit to both success and kill thresholds before running.
  • Testing on warm networks. Friends, family, your existing list — all skew massively positive. Test on cold or weakly-cold audiences for trustworthy signal.
  • Running too long. Past the planned window, you’re seeing late-stage signal and survivorship bias.
  • Single experiment, single decision. One landing-page test isn’t enough to commit to a $1M build. Plan a sequence: clicks → emails → pre-orders → MVP usage. Each step is a higher commitment with a higher signal.
  • Not following up with respondents. The people who took the action are your warmest research subjects. Always send a “what made you click / sign up / pay?” follow-up within 24 hours.
  • Treating “no signal” as “wait and see.” No signal is the signal. Honor your kill threshold; pivot or stop.