--- # === IDENTITY === id: business/startup/idea-validation-playbook/2026 canonical_question: "How do I actually validate a startup idea — run problem interviews, test willingness to pay, and build an MVP experiment?" aliases: - "startup idea validation step by step" - "how to test a business idea before building" - "problem interview to MVP test execution guide" - "lean validation methodology for startups" - "customer discovery interview to pre-sale pipeline" entity_type: execution_recipe domain: business > startup > Idea Validation Playbook region: global jurisdiction: global temporal_scope: 2024-2026 # === VERIFICATION === last_verified: 2026-03-11 confidence: 0.90 version: 2.0 first_published: 2026-03-10 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "AI-assisted validation tools (IdeaProof, Dovetail AI) reduced interview synthesis time by 60% in 2025; no-code landing page tools now include built-in A/B testing" next_review: 2026-09-07 change_sensitivity: high # === CONSTRAINTS === constraints: - "Problem interviews require minimum 15 conversations — smaller sample sizes produce pattern noise, not signal" - "Never pitch your solution during problem interviews — this contaminates all downstream data" - "MVP experiments must measure actual behavior (signups, payments, usage) not stated intent — 60-80% of verbal purchase intent never converts" - "Total validation timeline is 3-6 weeks — compressing below 2 weeks means insufficient interview count" - "Validation budget should stay under $2,000 — spending more means you crossed into product development" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs a strategic plan, not execution steps" use_instead: "business/startup/startup-launch-checklist/2026" - condition: "User has already validated demand and needs to build MVP" use_instead: "business/startup/mvp-scoping-framework/2026" - condition: "User already has paying customers and needs growth strategy" use_instead: "Search knowledgelib.io for post-PMF growth strategy — no dedicated unit yet" # === AGENT HINTS === inputs_needed: - key: tool_preference question: "Which landing page tool should be used for MVP testing?" type: choice options: ["Carrd", "Webflow", "Framer", "no preference — auto-select"] - 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 validation budget?" type: choice options: ["free tier only ($0)", "lean ($100-$500)", "standard ($500-$2,000)"] - key: target_market question: "Who is the target customer?" type: choice options: ["B2B — businesses or professionals", "B2C — individual consumers", "marketplace — connecting two sides", "developer tools — technical users"] # === EXECUTION METADATA === execution: required_inputs: - name: "Problem hypothesis" source: "Founder brainstorming or market observation" format: "document" - name: "Target customer profile" source: "Founder domain knowledge or initial research" format: "structured data" outputs: - name: "Validation decision document" format: "document" description: "Go/pivot/stop decision with supporting evidence from interviews, solution tests, and MVP experiment data" - name: "Interview synthesis database" format: "spreadsheet" description: "Pain point rankings, customer segments, willingness-to-pay data, and behavioral commitment records" - name: "MVP experiment results" format: "CSV" description: "Conversion metrics, traffic sources, signup/payment data, and channel performance" tools_required: - name: "Calendly" purpose: "Interview scheduling" tier: "free" cost: "$0 (free tier: unlimited 1-on-1 meetings)" alternatives: ["Cal.com (open source)", "Google Calendar direct"] - name: "Google Meet / Zoom" purpose: "Video interviews + recording" tier: "free" cost: "$0 (free tier: 40-60 min meetings)" alternatives: ["Riverside.fm", "Around"] - name: "Carrd / Webflow" purpose: "Landing page MVP test" tier: "free" cost: "$0-$16/mo" alternatives: ["Framer ($0-$15/mo)", "Typedream"] - name: "Stripe" purpose: "Pre-sale payment collection" tier: "paid" cost: "2.9% + $0.30 per transaction" alternatives: ["LemonSqueezy", "Gumroad"] - name: "PostHog / Microsoft Clarity" purpose: "Landing page analytics and heatmaps" tier: "free" cost: "$0 (free tier: 1M events/mo)" alternatives: ["Google Analytics 4", "Plausible"] - name: "Dovetail / Google Sheets" purpose: "Interview note synthesis and pattern analysis" tier: "free" cost: "$0 (Sheets) or $29/mo (Dovetail)" alternatives: ["Notion", "Airtable"] credentials_needed: - service: "Calendly" type: "OAuth" where_to_get: "https://calendly.com/signup" free_tier_limits: "Unlimited 1-on-1 meetings, 1 event type" - service: "Stripe" type: "API key" where_to_get: "https://dashboard.stripe.com/register" free_tier_limits: "No monthly fee — pay per transaction only" - service: "PostHog" type: "API key" where_to_get: "https://app.posthog.com/signup" free_tier_limits: "1M events/month, session recordings" estimated_duration: "3-6 weeks" estimated_cost: "$0 (free tier) to $2,000 (standard)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/startup/idea-validation-playbook/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)" # === RELATED UNITS === related_kos: depends_on: [] feeds_into: - id: "business/startup/mvp-scoping-framework/2026" label: "MVP scoping after validation confirms demand" - id: "business/startup/legal-formation-playbook/2026" label: "Legal formation after committing to build" related_to: - id: "business/startup/startup-launch-checklist/2026" label: "Full launch recipe that incorporates validation as Step 1" alternative_to: [] # === SOURCES === sources: - id: src1 title: "Startup Validation Framework 2026: How to Test Ideas Fast" author: Presta url: https://wearepresta.com/startup-validation-framework-2026-the-ultimate-guide-to-testing-ideas/ type: industry_report published: 2026-01-15 reliability: high - id: src2 title: "MVP Testing in 2026: What to Validate First" author: Valtorian url: https://www.valtorian.com/blog/mvp-testing-2026 type: industry_report published: 2026-01-01 reliability: high - id: src3 title: "Testing Business Ideas: Book Summary and Key Takeaways" author: Strategyzer url: https://www.strategyzer.com/library/testing-business-ideas-book-summary type: official_docs published: 2024-06-01 reliability: authoritative - id: src4 title: "10 Proven Methods to Validate a Startup Idea in 2025" author: The Startupgenic url: https://thestartupgenic.com/10-proven-methods-to-validate-a-startup-idea/ type: industry_report published: 2025-06-01 reliability: high - id: src5 title: "How to Validate Any Startup Idea in 90 Days" author: Lean Foundry url: https://www.leanfoundry.com/lean-1-2-3/jul-31-2025 type: industry_report published: 2025-07-31 reliability: high - id: src6 title: "Roadmap to Test Your Value Proposition" author: Strategyzer url: https://www.strategyzer.com/library/roadmap-to-test-your-value-proposition type: official_docs published: 2024-01-01 reliability: authoritative - id: src7 title: "How to Validate Your Startup Idea Before Writing Code" author: BuildMVPFast url: https://www.buildmvpfast.com/blog/how-to-validate-your-startup-idea type: industry_report published: 2025-04-01 reliability: high --- # Idea Validation Recipe: Problem Interviews to MVP Experiment ## Purpose This recipe produces a validated go/pivot/stop decision for a startup idea — backed by 15-25 problem interviews, solution willingness-to-pay data, and behavioral MVP experiment results — within 3-6 weeks at $0-$2,000. It outputs a structured interview synthesis, customer segment ranking, and conversion metrics that feed directly into MVP scoping and launch planning. [src1] ## Prerequisites - [ ] **Problem hypothesis** — "I believe [audience] struggles with [problem]" (can be rough) - [ ] **Target customer profile** — Identify 30+ reachable prospects (LinkedIn, communities, personal network) - [ ] **Calendly account** — Free tier at [calendly.com](https://calendly.com/signup) for scheduling - [ ] **Video conferencing** — Google Meet, Zoom, or similar (free tier sufficient) - [ ] **Spreadsheet** — Google Sheets or Notion for tracking interview data - [ ] **10-20 hours/week available** over 3-6 weeks for interviews and analysis ## Constraints - Minimum 15 problem interviews required before moving to solution testing — fewer produces unreliable signal. [src1] - Never pitch your solution during problem interviews — ask about their life, not your idea. Contaminated interviews must be discarded. [src7] - Weight behavior over words in all phases — "I'd definitely buy that" without a pre-order is a polite no. 60-80% of stated purchase intent never converts. [src4] - MVP experiment must run for minimum 7 days with 200+ visitors for statistically meaningful conversion data. [src2] - If validation fails at any gate, the correct action is pivot or stop — not "try harder with the same idea." [src3] ## Tool Selection Decision ``` Which path? ├── User is non-technical AND budget = $0 │ └── PATH A: Free Manual — Calendly + Google Meet + Google Sheets + Carrd Free ├── User is non-technical AND budget > $0 │ └── PATH B: No-Code Paid — Calendly + Zoom + Webflow + Stripe + PostHog ├── User is semi-technical AND budget = $0 │ └── PATH C: Semi-Technical Free — Cal.com + Google Meet + Carrd + PostHog Free └── User is developer AND budget > $0 └── PATH D: Full Stack — Calendly + Zoom + Custom landing page + Stripe + PostHog ``` | Path | Tools | Cost | Speed | Output Quality | |------|-------|------|-------|---------------| | A: Free Manual | Calendly, Meet, Sheets, Carrd | $0 | 4-6 weeks | Good — covers all phases with manual effort | | B: No-Code Paid | Calendly, Zoom, Webflow, Stripe, PostHog | $100-$500 | 3-5 weeks | High — professional landing page + payment test | | C: Semi-Tech Free | Cal.com, Meet, Carrd, PostHog | $0 | 3-5 weeks | Good — open-source tools + analytics | | D: Full Stack | Calendly, Zoom, custom LP, Stripe, PostHog | $200-$2,000 | 3-4 weeks | Excellent — custom MVP + full analytics | ## Execution Flow ### Step 1: Map Assumptions and Define Hypotheses **Duration**: 2-4 hours **Tool**: Google Sheets or Notion Write 5-10 core assumptions about the business: who the customer is, what problem they face, how often it occurs, how they currently solve it, and how much they spend on current solutions. Rank assumptions by risk — which ones, if wrong, kill the idea? Convert the top 5 riskiest assumptions into testable hypotheses with explicit pass/fail criteria. [src3] ``` Hypothesis template: "We believe [customer segment] has [problem] at [frequency]. We'll know this is true when [X] of [Y] interviewees confirm [specific behavior]." Example: "We believe SaaS founders spend 5+ hours/week on manual customer onboarding. We'll know this is true when 10 of 15 interviewees describe manual onboarding as a top-3 pain." ``` Plot assumptions on Strategyzer's evidence-impact matrix: high-impact + low-evidence assumptions get tested first. [src3] **Verify**: 5+ hypotheses documented with specific pass/fail thresholds **If failed**: If you cannot articulate 5 testable assumptions, spend 2 hours on competitor research and customer community lurking first ### Step 2: Recruit Interview Subjects (30-50 Prospects) **Duration**: 3-5 days **Tool**: LinkedIn, Slack/Discord communities, Reddit, personal network Identify 30-50 people matching the target customer profile. Source from LinkedIn (filter by role/industry), relevant Slack or Discord communities, subreddit communities, and personal network. Send short outreach: "I'm researching [topic] and would love 20 minutes of your time to understand your experience." Offer $25-$50 gift cards for B2B or coffee for consumer interviews (optional but improves response rates from 10% to 25%). [src1] ``` Outreach template (B2B): Subject: Quick question about [domain] Body: Hi [Name], I'm researching how [role] teams handle [problem area]. Would you have 20 minutes this week for a quick call? No pitch — just trying to understand workflows. Happy to share findings afterward. Target: Schedule 15-25 interviews within 5 days ``` **Verify**: 15+ interviews scheduled within 7 days **If failed**: If you cannot recruit 15 in a week, your target audience may be too narrow or hard to reach — this is a validation signal. Broaden the customer profile or try paid user research platforms (Respondent.io, UserTesting) at $50-$100/participant. [src5] ### Step 3: Conduct Problem Interviews (15-25 Conversations) **Duration**: 1-2 weeks **Tool**: Zoom/Google Meet (recording), Google Sheets (tracking) Use the Mom Test methodology: ask about their life, not your idea. Listen 80%, talk 20%. Never pitch, never lead, never suggest. Record with consent and take structured notes: pain intensity (1-10), frequency, current solutions, money spent, and emotional language. [src7] ``` Core interview questions (30 min format): 1. "What's the hardest part about [domain]?" (open-ended, let them talk) 2. "Tell me about the last time you dealt with [problem]" (specific recent behavior) 3. "What have you tried to solve it?" (current alternatives reveal pain intensity) 4. "How much time/money do you spend on this?" (quantifies the problem) 5. "If you could wave a magic wand, what would change?" (aspirational outcome) Tracking columns: Name | Date | Pain (1-10) | Frequency | Current Solution | Spend | Key Quotes ``` After each batch of 5 interviews, update the assumption map. Look for convergence: are 3+ people describing the same pain unprompted? After 15 interviews, synthesize patterns into a pain point ranking and customer segment map. [src5] **Verify**: 10+ interviewees independently confirm the same pain point; clear pattern in top 3 problems; at least one segment shows pain intensity 7+/10 and weekly+ frequency **If failed**: If mixed signals after 20+ interviews, narrow the customer segment and recruit 10 more from a tighter profile. If no consistent problem emerges after 25 interviews, pivot the hypothesis or stop. ### Step 4: Design and Test Solution Concept (10-15 Solution Interviews) **Duration**: 1-2 weeks **Tool**: Figma/Balsamiq (mockup), Zoom (calls), Google Sheets (tracking) Design a solution concept addressing the #1 validated pain point. Create a visual: wireframe, mockup, slide deck, or detailed written description. Define 2-3 pricing tiers to test — anchor high, customers negotiate down. [src6] Present the problem back first: "We found that [problem] is the biggest pain — is that true for you?" Then show the solution and push for commitment. Track two categories of response: [src5] ``` Strong signals (behavioral): Weak signals (verbal): - Puts down a deposit - "That sounds cool" - Pre-orders or pre-pays - "I'd definitely use that" - Gives detailed feature request - "Send me more info" - Introduces you to decision-maker - "Keep me posted" - Asks "when can I get this?" - "Interesting concept" Scoring: Strong signal = 1 point, Weak signal = 0 points Target: 30%+ of subjects score 1+ point ``` Run competitive positioning check in parallel: ask "How does this compare to [competitor]?" and "What would make you switch?" [src6] **Verify**: 30%+ express concrete willingness to pay (deposit, pre-order, or strong behavioral commitment); 5+ agree to beta test; clear positioning wedge articulated **If failed**: If interest is high but willingness to pay is low, test different pricing models or value framing. If <20% express any interest, return to Step 3 findings and redesign the solution concept. ### Step 5: Build and Launch MVP Experiment **Duration**: 3-7 days build + 1-2 weeks run **Tool**: Carrd/Webflow (landing page), Stripe (payments), PostHog (analytics) Choose experiment type based on validation goals: [src4] ``` Experiment selection: ├── Need to test demand broadly? │ └── Landing page + email signup (any business model) ├── Need to test willingness to pay? │ └── Pre-sale page with Stripe checkout ($X deposit) ├── Need to test service delivery? │ └── Concierge MVP — manually deliver to 3-5 customers ├── Need to test feature interest? │ └── Fake door test — button that measures clicks └── Need to test full workflow? └── Wizard of Oz — looks automated, runs manually ``` Build the landing page in 1-3 days (not weeks). Include: one-sentence value prop, 3 benefit bullets, clear CTA (signup/pre-order), and social proof from interviews. Set up PostHog or Clarity for analytics. Drive 200-500 targeted visitors from communities identified in Step 3, cold outreach, and optional paid ads ($5-$10/day). [src1] **Verify**: Landing page live with analytics tracking; 200+ unique visitors within 7-14 days; conversion data collecting **If failed**: If <100 visitors after 7 days, invest $50-$100 in targeted ads (Google Ads on problem keywords, or Reddit/LinkedIn). If landing page tool fails, switch to alternative (Carrd to Webflow or vice versa). ### Step 6: Analyze Results and Make Go/Pivot/Stop Decision **Duration**: 2-3 days **Tool**: Google Sheets (analysis), PostHog (metrics) Calculate conversion metrics against benchmarks and cross-reference with qualitative data from Steps 3-4. Combine all evidence into a single decision matrix. [src2] ``` Decision framework: ┌─────────────────────────────────┬──────────┬──────────┬──────────┐ │ Signal │ Stop │ Pivot │ Go │ ├─────────────────────────────────┼──────────┼──────────┼──────────┤ │ Problem interview pain score │ <5/10 │ 5-7/10 │ 7+/10 │ │ Problem pattern clarity │ No pattern│ Emerging │ 10+ same │ │ Solution WTP rate │ <10% │ 10-30% │ >30% │ │ Beta pre-commitments │ 0-1 │ 2-4 │ 5+ │ │ Landing page email conversion │ <2% │ 2-5% │ >5% │ │ Pre-sale conversion (if tested) │ 0 │ 1-2 │ 3+ │ │ Paid traffic CPC │ >$5 │ $2-$5 │ <$2 │ └─────────────────────────────────┴──────────┴──────────┴──────────┘ Scoring: 5+ "Go" signals = proceed to build 3+ "Pivot" signals = adjust hypothesis and re-test 3+ "Stop" signals = abandon this idea ``` Do not cherry-pick positive signals. If the overall pattern is weak, the honest answer is pivot or stop — false positives here cost months of building. [src3] **Verify**: Decision document completed with supporting evidence from all three phases; strongest acquisition channel identified; customer segment ranked by conversion **If failed**: If evidence is genuinely ambiguous after 3-6 weeks, extend by 1-2 weeks with tighter customer segment. If still ambiguous, treat as a "stop" — ambiguity at this scale means the signal is too weak. ## Output Schema ```json { "output_type": "validation_decision_package", "format": "document collection", "columns": [ {"name": "decision", "type": "string", "description": "Go, Pivot, or Stop with reasoning", "required": true}, {"name": "problem_validated", "type": "boolean", "description": "Whether problem interviews confirmed the pain", "required": true}, {"name": "top_pain_point", "type": "string", "description": "Highest-ranked pain from interview synthesis", "required": true}, {"name": "target_segment", "type": "string", "description": "Best-fit customer segment with profile details", "required": true}, {"name": "wtp_rate", "type": "number", "description": "Willingness-to-pay rate from solution interviews", "required": true}, {"name": "mvp_conversion_rate", "type": "number", "description": "Landing page or pre-sale conversion rate", "required": true}, {"name": "best_channel", "type": "string", "description": "Highest-performing acquisition channel tested", "required": true}, {"name": "interviews_completed", "type": "number", "description": "Total problem + solution interviews conducted", "required": true}, {"name": "pre_commitments", "type": "number", "description": "Beta signups, deposits, or pre-orders collected", "required": true} ], "expected_row_count": "1 (single validation decision)", "sort_order": "N/A", "deduplication_key": "problem_hypothesis + target_segment" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Problem interviews completed | 15 | 20 | 25+ | | Problem pattern clarity | 3+ describe same pain | 7+ describe same pain | 10+ unprompted | | Willingness-to-pay rate | >20% | >30% | >50% | | Beta pre-commitments | 3 | 5-10 | 10+ | | Landing page conversion (email) | >3% | >5% | >10% | | Pre-sale conversion (if tested) | 1 order | 3+ orders | 10+ orders | | Data completeness (interview notes) | >70% fields | >85% fields | >95% fields | **If below minimum**: Re-run Steps 2-3 with broader customer segment. If problem interviews are below 15, recruit more before proceeding — do not skip to MVP testing with insufficient data. [src5] ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Cannot recruit 15 interviewees in 7 days | Target audience too narrow or hard to reach | Broaden customer profile; try Respondent.io ($50-$100/participant); post in 3+ communities | | All interviewees are polite but describe no real pain | Problem hypothesis is wrong | Pivot: ask "what IS painful?" and let them lead; update hypothesis based on what emerges | | High verbal interest but zero pre-commitments | Solution does not justify switching cost | Redesign value proposition; test 10x lower price or freemium; test different customer segment | | Landing page <2% conversion after 500+ visitors | Value prop or messaging mismatch | A/B test headline and CTA; try different audience targeting; simplify to single benefit | | Zero traffic to landing page | Wrong distribution channels | Switch from organic to paid ($50 test budget); post in different communities; try cold outreach | | Stripe setup fails or payment form errors | Configuration issue | Test in Stripe test mode first; verify webhook URLs; use LemonSqueezy as fallback | | Analytics not tracking | PostHog snippet not firing | Check browser console for errors; verify script placement before ``; test with Clarity as backup | ## Cost Breakdown | Component | Free ($0) | Lean ($500) | Standard ($2,000) | |-----------|-----------|-------------|-------------------| | Interview incentives | $0 (goodwill) | $200 (gift cards) | $500 (gift cards + meals) | | Design/mockup tools | $0 (Figma free) | $0 (Figma free) | $50 (Figma Pro) | | Landing page | $0 (Carrd free) | $16 (Carrd Pro/mo) | $50 (Webflow + domain) | | Payment processing | $0 (skip pre-sale) | $0 (Stripe per-txn) | $0 (Stripe per-txn) | | Paid traffic testing | $0 (organic only) | $100 (7-day test) | $500 (14-day multi-channel) | | Analytics | $0 (PostHog free) | $0 (PostHog free) | $50 (Hotjar Pro) | | User research platform | $0 (DIY recruiting) | $100 (Respondent.io) | $500 (Respondent.io batch) | | Contingency | $0 | $84 | $350 | | **Total** | **$0** | **$500** | **$2,000** | **Constraint**: Spending more than $2,000 on validation means you crossed into product development. Pull back and evaluate what you are actually testing. [src1] ## Anti-Patterns ### Wrong: Asking friends and family if your idea is good Friends and family optimize for preserving the relationship, not giving honest feedback. The Mom Test exists because your mom will never tell you your idea is bad. Interview strangers who match your target customer profile — they have no social incentive to be polite. [src7] ### Correct: Use behavioral questions with strangers Ask "Tell me about the last time you dealt with [problem]" — not "Would you buy my product?" If they light up describing the pain and show you workarounds they built, the signal is real. [src5] ### Wrong: Building the product first, then looking for customers 42% of failed startups cite "no market need" as the primary cause. Building first means you cannot change direction without losing months of work and thousands of dollars. [src4] ### Correct: Validate before building — 3-6 weeks saves 3-6 months A $0-$2,000 validation process that takes 3-6 weeks is the cheapest insurance policy in entrepreneurship. Even if validation fails, you saved months. [src1] ### Wrong: Treating verbal interest as validation "That sounds cool, I'd definitely use that" means nothing without behavioral commitment. Studies show 60-80% of stated purchase intent never converts. Pre-orders, deposits, and detailed feature requests are real signals. Polite enthusiasm is not. [src4] ### Correct: Require concrete commitment at every stage Define a commitment ladder: Phase 1 = time commitment (interview), Phase 2 = social commitment (introduction to colleague), Phase 3 = financial commitment (deposit or pre-order). Each phase requires a stronger signal. [src3] ## When This Matters Use when a founder or agent needs to execute a structured idea validation — run the interviews, build the landing page, collect the data, and make the decision. Not a document about how to think about validation, but the actual execution steps. Requires a problem hypothesis as input; produces a validated go/pivot/stop decision as output. ## Related Units - [Startup Launch Checklist](/business/startup/startup-launch-checklist/2026) — full launch recipe that incorporates validation as Step 1 - [MVP Scoping Framework](/business/startup/mvp-scoping-framework/2026) — feature prioritization after validation confirms demand - [Legal Formation Playbook](/business/startup/legal-formation-playbook/2026) — entity formation after committing to build - [Financial Model Template Library](/business/startup/financial-model-template-library/2026) — financial modeling for fundraising