Startup Idea Validation

Systematic validation machine for testing ideas BEFORE building. Validate hypotheses, score opportunities, and make evidence-based GO/NO-GO decisions.

Modern Best Practices (Dec 2025):

• Run a validation ladder (interviews → smoke test → concierge/MVP → paid pilots) before building.
• Pre-register decision thresholds (avoid “moving goalposts” after seeing data).
• Separate evidence quality (strong/medium/weak) from confidence and excitement.
• Test willingness-to-pay early (pricing pages, pilots, LOIs) and treat time-to-value as a constraint.
• Handle customer/market data with purpose limitation, retention, and access controls.

When to Use This Skill

Validation Ladder (Dec 2025)

Use templates/validation-experiment-planner.md for experiment design and decision thresholds.

9-Dimension Validation Framework

Quick Reference

Verdict Thresholds

Dimension Deep Dives

1. Problem Severity (15%)

Question: Is this a "hair on fire" problem or a "nice to have"?

Signal Strength Indicators:

Evidence Sources:

• Review mining (G2, Capterra, Reddit) → startup-review-mining
• Customer interviews (5-10 minimum)
• Support ticket analysis
• Search volume for solutions

2. Market Size (12%)

Question: Is this market big enough to build a venture-scale business?

TAM/SAM/SOM Framework:

Sizing Methods:

• Top-down: Industry reports, analyst estimates
• Bottom-up: Customer count × ACV
• Comparable: Similar company revenue extrapolation

3. Market Timing (10%)

Question: Why now? What's changed that makes this possible/necessary?

Timing Signal Matrix:

Integration: Use startup-trend-prediction for timing analysis.

4. Competitive Moat (12%)

Question: What will make this defensible over time?

Moat Type Assessment:

5. Unit Economics (15%)

Question: Can this be a profitable business?

Key Metrics:

Formula Basics:

LTV = (ARPU × Gross Margin) / Monthly Churn
CAC = Total Sales & Marketing / New Customers

6. Founder-Market Fit (8%)

Question: Are you the right person/team to solve this?

Assessment Criteria:

7. Technical Feasibility (10%)

Question: Can we actually build this?

Feasibility Matrix:

8. GTM Clarity (10%)

Question: Do we know how to reach and convert customers?

GTM Readiness:

9. Risk Profile (8%)

Question: What could kill this and how likely?

Risk Categories:

Validation Workflow

START
  │
  ▼
┌─────────────────────────────────────┐
│ 1. PROBLEM VALIDATION               │
│    - Review mining (10+ sources)    │
│    - Customer interviews (5-10)     │
│    - Pain severity scoring          │
└─────────────────────────────────────┘
  │
  ▼
┌─────────────────────────────────────┐
│ 2. MARKET VALIDATION                │
│    - TAM/SAM/SOM calculation        │
│    - Timing analysis (trends)       │
│    - Competitive landscape          │
└─────────────────────────────────────┘
  │
  ▼
┌─────────────────────────────────────┐
│ 3. SOLUTION VALIDATION              │
│    - Technical feasibility          │
│    - Moat assessment                │
│    - Unit economics modeling        │
└─────────────────────────────────────┘
  │
  ▼
┌─────────────────────────────────────┐
│ 4. EXECUTION VALIDATION             │
│    - Founder-market fit             │
│    - GTM clarity                    │
│    - Risk assessment                │
└─────────────────────────────────────┘
  │
  ▼
┌─────────────────────────────────────┐
│ 5. SCORECARD & DECISION             │
│    - 9-dimension scoring            │
│    - GO/NO-GO verdict               │
│    - RAT identification             │
└─────────────────────────────────────┘
  │
  ▼
GO / CONDITIONAL GO / PIVOT / NO-GO

Navigation

Resources (Deep Dives)

Templates (Outputs)

Data

Integration Points

Receives From

• startup-review-mining - Pain point evidence
• startup-trend-prediction - Market timing data
• startup-competitive-analysis - Competitor data

Feeds Into

• router-startup - Validation results
• product-management - Validated requirements
• startup-business-models - Monetization decisions

Quick Start

Minimum Viable Validation

For rapid first-pass validation:

1. Pain Check (15 min)

   • Search G2/Capterra for competitor complaints
   • Search Reddit for problem discussions
   • Score: Is this severe enough to trigger action (not “nice to have”)?

2. Size Check (15 min)

   • How many potential customers?
   • What would they pay?
   • Is the market plausibly large enough for your target outcome? [Inference]

3. Timing Check (10 min)

   • Why now vs 2 years ago?
   • What changed?

4. Competition Check (15 min)

   • Who else is doing this?
   • What's wrong with existing solutions?

If all 4 checks pass: Proceed to full validation scorecard. If any fail: Pivot or abandon.

Key Principles

Evidence Over Opinion

Every score must have evidence:

• GOOD: "Pain score 8/10: 47 reviews mention this specific complaint (sources linked)"
• BAD: "Pain score 8/10: I think this is a real problem"

Invalidate Fast

Goal is to find reasons NOT to build:

• Cheap to kill ideas, expensive to build
• Seek disconfirming evidence
• Run the riskiest assumption test first

Iterate the Idea, Not Just the Validation

If validation reveals issues:

• Don't just re-score, adjust the idea
• Pivot to stronger position
• Find the version that scores 80+

Do / Avoid (Dec 2025)

Do

• Validate the riskiest assumption first (RAT), not the easiest to test.
• Use the ladder: interviews → smoke → concierge → paid pilots.
• Treat willingness-to-pay as a primary signal, not an afterthought.
• Write decision thresholds before running experiments.

Avoid

• Survey-only validation and hypothetical questions (“Would you use this?”).
• Sampling bias (friends, one subreddit, one review site) without triangulation.
• Building an MVP as “validation” without falsifiable hypotheses.

What Good Looks Like

• ICP: one narrow segment with a clear job, pain severity, and buying trigger.
• Evidence: 10+ direct conversations in the ICP with repeatable pain patterns (not one-off anecdotes).
• WTP: explicit pricing tests and at least one “paid” signal (deposit, pilot fee, LOI with price).
• Experiments: hypotheses + success metrics + stop rules written before execution.
• Decision: a documented go/no-go with the next smallest reversible step.

Optional: AI / Automation

Use only when explicitly requested and policy-compliant.

• Summarization/clustering: speed up synthesis, but keep raw notes + spot-checks.
• Copy drafting: generate landing page variants; humans verify claims and compliance.