Skip to content
Back to Idea Validation

Demand Validation

Confirm that people will actually pay or switch — not just say they are interested.

Why

"That sounds interesting, I would use that" is the most dangerous sentence in product development — it costs the user nothing to say and you everything to believe. Demand validation tests the only behaviors that matter: will they pay money, will they switch from their current tool, will they change their workflow. Interest is free; action has a cost. A product can have 10,000 interested people and zero paying customers. The methods below force the cost to be paid upfront — a pre-order, a deposit, a commitment to switch — so you know the demand is real before you build, not after you launch to crickets.

When

After segmentation and before building the MVP. Takes 1-3 weeks depending on method. This is the last gate before engineering investment.

How

1. Choose a validation method (by cost to user)
   - Lowest: email waitlist (free to join) — weak signal
   - Medium: pre-order / deposit (commits money) — strong signal
   - High: letter of intent / LOI (B2B, commits to buy) — strongest signal
   - Highest: concierge / pilot (commits to use + pay now) — real revenue

2. Set up the commitment mechanism
   - Pre-order: Stripe checkout for a discounted future price
   - Deposit: $50 refundable deposit to hold a spot
   - LOI: signed document committing to purchase if built
   - Pilot: paid pilot program, you deliver manually

3. Drive traffic to the commitment
   - Your smoke-test responders and waitlist
   - Targeted ads ($100-500 spend)
   - Direct outreach to 50 target-segment prospects

4. Measure the conversion
   - Visitors → committed: what % paid/signed?
   - Compare to benchmark: > 2% pre-order is strong, > 10% email signup is strong
   - Count absolute numbers: 30 pre-orders is a business; 3 is a hobby

5. Interview the committed
   - Why did you pay? What were you hoping for?
   - What would make you cancel? (your biggest risk)
   - This is your highest-signal user research

Example

Product: a database migration tool for teams that hate downtime.
Method: pre-order at 50% off ($150 instead of $300/yr).

Setup (3 days):
  - Landing page with the value prop + "pre-order at 50% off" button
  - Stripe checkout, clearly labeled "product ships Q1, full refund if delayed"

Traffic (2 weeks):
  - Emailed 80-person waitlist from earlier smoke test
  - $300 in targeted ads (r/aws, r/devops)
  - 10 direct DMs to active commenters

Results:
  - 1,200 visitors, 38 pre-orders ($5,700 revenue) = 3.2% conversion
  - 6 pre-orderers agreed to a 20-min interview
  - Top reason: "downtime during migrations has woken me up at 3am"
  - Cancellation trigger: "if it does not support Postgres replicas"

Decision: 38 paying pre-orders + clear pain → build, prioritize Postgres replica support.

Common Problems

  • ⚠Using email signups as a demand signal — email is free and people sign up for everything; it correlates with interest, not demand.
  • ⚠Not making the commitment real — a "notify me" button tests nothing; money or a signed document is the only proof.
  • ⚠Discounting too heavily — a 90% off pre-order gets buyers who will not pay full price; you validate price-sensitive freeloaders, not your market.
  • ⚠Ignoring the interviews — the 30 people who pre-ordered are your most important data; their cancellation triggers are your build spec.

Best Practices

  • ✓Charge real money, even a small amount — $10 separates people with intent from people with opinions, and the refund option removes the risk excuse.
  • ✓Set a clear ship date and offer full refunds if you miss it — this removes the "I will pay when it exists" objection and tests true intent.
  • ✓Interview every pre-orderer you can — 15-minute calls with 10 paying users are more valuable than 1000 survey responses.
  • ✓Track the cancellation trigger: "I would cancel if ___" — aggregate these across interviews and the top 3 become your must-have features.