Every successful product started with validation. Every failed product skipped it.
The difference between a $100M company and a expensive hobby project often comes down to one thing: systematic validation before building. Yet most founders spend 6+ months building products nobody wants because they assumed they understood the market.
This guide presents a complete, battle-tested validation framework used by Y Combinator startups, Fortune 500 innovation teams, and solo entrepreneurs alike. By the end, you'll have a systematic process to test any product idea with confidence.
📑 Table of Contents
- Why Frameworks Beat Gut Instinct
- The 6-Stage Validation Framework Overview
- Stage 1: Problem Validation
- Stage 2: Solution Validation
- Stage 3: Market Validation
- Stage 4: Channel Validation
- Stage 5: Revenue Validation
- Stage 6: Scale Validation
- Validation Methods Library
- Evidence Quality Scoring
- Go/No-Go Decision Framework
- Framework Templates & Tools
- Case Studies: Framework in Action
- Common Validation Mistakes
- FAQ
- Summary & Action Steps
Why Frameworks Beat Gut Instinct {#why-frameworks-beat-gut-instinct}
🧠 The Problem with Intuition
Founders are notoriously overconfident about their ideas:
┌─────────────────────────────────────────────────────────────────────┐
│ FOUNDER CONFIDENCE vs REALITY │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ What founders believe: │
│ ├── "I understand the problem perfectly" (Usually wrong) │
│ ├── "Customers will definitely pay for this" (Often wrong) │
│ ├── "Nobody else is solving this well" (Rarely true) │
│ └── "I just need to build it and they'll come" (Almost never) │
│ │
│ What data shows: │
│ ├── 42% of startups fail due to no market need │
│ ├── 72% of new products fail to meet revenue expectations │
│ ├── Avg founder spends 18 months on failed products │
│ └── 90% of ideas change significantly during validation │
│ │
└─────────────────────────────────────────────────────────────────────┘
📊 Why Structured Frameworks Work
| Approach | Success Rate | Time to Learn | Avg Cost |
|---|---|---|---|
| Gut instinct | 8-12% | 12-18 months | $50K-$500K |
| Informal validation | 15-25% | 6-12 months | $20K-$100K |
| Structured framework | 35-50% | 2-4 months | $2K-$20K |
| Framework + iteration | 50-70% | 4-8 months | $5K-$30K |
A framework provides: - ✅ Systematic bias reduction - ✅ Clear decision criteria - ✅ Documented evidence trail - ✅ Faster pivots when needed - ✅ Team alignment on assumptions - ✅ Investor-ready validation story
The 6-Stage Validation Framework {#the-6-stage-validation-framework}
🎯 Framework Overview
┌─────────────────────────────────────────────────────────────────────────────┐
│ THE 6-STAGE VALIDATION FRAMEWORK │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ Stage 1 Stage 2 Stage 3 Stage 4 │
│ PROBLEM → SOLUTION → MARKET → CHANNEL │
│ ┌───────┐ ┌───────┐ ┌───────┐ ┌───────┐ │
│ │ Pain │ │ Fix │ │ Size │ │ Reach │ │
│ │ Real? │ │ Work? │ │ Big? │ │ Work? │ │
│ └───────┘ └───────┘ └───────┘ └───────┘ │
│ │ │ │ │ │
│ ▼ ▼ ▼ ▼ │
│ "Do people "Does our "Is there "Can we │
│ have this solution enough reach them │
│ problem?" work?" demand?" efficiently?" │
│ │
│ Stage 5 Stage 6 │
│ REVENUE → SCALE │
│ ┌───────┐ ┌───────┐ │
│ │ Pay │ │ Grow │ │
│ │ Work? │ │ Work? │ │
│ └───────┘ └───────┘ │
│ │ │ │
│ ▼ ▼ │
│ "Will they "Can we │
│ pay?" scale it?" │
│ │
├─────────────────────────────────────────────────────────────────────────────┤
│ KEY PRINCIPLE: Each stage must reach threshold before proceeding │
│ KILL CRITERIA: Failing any stage → Pivot or abandon │
│ EVIDENCE: Document everything for pattern recognition │
└─────────────────────────────────────────────────────────────────────────────┘
📋 Stage Thresholds Summary
| Stage | Key Question | Minimum Evidence | Typical Duration |
|---|---|---|---|
| 1. Problem | Is the pain real? | 20+ interviews, 80%+ confirm | 2-3 weeks |
| 2. Solution | Does it solve the problem? | 10+ users test, 60%+ succeed | 2-4 weeks |
| 3. Market | Is the market big enough? | TAM >$100M, SAM >$10M | 1-2 weeks |
| 4. Channel | Can we reach them? | 2+ channels <$50 CAC | 2-4 weeks |
| 5. Revenue | Will they pay enough? | 5+ paying customers | 2-4 weeks |
| 6. Scale | Can we grow profitably? | Unit economics positive | 4-8 weeks |
🔄 The Validation Loop
Each stage follows the same pattern:
┌─────────────────────────────────────────────────────────────────┐
│ THE VALIDATION LOOP │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────┐ │
│ │ 1. ASSUME │ ← State your hypothesis clearly │
│ └──────┬───────┘ │
│ │ │
│ ▼ │
│ ┌──────────────┐ │
│ │ 2. DESIGN │ ← Design smallest test possible │
│ └──────┬───────┘ │
│ │ │
│ ▼ │
│ ┌──────────────┐ │
│ │ 3. TEST │ ← Run the experiment │
│ └──────┬───────┘ │
│ │ │
│ ▼ │
│ ┌──────────────┐ │
│ │ 4. MEASURE │ ← Collect quantitative data │
│ └──────┬───────┘ │
│ │ │
│ ▼ │
│ ┌──────────────┐ │
│ │ 5. LEARN │ ← Extract insights │
│ └──────┬───────┘ │
│ │ │
│ ▼ │
│ ┌──────────────┐ │
│ │ 6. DECIDE │ ← Proceed, pivot, or kill │
│ └──────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
Stage 1: Problem Validation {#stage-1-problem-validation}
🎯 Goal
Confirm that real people have the problem you think they have, and it's painful enough to solve.
┌─────────────────────────────────────────────────────────────────┐
│ PROBLEM VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Your assumption about a customer problem │
│ OUTPUT: Validated (or invalidated) problem statement │
│ │
│ KEY QUESTIONS: │
│ ├── Does this problem actually exist? │
│ ├── How frequently does it occur? │
│ ├── How painful is it (scale 1-10)? │
│ ├── Are people actively trying to solve it? │
│ └── Will they pay to solve it? │
│ │
│ SUCCESS CRITERIA: │
│ ├── 80%+ of target users confirm the problem │
│ ├── Average pain score 7+/10 │
│ ├── 50%+ have tried to solve it before │
│ └── 30%+ have spent money on solutions │
│ │
└─────────────────────────────────────────────────────────────────┘
📝 Problem Hypothesis Template
Before any research, document your assumptions:
## Problem Hypothesis
**Target Customer:** [WHO specifically has this problem?]
**Problem Statement:** [WHAT is the problem in their words?]
**Current Behavior:** [HOW are they solving it now?]
**Frequency:** [HOW often do they face this?]
**Severity:** [HOW much does it cost them?]
**Trigger:** [WHEN does this problem occur?]
### Assumptions to Test:
1. [Assumption about who has the problem]
2. [Assumption about problem severity]
3. [Assumption about current solutions]
4. [Assumption about willingness to pay]
### Kill Criteria:
- If <60% confirm problem exists → Kill/Pivot
- If avg pain <5/10 → Consider pivoting
- If 0% have tried to solve → Validate motivation
🎤 Customer Interview Framework
The Mom Test Rules: 1. Talk about their life, not your idea 2. Ask about specifics in the past, not hypotheticals 3. Talk less, listen more 4. Look for emotion and behavior, not opinions
Problem Discovery Questions:
| Phase | Questions |
|---|---|
| Context | "Walk me through your day when you're [doing relevant task]" |
| "What's the hardest part of [problem area]?" | |
| Specifics | "Tell me about the last time this happened" |
| "What did you do? What happened next?" | |
| Pain | "How did that make you feel?" |
| "What did it cost you (time/money/stress)?" | |
| Behavior | "What have you tried to solve this?" |
| "Why did/didn't that work?" | |
| Commitment | "Would you pay to solve this? How much?" |
| "If I built X, would you use it today?" |
📊 Problem Validation Scorecard
Rate each interview:
| Signal | Score | Criteria |
|---|---|---|
| Problem Exists | 0-3 | 0=No, 1=Maybe, 2=Yes, 3=Definitely |
| High Frequency | 0-3 | 0=Rare, 1=Monthly, 2=Weekly, 3=Daily |
| High Pain | 0-3 | 0=Annoying, 1=Frustrating, 2=Painful, 3=Urgent |
| Active Solutions | 0-3 | 0=Nothing, 1=Workarounds, 2=Competitors, 3=Spending $ |
| Willing to Pay | 0-3 | 0=No, 1=Maybe, 2=Likely, 3=Name price |
Scoring: - 12-15: 🟢 Strong validation - proceed - 8-11: 🟡 Moderate - dig deeper - 4-7: 🟠 Weak - consider pivot - 0-3: 🔴 No validation - kill or major pivot
✅ Stage 1 Checklist
- [ ] Problem hypothesis documented
- [ ] 20+ target customer interviews completed
- [ ] Interview notes captured and analyzed
- [ ] Problem scorecard calculated
- [ ] Pain points ranked by frequency and severity
- [ ] Current solutions mapped
- [ ] Willingness to pay assessed
- [ ] Go/No-go decision documented
Related guide: Product Idea Research for in-depth research methodology.
Stage 2: Solution Validation {#stage-2-solution-validation}
🎯 Goal
Prove your proposed solution actually solves the validated problem.
┌─────────────────────────────────────────────────────────────────┐
│ SOLUTION VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Validated problem + proposed solution concept │
│ OUTPUT: Evidence that solution solves the problem │
│ │
│ KEY QUESTIONS: │
│ ├── Does our solution address the core problem? │
│ ├── Can users accomplish their goal with it? │
│ ├── Is it 10x better than current alternatives? │
│ ├── Do users understand how to use it? │
│ └── Would users switch from current solution? │
│ │
│ SUCCESS CRITERIA: │
│ ├── 60%+ complete core task successfully │
│ ├── 70%+ say it solves their problem │
│ ├── Net Promoter Score > 40 │
│ └── 50%+ prefer it to current solution │
│ │
└─────────────────────────────────────────────────────────────────┘
🛠️ Solution Validation Methods
Ordered by fidelity (low to high):
┌───────────────────────────────────────────────────────────────────────────┐
│ SOLUTION VALIDATION LADDER │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Level 5: Functional MVP (Real product, limited features) │
│ └── Evidence: Usage data, retention, referrals │
│ │
│ Level 4: Wizard of Oz (Looks real, manual backend) │
│ └── Evidence: Task completion, willingness to pay │
│ │
│ Level 3: Interactive Prototype (Clickable mockup) │
│ └── Evidence: Task success rate, comprehension │
│ │
│ Level 2: Concept Test (Mockups + explanation) │
│ └── Evidence: Interest, understanding, objections │
│ │
│ Level 1: Smoke Test (Landing page only) │
│ └── Evidence: Sign-up rate, email capture │
│ │
└───────────────────────────────────────────────────────────────────────────┘
📝 Solution Hypothesis Template
## Solution Hypothesis
**Problem Being Solved:** [Validated problem statement]
**Proposed Solution:** [What we'll build]
**Core Value Proposition:** [Why this is 10x better]
**Key Features (MVP only):**
1. [Feature that solves main pain point]
2. [Feature that enables core workflow]
3. [Feature for differentiation]
### Assumptions to Test:
1. Users can complete [task] with our solution
2. Users prefer our solution to [current alternative]
3. Users understand the value without extensive explanation
4. Solution is technically feasible at target price
### Kill Criteria:
- If <40% can complete core task → Major redesign
- If <50% say it solves problem → Pivot solution approach
- If NPS < 0 → Rethink fundamental approach
🧪 Prototype Testing Protocol
For interactive prototypes/MVPs:
┌─────────────────────────────────────────────────────────────────┐
│ USABILITY TEST PROTOCOL │
├─────────────────────────────────────────────────────────────────┤
│ │
│ SETUP (5 min): │
│ ├── Thank participant, explain purpose │
│ ├── "Think out loud as you go" │
│ └── "There are no wrong answers" │
│ │
│ CONTEXT (5 min): │
│ ├── Confirm they have the validated problem │
│ └── Ask about current solution/workaround │
│ │
│ TASKS (20 min): │
│ ├── Task 1: [Core value action] │
│ │ └── Observe: Confusion points, time to complete │
│ ├── Task 2: [Secondary workflow] │
│ │ └── Observe: Feature discovery, expectations │
│ └── Task 3: [Edge case or setting] │
│ └── Observe: Error handling, recovery │
│ │
│ DEBRIEF (10 min): │
│ ├── "What stood out to you?" │
│ ├── "What was confusing or frustrating?" │
│ ├── "Would this solve your [problem]?" │
│ ├── "How does this compare to [current solution]?" │
│ └── "Would you pay for this? How much?" │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Solution Validation Metrics
Track these during testing:
| Metric | Target | Measure |
|---|---|---|
| Task Completion Rate | >60% | % completing core task without help |
| Time to Value | <5 min | Time to first "aha" moment |
| Error Rate | <20% | % encountering blocking errors |
| Comprehension | >80% | % understanding value prop without explanation |
| Preference | >50% | % preferring to current solution |
| NPS | >40 | "Would you recommend?" (0-10 scale) |
| Purchase Intent | >30% | "Would you pay?" yes rate |
✅ Stage 2 Checklist
- [ ] Solution hypothesis documented
- [ ] Prototype/MVP built (minimum viable)
- [ ] 10+ usability tests conducted
- [ ] Task completion rates measured
- [ ] User feedback synthesized
- [ ] NPS calculated
- [ ] Solution iterations completed
- [ ] Go/No-go decision documented
Related guide: Software Idea Validation for tech-specific testing methods.
Stage 3: Market Validation {#stage-3-market-validation}
🎯 Goal
Confirm the market is large enough to build a sustainable business.
┌─────────────────────────────────────────────────────────────────┐
│ MARKET VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Validated problem + validated solution │
│ OUTPUT: Market size estimates with supporting evidence │
│ │
│ KEY QUESTIONS: │
│ ├── How many people have this problem? (TAM) │
│ ├── How many can we realistically reach? (SAM) │
│ ├── How many can we capture in 3 years? (SOM) │
│ ├── What's the revenue potential? │
│ └── Is the market growing or shrinking? │
│ │
│ SUCCESS CRITERIA: │
│ ├── TAM > $100M (for VC-scale) │
│ ├── SAM > $10M (for sustainable business) │
│ ├── SOM > $1M (achievable in 3 years) │
│ └── Market growing >10% annually │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Market Sizing Framework
┌─────────────────────────────────────────────────────────────────────────┐
│ TAM / SAM / SOM HIERARCHY │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────────────────────────────────────────────────────┐ │
│ │ TAM │ │
│ │ Total Addressable Market │ │
│ │ "Everyone who could ever buy this" │ │
│ │ │ │
│ │ ┌───────────────────────────────────────────────────┐ │ │
│ │ │ SAM │ │ │
│ │ │ Serviceable Addressable Market │ │ │
│ │ │ "Everyone we can realistically reach" │ │ │
│ │ │ │ │ │
│ │ │ ┌───────────────────────────────────┐ │ │ │
│ │ │ │ SOM │ │ │ │
│ │ │ │ Serviceable Obtainable Market │ │ │ │
│ │ │ │ "What we can capture in 3 yrs" │ │ │ │
│ │ │ └───────────────────────────────────┘ │ │ │
│ │ │ │ │ │
│ │ └───────────────────────────────────────────────────┘ │ │
│ │ │ │
│ └─────────────────────────────────────────────────────────────────┘ │
│ │
├─────────────────────────────────────────────────────────────────────────┤
│ Example: Chrome Extension for Developers │
│ ├── TAM: 27M developers worldwide × $20/yr = $540M │
│ ├── SAM: 5M web developers × $20/yr = $100M │
│ └── SOM: 50K users × $20/yr = $1M (Year 3) │
└─────────────────────────────────────────────────────────────────────────┘
🔬 Market Research Methods
| Method | Best For | Data Quality | Cost |
|---|---|---|---|
| Industry Reports | TAM sizing | High | $0-$5K |
| Government Data | Demographics, business counts | High | Free |
| Competitor Analysis | SAM estimation | Medium | Free |
| Google Trends | Market trajectory | Medium | Free |
| Keyword Research | Demand signals | Medium | Free-$100 |
| Survey Research | Custom segmentation | Medium | $500-$5K |
| Expert Interviews | Market dynamics | High | $0-$2K |
📈 Market Trajectory Analysis
┌─────────────────────────────────────────────────────────────────┐
│ MARKET TRAJECTORY INDICATORS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 🟢 GROWING MARKET: │
│ ├── Search volume increasing year-over-year │
│ ├── New competitors entering the space │
│ ├── VC funding flowing into the category │
│ ├── Industry reports show positive growth │
│ └── Customer base expanding (new demographics) │
│ │
│ 🟡 STABLE MARKET: │
│ ├── Consistent search volume │
│ ├── Established competitors, few new entrants │
│ ├── Mature industry with predictable dynamics │
│ └── Opportunity through differentiation │
│ │
│ 🔴 DECLINING MARKET: │
│ ├── Search volume decreasing │
│ ├── Competitors exiting or consolidating │
│ ├── Technology disruption (problem going away) │
│ └── Customer base shrinking │
│ │
└─────────────────────────────────────────────────────────────────┘
✅ Stage 3 Checklist
- [ ] TAM calculated with methodology documented
- [ ] SAM defined with realistic constraints
- [ ] SOM projected for years 1-3
- [ ] Market growth rate researched
- [ ] 3+ data sources corroborate estimates
- [ ] Competitive landscape mapped
- [ ] Market timing assessed
- [ ] Go/No-go decision documented
Related guide: Niche Market Size Estimation for detailed sizing methodology.
Stage 4: Channel Validation {#stage-4-channel-validation}
🎯 Goal
Prove you can reach your target customers affordably and at scale.
┌─────────────────────────────────────────────────────────────────┐
│ CHANNEL VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Validated problem + solution + market │
│ OUTPUT: Proven customer acquisition channels │
│ │
│ KEY QUESTIONS: │
│ ├── Where do our target customers spend time? │
│ ├── What channels can we realistically use? │
│ ├── What's the cost per acquisition (CAC)? │
│ ├── How scalable is each channel? │
│ └── Can we achieve CAC < 1/3 of LTV? │
│ │
│ SUCCESS CRITERIA: │
│ ├── 2+ channels with CAC < $50 (for low-cost products) │
│ ├── At least 1 scalable channel identified │
│ ├── Customer acquisition funnel documented │
│ └── CAC:LTV ratio appears sustainable │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Channel Options Matrix
| Channel | Scale Potential | CAC Range | Timeline | Best For |
|---|---|---|---|---|
| Organic Search (SEO) | Very High | $0-50 | 6-12 months | Content-fit products |
| Content Marketing | High | $20-100 | 3-6 months | Educational products |
| Paid Search (PPC) | High | $30-200 | Immediate | Intent-based products |
| Social Organic | Medium | $0-30 | 3-6 months | Viral/social products |
| Social Paid | High | $10-150 | Immediate | Consumer products |
| Influencer | Medium | $50-500 | 1-2 months | Niche products |
| Partnerships | Medium | $0-100 | 3-6 months | B2B products |
| Product Hunt | Low | $0-50 | One-time | Dev/tech products |
| App Stores | High | $20-200 | Ongoing | Apps/extensions |
| Cold Outreach | Low | $50-300 | Immediate | B2B/enterprise |
| Referral | Medium | $0-50 | 3-6 months | High-NPS products |
| Communities | Low-Med | $0-30 | 2-4 months | Niche products |
🧪 Channel Experiment Framework
Run micro-experiments to test each channel:
┌─────────────────────────────────────────────────────────────────┐
│ CHANNEL TEST PROTOCOL │
├─────────────────────────────────────────────────────────────────┤
│ │
│ BUDGET: $100-500 per channel test │
│ DURATION: 1-2 weeks per test │
│ GOAL: Determine CAC potential and scalability │
│ │
│ TEST STRUCTURE: │
│ ├── Hypothesis: "We can acquire users via X for <$Y" │
│ ├── Metric: Sign-ups, trials, or purchases │
│ ├── Budget: Fixed amount ($100-500) │
│ ├── Duration: Fixed time (7-14 days) │
│ └── Variants: Test 2-3 messages/creatives │
│ │
│ MEASUREMENTS: │
│ ├── Impressions → Reach potential │
│ ├── Clicks → Interest level │
│ ├── Conversions → Acquisition cost │
│ ├── Quality → Retention of acquired users │
│ └── CAC → Total spend / conversions │
│ │
└─────────────────────────────────────────────────────────────────┘
📈 Channel Scoring Matrix
| Channel | Volume (1-5) | CAC Score (1-5) | Scalability (1-5) | Fit (1-5) | Total |
|---|---|---|---|---|---|
| SEO | 4 | 5 | 5 | ? | ? |
| PPC | 5 | 3 | 4 | ? | ? |
| Social | 3 | 4 | 3 | ? | ? |
| Content | 3 | 4 | 4 | ? | ? |
Scoring Guide: - Volume: How many users can this channel deliver? - CAC Score: 5=<$20, 4=$20-50, 3=$50-100, 2=$100-200, 1=>$200 - Scalability: Can you 10x spend without 10x CAC? - Fit: Does the channel match your product and team?
✅ Stage 4 Checklist
- [ ] 5+ channels identified for testing
- [ ] $500-1000 budget allocated for tests
- [ ] 3+ channel experiments completed
- [ ] CAC calculated for each channel
- [ ] Top 2 channels identified
- [ ] Acquisition funnel documented
- [ ] Scalability potential assessed
- [ ] Go/No-go decision documented
Related guide: Low Competition Niches for finding channels with less competition.
Stage 5: Revenue Validation {#stage-5-revenue-validation}
🎯 Goal
Prove customers will actually pay money for your solution.
┌─────────────────────────────────────────────────────────────────┐
│ REVENUE VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Validated problem + solution + market + channels │
│ OUTPUT: Proven revenue model with paying customers │
│ │
│ KEY QUESTIONS: │
│ ├── What price will customers pay? │
│ ├── What pricing model works best? │
│ ├── What's the conversion rate from free to paid? │
│ ├── What's the average revenue per user (ARPU)? │
│ └── Can we achieve target unit economics? │
│ │
│ SUCCESS CRITERIA: │
│ ├── 5+ paying customers (not friends/family) │
│ ├── Price validated at sustainable level │
│ ├── LTV:CAC > 3:1 appears achievable │
│ └── Churn rate acceptable for model │
│ │
└─────────────────────────────────────────────────────────────────┘
💰 Revenue Model Options
| Model | Best For | Key Metrics | Validation Method |
|---|---|---|---|
| Subscription | Ongoing value | MRR, Churn, LTV | Free trial → paid |
| Freemium | Network effects | Conversion rate | Feature gates |
| One-time | Tools, assets | AOV, repeat rate | Direct purchase |
| Usage-based | Variable usage | Usage growth, ARPU | Metered trial |
| Ads | Mass audience | DAU, engagement | Early ad testing |
| Marketplace | Two-sided | Take rate, GMV | Transaction tests |
🧪 Pricing Experiments
Method 1: Van Westendorp Price Sensitivity
Ask these four questions: 1. At what price would this be too cheap (quality concern)? 2. At what price is this a great deal? 3. At what price does it start to get expensive? 4. At what price is it too expensive to consider?
Method 2: Willingness to Pay Direct
"If this product were available today:
□ I would not buy it at any price
□ I would pay up to $X/month
□ I would pay $Y-Z/month
□ I would pay more than $Z/month"
Method 3: Price Ladder Testing
| Test Group | Price | Conversion | Revenue |
|---|---|---|---|
| A | $9/mo | 8% | $720/1000 visitors |
| B | $19/mo | 5% | $950/1000 visitors |
| C | $29/mo | 3% | $870/1000 visitors |
📊 Unit Economics Validation
┌─────────────────────────────────────────────────────────────────┐
│ UNIT ECONOMICS CHECK │
├─────────────────────────────────────────────────────────────────┤
│ │
│ REVENUE SIDE: │
│ ├── ARPU: Average revenue per user/month │
│ ├── Retention: Monthly retention rate │
│ └── LTV: ARPU × (1 / (1 - Retention)) │
│ │
│ COST SIDE: │
│ ├── CAC: Cost to acquire a customer │
│ ├── COGS: Cost to serve a customer │
│ └── Gross Margin: (Revenue - COGS) / Revenue │
│ │
│ KEY RATIOS: │
│ ├── LTV:CAC > 3:1 (healthy) │
│ ├── CAC Payback < 12 months (sustainable) │
│ └── Gross Margin > 70% (scalable) │
│ │
│ EXAMPLE: │
│ ├── ARPU: $20/month │
│ ├── Retention: 95% │
│ ├── LTV: $20 × 20 = $400 │
│ ├── CAC: $80 │
│ ├── LTV:CAC: 5:1 ✅ │
│ └── Payback: 4 months ✅ │
│ │
└─────────────────────────────────────────────────────────────────┘
✅ Stage 5 Checklist
- [ ] Pricing hypothesis documented
- [ ] Price sensitivity research completed
- [ ] 2+ pricing experiments run
- [ ] Optimal price point identified
- [ ] 5+ paying customers acquired
- [ ] Unit economics calculated
- [ ] LTV:CAC ratio validated
- [ ] Go/No-go decision documented
Related guide: Niche Profitability Analysis for detailed economics modeling.
Stage 6: Scale Validation {#stage-6-scale-validation}
🎯 Goal
Prove the business can grow profitably beyond early adopters.
┌─────────────────────────────────────────────────────────────────┐
│ SCALE VALIDATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Validated problem + solution + market + channels + │
│ revenue model │
│ OUTPUT: Evidence that growth is sustainable and profitable │
│ │
│ KEY QUESTIONS: │
│ ├── Do unit economics hold as we scale? │
│ ├── Can we grow without burning cash? │
│ ├── Does the team have capacity to scale? │
│ ├── Is there a path to market leadership? │
│ └── Are there network effects or moats? │
│ │
│ SUCCESS CRITERIA: │
│ ├── Unit economics stable at 2x current scale │
│ ├── Organic growth rate > 20% month-over-month │
│ ├── NPS remains > 40 at scale │
│ └── Clear path to profitability documented │
│ │
└─────────────────────────────────────────────────────────────────┘
📈 Scale Indicators
┌─────────────────────────────────────────────────────────────────┐
│ SCALE READINESS SIGNALS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 🟢 READY TO SCALE: │
│ ├── Unit economics profitable at current scale │
│ ├── CAC decreasing as brand awareness grows │
│ ├── Referral/word-of-mouth driving >30% of growth │
│ ├── Retention improving or stable │
│ ├── Support load manageable per customer │
│ └── Technical infrastructure can handle 10x load │
│ │
│ 🟡 OPTIMIZE FIRST: │
│ ├── Unit economics marginal (2-3x LTV:CAC) │
│ ├── Heavy reliance on paid acquisition │
│ ├── Retention declining slightly │
│ ├── Support becoming bottleneck │
│ └── Technical debt accumulating │
│ │
│ 🔴 NOT READY: │
│ ├── Unit economics negative │
│ ├── CAC increasing with scale │
│ ├── High churn (>10% monthly) │
│ ├── Quality issues at current scale │
│ └── Team burnout signs │
│ │
└─────────────────────────────────────────────────────────────────┘
🧪 Scale Tests
| Test | How to Run | What to Learn |
|---|---|---|
| 2x Spend Test | Double marketing spend for 2 weeks | Does CAC hold? |
| Load Test | Simulate 10x traffic | Can tech handle scale? |
| Support Ratio | Track tickets per 100 users | Is support scalable? |
| Cohort Analysis | Compare early vs recent users | Is quality declining? |
| Referral Rate | Track viral coefficient | Is organic growth real? |
✅ Stage 6 Checklist
- [ ] Scale hypothesis documented
- [ ] 2x marketing spend test completed
- [ ] Unit economics at higher scale measured
- [ ] Technical scalability assessed
- [ ] Support/operations scalability assessed
- [ ] Growth engine identified
- [ ] Competitive moat documented
- [ ] Full go/no-go decision made
Validation Methods Library {#validation-methods-library}
📚 Quick Reference: When to Use What
| Method | Best For | Time | Cost | Evidence Quality |
|---|---|---|---|---|
| Customer Interviews | Problem validation | 2-4 weeks | $0 | High |
| Surveys | Quantifying known insights | 1-2 weeks | $0-500 | Medium |
| Landing Page | Demand signal | 1 week | $50-200 | Medium |
| Smoke Test Ads | Interest validation | 1-2 weeks | $100-500 | Medium |
| Explainer Video | Solution interest | 1-2 weeks | $200-1000 | Medium |
| Concierge MVP | Solution validation | 2-4 weeks | $0 | High |
| Wizard of Oz | Behavior validation | 2-4 weeks | $500-2000 | High |
| Prototype Testing | Usability validation | 1-2 weeks | $0-500 | High |
| Pre-sales | Willingness to pay | 2-4 weeks | $0-200 | Very High |
| Crowdfunding | Demand + willingness | 4-6 weeks | $500-2000 | Very High |
| Beta Launch | Full product validation | 4-8 weeks | Variable | Very High |
🎯 Method Selection Guide
┌─────────────────────────────────────────────────────────────────┐
│ VALIDATION METHOD SELECTION TREE │
├─────────────────────────────────────────────────────────────────┤
│ │
│ What stage are you validating? │
│ │ │
│ ├── PROBLEM │
│ │ ├── Qualitative → Customer Interviews │
│ │ └── Quantitative → Surveys, Forum Analysis │
│ │ │
│ ├── SOLUTION │
│ │ ├── Concept → Concept Test, Explainer Video │
│ │ ├── Usability → Prototype Testing │
│ │ └── Behavior → Concierge, Wizard of Oz │
│ │ │
│ ├── MARKET │
│ │ ├── Size → Industry Reports, Bottom-up Analysis │
│ │ └── Timing → Trend Analysis, Expert Interviews │
│ │ │
│ ├── CHANNEL │
│ │ ├── Demand → Landing Page, Smoke Tests │
│ │ └── Acquisition → Channel Experiments, CAC Tests │
│ │ │
│ ├── REVENUE │
│ │ ├── Interest → Pre-sales, Waitlist │
│ │ └── Commitment → Crowdfunding, Beta w/ Payment │
│ │ │
│ └── SCALE │
│ ├── Economics → Cohort Analysis, Unit Economics │
│ └── Operations → Load Tests, Support Scaling │
│ │
└─────────────────────────────────────────────────────────────────┘
Evidence Quality Scoring {#evidence-quality-scoring}
📊 Evidence Hierarchy
Not all validation evidence is equal. Use this hierarchy:
┌─────────────────────────────────────────────────────────────────┐
│ EVIDENCE QUALITY PYRAMID │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────┐ │
│ │ Revenue │ ← Strongest │
│ │ $$$ │ (They paid money) │
│ ┌┴─────────┴┐ │
│ │ Behavior │ ← Strong │
│ │ Actions │ (They did something) │
│ ┌┴───────────┴┐ │
│ │ Intent │ ← Medium │
│ │ Commitment │ (They committed) │
│ ┌┴─────────────┴┐ │
│ │ Interest │ ← Weak │
│ │ Opinions │ (They said something) │
│ ┌┴───────────────┴┐ │
│ │ Awareness │ ← Weakest │
│ │ Views/Reads │ (They saw it) │
│ └─────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
📋 Evidence Scoring Matrix
| Evidence Type | Example | Quality Score |
|---|---|---|
| Paid Revenue | Customer bought product | 10 |
| Pre-paid Commitment | Crowdfunding pledge | 9 |
| Signed LOI | Letter of Intent | 8 |
| Deposit Paid | Non-refundable deposit | 8 |
| Free Trial Active Use | Daily active usage | 7 |
| Waitlist Signup | Email + context provided | 6 |
| Meeting Booked | Demo/call scheduled | 5 |
| Email Signup | Email only | 4 |
| Survey Response | Completed survey | 3 |
| Social Engagement | Like/comment/share | 2 |
| Page View | Visited landing page | 1 |
🎯 Minimum Evidence Thresholds
| Stage | Minimum Evidence | Quality Required |
|---|---|---|
| Problem | 20+ interviews | 15+ score 8+/15 |
| Solution | 10+ user tests | 6+ successful tasks |
| Market | 3+ data sources | All corroborating |
| Channel | 3+ experiments | 2+ CAC < target |
| Revenue | 5+ customers | Real payment received |
| Scale | 4+ weeks data | Trends positive |
Go/No-Go Decision Framework {#go-no-go-decision-framework}
🚦 Decision Matrix
┌─────────────────────────────────────────────────────────────────┐
│ GO / NO-GO DECISION MATRIX │
├─────────────────────────────────────────────────────────────────┤
│ │
│ For each stage, rate your validation strength: │
│ │
│ Stage Score (1-10) Weight Weighted │
│ ───────────────────────────────────────────────────────────── │
│ Problem Validation [ ] × 1.5 = [ ] │
│ Solution Validation [ ] × 1.5 = [ ] │
│ Market Validation [ ] × 1.0 = [ ] │
│ Channel Validation [ ] × 1.0 = [ ] │
│ Revenue Validation [ ] × 1.5 = [ ] │
│ Scale Validation [ ] × 0.5 = [ ] │
│ ───────────────────────────────────────────────────────────── │
│ TOTAL: [ ]/70 │
│ │
│ DECISION THRESHOLDS: │
│ ├── 56-70 (80%+): 🟢 STRONG GO - Full commitment │
│ ├── 42-55 (60-79%): 🟡 CONDITIONAL GO - Address gaps first │
│ ├── 28-41 (40-59%): 🟠 PIVOT - Major changes needed │
│ └── 0-27 (<40%): 🔴 NO GO - Kill or restart │
│ │
└─────────────────────────────────────────────────────────────────┘
🎯 Stage-Specific Kill Criteria
| Stage | Kill If... | Pivot If... |
|---|---|---|
| Problem | <50% confirm problem | <70% confirm problem |
| Solution | <30% can complete core task | <50% prefer to current |
| Market | TAM <$10M | TAM <$50M |
| Channel | All channels >$200 CAC | Best channel >$100 CAC |
| Revenue | 0 paying customers after 4 weeks | <2% conversion rate |
| Scale | Unit economics negative | LTV:CAC <2:1 |
📋 Go/No-Go Documentation Template
## Validation Summary: [Product Name]
**Date:** [Date]
**Stage Completed:** [1-6]
**Decision:** [GO / CONDITIONAL GO / PIVOT / KILL]
### Stage Scores
| Stage | Score | Evidence Summary |
|-------|-------|------------------|
| Problem | X/10 | [Key findings] |
| Solution | X/10 | [Key findings] |
| Market | X/10 | [Key findings] |
| Channel | X/10 | [Key findings] |
| Revenue | X/10 | [Key findings] |
| Scale | X/10 | [Key findings] |
**Total: XX/70 (XX%)**
### Key Risks
1. [Risk 1 and mitigation]
2. [Risk 2 and mitigation]
3. [Risk 3 and mitigation]
### Next Steps
- [ ] [Action item 1]
- [ ] [Action item 2]
- [ ] [Action item 3]
### Decision Rationale
[Why this decision was made]
Framework Templates and Tools {#framework-templates-and-tools}
📋 Master Validation Tracker
┌─────────────────────────────────────────────────────────────────────────────┐
│ PRODUCT VALIDATION TRACKER │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ PRODUCT: _______________________ START DATE: ___________ │
│ │
│ ┌─────────┬─────────┬─────────┬─────────┬─────────┬─────────┐ │
│ │ STAGE 1 │ STAGE 2 │ STAGE 3 │ STAGE 4 │ STAGE 5 │ STAGE 6 │ │
│ │ Problem │Solution │ Market │ Channel │ Revenue │ Scale │ │
│ ├─────────┼─────────┼─────────┼─────────┼─────────┼─────────┤ │
│ │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ Started │
│ │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ Evidence │
│ │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ [ ] │ Decision │
│ └─────────┴─────────┴─────────┴─────────┴─────────┴─────────┘ │
│ │
│ CURRENT STAGE: _____ BLOCKING ISSUE: _____________________ │
│ │
│ KEY METRICS: │
│ ├── Interviews completed: ___/20 │
│ ├── Solution tests: ___/10 │
│ ├── Channel experiments: ___/3 │
│ ├── Paying customers: ___ │
│ └── Current CAC: $___ │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
📝 Assumption Tracking Template
## Assumption Log
### Critical Assumptions (Must Validate)
| ID | Assumption | Test Method | Result | Confidence |
|----|------------|-------------|--------|------------|
| A1 | Users have problem X | Interviews | 85% confirm | High |
| A2 | They'll pay $Y/mo | Pre-sale | 5 paid | Medium |
| A3 | We can reach via Z | Ad test | $40 CAC | Medium |
### Risky Assumptions (Should Validate)
| ID | Assumption | Test Method | Result | Confidence |
|----|------------|-------------|--------|------------|
| B1 | Tech is feasible | Prototype | Works | High |
| B2 | Retention >90% | Beta cohort | TBD | Unknown |
### Assumptions We're Taking (Low Risk)
| ID | Assumption | Why Low Risk |
|----|------------|--------------|
| C1 | Market won't shrink | Growing industry |
| C2 | No major competitor | Long runway |
🛠️ Recommended Tools
| Stage | Tool | Purpose | Cost |
|---|---|---|---|
| All | Notion/Airtable | Track all validation data | $0-10/mo |
| Problem | Calendly | Schedule interviews | Free |
| Problem | Otter.ai | Transcribe interviews | $8/mo |
| Solution | Figma | Create prototypes | Free |
| Solution | Maze | Run usability tests | Free-$75/mo |
| Market | SimilarWeb | Competitor research | Free-$200/mo |
| Channel | Google Ads | Test paid channels | Variable |
| Channel | Carrd | Quick landing pages | $19/yr |
| Revenue | Stripe | Process payments | 2.9% + 30¢ |
| Revenue | Gumroad | Sell beta access | 10% + processing |
| All | NicheCheck | All-in-one validation | Free-$29/mo |
Case Studies: Framework in Action {#case-studies-framework-in-action}
📖 Case Study 1: Password Manager Extension (GO)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: PASSWORD MANAGER EXTENSION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ HYPOTHESIS: Developers need better password management for │
│ team credentials (API keys, shared logins) │
│ │
│ STAGE 1 - PROBLEM (Score: 9/10) │
│ ├── 25 developer interviews conducted │
│ ├── 88% confirmed pain point │
│ ├── Average pain score: 8.2/10 │
│ └── 72% currently using insecure workarounds │
│ │
│ STAGE 2 - SOLUTION (Score: 8/10) │
│ ├── Built Figma prototype │
│ ├── 12 usability tests │
│ ├── 83% completed core task │
│ └── NPS: 52 │
│ │
│ STAGE 3 - MARKET (Score: 7/10) │
│ ├── TAM: $2.8B (password management market) │
│ ├── SAM: $280M (developer-focused segment) │
│ └── SOM: $2.8M (1% in 3 years) │
│ │
│ STAGE 4 - CHANNEL (Score: 8/10) │
│ ├── Reddit/HN posts: $18 CAC │
│ ├── Google Ads: $45 CAC │
│ └── Content marketing: $22 CAC │
│ │
│ STAGE 5 - REVENUE (Score: 8/10) │
│ ├── Pricing tested: $5, $9, $15/mo │
│ ├── Optimal: $9/mo (5.2% conversion) │
│ ├── 23 paying customers in beta │
│ └── LTV:CAC = 4.8:1 │
│ │
│ TOTAL SCORE: 62/70 (89%) → STRONG GO │
│ │
│ OUTCOME: Launched, hit $10K MRR in 6 months │
│ │
└─────────────────────────────────────────────────────────────────┘
📖 Case Study 2: AI Writing Assistant (PIVOT)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: AI WRITING ASSISTANT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ HYPOTHESIS: Marketers need AI to write social media posts │
│ │
│ STAGE 1 - PROBLEM (Score: 8/10) │
│ ├── 22 marketer interviews │
│ ├── 82% confirmed time problem │
│ └── But: 65% already using ChatGPT │
│ │
│ STAGE 2 - SOLUTION (Score: 5/10) │
│ ├── Built MVP with GPT-4 │
│ ├── Users: "Nice but not different from ChatGPT" │
│ └── NPS: 18 (low) │
│ │
│ STAGE 3 - MARKET (Score: 4/10) │
│ ├── 50+ competitors in space │
│ ├── Jasper, Copy.ai dominant │
│ └── Hard to differentiate │
│ │
│ TOTAL SCORE: 38/70 (54%) → PIVOT │
│ │
│ DECISION: Pivot to niche (real estate agents) │
│ ├── Smaller market but less competition │
│ ├── Can build domain-specific features │
│ └── Higher willingness to pay ($49/mo) │
│ │
│ POST-PIVOT: Re-validated, scored 58/70 → GO │
│ │
└─────────────────────────────────────────────────────────────────┘
📖 Case Study 3: Habit Tracker App (KILL)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: HABIT TRACKER APP │
├─────────────────────────────────────────────────────────────────┤
│ │
│ HYPOTHESIS: People want a gamified habit tracking app │
│ │
│ STAGE 1 - PROBLEM (Score: 6/10) │
│ ├── 20 interviews conducted │
│ ├── 70% said "habits are hard" │
│ ├── But: Only 25% actively trying to solve │
│ └── Pain score: 5.2/10 (moderate) │
│ │
│ STAGE 2 - SOLUTION (Score: 4/10) │
│ ├── Built prototype with gamification │
│ ├── Initial excitement high │
│ ├── Week 2 retention: 15% │
│ └── Users: "Fun at first, then forgot about it" │
│ │
│ STAGE 3 - MARKET (Score: 3/10) │
│ ├── 200+ habit apps in app stores │
│ ├── Most free or <$5 │
│ └── Habitica (main competitor) struggling to monetize │
│ │
│ TOTAL SCORE: 26/70 (37%) → KILL │
│ │
│ DECISION: Kill project │
│ ├── Problem not urgent enough │
│ ├── Retention fundamentally broken │
│ ├── Market too competitive, low willingness to pay │
│ └── Better to invest time elsewhere │
│ │
│ TIME SAVED: ~6 months of building the wrong product │
│ │
└─────────────────────────────────────────────────────────────────┘
Common Validation Mistakes {#common-validation-mistakes}
❌ Top 15 Validation Mistakes
| # | Mistake | Why It's Deadly | Prevention |
|---|---|---|---|
| 1 | Skipping problem validation | Building solutions to non-problems | 20+ interviews before any building |
| 2 | Asking friends and family | They'll lie to be nice | Only interview target customers |
| 3 | Leading questions | Confirming your bias | Use Mom Test methodology |
| 4 | Accepting "I would buy" | Opinions ≠ behavior | Demand payment or commitment |
| 5 | Building too much | Wasting time on features | Minimum viable test always |
| 6 | Ignoring negative signals | Confirmation bias | Document all feedback, good and bad |
| 7 | One channel testing | Missing better options | Test 3+ channels |
| 8 | Assuming pricing | Leaving money on table | Test 3+ price points |
| 9 | No kill criteria | Zombie projects live forever | Define failure thresholds upfront |
| 10 | Validation theater | Going through motions | Demand real evidence |
| 11 | Too small sample size | Noise over signal | Minimum 20 for patterns |
| 12 | Skipping stages | Missing critical gaps | Complete each stage fully |
| 13 | No documentation | Losing insights | Track everything |
| 14 | Pivoting too fast | Giving up prematurely | Exhaust options before pivoting |
| 15 | Pivoting too slow | Sunk cost fallacy | Set clear pivot triggers |
🔧 Mistake Prevention Checklist
- [ ] Written hypothesis for each stage
- [ ] Defined kill criteria before starting
- [ ] Using interview scripts (not winging it)
- [ ] Documenting all feedback (not just positive)
- [ ] Getting commitments, not compliments
- [ ] Testing multiple channels
- [ ] Running pricing experiments
- [ ] Weekly validation reviews
- [ ] External accountability (advisor, co-founder)
FAQ {#faq}
❓ How long should validation take?
Typical timeline by stage: - Problem validation: 2-3 weeks - Solution validation: 2-4 weeks - Market validation: 1-2 weeks - Channel validation: 2-4 weeks - Revenue validation: 2-4 weeks - Scale validation: 4-8 weeks
Total: 3-6 months for full validation
You can parallelize some stages (market research during problem interviews), but don't skip stages.
❓ Can I validate multiple ideas simultaneously?
Yes, but only in early stages: - Problem validation: Can run 2-3 idea interviews in parallel - Solution validation: Focus on one to avoid dilution - Revenue onward: One idea only
The goal is to quickly kill bad ideas, not slowly validate many.
❓ What if my idea is unique with no competitors?
Three possibilities: 1. You haven't looked hard enough - Search harder 2. The problem isn't big enough - Competitors tried and failed 3. It's genuinely new timing - Rare, but possible
If truly unique, validate extra carefully—you can't learn from competitor success/failure.
❓ How do I validate B2B vs B2C differently?
| Aspect | B2B | B2C |
|---|---|---|
| Sample size | 10-20 interviews sufficient | 30-50 for patterns |
| Willingness to pay | Easier to validate (budgets exist) | Harder (discretionary spend) |
| Sales cycle | Longer, include in timeline | Shorter, can test quickly |
| Decision makers | Multiple, identify all | Usually individual |
| Revenue validation | LOI/pilot contracts | Pre-sales/crowdfunding |
❓ When should I give up on an idea?
Give up when: - ✅ You've completed full validation with good methodology - ✅ Scores are below threshold with no clear pivot - ✅ You've tried 2+ significant pivots without improvement - ✅ You've spent 3+ months without positive signals - ✅ Your enthusiasm is gone (founder-market fit matters)
Don't give up because: - ❌ One person said no - ❌ First channel didn't work - ❌ It's taking longer than expected - ❌ Someone said the idea is bad (without data)
❓ How do I validate during a day job?
Part-time validation schedule: - Weekday mornings (1hr): Research, analysis, planning - Weekday lunches (30min): Customer interviews (phone/video) - Weekday evenings (1hr): Building prototypes, running experiments - Weekends (4-6hrs): Larger validation activities
Key: Focus on learning speed, not hours. One good interview beats 10 hours of feature building.
Summary and Action Steps {#summary-and-action-steps}
📋 Key Takeaways
┌─────────────────────────────────────────────────────────────────┐
│ FRAMEWORK SUMMARY │
├─────────────────────────────────────────────────────────────────┤
│ │
│ THE 6 STAGES: │
│ 1. Problem → "Is the pain real and urgent?" │
│ 2. Solution → "Does our fix actually work?" │
│ 3. Market → "Is the opportunity big enough?" │
│ 4. Channel → "Can we reach them affordably?" │
│ 5. Revenue → "Will they pay enough?" │
│ 6. Scale → "Can we grow profitably?" │
│ │
│ EVIDENCE HIERARCHY: │
│ Revenue > Behavior > Intent > Interest > Awareness │
│ │
│ KEY PRINCIPLES: │
│ ├── Document everything (assumptions, tests, results) │
│ ├── Demand evidence, not opinions │
│ ├── Define kill criteria before testing │
│ ├── Complete each stage before proceeding │
│ └── Pivot on data, not frustration │
│ │
│ SUCCESS THRESHOLDS: │
│ ├── 80%+ problem confirmation │
│ ├── 60%+ solution task completion │
│ ├── TAM >$100M, SAM >$10M │
│ ├── 2+ channels with <$50 CAC │
│ ├── 5+ paying customers │
│ └── Positive unit economics │
│ │
└─────────────────────────────────────────────────────────────────┘
✅ Your Next Steps
This week: 1. [ ] Document your current idea hypothesis 2. [ ] List all assumptions you're making 3. [ ] Define kill criteria for Stage 1 4. [ ] Schedule 5 customer interviews 5. [ ] Set up validation tracking (Notion/spreadsheet)
This month: 1. [ ] Complete 20+ problem validation interviews 2. [ ] Score your problem validation 3. [ ] Make go/no-go decision for Stage 1 4. [ ] If GO, begin solution prototyping
Tools to use: - NicheCheck - Validate market opportunity and competition - Product Idea Research Guide - Deep-dive on research methods - Niche Scoring System - Quantify your opportunity
Free tool: Quickly check if your niche is already taken with our free niche checker -- no signup required.
🚀 Ready to Validate Your Idea?
Stop guessing. Start validating.
Try NicheCheck Free → and get instant validation data for your product idea: - ✅ Market size estimation - ✅ Competition analysis - ✅ Channel opportunity scoring - ✅ Revenue potential calculation - ✅ GO/MAYBE/NO-GO verdict
Join 2,000+ founders making smarter build decisions.
Ready to Validate Your Idea?
Get instant insights on market demand, competition, and revenue potential.
Try NicheCheck Free