The definitive checklist that separates billion-dollar opportunities from expensive mistakes—used by YC founders, bootstrappers, and serial entrepreneurs to validate ideas before writing a single line of code.

Table of Contents

  1. Introduction: Why You Need a Systematic Checklist
  2. The Validation Mindset
  3. Phase 1: Problem Validation Checklist (27 Points)
  4. Phase 2: Solution Validation Checklist (23 Points)
  5. Phase 3: Market Validation Checklist (21 Points)
  6. Phase 4: Competitive Analysis Checklist (18 Points)
  7. Phase 5: Technical Feasibility Checklist (15 Points)
  8. Phase 6: Business Model Checklist (14 Points)
  9. Phase 7: Go-to-Market Checklist (9 Points)
  10. The Master Scoring System
  11. Checklist by Startup Type
  12. Red Flags and Dealbreakers
  13. Case Studies: Checklists in Action
  14. Printable Checklist Templates
  15. Common Mistakes and How to Avoid Them
  16. FAQ
  17. Summary and Next Steps

Introduction: Why You Need a Systematic Checklist {#introduction}

Here's a sobering statistic: 90% of startups fail, and the #1 reason cited is "no market need." Not running out of money. Not bad teams. Not poor execution. Simply building something nobody wants.

Yet founders continue to skip validation, convinced their idea is different. Spoiler: it's not.

┌─────────────────────────────────────────────────────────────────┐
│                    THE STARTUP GRAVEYARD                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│   💀 "We built it but nobody came"          - 42% of failures  │
│   💀 "We ran out of money"                  - 29% of failures  │
│   💀 "Wrong team"                           - 23% of failures  │
│   💀 "Got outcompeted"                      - 19% of failures  │
│   💀 "Pricing/cost issues"                  - 18% of failures  │
│                                                                 │
│   ┌─────────────────────────────────────────────────────────┐  │
│   │  ALL of these could have been caught with proper        │  │
│   │  validation BEFORE building. This checklist helps.      │  │
│   └─────────────────────────────────────────────────────────┘  │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

What This Checklist Covers

This isn't a theoretical framework—it's a battle-tested validation system covering:

Phase Focus Area Checkpoints Time to Complete
1 Problem Validation 27 points 1-2 weeks
2 Solution Validation 23 points 1-2 weeks
3 Market Validation 21 points 1 week
4 Competitive Analysis 18 points 3-5 days
5 Technical Feasibility 15 points 2-3 days
6 Business Model 14 points 2-3 days
7 Go-to-Market 9 points 2-3 days
Total Full Validation 127 points 4-8 weeks

Who This Checklist Is For

  • 🚀 First-time founders who want to avoid expensive mistakes
  • 🔄 Serial entrepreneurs who need a systematic approach
  • 💼 Corporate innovators evaluating internal ventures
  • 👨‍💻 Technical founders who tend to skip market validation
  • 💰 Investors doing due diligence on opportunities
  • 🎓 Students learning lean startup methodology

How to Use This Checklist

┌─────────────────────────────────────────────────────────────────┐
│                   CHECKLIST USAGE GUIDE                         │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  1. GO SEQUENTIAL                                               │
│     Complete each phase before moving to the next.              │
│     Skipping ahead creates blind spots.                         │
│                                                                 │
│  2. BE HONEST                                                   │
│     Mark items as ✅ only when you have real evidence.          │
│     "I think so" doesn't count. Data counts.                    │
│                                                                 │
│  3. DOCUMENT EVERYTHING                                         │
│     Keep notes for each checkbox. You'll reference these        │
│     in investor meetings, team discussions, and pivots.         │
│                                                                 │
│  4. REVISIT REGULARLY                                           │
│     Validation isn't one-and-done. Re-run the checklist         │
│     after significant pivots or new information.                │
│                                                                 │
│  5. KNOW YOUR MINIMUMS                                          │
│     Some items are critical (marked 🔴). Failing these          │
│     is a dealbreaker. Others are nice-to-have (marked 🟡).      │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

The Validation Mindset {#validation-mindset}

Before diving into the checklist, you need to adopt the right mindset. Most founders fail at validation not because they lack the tools, but because they approach it wrong.

🧠 Mindset Shift #1: You're a Scientist, Not a Salesperson

Your job is to disprove your idea, not prove it. Seek disconfirming evidence actively.

Wrong approach:

"Let me find people who love my idea!"

Right approach:

"Let me find every reason this could fail—and see if I can address them."

🧠 Mindset Shift #2: Validation is Not Asking Friends

Friends lie. Family lies. Colleagues are polite. Real validation requires:

Source Validity Why
Friends and family ❌ Low Social pressure to be supportive
Cold outreach to strangers ✅ High No relationship to preserve
People who pay money ✅✅ Highest Money is the ultimate validation
Industry experts ✅ High No skin in the game
Potential customers ✅ High If properly interviewed

🧠 Mindset Shift #3: Speed Beats Perfection

┌─────────────────────────────────────────────────────────────────┐
│                   VALIDATION SPEED MATTERS                      │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│   Slow validation (6+ months):                                  │
│   ├── Market changes while you analyze                          │
│   ├── Competitors ship while you study                          │
│   ├── Motivation dies from analysis paralysis                   │
│   └── Resources drain before you start                          │
│                                                                 │
│   Fast validation (4-8 weeks):                                  │
│   ├── Quick feedback loops                                      │
│   ├── Preserve capital for building                             │
│   ├── Maintain founder energy                                   │
│   └── Can run multiple ideas in parallel                        │
│                                                                 │
│   ⚡ Target: Complete this checklist in 4-8 weeks max           │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🧠 Mindset Shift #4: Failing Fast is Winning

Every "no" saves you months of building the wrong thing. Celebrate when you invalidate an idea—you just saved potentially years of your life.

The math: - Building an unvalidated startup: 12-24 months of your life - Validating and killing a bad idea: 4-8 weeks - Time saved: 10-22 months - At $150K opportunity cost/year: $125K-$275K saved

Phase 1: Problem Validation Checklist (27 Points) {#problem-validation}

Before solving anything, you must prove the problem exists and is worth solving.

1.1 Problem Existence (9 Points)

🔴 Critical Items:

  • [ ] P1.1 I can describe the problem in one sentence without jargon

  • Evidence needed: Write it down. Test if a stranger understands it.

  • [ ] P1.2 I have personally experienced this problem OR spent 20+ hours with people who have

  • Evidence needed: Personal experience or interview transcripts

  • [ ] P1.3 I have found at least 10 people actively looking for solutions online

  • Evidence needed: Forum posts, Reddit threads, Quora questions, review complaints

  • [ ] P1.4 The problem exists today (not "will exist when X happens")

  • Evidence needed: Current evidence, not future speculation

  • [ ] P1.5 People can articulate the problem without me explaining it

  • Evidence needed: Unprompted problem descriptions from interviews

🟡 Important Items:

  • [ ] P1.6 The problem has existed for at least 12 months (not a fad)

  • Evidence needed: Historical forum posts, articles, search trends

  • [ ] P1.7 I can find communities dedicated to discussing this problem

  • Evidence needed: Subreddits, Facebook groups, Slack communities, forums

  • [ ] P1.8 Industry experts acknowledge this problem exists

  • Evidence needed: Blog posts, conference talks, research papers

  • [ ] P1.9 The problem appears in multiple geographic markets

  • Evidence needed: International forum posts, global search data

1.2 Problem Severity (9 Points)

┌─────────────────────────────────────────────────────────────────┐
│                   PROBLEM SEVERITY SCALE                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Level 5 ⬛⬛⬛⬛⬛  Hair on Fire (Mission-critical problem)     │
│  Level 4 ⬛⬛⬛⬛⬜  Painful (Significant daily impact)          │
│  Level 3 ⬛⬛⬛⬜⬜  Annoying (Regular frustration)              │
│  Level 2 ⬛⬛⬜⬜⬜  Inconvenient (Occasional issue)             │
│  Level 1 ⬛⬜⬜⬜⬜  Latent (Problem exists but not felt)        │
│                                                                 │
│  ✅ Target: Level 4-5 problems only                             │
│  ❌ Avoid: Level 1-2 problems (nobody will pay)                 │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] P1.10 People actively spend money trying to solve this problem

  • Evidence needed: Existing products, services, or workarounds they pay for

  • [ ] P1.11 People spend significant time on workarounds (2+ hours/week)

  • Evidence needed: Interview data, observed behavior

  • [ ] P1.12 The problem causes measurable negative outcomes (revenue loss, wasted time, missed opportunities)

  • Evidence needed: Quantified impact from interviews

🟡 Important Items:

  • [ ] P1.13 Failing to solve this problem has consequences

  • Evidence needed: Examples of negative outcomes from interviews

  • [ ] P1.14 The problem frequency is high (daily/weekly, not yearly)

  • Evidence needed: Interview data on problem occurrence

  • [ ] P1.15 People have tried to solve this problem before and failed

  • Evidence needed: Failed attempts mentioned in interviews

  • [ ] P1.16 The problem is getting worse over time, not better

  • Evidence needed: Trend data, interview sentiment

  • [ ] P1.17 Solving this problem would significantly improve quality of life/work

  • Evidence needed: Interview responses on impact

  • [ ] P1.18 People would be willing to change their behavior to solve it

  • Evidence needed: Past behavior changes mentioned in interviews

1.3 Customer Understanding (9 Points)

🔴 Critical Items:

  • [ ] P1.19 I can describe my ideal customer in specific detail (demographics, psychographics, behaviors)

  • Evidence needed: Written ICP with specific attributes

  • [ ] P1.20 I have conducted at least 15 problem discovery interviews

  • Evidence needed: Interview notes, recordings

  • [ ] P1.21 I know where my target customers spend time online

  • Evidence needed: List of specific communities, platforms

🟡 Important Items:

  • [ ] P1.22 I understand the customer's day-to-day workflow

  • Evidence needed: Workflow documentation from observation

  • [ ] P1.23 I know what triggers the problem occurrence

  • Evidence needed: Trigger patterns from interviews

  • [ ] P1.24 I understand the customer's buying process and decision-makers

  • Evidence needed: Buying journey documentation

  • [ ] P1.25 I know the customer's current alternatives and why they're insufficient

  • Evidence needed: Competitive analysis from customer perspective

  • [ ] P1.26 I can segment customers into distinct groups with different needs

  • Evidence needed: Customer segmentation document

  • [ ] P1.27 I have identified early adopters who are most desperate for a solution

  • Evidence needed: Early adopter profile and contact list

Problem Validation Score Card

Section Points Possible Your Score Minimum Required
Problem Existence 9 ___ /9 7
Problem Severity 9 ___ /9 6
Customer Understanding 9 ___ /9 6
Total Phase 1 27 ___ /27 19

🚦 GO/NO-GO Decision: - ✅ GO if score ≥ 19 with all 🔴 Critical items checked - 🟡 PAUSE if score 15-18, address gaps before proceeding - ❌ NO-GO if score < 15 or missing 🔴 Critical items

Phase 2: Solution Validation Checklist (23 Points) {#solution-validation}

You've validated the problem. Now validate that YOUR solution is the right approach.

2.1 Solution-Problem Fit (8 Points)

🔴 Critical Items:

  • [ ] S2.1 My solution directly addresses the root cause, not symptoms

  • Evidence needed: Mapping solution features to root causes

  • [ ] S2.2 Customers confirm the solution would solve their problem (not just "interesting")

  • Evidence needed: Solution validation interview responses

  • [ ] S2.3 The solution can be explained in under 30 seconds

  • Evidence needed: Elevator pitch tested with strangers

🟡 Important Items:

  • [ ] S2.4 The solution doesn't require significant behavior change from users

  • Evidence needed: Behavior change assessment

  • [ ] S2.5 The solution fits into existing customer workflows

  • Evidence needed: Workflow integration analysis

  • [ ] S2.6 The solution is 10x better than current alternatives (not just 2x)

  • Evidence needed: Feature/benefit comparison with 10x improvements identified

  • [ ] S2.7 Users can understand the value without a demo

  • Evidence needed: Landing page tests, one-liner comprehension tests

  • [ ] S2.8 The solution timing is right (technology, market, culture ready)

  • Evidence needed: Technology readiness assessment, cultural trend analysis

2.2 Solution Differentiation (7 Points)

┌─────────────────────────────────────────────────────────────────┐
│               DIFFERENTIATION FRAMEWORK                         │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Strong Differentiation (Pick at least 2):                      │
│                                                                 │
│  💎 10x Better       Do one thing 10x better than anyone        │
│  💰 10x Cheaper      Same quality at 1/10th the price           │
│  ⚡ 10x Faster       Dramatically faster to value               │
│  🎯 New Segment      Serve an underserved customer segment      │
│  🔧 New Tech         Leverage technology nobody else has        │
│  📦 New Model        Fundamentally different business model     │
│                                                                 │
│  Weak Differentiation (Avoid):                                  │
│  ❌ "Better UX" (everyone says this)                            │
│  ❌ "More features" (leads to bloat)                            │
│  ❌ "Lower price only" (race to bottom)                         │
│  ❌ "We work harder" (not sustainable)                          │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] S2.9 I can articulate 2+ strong differentiators (see framework above)

  • Evidence needed: Written differentiation statement

  • [ ] S2.10 My differentiation is defensible (not easily copied)

  • Evidence needed: Defensibility analysis

🟡 Important Items:

  • [ ] S2.11 Customers value my differentiators (not just me)

  • Evidence needed: Customer feedback on differentiators

  • [ ] S2.12 Differentiation grows stronger over time (network effects, data, brand)

  • Evidence needed: Moat analysis

  • [ ] S2.13 I can explain why competitors haven't done this

  • Evidence needed: Competitive gap analysis

  • [ ] S2.14 The differentiation is obvious in the first interaction

  • Evidence needed: First-use testing feedback

  • [ ] S2.15 I have evidence the market values this type of differentiation

  • Evidence needed: Similar differentiation success stories

2.3 Solution Validation Methods (8 Points)

🔴 Critical Items:

  • [ ] S2.16 I have shown mockups/prototypes to 10+ potential customers

  • Evidence needed: Prototype test results

  • [ ] S2.17 I have received at least one pre-order or letter of intent

  • Evidence needed: LOIs, pre-orders, deposits

  • [ ] S2.18 I have a landing page with signup data

  • Evidence needed: Landing page URL and conversion data

🟡 Important Items:

  • [ ] S2.19 I have run a "fake door" test to measure interest

  • Evidence needed: Ad click data, signup rates

  • [ ] S2.20 I have conducted solution validation interviews (distinct from problem interviews)

  • Evidence needed: Solution interview transcripts

  • [ ] S2.21 I have created and tested a concierge MVP

  • Evidence needed: Concierge service delivery results

  • [ ] S2.22 Email/waitlist signup rate exceeds 5%

  • Evidence needed: Conversion rate data

  • [ ] S2.23 Potential customers have shared the concept with others (viral coefficient > 0)

  • Evidence needed: Referral tracking, sharing data

Solution Validation Score Card

Section Points Possible Your Score Minimum Required
Solution-Problem Fit 8 ___ /8 5
Solution Differentiation 7 ___ /7 5
Solution Validation Methods 8 ___ /8 5
Total Phase 2 23 ___ /23 15

🚦 GO/NO-GO Decision: - ✅ GO if score ≥ 15 with all 🔴 Critical items checked - 🟡 PAUSE if score 12-14, strengthen validation before proceeding - ❌ NO-GO if score < 12 or missing 🔴 Critical items

Phase 3: Market Validation Checklist (21 Points) {#market-validation}

A great solution to a real problem in a tiny market is still a bad startup. Validate the market.

3.1 Market Size (7 Points)

┌─────────────────────────────────────────────────────────────────┐
│                    MARKET SIZE FRAMEWORK                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  TAM (Total Addressable Market)                                 │
│  └── Everyone who could possibly buy                            │
│      "All SMBs that do email marketing"                         │
│                                                                 │
│  SAM (Serviceable Addressable Market)                           │
│  └── Market you could reach with your model                     │
│      "English-speaking SMBs using Shopify"                      │
│                                                                 │
│  SOM (Serviceable Obtainable Market)                            │
│  └── Realistic market share in 3-5 years                        │
│      "500 Shopify stores we can acquire"                        │
│                                                                 │
│  ┌─────────────────────────────────────────────────────────┐   │
│  │  Minimum viable market sizes:                            │   │
│  │  • VC-backed: SAM > $1B                                  │   │
│  │  • Bootstrapped: SAM > $10M                              │   │
│  │  • Indie/Lifestyle: SAM > $1M                            │   │
│  └─────────────────────────────────────────────────────────┘   │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] M3.1 I have calculated TAM using bottom-up methodology (not top-down)

  • Evidence needed: TAM calculation spreadsheet

  • [ ] M3.2 SAM is large enough for my business goals

  • Evidence needed: SAM calculation with reasoning

  • [ ] M3.3 I can identify 100+ potential customers by name/company today

  • Evidence needed: Prospect list

🟡 Important Items:

  • [ ] M3.4 The market is growing (>10% YoY)

  • Evidence needed: Market growth data from reports/trends

  • [ ] M3.5 I have validated market size with industry reports or surveys

  • Evidence needed: Report citations, survey data

  • [ ] M3.6 I understand market concentration (fragmented vs. consolidated)

  • Evidence needed: Market concentration analysis

  • [ ] M3.7 Adjacent markets could expand my TAM over time

  • Evidence needed: Adjacent market identification

3.2 Market Dynamics (7 Points)

🔴 Critical Items:

  • [ ] M3.8 I understand who the market incumbents are and their market share

  • Evidence needed: Competitive landscape map

  • [ ] M3.9 I know why now is the right time for this market

  • Evidence needed: Timing analysis (technology, regulation, behavior shifts)

🟡 Important Items:

  • [ ] M3.10 I understand market trends affecting my category

  • Evidence needed: Trend analysis document

  • [ ] M3.11 I have identified tailwinds that will grow this market

  • Evidence needed: Tailwind documentation

  • [ ] M3.12 I understand regulatory environment and potential changes

  • Evidence needed: Regulatory analysis

  • [ ] M3.13 Technology changes favor new entrants (not incumbents)

  • Evidence needed: Technology shift analysis

  • [ ] M3.14 Customer behavior is shifting in ways that help my solution

  • Evidence needed: Behavior trend data

3.3 Market Accessibility (7 Points)

🔴 Critical Items:

  • [ ] M3.15 I have a clear path to reach my first 100 customers

  • Evidence needed: Customer acquisition plan

  • [ ] M3.16 Customer acquisition channels exist and are not saturated

  • Evidence needed: Channel analysis

🟡 Important Items:

  • [ ] M3.17 I can access my target market without massive capital requirements

  • Evidence needed: Capital requirements analysis

  • [ ] M3.18 Customers are reachable through digital channels

  • Evidence needed: Digital channel identification

  • [ ] M3.19 There are communities where my customers congregate

  • Evidence needed: Community mapping

  • [ ] M3.20 Word-of-mouth potential exists in this market

  • Evidence needed: Viral coefficient analysis

  • [ ] M3.21 Gatekeepers/intermediaries won't block my access

  • Evidence needed: Gatekeeper analysis

Market Validation Score Card

Section Points Possible Your Score Minimum Required
Market Size 7 ___ /7 5
Market Dynamics 7 ___ /7 4
Market Accessibility 7 ___ /7 4
Total Phase 3 21 ___ /21 13

Phase 4: Competitive Analysis Checklist (18 Points) {#competitive-analysis}

Understanding competition isn't about copying—it's about finding gaps and opportunities.

4.1 Competitor Identification (6 Points)

┌─────────────────────────────────────────────────────────────────┐
│                 COMPETITOR CATEGORIES                           │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Direct Competitors                                             │
│  └── Same problem, same solution type                           │
│      Example: Notion vs. Coda                                   │
│                                                                 │
│  Indirect Competitors                                           │
│  └── Same problem, different solution type                      │
│      Example: Notion vs. pen and paper                          │
│                                                                 │
│  Potential Competitors                                          │
│  └── Could easily enter your market                             │
│      Example: Microsoft adding Notion-like features             │
│                                                                 │
│  Substitute Solutions                                           │
│  └── Alternative ways customers solve the problem               │
│      Example: Hiring a virtual assistant                        │
│                                                                 │
│  ⚠️  "No competition" is usually a RED FLAG, not a green light  │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] C4.1 I have identified at least 5 direct competitors

  • Evidence needed: Competitor list with URLs

  • [ ] C4.2 I understand why customers choose each competitor

  • Evidence needed: Competitor positioning analysis

🟡 Important Items:

  • [ ] C4.3 I have mapped indirect competitors and substitutes

  • Evidence needed: Substitute solution list

  • [ ] C4.4 I have identified potential future competitors

  • Evidence needed: Potential competitor analysis

  • [ ] C4.5 I know which competitors are well-funded and growing

  • Evidence needed: Funding and growth data

  • [ ] C4.6 I understand competitor pricing strategies

  • Evidence needed: Pricing comparison table

4.2 Competitive Positioning (6 Points)

🔴 Critical Items:

  • [ ] C4.7 I have a positioning statement that differentiates from top 3 competitors

  • Evidence needed: Written positioning statement

  • [ ] C4.8 I can articulate why a customer would switch from each top competitor

  • Evidence needed: Switch motivation analysis

🟡 Important Items:

  • [ ] C4.9 I have identified underserved segments competitors are ignoring

  • Evidence needed: Segment gap analysis

  • [ ] C4.10 I know competitor weaknesses (validated, not assumed)

  • Evidence needed: Competitor reviews, customer interviews

  • [ ] C4.11 I understand competitor strengths and how to counter them

  • Evidence needed: Competitive counter-strategy

  • [ ] C4.12 I have a clear "wedge" strategy to enter the market

  • Evidence needed: Wedge strategy document

4.3 Competitive Sustainability (6 Points)

🔴 Critical Items:

  • [ ] C4.13 I have identified how I'll maintain differentiation over time
  • Evidence needed: Moat strategy

🟡 Important Items:

  • [ ] C4.14 Competitors can't easily copy my core differentiation

  • Evidence needed: Defensibility analysis

  • [ ] C4.15 I have network effects or other compounding advantages planned

  • Evidence needed: Network effect strategy

  • [ ] C4.16 I can win a price war if one occurs (or have a plan to avoid it)

  • Evidence needed: Pricing resilience analysis

  • [ ] C4.17 I understand competitor response to new entrants (aggressive vs. passive)

  • Evidence needed: Historical competitor response analysis

  • [ ] C4.18 I have a plan for if a large company enters my space

  • Evidence needed: Big company entry contingency plan

Competitive Analysis Score Card

Section Points Possible Your Score Minimum Required
Competitor Identification 6 ___ /6 4
Competitive Positioning 6 ___ /6 4
Competitive Sustainability 6 ___ /6 3
Total Phase 4 18 ___ /18 11

Phase 5: Technical Feasibility Checklist (15 Points) {#technical-feasibility}

Can you actually build this? This section is especially critical for non-technical founders.

5.1 Core Technology (5 Points)

🔴 Critical Items:

  • [ ] T5.1 The core technology to build this exists today

  • Evidence needed: Technology stack identification

  • [ ] T5.2 I (or my team) have the skills to build the MVP

  • Evidence needed: Skills assessment

🟡 Important Items:

  • [ ] T5.3 No dependencies on unproven or experimental technology

  • Evidence needed: Technology maturity assessment

  • [ ] T5.4 Open-source tools or affordable platforms exist to accelerate development

  • Evidence needed: Tool/platform list

  • [ ] T5.5 The technology stack is maintainable long-term

  • Evidence needed: Tech stack sustainability analysis

5.2 Development Scope (5 Points)

┌─────────────────────────────────────────────────────────────────┐
│                      MVP SCOPE FRAMEWORK                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Good MVP Scope:                                                │
│  ├── Solves the core problem completely (not partially)         │
│  ├── Does ONE thing exceptionally well                          │
│  ├── Can be built in 4-12 weeks                                 │
│  ├── Requires no external integrations to be useful             │
│  └── Can acquire first 100 users                                │
│                                                                 │
│  Bad MVP Scope (Over-scoped):                                   │
│  ├── "Full platform" from day one                               │
│  ├── Multiple user types with different features                │
│  ├── Complex integrations required                              │
│  ├── Enterprise features before having any users                │
│  └── "Must be complete" before launching                        │
│                                                                 │
│  ⏱️  Rule of Thumb: If MVP takes > 3 months, scope is wrong     │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] T5.6 MVP can be built in 3 months or less

  • Evidence needed: Development timeline estimate

  • [ ] T5.7 MVP scope is defined and written down

  • Evidence needed: MVP feature spec

🟡 Important Items:

  • [ ] T5.8 I've identified what NOT to build in the MVP

  • Evidence needed: "Not MVP" feature list

  • [ ] T5.9 Technical complexity is proportional to value delivered

  • Evidence needed: Value vs. complexity mapping

  • [ ] T5.10 I have a plan to handle scale if traction occurs

  • Evidence needed: Scaling roadmap (high-level)

5.3 Technical Risks (5 Points)

🔴 Critical Items:

  • [ ] T5.11 I have identified the biggest technical risks
  • Evidence needed: Technical risk register

🟡 Important Items:

  • [ ] T5.12 I have mitigation plans for each technical risk

  • Evidence needed: Risk mitigation strategies

  • [ ] T5.13 Third-party API dependencies are stable and have alternatives

  • Evidence needed: API dependency analysis

  • [ ] T5.14 Data storage and privacy requirements are understood

  • Evidence needed: Data/privacy requirements doc

  • [ ] T5.15 Infrastructure costs are estimated and affordable

  • Evidence needed: Infrastructure cost projections

Technical Feasibility Score Card

Section Points Possible Your Score Minimum Required
Core Technology 5 ___ /5 4
Development Scope 5 ___ /5 3
Technical Risks 5 ___ /5 2
Total Phase 5 15 ___ /15 9

Phase 6: Business Model Checklist (14 Points) {#business-model}

How will you make money, and does the math work?

6.1 Revenue Model (5 Points)

┌─────────────────────────────────────────────────────────────────┐
│                   REVENUE MODEL OPTIONS                         │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Subscription (SaaS)                                            │
│  ├── Pros: Recurring, predictable, high LTV                     │
│  ├── Cons: Churn risk, long payback period                      │
│  └── Best for: B2B tools, productivity apps                     │
│                                                                 │
│  One-Time Purchase                                              │
│  ├── Pros: Simple, no churn                                     │
│  ├── Cons: Lower LTV, must keep acquiring                       │
│  └── Best for: Extensions, utilities, games                     │
│                                                                 │
│  Usage-Based                                                    │
│  ├── Pros: Scales with customer value                           │
│  ├── Cons: Revenue volatility                                   │
│  └── Best for: APIs, infrastructure, AI tools                   │
│                                                                 │
│  Freemium                                                       │
│  ├── Pros: Wide adoption, viral growth                          │
│  ├── Cons: Low conversion rates (2-5%)                          │
│  └── Best for: Consumer apps, developer tools                   │
│                                                                 │
│  Marketplace/Transaction Fee                                    │
│  ├── Pros: Aligned incentives                                   │
│  ├── Cons: Chicken-egg problem, leakage                         │
│  └── Best for: Two-sided platforms                              │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] B6.1 I have chosen a revenue model that fits my solution

  • Evidence needed: Revenue model selection rationale

  • [ ] B6.2 Target customers have budget for this type of purchase

  • Evidence needed: Budget validation from interviews

🟡 Important Items:

  • [ ] B6.3 Pricing is validated with potential customers

  • Evidence needed: Pricing survey/interview data

  • [ ] B6.4 Revenue model aligns with customer value perception

  • Evidence needed: Value-pricing alignment analysis

  • [ ] B6.5 I have a pricing page/strategy designed

  • Evidence needed: Pricing page mockup or strategy doc

6.2 Unit Economics (5 Points)

🔴 Critical Items:

  • [ ] B6.6 I have calculated Customer Acquisition Cost (CAC) estimate

  • Evidence needed: CAC calculation

  • [ ] B6.7 I have estimated Lifetime Value (LTV)

  • Evidence needed: LTV calculation

  • [ ] B6.8 LTV:CAC ratio is at least 3:1 (or path to get there)

  • Evidence needed: LTV:CAC ratio calculation

🟡 Important Items:

  • [ ] B6.9 Payback period is acceptable (<12 months for bootstrapped, <18 for VC)

  • Evidence needed: Payback period calculation

  • [ ] B6.10 I understand my gross margin and it's healthy (>50%)

  • Evidence needed: Gross margin calculation

6.3 Business Viability (4 Points)

🔴 Critical Items:

  • [ ] B6.11 I have calculated runway needs (months to break-even)
  • Evidence needed: Runway calculation

🟡 Important Items:

  • [ ] B6.12 I have funding strategy aligned with business needs

  • Evidence needed: Funding strategy document

  • [ ] B6.13 Revenue potential justifies the effort (minimum viable outcome)

  • Evidence needed: Revenue projections

  • [ ] B6.14 Business can be profitable at reasonable scale

  • Evidence needed: Break-even analysis

Business Model Score Card

Section Points Possible Your Score Minimum Required
Revenue Model 5 ___ /5 3
Unit Economics 5 ___ /5 4
Business Viability 4 ___ /4 2
Total Phase 6 14 ___ /14 9

Phase 7: Go-to-Market Checklist (9 Points) {#go-to-market}

How will you get this product in front of customers?

7.1 Acquisition Strategy (5 Points)

┌─────────────────────────────────────────────────────────────────┐
│               ACQUISITION CHANNEL MATRIX                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Channel          │ Cost │ Speed │ Scale │ Best For            │
│  ─────────────────┼──────┼───────┼───────┼─────────────────────│
│  Content/SEO      │ Low  │ Slow  │ High  │ Education, SaaS     │
│  Paid Ads         │ High │ Fast  │ High  │ Proven products     │
│  Social Media     │ Low  │ Med   │ Med   │ Consumer, B2C       │
│  Communities      │ Low  │ Med   │ Low   │ Niche products      │
│  Product Hunt     │ Low  │ Fast  │ Low   │ Tech, dev tools     │
│  Partnerships     │ Med  │ Med   │ High  │ B2B, enterprise     │
│  Referral         │ Low  │ Med   │ High  │ High-value products │
│  Outbound Sales   │ High │ Med   │ Med   │ B2B, high ACV       │
│  App Stores       │ Low  │ Med   │ High  │ Mobile, extensions  │
│                                                                 │
│  Rule: Test 2-3 channels initially, double down on winners     │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

🔴 Critical Items:

  • [ ] G7.1 I have identified my primary acquisition channel

  • Evidence needed: Primary channel selection with rationale

  • [ ] G7.2 I have a plan to get my first 10 customers

  • Evidence needed: First 10 customers plan

🟡 Important Items:

  • [ ] G7.3 I have identified 2-3 backup channels

  • Evidence needed: Backup channel list

  • [ ] G7.4 Acquisition channels are affordable at my stage

  • Evidence needed: Channel cost analysis

  • [ ] G7.5 I understand the metrics I'll track for each channel

  • Evidence needed: Channel metrics framework

7.2 Launch Strategy (4 Points)

🔴 Critical Items:

  • [ ] G7.6 I have a launch plan with specific tactics
  • Evidence needed: Launch plan document

🟡 Important Items:

  • [ ] G7.7 I have a waitlist or early access strategy

  • Evidence needed: Waitlist/early access setup

  • [ ] G7.8 I understand post-launch retention/activation requirements

  • Evidence needed: Retention/activation strategy

  • [ ] G7.9 I have feedback collection mechanisms planned

  • Evidence needed: Feedback collection plan

Go-to-Market Score Card

Section Points Possible Your Score Minimum Required
Acquisition Strategy 5 ___ /5 3
Launch Strategy 4 ___ /4 2
Total Phase 7 9 ___ /9 5

The Master Scoring System {#scoring-system}

Total Validation Score

Phase Max Points Your Score Min Required Pass?
1. Problem Validation 27 ___ 19 ⬜
2. Solution Validation 23 ___ 15 ⬜
3. Market Validation 21 ___ 13 ⬜
4. Competitive Analysis 18 ___ 11 ⬜
5. Technical Feasibility 15 ___ 9 ⬜
6. Business Model 14 ___ 9 ⬜
7. Go-to-Market 9 ___ 5 ⬜
TOTAL 127 ___ 81 ⬜

🚦 Final Verdict

┌─────────────────────────────────────────────────────────────────┐
│                      FINAL VERDICT                              │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ✅ GO (Score ≥ 100, all phases pass, all 🔴 items checked)     │
│     Start building! You have strong validation.                 │
│                                                                 │
│  🟡 MAYBE (Score 81-99, most phases pass)                       │
│     Address specific gaps before committing fully.              │
│     Consider a smaller MVP or different approach.               │
│                                                                 │
│  ❌ NO-GO (Score < 81, or any phase fails, or missing 🔴 items) │
│     Pivot the idea or move to a different concept.              │
│     This idea has significant validation gaps.                  │
│                                                                 │
│  ⚠️  Dealbreaker: Missing ANY 🔴 Critical item = automatic NO-GO│
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Critical Item Tracker

Count your 🔴 Critical items (must ALL be checked for GO):

Phase Critical Items Checked
1. Problem P1.1, P1.2, P1.3, P1.4, P1.5, P1.10, P1.11, P1.12, P1.19, P1.20, P1.21 ___/11
2. Solution S2.1, S2.2, S2.3, S2.9, S2.10, S2.16, S2.17, S2.18 ___/8
3. Market M3.1, M3.2, M3.3, M3.8, M3.9, M3.15, M3.16 ___/7
4. Competitive C4.1, C4.2, C4.7, C4.8, C4.13 ___/5
5. Technical T5.1, T5.2, T5.6, T5.7, T5.11 ___/5
6. Business B6.1, B6.2, B6.6, B6.7, B6.8, B6.11 ___/6
7. GTM G7.1, G7.2, G7.6 ___/3
TOTAL 45 Critical Items ___/45

Checklist by Startup Type {#by-startup-type}

Different startup types need different emphasis. Here's how to weight each phase:

🖥️ SaaS Startup

Phase Standard Weight SaaS Weight Focus Areas
Problem Validation 21% 25% Workflow integration, frequency
Solution Validation 18% 20% Time savings, efficiency gains
Market Validation 17% 15% Can be niche initially
Competitive Analysis 14% 15% Feature comparison, switching costs
Technical Feasibility 12% 10% Standard web tech
Business Model 11% 10% MRR, churn, expansion
Go-to-Market 7% 5% Content, product-led growth

Key SaaS Checklist Additions: - [ ] Monthly recurring value (MRV) calculation completed - [ ] Churn drivers identified and mitigation planned - [ ] Expansion revenue opportunities mapped - [ ] Self-serve vs. sales-assist decision made - [ ] Free trial or freemium strategy validated

🧩 Browser Extension

Phase Standard Weight Extension Weight Focus Areas
Problem Validation 21% 20% Browser workflow problems
Solution Validation 18% 15% Quick value demonstration
Market Validation 17% 15% Chrome Web Store data
Competitive Analysis 14% 20% CWS search rankings
Technical Feasibility 12% 10% Browser API capabilities
Business Model 11% 10% Monetization model choice
Go-to-Market 7% 10% CWS optimization critical

Key Extension Checklist Additions: - [ ] Chrome Web Store keyword research completed - [ ] Competitor user counts and ratings analyzed - [ ] Browser API permissions requirements mapped - [ ] Monetization model selected (freemium, one-time, subscription) - [ ] CWS listing optimization strategy planned - [ ] Cross-browser strategy considered

For comprehensive extension validation, see our Chrome Extension Validation Guide.

📱 Mobile App

Phase Standard Weight Mobile Weight Focus Areas
Problem Validation 21% 20% Mobile-first problems
Solution Validation 18% 15% UX, immediate value
Market Validation 17% 20% App store data
Competitive Analysis 14% 15% App store rankings
Technical Feasibility 12% 10% Platform considerations
Business Model 11% 10% In-app purchases, subscriptions
Go-to-Market 7% 10% ASO, paid acquisition

Key Mobile Checklist Additions: - [ ] iOS vs. Android priority decision made - [ ] App Store Optimization (ASO) keywords researched - [ ] Competitor download estimates gathered - [ ] In-app purchase or subscription model validated - [ ] User session frequency estimates calculated - [ ] App store review management planned

🏢 B2B/Enterprise

Phase Standard Weight B2B Weight Focus Areas
Problem Validation 21% 25% Business impact, ROI
Solution Validation 18% 20% Integration, security
Market Validation 17% 15% Industry focus
Competitive Analysis 14% 10% Often greenfield
Technical Feasibility 12% 10% Enterprise requirements
Business Model 11% 10% ACV, sales cycle
Go-to-Market 7% 10% Sales process critical

Key B2B Checklist Additions: - [ ] Buyer persona vs. user persona mapped - [ ] Decision-maker identification process validated - [ ] Sales cycle length estimated - [ ] Security and compliance requirements documented - [ ] Integration requirements mapped - [ ] Contract value and terms validated

Red Flags and Dealbreakers {#red-flags}

🚨 Absolute Dealbreakers

Stop immediately if you encounter any of these:

┌─────────────────────────────────────────────────────────────────┐
│                    ABSOLUTE DEALBREAKERS                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ❌ Nobody will describe the problem without prompting          │
│     → Problem doesn't exist in their minds                      │
│                                                                 │
│  ❌ Nobody is currently spending money on solutions             │
│     → Problem isn't painful enough to pay for                   │
│                                                                 │
│  ❌ Can't find 100 potential customers by name                  │
│     → Market doesn't exist or is too hard to reach              │
│                                                                 │
│  ❌ Zero pre-orders after 50+ conversations                     │
│     → Solution isn't compelling                                 │
│                                                                 │
│  ❌ Core technology doesn't exist                               │
│     → Building infrastructure, not product                      │
│                                                                 │
│  ❌ LTV:CAC < 1:1 with no path to improvement                   │
│     → Business model fundamentally broken                       │
│                                                                 │
│  ❌ Requires regulatory approval you can't get                  │
│     → Legal blockers kill startups                              │
│                                                                 │
│  ❌ You need a big company's permission to succeed              │
│     → Platform risk too high                                    │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

⚠️ Serious Warning Signs

These aren't automatic dealbreakers, but require serious consideration:

Warning Sign Risk Level Required Action
Only friends/family validate the idea High Get 10+ strangers to validate
"Everyone" is the target customer High Define specific ICP
Solution looking for problem High Start over with problem interviews
Requires behavior change Medium Validate willingness to change
Complex technical dependencies Medium De-risk with spikes/prototypes
Crowded market with funded players Medium Validate differentiation rigorously
Long sales cycle (6+ months) Medium Ensure runway matches
One-time purchase, low ACV Medium Calculate volume requirements
Dependent on a single channel Medium Identify backup channels
Requires network effects to be useful Medium Plan critical mass strategy

🟡 Minor Concerns (Manageable)

Concern Mitigation Strategy
Small initial market Start niche, expand later
Existing competitors Differentiate aggressively
Technical learning curve Partner or hire expertise
Limited initial budget Bootstrap-friendly approach
Solo founder Find co-founder or advisors

Case Studies: Checklists in Action {#case-studies}

Case Study 1: GO Decision — B2B Scheduling Tool

┌─────────────────────────────────────────────────────────────────┐
│  CASE STUDY: CalendarHero (Fictional B2B Scheduling Tool)       │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Founder: Sarah, former sales manager                           │
│  Idea: AI-powered scheduling for sales teams                    │
│                                                                 │
│  VALIDATION RESULTS:                                            │
│                                                                 │
│  Phase 1: Problem ✅ 24/27                                      │
│  ├── Interviewed 25 sales managers                              │
│  ├── Found they waste 8 hours/week on scheduling                │
│  ├── Current tools cost $500/month per team                     │
│  └── Identified "demo no-shows" as acute pain point             │
│                                                                 │
│  Phase 2: Solution ✅ 19/23                                     │
│  ├── Prototype shown to 15 potential customers                  │
│  ├── 4 pre-orders secured at $200/month                         │
│  ├── Clear 10x improvement in no-show rates                     │
│  └── Landing page: 12% conversion rate                          │
│                                                                 │
│  Phase 3: Market ✅ 17/21                                       │
│  ├── TAM: $2.3B scheduling software market                      │
│  ├── SAM: $450M (sales teams, English-speaking)                 │
│  ├── Growing 15% YoY                                            │
│  └── 500+ sales teams identified in target segment              │
│                                                                 │
│  Phase 4: Competitive ✅ 14/18                                  │
│  ├── Main competitors: Calendly, HubSpot                        │
│  ├── Gap: No AI-powered no-show prediction                      │
│  ├── Switching cost is low                                      │
│  └── Clear wedge strategy via demo scheduling                   │
│                                                                 │
│  Phase 5: Technical ✅ 12/15                                    │
│  ├── Standard web stack + calendar APIs                         │
│  ├── ML component for predictions                               │
│  ├── MVP scope: 8 weeks                                         │
│  └── Sarah's brother is a full-stack dev                        │
│                                                                 │
│  Phase 6: Business ✅ 11/14                                     │
│  ├── $200/month per team subscription                           │
│  ├── CAC estimate: $400 (content + trials)                      │
│  ├── LTV estimate: $4,800 (2-year retention)                    │
│  └── LTV:CAC = 12:1 ✅                                          │
│                                                                 │
│  Phase 7: GTM ✅ 7/9                                            │
│  ├── Primary channel: LinkedIn content + cold outreach          │
│  ├── Secondary: Product Hunt, partnerships                      │
│  └── First 10 customers: warm network + pre-orders              │
│                                                                 │
│  TOTAL SCORE: 104/127 ✅                                        │
│  CRITICAL ITEMS: 45/45 ✅                                       │
│                                                                 │
│  VERDICT: ✅ GO                                                 │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Key Success Factors: - Deep domain expertise from personal experience - Pre-orders before building - Clear differentiation (AI-powered predictions) - Healthy unit economics - Specific ICP (sales teams, not "everyone")

Case Study 2: NO-GO Decision — General Productivity App

┌─────────────────────────────────────────────────────────────────┐
│  CASE STUDY: TaskMaster Pro (Fictional Productivity App)        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Founder: Mike, software developer                              │
│  Idea: All-in-one productivity app to replace everything        │
│                                                                 │
│  VALIDATION RESULTS:                                            │
│                                                                 │
│  Phase 1: Problem ⚠️ 14/27                                      │
│  ├── Interviewed only 8 people (all tech friends)               │
│  ├── Problem described as "too many tools"                      │
│  ├── But people aren't actively seeking solutions               │
│  └── No $ spent on solving this specific problem                │
│                                                                 │
│  Phase 2: Solution ❌ 9/23                                      │
│  ├── No prototype tested                                        │
│  ├── Zero pre-orders                                            │
│  ├── Landing page: 1.2% conversion rate                         │
│  └── Differentiation: "we do everything" (not specific)         │
│                                                                 │
│  Phase 3: Market ⚠️ 11/21                                       │
│  ├── TAM: $15B productivity market                              │
│  ├── SAM: Unclear ("everyone")                                  │
│  ├── Couldn't identify 100 prospects by name                    │
│  └── Market oversaturated                                       │
│                                                                 │
│  Phase 4: Competitive ❌ 6/18                                   │
│  ├── Competitors: Notion, Todoist, Asana, etc.                  │
│  ├── No clear differentiation                                   │
│  ├── Competing against well-funded players                      │
│  └── No defensible moat                                         │
│                                                                 │
│  Phase 5: Technical ⚠️ 8/15                                     │
│  ├── Scope too large for MVP                                    │
│  ├── Estimates: 6+ months to basic version                      │
│  └── Many integrations required                                 │
│                                                                 │
│  Phase 6: Business ❌ 5/14                                      │
│  ├── Freemium model, 2% conversion estimate                     │
│  ├── CAC: Unknown, likely high in crowded market                │
│  ├── LTV: Low due to heavy churn in productivity                │
│  └── LTV:CAC < 1:1                                              │
│                                                                 │
│  Phase 7: GTM ⚠️ 4/9                                            │
│  ├── No clear primary channel                                   │
│  ├── Hoping for "viral growth"                                  │
│  └── No plan for first 10 customers                             │
│                                                                 │
│  TOTAL SCORE: 57/127 ❌                                         │
│  CRITICAL ITEMS: 28/45 ❌                                       │
│                                                                 │
│  VERDICT: ❌ NO-GO                                              │
│                                                                 │
│  RECOMMENDATION:                                                │
│  Narrow down to ONE specific workflow for ONE user type.        │
│  Example: "Task management for freelance designers"             │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Key Failure Points: - Too broad a vision ("everything for everyone") - No clear differentiation from established players - Insufficient customer interviews - Zero pre-orders or concrete interest - Overscoped MVP

Case Study 3: PIVOT Decision — Chrome Extension

┌─────────────────────────────────────────────────────────────────┐
│  CASE STUDY: TabSaver Extension (Real Example, Anonymized)      │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Original Idea: Tab manager for power users                     │
│  Initial Score: 68/127 (MAYBE territory)                        │
│                                                                 │
│  KEY FINDING DURING VALIDATION:                                 │
│                                                                 │
│  During customer interviews, founder discovered:                │
│  ├── Tab management wasn't the core pain                        │
│  ├── Research workflows were the real problem                   │
│  ├── Users wanted to save "research sessions"                   │
│  └── Existing solutions focused on tabs, not research           │
│                                                                 │
│  PIVOT: Tab manager → Research Session Manager                  │
│                                                                 │
│  POST-PIVOT VALIDATION:                                         │
│                                                                 │
│  Problem Validation: 22/27 (up from 15)                         │
│  ├── Clear pain point: losing research context                  │
│  ├── Users spending hours recreating sessions                   │
│  └── Specific audience: academics, journalists, analysts        │
│                                                                 │
│  Solution Validation: 18/23 (up from 10)                        │
│  ├── 6 pre-orders at $29 one-time                               │
│  ├── Prototype tested with 12 researchers                       │
│  └── Clear differentiation: research context, not tabs          │
│                                                                 │
│  NEW TOTAL: 92/127 ✅                                           │
│                                                                 │
│  VERDICT: ✅ GO (after pivot)                                   │
│                                                                 │
│  OUTCOME: Extension launched, 2,000 users in 3 months,          │
│           $2,400 MRR with lifetime license model                │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Key Pivot Insights: - The checklist revealed a weak score, prompting deeper investigation - Customer interviews uncovered the real problem (research context, not tab management) - Narrow focus enabled differentiation - Same technology, different positioning = success

Printable Checklist Templates {#templates}

Quick Reference Card

┌─────────────────────────────────────────────────────────────────┐
│           STARTUP IDEA VALIDATION QUICK REFERENCE               │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  PHASE 1: PROBLEM (Min 19/27)                                   │
│  ⬜ Can describe in one sentence                                │
│  ⬜ 10+ people seeking solutions online                         │
│  ⬜ 15+ problem discovery interviews                            │
│  ⬜ People spending money on solutions                          │
│  ⬜ Problem frequency is high                                   │
│                                                                 │
│  PHASE 2: SOLUTION (Min 15/23)                                  │
│  ⬜ Addresses root cause                                        │
│  ⬜ 10x better than alternatives                                │
│  ⬜ Prototype shown to 10+ customers                            │
│  ⬜ At least 1 pre-order or LOI                                 │
│  ⬜ Landing page with 5%+ signup rate                           │
│                                                                 │
│  PHASE 3: MARKET (Min 13/21)                                    │
│  ⬜ TAM calculated bottom-up                                    │
│  ⬜ SAM matches business goals                                  │
│  ⬜ 100+ prospects identified by name                           │
│  ⬜ Clear path to first 100 customers                           │
│  ⬜ Customer acquisition channels exist                         │
│                                                                 │
│  PHASE 4: COMPETITION (Min 11/18)                               │
│  ⬜ 5+ direct competitors identified                            │
│  ⬜ Clear differentiation articulated                           │
│  ⬜ Wedge strategy defined                                      │
│  ⬜ Moat strategy planned                                       │
│                                                                 │
│  PHASE 5: TECHNICAL (Min 9/15)                                  │
│  ⬜ Technology exists today                                     │
│  ⬜ Team can build MVP                                          │
│  ⬜ MVP scope < 3 months                                        │
│  ⬜ Technical risks identified                                  │
│                                                                 │
│  PHASE 6: BUSINESS (Min 9/14)                                   │
│  ⬜ Revenue model chosen                                        │
│  ⬜ CAC estimated                                               │
│  ⬜ LTV estimated                                               │
│  ⬜ LTV:CAC ≥ 3:1                                               │
│  ⬜ Runway calculated                                           │
│                                                                 │
│  PHASE 7: GTM (Min 5/9)                                         │
│  ⬜ Primary channel identified                                  │
│  ⬜ First 10 customers plan                                     │
│  ⬜ Launch plan documented                                      │
│                                                                 │
│  TOTAL MINIMUM: 81/127                                          │
│  ALL CRITICAL ITEMS: Required for GO                            │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Weekly Validation Sprint Template

Day Focus Activities Deliverable
Mon Problem 3 customer interviews Interview notes
Tue Problem Community research, competitor reviews Pain point list
Wed Solution Prototype iteration Updated prototype
Thu Solution Prototype testing (3 tests) Test feedback
Fri Market/GTM Market sizing, channel research TAM calculation
Sat Review Score checklist, identify gaps Updated scores
Sun Plan Next week priorities Sprint plan

Common Mistakes and How to Avoid Them {#common-mistakes}

❌ Mistake 1: Asking Leading Questions

Wrong:

"Wouldn't it be great if there was an app that automatically organized your photos?"

Right:

"Walk me through how you currently manage your photos. What's most frustrating about that process?"

Why it matters: Leading questions confirm your bias, not reality.

❌ Mistake 2: Stopping at "That's a Cool Idea"

Wrong:

Customer: "That's a cool idea!" Founder: "Great, validation complete!"

Right:

Customer: "That's a cool idea!" Founder: "Thanks! Would you pay $29/month for this?" Customer: "Well, maybe..." Founder: "What would need to change for you to commit today?"

Why it matters: Compliments are free. Money is validation.

❌ Mistake 3: Skipping Competitive Research

Wrong:

"There's no competition, so the market is wide open!"

Right:

"No visible competition could mean no market. Let me dig deeper into how people currently solve this."

Why it matters: No competition usually means no market, not blue ocean.

❌ Mistake 4: Validating Features Instead of Problems

Wrong:

"Do you want a feature that does X?"

Right:

"Tell me about the last time you struggled with [problem]. What happened?"

Why it matters: Features can be wrong. Problems are truth.

❌ Mistake 5: Surveying Instead of Interviewing

Method Quality Why
Survey Low No follow-up, superficial answers
Interview High Can probe, observe body language
Observation Highest See actual behavior

The rule: Surveys confirm. Interviews discover.

❌ Mistake 6: Over-Building Before Validating

┌─────────────────────────────────────────────────────────────────┐
│              VALIDATION-TO-BUILD RATIO                          │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Ideal ratio:     70% validation / 30% building                 │
│  Common mistake:  20% validation / 80% building                 │
│                                                                 │
│  VALIDATION PROGRESSION:                                        │
│                                                                 │
│  Stage 1: Problem interviews (no building)                      │
│  Stage 2: Solution mockups (minimal building)                   │
│  Stage 3: Concierge MVP (manual, no code)                       │
│  Stage 4: MVP (finally, some code)                              │
│                                                                 │
│  ⚠️  If you're coding before Stage 4, you're doing it wrong    │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

❌ Mistake 7: Giving Up Too Early

Reality: The first version of your checklist will have gaps. That's normal.

Score Range Action Timeline
< 50 Kill idea or major pivot Now
50-80 Targeted improvements 2-4 more weeks
81-99 Minor adjustments 1-2 more weeks
100+ Build! Now

FAQ {#faq}

How long should the full validation process take?

Target: 4-8 weeks. Faster if you're experienced. Slower is rarely better—you're not doing a PhD thesis.

What if I can't get customer interviews?

Try these approaches: 1. Cold outreach on LinkedIn (5-10% response rate) 2. Reddit/forum participation (earn trust, then DM) 3. Pay for interviews ($50-100 Amazon cards) 4. Use respondent.io or similar services 5. Attend industry events (virtual or in-person)

If you truly can't reach customers, that's a red flag about market accessibility.

Can I validate multiple ideas at once?

Yes, but carefully: - Run 2-3 ideas through Phase 1 in parallel - Only advance the winner to Phase 2+ - Don't spread yourself too thin

What if the checklist says NO-GO but I still believe in the idea?

Ask yourself: 1. Do I have evidence the checklist missed? 2. Am I emotionally attached? 3. What would change my mind?

If you have new evidence, re-run that section. If not, trust the process—it exists to protect you from confirmation bias.

How do I validate a marketplace or network-effect business?

Extra focus on: - Both sides of the market (separate Phase 1 for each) - Critical mass requirements - Chicken-egg solution - Geographic or vertical focusing

See our Marketplace Validation Guide for detailed checklist additions.

Is this checklist different for bootstrapped vs. VC-backed?

Mostly the same, with these differences:

Aspect Bootstrapped VC-Backed
Market size minimum SAM > $10M SAM > $1B
Timeline pressure Lower Higher
LTV:CAC acceptable 3:1 3:1 (but higher CAC OK)
Runway concerns Critical Less critical (raised)
Growth rate expectations Sustainable Aggressive

What validation tools do you recommend?

For a comprehensive list, see our Startup Validation Tools Guide.

Quick recommendations: - Customer interviews: Zoom, Grain - Landing pages: Carrd, Framer - Surveys: Typeform, Tally - Competitor analysis: SimilarWeb, BuiltWith - Idea validation: NicheCheck (our tool!)

Summary and Next Steps {#summary}

Key Takeaways

  1. 127 checkpoints, 7 phases, 45 critical items — this is the complete validation framework
  2. Minimum score: 81/127 with all critical items checked for a GO decision
  3. Order matters — complete phases sequentially, don't skip ahead
  4. Evidence required — checking a box requires actual proof, not assumptions
  5. Speed matters — target 4-8 weeks for full validation
  6. Failure is learning — killing a bad idea early saves months/years

Your Next Steps

If you haven't started: 1. Download this checklist (bookmark this page) 2. Schedule your first 5 customer interviews this week 3. Start with Phase 1: Problem Validation 4. Track your scores as you progress

If you're mid-validation: 1. Score your current progress honestly 2. Identify gaps in critical items 3. Address gaps before proceeding 4. Don't rationalize weak scores

If you're complete: 1. Calculate your total score 2. Check all 45 critical items 3. Make your GO/MAYBE/NO-GO decision 4. If GO: Start building your MVP 5. If MAYBE: Address specific gaps 6. If NO-GO: Pivot or move to next idea

Validate Faster with NicheCheck

Tired of manual validation? NicheCheck automates key parts of this checklist:

  • ✅ Competitive analysis (Phase 4)
  • ✅ Market sizing estimates (Phase 3)
  • ✅ Search volume data (demand validation)
  • ✅ Technical complexity assessment (Phase 5)

Get your GO/MAYBE/NO-GO verdict in minutes, not weeks.

Try NicheCheck Free →

Free tool: Quickly check if your niche is already taken with our free niche checker -- no signup required.

Last updated: December 2024

This checklist is based on lean startup methodology, combined with learnings from 500+ startup validation interviews and analysis of why startups fail. Use it wisely—your future self will thank you.