---
# === IDENTITY ===
id: business/customer-validation/demand-signal-testing/2026
canonical_question: "How do I test demand signals — fake door tests, waitlist conversion, Kickstarter validation, concierge MVP methodology?"
aliases:
  - "How to validate demand before building a product"
  - "Fake door test vs waitlist vs crowdfunding for startup validation"
  - "Landing page smoke test to measure customer interest"
  - "Concierge MVP and Wizard of Oz testing methodology"
entity_type: execution_recipe
domain: business > customer-validation > demand signal testing
region: global
jurisdiction: global
temporal_scope: 2024-2026

# === VERIFICATION ===
last_verified: 2026-03-11
confidence: 0.88
version: 1.0
first_published: 2026-03-11

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: stable
  last_breaking_change: null
  next_review: 2026-09-07
  change_sensitivity: medium

# === CONSTRAINTS ===
constraints:
  - "Never invest more than $500-2,000 in ad spend per demand test — if you need more data, your test design is wrong"
  - "Fake door tests in regulated industries (healthcare, finance) can create compliance risk — consult legal before deploying"
  - "Waitlist signup alone is a weak signal — conversion to paid or active use is the real metric"
  - "Crowdfunding campaigns require 4-8 weeks of pre-launch audience building for reliable signal"
  - "All tests must define success/failure thresholds BEFORE launching — do not move goalposts after seeing data"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "Already have paying customers and need to validate a new feature"
    use_instead: "business/customer-research/customer-interview-guide-template/2026"
  - condition: "Need a strategic framework for which validation method to use"
    use_instead: "Search knowledgelib.io for choosing a validation method — no dedicated unit yet"
  - condition: "Ready to build an MVP after validation — need execution plan"
    use_instead: "business/startup/mvp-scoping-framework/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: test_type
    question: "Which demand signal test should be run?"
    type: choice
    options: ["fake door / painted door test", "waitlist / landing page signup", "crowdfunding campaign (Kickstarter/Indiegogo)", "concierge MVP", "wizard of oz MVP", "auto-select based on context"]
  - key: technical_skill
    question: "What is the user's technical skill level?"
    type: choice
    options: ["non-technical (no-code only)", "semi-technical (can edit code)", "developer (can write code)"]
  - key: budget_for_tools
    question: "What's the testing budget?"
    type: choice
    options: ["free tier only", "up to $200", "up to $1,000", "up to $5,000"]
  - key: audience_size
    question: "Does the user have an existing audience?"
    type: choice
    options: ["no audience (cold traffic only)", "small audience (100-1,000)", "medium audience (1,000-10,000)", "large audience (10,000+)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Product concept description"
      source: "user/founder or agents/startup/idea-structuring"
      format: "text — 2-3 sentences describing the product and target customer"
    - name: "Target customer profile"
      source: "user/founder or agents/startup/persona-builder"
      format: "structured data — demographics, pain points, where they gather online"
  outputs:
    - name: "Demand Signal Report"
      format: "structured JSON + narrative summary"
      description: "Quantified demand metrics (CTR, signup rate, conversion rate) with go/no-go recommendation and confidence intervals"
    - name: "Raw engagement data"
      format: "CSV or analytics export"
      description: "Click-through rates, signups, email addresses, survey responses, payment attempts"
    - name: "Test artifacts"
      format: "URLs, screenshots, ad creatives"
      description: "Landing page URL, ad copy variants, email sequences — reusable for launch"
  tools_required:
    - name: "Landing page builder"
      purpose: "Create fake door or waitlist page"
      tier: free
      cost: "$0-29/month"
      alternatives: ["Carrd ($0)", "Unbounce ($99/mo)", "Leadpages ($49/mo)", "Webflow ($0-16/mo)", "Framer ($0)"]
    - name: "Analytics tool"
      purpose: "Track visitor behavior and conversion rates"
      tier: free
      cost: "$0"
      alternatives: ["Google Analytics (free)", "Mixpanel (free tier)", "PostHog (free tier)"]
    - name: "Ad platform"
      purpose: "Drive targeted traffic to test page"
      tier: paid
      cost: "$200-1,000 per test"
      alternatives: ["Google Ads", "Meta Ads (Facebook/Instagram)", "Reddit Ads", "LinkedIn Ads (B2B)"]
    - name: "Email collection tool"
      purpose: "Capture and manage signups"
      tier: free
      cost: "$0"
      alternatives: ["Mailchimp (free to 500)", "ConvertKit (free to 1,000)", "GetWaitlist.com (free)"]
  credentials_needed:
    - service: "Google Ads"
      type: "account + billing"
      where_to_get: "https://ads.google.com"
      free_tier_limits: "No free tier — minimum $5/day recommended"
    - service: "Google Analytics"
      type: "tracking ID"
      where_to_get: "https://analytics.google.com"
      free_tier_limits: "Unlimited for standard use"
  estimated_duration: "3-14 days depending on test type and traffic volume"
  estimated_cost: "$0 (organic/concierge) to $2,000 (paid traffic fake door test)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/customer-validation/demand-signal-testing/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "business/startup-planning/startup-idea-structuring-template/2026"
      label: "Product concept definition (required input)"
  feeds_into:
    - id: "business/startup/mvp-scoping-framework/2026"
      label: "MVP scoping framework — feature inventory, MoSCoW/value-vs-effort cut line, technical task breakdown with timeline estimation, and scope lock"
    - id: "business/startup/financial-model-template-library/2026"
      label: "Stage-appropriate startup financial model template — assumptions sheet, bottom-up revenue build, P&L, cash flow by funding stage"
  related_to:
    - id: "business/customer-research/customer-interview-guide-template/2026"
      label: "Stage-specific customer interview guides — Path A problem discovery, Path B solution validation, Path C post-launch/paying customers, Path D win-loss, with exact question scripts and leading-question anti-patterns"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "How to validate your startup idea"
    author: Todd Jackson / Lenny's Newsletter
    url: https://www.lennysnewsletter.com/p/validating-your-startup-idea
    type: technical_blog
    published: 2023-09-01
    reliability: authoritative
  - id: src2
    title: "Fake Door Testing: Definition + How to Run"
    author: Userpilot
    url: https://userpilot.com/blog/fake-door-testing/
    type: technical_blog
    published: 2024-06-01
    reliability: high
  - id: src3
    title: "Waitlist Benchmarks & Conversion Rates"
    author: GetWaitlist
    url: https://getwaitlist.com/blog/waitlist-benchmarks-conversion-rates
    type: industry_report
    published: 2025-01-15
    reliability: high
  - id: src4
    title: "Crowdfunding Validation Method"
    author: Learning Loop
    url: https://learningloop.io/plays/crowdfunding
    type: technical_blog
    published: 2024-01-01
    reliability: high
  - id: src5
    title: "The Lean Startup"
    author: Eric Ries
    url: https://theleanstartup.com
    type: book
    published: 2011-09-13
    reliability: authoritative
  - id: src6
    title: "Landing Page Conversion Rates by Industry: 2026 Report"
    author: First Page Sage
    url: https://firstpagesage.com/seo-blog/landing-page-conversion-rates-by-industry/
    type: industry_report
    published: 2026-01-10
    reliability: high
  - id: src7
    title: "How to validate your B2B startup idea"
    author: Lenny Rachitsky
    url: https://www.lennysnewsletter.com/p/how-to-validate-your-b2b-startup
    type: technical_blog
    published: 2024-03-01
    reliability: authoritative
---

# Demand Signal Testing

## Purpose

This recipe produces a quantified Demand Signal Report by guiding you through selecting, building, launching, and measuring one of five demand validation tests: fake door (painted door), waitlist/landing page, crowdfunding campaign, concierge MVP, or Wizard of Oz MVP. The output is a structured dataset of engagement metrics — click-through rates, signup conversion rates, payment intent signals — with a clear go/pivot/kill recommendation based on pre-defined thresholds. [src1]

## Prerequisites

- [ ] **Product concept description** — 2-3 sentence summary of what you are building and for whom — from founder or [Startup Idea Structuring Template](/business/startup-planning/startup-idea-structuring-template/2026)
- [ ] **Target customer profile** — demographics, pain points, and where they gather online — from founder or persona-builder agent
- [ ] **Landing page builder** — Carrd (free), Webflow, Framer, or Unbounce account
- [ ] **Analytics tracking** — Google Analytics property or Mixpanel project configured
- [ ] **Ad platform account** (if using paid traffic) — Google Ads or Meta Ads with billing enabled
- [ ] **Pre-defined success thresholds** — written down BEFORE launching the test (see Quality Benchmarks below)

## Constraints

- Never spend more than $500-2,000 in ad spend per individual demand test. If the signal is unclear at that budget, the problem is test design or audience targeting, not sample size. [src1]
- Fake door tests placed inside existing products can erode user trust if overused. Limit to one active fake door test at a time and always show a graceful fallback message. [src2]
- Waitlist signups are an intent signal, not a demand signal. The real metric is conversion from waitlist to paid or active user. Average waitlist-to-customer conversion is only 2-5% for cold traffic. [src3]
- Crowdfunding campaigns require 4-8 weeks of pre-launch audience building (email list, social media). Launching cold on Kickstarter typically fails regardless of product quality. [src4]
- All demand tests must define quantitative success/failure thresholds before launch. Moving goalposts after seeing data invalidates the experiment.

## Tool Selection Decision

<!-- Agent selects the right test type based on user inputs. -->

```
Which test type?
├── User wants fastest signal (1-3 days) AND has ad budget
│   └── TEST A: Fake Door / Painted Door — landing page + paid traffic
├── User wants pre-launch buzz AND 1-2 week timeline
│   └── TEST B: Waitlist Landing Page — signup page + email sequence
├── User has physical/hardware product AND 4-8 week timeline
│   └── TEST C: Crowdfunding Campaign — Kickstarter or Indiegogo
├── User has service/consulting product AND wants deep validation
│   └── TEST D: Concierge MVP — manual delivery to 5-15 customers
└── User has software product AND wants to simulate automation
    └── TEST E: Wizard of Oz MVP — human-powered backend, real frontend
```

| Test | Best For | Cost | Timeline | Signal Strength |
|------|----------|------|----------|-----------------|
| A: Fake Door | Any product, fastest | $200-1,000 ad spend | 1-7 days | Moderate (measures intent, not payment) |
| B: Waitlist | SaaS, apps, digital products | $0-500 | 7-14 days | Moderate (email = weak commitment) |
| C: Crowdfunding | Physical products, hardware | $1,000-5,000 | 30-60 days | Strong (payment = real commitment) |
| D: Concierge MVP | Services, consulting, marketplaces | $0-200 | 7-21 days | Very strong (actual delivery + feedback) |
| E: Wizard of Oz | Software with complex backend | $0-500 | 14-30 days | Very strong (real usage, manual backend) |

## Execution Flow

### Step 1: Define Success Thresholds

**Duration**: 30 minutes
**Tool**: Spreadsheet or text document

Before building anything, write down your pass/fail criteria. This prevents confirmation bias after you see data.

```
DEMAND SIGNAL THRESHOLDS
═══════════════════════════════════════════
Test Type: _______________
Primary Metric: _______________

          KILL         PIVOT        GO
          (stop)       (iterate)    (build)
─────────────────────────────────────────
Fake Door CTR:    <2%         2-5%         >5%
Waitlist signup:  <3%         3-8%         >8%
Waitlist→paid:    <2%         2-10%        >10%
Crowdfund goal:   <30%        30-100%      >100%
Concierge NPS:    <30         30-50        >50
Wizard retention: <20%        20-40%       >40%

My threshold: _______ = GO
My threshold: _______ = KILL
Sample size needed: minimum 200 visitors (fake door/waitlist)
                    minimum 5 customers (concierge/wizard)
```

**Verify**: Thresholds written down and shared with at least one advisor or co-founder.
**If failed**: Do not proceed without written thresholds. Every demand test without pre-set criteria becomes a vanity exercise.

### Step 2: Build the Test Asset

**Duration**: 2-8 hours depending on test type
**Tool**: Landing page builder (Carrd, Webflow, Framer) + analytics

**For Test A (Fake Door) and Test B (Waitlist):**

Build a single-page landing page with these elements:

```
Landing Page Structure:
═══════════════════════════════════════════
1. HEADLINE: Clear value proposition (what + for whom)
   - Bad: "The Future of Productivity"
   - Good: "Save 5 Hours/Week on Invoice Processing"

2. SUBHEADLINE: How it works in one sentence

3. SOCIAL PROOF (if any): waitlist count, testimonials,
   logos of beta users

4. SINGLE CTA:
   - Fake Door: "Get Early Access" or "Start Free Trial"
     → clicks to interest form or waitlist
   - Waitlist: "Join the Waitlist" → email capture

5. BRIEF FEATURE LIST: 3-4 bullet points maximum

6. OBJECTION HANDLER: FAQ or trust signals
═══════════════════════════════════════════

DO NOT include: pricing pages, feature comparisons,
team bios, blog links, or anything that distracts
from the single CTA.
```

**For Test C (Crowdfunding):**

Build campaign page on Kickstarter or Indiegogo with product video (2-3 minutes), reward tiers, and stretch goals. Budget $1,000-2,000 for pre-launch ads to build an email list of 500+ before launch day. [src4]

**For Test D (Concierge MVP):**

No technology needed. Identify 5-15 target customers from your network or cold outreach. Offer to deliver the service manually for free or at heavy discount. Use email, Calendly, and Google Docs as your entire stack. [src5]

**For Test E (Wizard of Oz):**

Build a real-looking frontend (landing page + signup flow + basic dashboard) but handle all backend processing manually. The customer believes they are using automated software. You are the automation. [src5]

**Verify**: Page loads in under 3 seconds, CTA button is visible above the fold, analytics tracking fires on page load and CTA click.
**If failed**: Use Google PageSpeed Insights to diagnose load issues. Ensure analytics tag is in the page header, not footer.

### Step 3: Drive Traffic to the Test

**Duration**: 1-14 days depending on test type
**Tool**: Ad platform (Google Ads, Meta Ads) or organic channels

**Paid traffic approach (recommended for fake door and waitlist):**

```
Ad Campaign Setup:
═══════════════════════════════════════════
Platform: Google Ads (search intent) or Meta Ads (awareness)
Budget: $20-50/day for 7-14 days
Targeting:
  - Google: Keywords matching the problem your product solves
  - Meta: Interest-based targeting matching your ICP demographics

Ad Copy Formula:
  Headline: [Problem] → [Solution]
  Description: [Specific benefit] + [Social proof if available]
  CTA: "Learn More" (not "Buy Now" — you are measuring interest)

Example (B2B invoice tool):
  Headline: "Still Processing Invoices Manually?"
  Description: "Automate AP workflows in 10 minutes.
                500+ companies on waitlist."
  CTA: "Get Early Access"
═══════════════════════════════════════════

Minimum sample: 500 ad clicks or 200 page visitors
                 (whichever comes first)
```

**Organic traffic approach (free, slower):**

Post in 5-10 relevant online communities (Reddit, Hacker News, niche forums, LinkedIn groups) with a genuine ask for feedback — not a sales pitch. Share the landing page link in your bio or as a resource. Expect 2-4 weeks to reach 200+ visitors organically.

**Rate limit**: Meta Ads can take 24-48 hours to exit the learning phase. Do not judge results from the first 48 hours of any paid campaign.

**Expected output**: 200+ unique visitors with analytics data on page views, bounce rate, CTA clicks, and signups.
**Verify**: Analytics shows traffic arriving and events firing. CTR from ad to landing page should be 1-5% (if below 1%, ad copy or targeting is wrong).
**If failed**: If CTR from ad is below 1%, rewrite ad copy to be more specific about the problem. If bounce rate on landing page exceeds 80%, simplify the page and strengthen the headline.

### Step 4: Measure and Record Signals

**Duration**: Ongoing during traffic phase, 1-2 hours for final analysis
**Tool**: Analytics dashboard + spreadsheet

Track these metrics daily during the test:

```
Daily Tracking Sheet:
═══════════════════════════════════════════
Date | Visitors | CTA Clicks | Signups | CTR  | Cost
─────┼──────────┼────────────┼─────────┼──────┼──────
     |          |            |         |      |
     |          |            |         |      |
─────┼──────────┼────────────┼─────────┼──────┼──────
TOTAL|          |            |         |      |

Key Metrics:
  Click-Through Rate (CTR) = CTA Clicks / Visitors
  Signup Rate = Signups / Visitors
  Cost Per Signup = Total Ad Spend / Signups
  Cost Per Click = Total Ad Spend / CTA Clicks

Secondary Signals (qualitative):
  - Unsolicited replies to confirmation email?   Y/N
  - Users asking "when does this launch?"         Y/N
  - Users sharing the page with others?           Y/N
  - Users offering to pay for early access?       Y/N
═══════════════════════════════════════════
```

**For concierge/wizard tests, track:**

```
Customer Engagement Sheet:
═══════════════════════════════════════════
Customer | Engaged? | Completed? | NPS | Would Pay? | Amount
─────────┼──────────┼────────────┼─────┼────────────┼───────
         |          |            |     |            |
─────────┼──────────┼────────────┼─────┼────────────┼───────

Retention: Did they come back for session 2?  ___/___
Referral:  Did they refer someone else?       ___/___
WTP:       Stated willingness-to-pay average: $______
═══════════════════════════════════════════
```

**Verify**: Minimum 200 visitors (quantitative tests) or 5 completed customer engagements (qualitative tests) before drawing conclusions.
**If failed**: If you cannot reach 200 visitors in 14 days with paid traffic, your targeting is too narrow or your ad budget is too low. Double the daily spend or broaden targeting.

### Step 5: Analyze Results and Generate Recommendation

**Duration**: 1-2 hours
**Tool**: Spreadsheet

Apply your pre-defined thresholds from Step 1 to the measured data.

```
DEMAND SIGNAL REPORT
═══════════════════════════════════════════
Test Type:          _______________
Test Duration:      ___ days
Total Spend:        $______
Total Visitors:     ______
Total Signups:      ______

PRIMARY METRIC:     _______ (threshold was: _______)
SECONDARY METRICS:
  CTR:              _______%
  Signup Rate:      _______%
  Cost Per Signup:  $_______
  Qualitative signals (count of Y answers): ___/4

RECOMMENDATION:
  [ ] GO — Primary metric exceeds GO threshold.
      Demand validated. Proceed to MVP build.
  [ ] PIVOT — Between KILL and GO thresholds.
      Demand is ambiguous. Iterate on value prop,
      re-run test with refined messaging.
  [ ] KILL — Below KILL threshold.
      Insufficient demand. Explore different problem
      or different customer segment.

CONFIDENCE LEVEL:
  High (>500 visitors, clear signal)
  Medium (200-500 visitors, directional signal)
  Low (<200 visitors, insufficient data)

NEXT STEPS:
  If GO:    ___________________________________
  If PIVOT: ___________________________________
  If KILL:  ___________________________________
═══════════════════════════════════════════
```

**Verify**: Recommendation matches pre-set thresholds, not post-hoc rationalization. If the data says KILL, respect it.
**If failed**: If recommendation is ambiguous (right on the threshold), run a second test with different messaging or a different audience segment before deciding.

### Step 6: Preserve Test Artifacts for Launch

**Duration**: 30 minutes
**Tool**: File storage

Save everything — successful demand tests produce reusable assets for actual launch.

```
Archive Checklist:
  [ ] Landing page URL and screenshot
  [ ] Ad copy variants and performance data
  [ ] Email list of signups (GDPR-compliant)
  [ ] Analytics export (raw data)
  [ ] Demand Signal Report (from Step 5)
  [ ] Customer feedback quotes (concierge/wizard)
  [ ] Test page design files (Figma/Canva source)
```

**Output files**:
- `demand-signal-report.json` — Structured recommendation with all metrics
- `engagement-data.csv` — Raw daily tracking data
- `test-artifacts/` — Landing page screenshots, ad creatives, email sequences

## Output Schema

```json
{
  "output_type": "demand_signal_report",
  "format": "JSON",
  "columns": [
    {"name": "test_type", "type": "string", "description": "Which demand test was run (fake_door, waitlist, crowdfunding, concierge, wizard_of_oz)", "required": true},
    {"name": "test_duration_days", "type": "number", "description": "Number of days the test ran", "required": true},
    {"name": "total_spend", "type": "number", "description": "Total cost in USD including ad spend and tools", "required": true},
    {"name": "total_visitors", "type": "number", "description": "Unique visitors to test asset", "required": true},
    {"name": "primary_metric_value", "type": "number", "description": "Value of the primary conversion metric (CTR, signup rate, funding %, NPS, retention %)", "required": true},
    {"name": "primary_metric_threshold", "type": "number", "description": "Pre-defined GO threshold for the primary metric", "required": true},
    {"name": "recommendation", "type": "string", "description": "GO, PIVOT, or KILL based on threshold comparison", "required": true},
    {"name": "confidence_level", "type": "string", "description": "HIGH (>500 visitors), MEDIUM (200-500), LOW (<200)", "required": true},
    {"name": "cost_per_signup", "type": "number", "description": "Total spend divided by total signups", "required": false},
    {"name": "qualitative_signals", "type": "number", "description": "Count of positive qualitative signals (0-4)", "required": false}
  ],
  "expected_row_count": "1",
  "sort_order": "N/A — single row output",
  "deduplication_key": "test_type"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Fake door CTR (ad click to CTA click) | > 2% | > 5% | > 10% |
| Waitlist signup rate (visitor to email) | > 3% | > 8% | > 15% |
| Waitlist to paid conversion | > 2% | > 10% | > 20% |
| Crowdfunding goal reached | > 30% funded | > 100% funded | > 200% funded |
| Concierge NPS score | > 30 | > 50 | > 70 |
| Wizard of Oz week-2 retention | > 20% | > 40% | > 60% |
| Sample size (quantitative) | 200 visitors | 500 visitors | 1,000+ visitors |
| Sample size (qualitative) | 5 customers | 10 customers | 15+ customers |

**If below minimum**: Do not interpret as demand failure yet. First check: (1) was the headline clear about the problem being solved? (2) was traffic targeted to the right audience? (3) was the CTA specific and low-friction? If all three are yes and metrics are still below minimum, demand is likely insufficient. [src6]

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Zero ad clicks after 48 hours | Ad rejected, targeting too narrow, or bid too low | Check ad approval status, broaden audience by 2x, increase bid to suggested range |
| High bounce rate (>85%) on landing page | Slow load time, headline mismatch with ad copy, or mobile rendering broken | Run PageSpeed test, ensure headline matches ad promise exactly, test on mobile device |
| High signups but zero responses to follow-up email | Email going to spam, or signup was low-intent (curiosity clicks) | Check sender reputation with mail-tester.com, add double opt-in, improve email subject line |
| Crowdfunding stalls after day 3 | No pre-launch audience, middle-of-campaign slump is normal | Activate press outreach, post updates, email your pre-launch list again — most campaigns follow a U-curve |
| Concierge customers ghost after first session | Value was unclear or delivery was too manual/slow | Send a brief survey asking why, simplify the offering, reduce time-to-value in next session |
| Conflicting data (high CTR but low signup) | Friction in signup flow or asking for too much information | Reduce form to email-only, remove all optional fields, test single-field signup |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| Landing page builder | Carrd ($0), Framer free | Unbounce ($99/mo), Webflow ($16/mo) | N/A — single page needed |
| Analytics | Google Analytics ($0), PostHog ($0) | Mixpanel ($28/mo) | N/A |
| Ad spend (fake door/waitlist) | $0 (organic only) | $200-500 per test | $1,000-2,000 per test |
| Ad spend (crowdfunding pre-launch) | $0 (organic) | $1,000-2,000 | $3,000-5,000 |
| Email tool | Mailchimp free (500 contacts) | ConvertKit ($29/mo) | N/A |
| Crowdfunding platform fee | N/A | 5-8% of funds raised | 5-8% of funds raised |
| **Total for one demand test** | **$0** | **$200-1,000** | **$1,000-5,000** |

## Anti-Patterns

### Wrong: Running a fake door test and declaring demand validated from clicks alone
A 10% click-through rate on a "Start Free Trial" button means people are curious, not that they will pay. Clicks measure interest, not commitment. Flexport's founder validated with 300 company signups to a completely fake product — but the signal was that companies filled out detailed onboarding forms, not just that they clicked. [src1]

### Correct: Layer commitment depth into every test
After the initial click, add a second action: email signup, survey completion, payment info, or scheduling a call. Each additional step filters for real intent. A 10% CTR that drops to 0.5% on email signup is a very different signal than 10% CTR with 3% email signup.

### Wrong: Interpreting waitlist size as demand validation
100,000 waitlist signups is a vanity metric. The critical number is what percentage convert to active users when invited. Timing matters enormously — conversion averages approximately 50% if access is granted within a month but drops below 20% after three months. [src3]

### Correct: Measure waitlist-to-active conversion within a 30-day window
Invite waitlist users in cohorts and measure activation rate per cohort. If you cannot grant access within 30 days, keep the waitlist warm with weekly updates showing progress.

### Wrong: Launching a crowdfunding campaign without a pre-launch audience
Cold launches on Kickstarter almost always fail. The platform's algorithm rewards early momentum — campaigns that hit 30% of goal in the first 48 hours get featured, creating a virtuous cycle. Without a pre-built email list, you miss this window. [src4]

### Correct: Build a 500+ email list before pressing launch
Spend 4-6 weeks before campaign launch running landing page ads that collect emails. On launch day, email the entire list with a direct link. First 48 hours determine campaign trajectory.

## When This Matters

Use this recipe when a founder or agent needs to produce quantified evidence of customer demand before committing to building a product. It replaces gut feelings and anecdotal interest with structured, measurable signals. The output directly feeds into MVP planning (if GO), pivot strategy (if PIVOT), or idea retirement (if KILL). Requires a product concept and target customer profile as input — run the idea structuring template first if these do not exist.

## Related Units

- [Startup Idea Structuring Template](/business/startup-planning/startup-idea-structuring-template/2026) — prerequisite: defines the product concept this test validates
- [Customer Interview Design](/business/customer-validation/customer-interview-design/2026) — qualitative complement to quantitative demand signals
- [MVP Development Playbook](/business/startup-planning/mvp-development-playbook/2026) — next step after demand is validated (GO recommendation)
- [Startup Financial Model Template](/business/startup-finance/startup-financial-model-template/2026) — uses demand data to build revenue projections