Back to list
vasilyu1983

startup-idea-validation

by vasilyu1983

25🍴 6📅 Jan 23, 2026

SKILL.md


name: startup-idea-validation description: "Systematic 9-dimension validation machine for testing ideas before building. Covers problem severity, market sizing, timing, competitive moats, unit economics, founder-market fit, technical feasibility, GTM clarity, and risk profile. Makes GO/NO-GO decisions based on evidence, not assumptions." metadata: globs: | **/*.md /validation/ /ideas/ /hypothesis/

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

TriggerAction
"Validate this idea"Run full 9-dimension validation
"Is this worth building?"Run validation scorecard
"Test my hypothesis"Run hypothesis canvas
"Market size for X"Run market sizing
"Should I build X or Y?"Run comparative validation
"What's the riskiest assumption?"Run RAT analysis
"What's my runway?"Run financial modeling calculator
"Will this be profitable?"Run unit economics + cash analysis

Validation Ladder (Dec 2025)

StepGoalStrong signalWeak signalOutput
Customer interviewsValidate problem + contextRepeated pain + real workaroundsHypothetical enthusiasmNotes + quotes + JTBD
Smoke testValidate demandClicks/signups with clear intentSurvey-only interestLanding page metrics
Concierge / Wizard-of-OzValidate workflow valueUsers complete job and returnOne-off curiosityLearning report
Paid pilotValidate willingness-to-payPaid, renewed, or expanded“Will pay later”Pilot results + pricing

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

9-Dimension Validation Framework

Quick Reference

DimensionWeightKey QuestionScore Range
Problem Severity15%Hair on fire or nice to have?0-10
Market Size12%Big enough to matter?0-10
Market Timing10%Why now?0-10
Competitive Moat12%Defensible advantage?0-10
Unit Economics15%Can this be profitable?0-10
Founder-Market Fit8%Right team for this?0-10
Technical Feasibility10%Can we actually build it?0-10
GTM Clarity10%Know how to reach customers?0-10
Risk Profile8%Manageable risk level?0-10

Verdict Thresholds

ScoreVerdictAction
80-100Strong GOProceed to build
60-79Conditional GOValidate riskiest assumptions first
40-59PIVOTCore hypothesis needs rework
<40NO-GOFundamental issues, don't build

Dimension Deep Dives

1. Problem Severity (15%)

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

Signal Strength Indicators:

ScoreDescriptionEvidence
9-10Hair on fireCustomers actively seeking solutions, willing to pay premium
7-8Significant painMultiple workarounds in use, clear cost of problem
5-6Real but manageableOccasional complaints, spreadsheet solutions exist
3-4Nice to haveWould be good but not urgent
1-2No real painSolution looking for a problem

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:

MetricDefinitionMinimum Threshold
TAMTotal Addressable Market$1B+
SAMServiceable Addressable Market$100M+
SOMServiceable Obtainable Market (3yr)$10M+

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:

SignalStrongWeak
Technology enablerJust became viableHas existed for years
Regulatory changeNew opportunityNo change
Behavior shiftCOVID/platform shifts changed habitsStatus quo
Cost curve10x cheaper nowSame cost
CompetitionMarket formingSaturated

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

4. Competitive Moat (12%)

Question: What will make this defensible over time?

Moat Type Assessment:

Moat TypeStrengthBuild TimeExample
Network EffectsVery Strong18-24moMarketplace, social
Switching CostsStrong12-18moWorkflow integration
Data MoatsMedium6-12moProprietary datasets
BrandMedium24mo+Trust, reputation
RegulatoryStrongVariableLicenses, compliance
TechnologyWeak<6moCan be copied

5. Unit Economics (15%)

Question: Can this be a profitable business?

Key Metrics (2026 Benchmarks):

MetricTargetRed Flag
LTV:CAC>4:1<2:1
Payback Period<12 months>24 months
Gross Margin>70% (SaaS)<50%
NRR>100%<80%

Formula Basics:

LTV = (ARPU × Gross Margin) / Monthly Churn
CAC = Total Sales & Marketing / New Customers
Runway = Current Cash / Net Monthly Burn

Deep Analysis: Use financial-modeling-calculator.md for cash runway, scenario analysis, and investor-ready projections.

6. Founder-Market Fit (8%)

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

Assessment Criteria:

FactorStrongWeak
Domain Expertise5+ years in spaceNo experience
NetworkDirect access to buyersCold outreach only
InsightUnique perspectiveGeneric understanding
PassionPersonal connectionPure opportunity
Ability to ExecuteBuilt similar beforeFirst attempt

7. Technical Feasibility (10%)

Question: Can we actually build this?

Feasibility Matrix:

FactorScore
Core technology exists+3
Similar products exist+2
Team has built similar+2
<6 month MVP possible+2
No regulatory blockers+1

8. GTM Clarity (10%)

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

GTM Readiness:

ElementClearUnclear
ICP definitionSpecific persona"Everyone"
Acquisition channelTested, CAC knownGuessing
Sales motionPLG/Sales/Hybrid decidedTBD
PricingMarket-validatedAssumed
First 10 customersIdentifiedUnknown

9. Risk Profile (8%)

Question: What could kill this and how likely?

Risk Categories:

Risk TypeExampleMitigation
MarketDemand doesn't materializeValidate with pre-sales
TechnicalCan't build at scalePrototype early
ExecutionTeam can't deliverStart small
RegulatoryLaw changesLegal review
FundingCan't raiseBootstrap path
CompetitionIncumbent pivotsSpeed, niche

Financial Viability Analysis

Cash Runway Requirements

StageMinimum RunwayRaise Trigger
Pre-seed12 months<6 months remaining
Seed18 months<9 months remaining
Series A24 months<12 months remaining

Three-Scenario Modeling (Required for Investors)

Startups with 3+ financial scenarios secure 1.8x more funding (Abacum 2025).

ScenarioProbabilityPurpose
Pessimistic25%Stress-test runway, identify survival path
Base Case50%Primary planning scenario
Optimistic25%Upside potential, expansion triggers

Financial Red Flags (Automatic NO-GO)

FlagDescription
LTV:CAC < 2:1Unit economics fundamentally broken
Payback > 24 monthsToo long to recover customer acquisition cost
Gross margin < 50%Insufficient margin to build sustainable business
Runway < 6 monthsDesperation fundraising position
No break-even pathCannot demonstrate profitability trajectory

Full Calculator: Use financial-modeling-calculator.md for complete analysis.


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

Resources (Deep Dives)

ResourcePurpose
validation-methodology.md9-dimension scoring system details
hypothesis-testing-guide.mdHow to run validation experiments
market-sizing-patterns.mdTAM/SAM/SOM calculation methods
moat-assessment-framework.mdCompetitive barrier analysis

Templates (Outputs)

TemplateUse For
validation-scorecard.mdFull 9-dimension scoring
hypothesis-canvas.mdHypothesis testing template
validation-experiment-planner.mdHypothesis → method → metric → decision
riskiest-assumption-test.mdRAT experiment design
market-sizing-worksheet.mdTAM/SAM/SOM calculation
financial-modeling-calculator.mdBurn rate, runway, scenario analysis
go-no-go-decision.mdFinal decision template

Data

FileContents
sources.jsonValidation resources (YC, a16z, SVPG, etc.)

Integration Points

Receives From

Feeds Into


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.

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon