Not all valid ideas are viable ideas.
An idea can be validated—meaning customers have the problem and want a solution—but still fail catastrophically. Why? Because viability encompasses far more than customer demand. It includes your ability to build it, your capacity to sustain it, the economics of operating it, and the timing of launching it.
This comprehensive guide will teach you to assess every dimension of viability before committing months or years to an idea that was doomed from the start.
📑 Table of Contents
- Validation vs Viability: Critical Distinction
- The 5 Dimensions of Product Viability
- Dimension 1: Technical Feasibility
- Dimension 2: Business Model Viability
- Dimension 3: Resource Assessment
- Dimension 4: Market Timing Analysis
- Dimension 5: Founder-Market Fit
- The Viability Scoring Matrix
- Risk Assessment Framework
- Viability by Product Type
- Case Studies: Viability in Practice
- Common Viability Killers
- Templates & Tools
- FAQ
- Summary & Next Steps
Validation vs Viability: Critical Distinction {#validation-vs-viability}
🔍 Understanding the Difference
┌─────────────────────────────────────────────────────────────────────────┐
│ VALIDATION vs VIABILITY │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ VALIDATION answers: VIABILITY answers: │
│ ────────────────── ───────────────── │
│ "Do customers want this?" "Can WE successfully build and │
│ deliver this?" │
│ │
│ ┌─────────────────┐ ┌─────────────────────────────────────┐ │
│ │ VALIDATION │ │ VIABILITY │ │
│ │ │ │ │ │
│ │ • Problem │ │ • Technical: Can we build it? │ │
│ │ exists │ │ • Business: Will economics work? │ │
│ │ • Solution │ │ • Resources: Do we have capacity? │ │
│ │ wanted │ │ • Timing: Is market ready? │ │
│ │ • Price │ │ • Fit: Are we the right team? │ │
│ │ acceptable │ │ │ │
│ └─────────────────┘ └─────────────────────────────────────┘ │
│ │
│ A product can be VALIDATED but NOT VIABLE: │
│ ├── Customers want it, but we can't build it │
│ ├── Market exists, but we can't reach them affordably │
│ ├── Revenue possible, but costs exceed it │
│ ├── Demand exists, but timing is wrong │
│ └── Opportunity real, but we're not the right team │
│ │
└─────────────────────────────────────────────────────────────────────────┘
📊 The Validation-Viability Matrix
| Low Viability | High Viability | |
|---|---|---|
| High Validation | 🟡 Frustrating: Customers want it, you can't deliver | 🟢 Ideal: Clear market + ability to capture |
| Low Validation | 🔴 Kill: No demand, no ability | 🟠 Risky: You could build it, but should you? |
🎯 When to Assess Viability
┌─────────────────────────────────────────────────────────────────┐
│ ASSESSMENT TIMING │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. INITIAL IDEA PHASE (Quick Check) │
│ └── 30-minute viability gut check │
│ Can we obviously build this? Do we have resources? │
│ │
│ 2. POST-PROBLEM VALIDATION (Moderate Assessment) │
│ └── 2-4 hour deep dive │
│ Now that demand is validated, can we capture it? │
│ │
│ 3. PRE-COMMITMENT (Full Assessment) │
│ └── 1-2 day comprehensive analysis │
│ Before major investment, verify all dimensions │
│ │
│ 4. ONGOING (Continuous Monitoring) │
│ └── Monthly viability check-ins │
│ Has anything changed that affects viability? │
│ │
└─────────────────────────────────────────────────────────────────┘
The 5 Dimensions of Product Viability {#the-5-dimensions-of-viability}
🎯 Framework Overview
┌─────────────────────────────────────────────────────────────────────────┐
│ THE 5 DIMENSIONS OF VIABILITY │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌───────────────┐ │
│ │ VIABILITY │ │
│ │ SCORE │ │
│ └───────┬───────┘ │
│ │ │
│ ┌───────────────────────┼───────────────────────┐ │
│ │ │ │ │ │ │
│ ▼ ▼ ▼ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │TECHNICAL│ │BUSINESS │ │RESOURCE │ │ MARKET │ │FOUNDER │ │
│ │FEASIBLE │ │ MODEL │ │CAPACITY │ │ TIMING │ │ FIT │ │
│ └─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │ │ │ │
│ Can we Will the Do we Is now Are we │
│ build it? economics have what the right the right │
│ work? we need? time? team? │
│ │
├─────────────────────────────────────────────────────────────────────────┤
│ All 5 dimensions must score above threshold for viability │
│ One dimension failing can kill an otherwise promising product │
└─────────────────────────────────────────────────────────────────────────┘
📊 Dimension Weights by Product Type
| Product Type | Technical | Business | Resources | Timing | Founder Fit |
|---|---|---|---|---|---|
| SaaS | 25% | 30% | 15% | 15% | 15% |
| Mobile App | 20% | 25% | 15% | 25% | 15% |
| Browser Extension | 15% | 30% | 10% | 25% | 20% |
| Hardware | 35% | 20% | 25% | 10% | 10% |
| Marketplace | 15% | 35% | 20% | 20% | 10% |
| AI/ML Product | 35% | 25% | 20% | 15% | 5% |
Dimension 1: Technical Feasibility {#dimension-1-technical-feasibility}
🎯 Core Question: Can We Actually Build This?
┌─────────────────────────────────────────────────────────────────┐
│ TECHNICAL FEASIBILITY ASSESSMENT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ EVALUATE: │
│ ├── Is the core technology proven? │
│ ├── Do we have (or can we get) the required skills? │
│ ├── Are there technical dependencies we don't control? │
│ ├── What's the estimated development complexity? │
│ └── Are there regulatory/compliance requirements? │
│ │
│ FEASIBILITY SPECTRUM: │
│ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Known Unknown │ │
│ │ Technology ←──────────────────────────────→ Research │ │
│ │ │ │
│ │ 🟢 Easy 🟢 Standard 🟡 Complex 🟠 Hard 🔴 R&D │ │
│ │ │ │
│ │ Proven Proven with Requires Novel Needs │ │
│ │ stack some new significant combinations research │
│ │ integrations engineering or custom tech │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
📋 Technical Feasibility Checklist
Core Technology Assessment:
| Factor | Score (1-5) | Notes |
|---|---|---|
| Technology Maturity | Is the core tech proven in production? | |
| API/Integration Stability | Are required APIs stable and well-documented? | |
| Scalability Path | Can architecture scale with user growth? | |
| Security Requirements | Are security needs achievable? | |
| Performance Requirements | Can we hit required speed/reliability? |
Team Capability Assessment:
| Factor | Score (1-5) | Notes |
|---|---|---|
| Current Skills Match | Does team have required expertise? | |
| Learning Curve | How long to acquire missing skills? | |
| Hiring Feasibility | Can we hire needed talent? | |
| External Resources | Are contractors/agencies available? |
Dependency Assessment:
| Dependency | Risk Level | Mitigation |
|---|---|---|
| Third-party APIs | High/Med/Low | |
| Platform policies | High/Med/Low | |
| Open source libraries | High/Med/Low | |
| Cloud services | High/Med/Low | |
| Hardware suppliers | High/Med/Low |
🧪 Technical Feasibility Tests
| Test | Purpose | Duration | Cost |
|---|---|---|---|
| Spike/Proof of Concept | Validate core technical assumptions | 1-3 days | $0 |
| Architecture Review | Identify scalability issues early | 1 day | $0-$500 |
| API Integration Test | Confirm third-party integrations work | 1-2 days | $0-$100 |
| Load Testing (Simulated) | Estimate infrastructure needs | 1 day | $0-$200 |
| Security Assessment | Identify compliance requirements | 1-2 days | $0-$2000 |
📊 Technical Feasibility Scoring
┌─────────────────────────────────────────────────────────────────┐
│ TECHNICAL FEASIBILITY SCORECARD │
├─────────────────────────────────────────────────────────────────┤
│ │
│ CATEGORY SCORE (1-10) WEIGHT │
│ ───────────────────────────────────────────────────────────── │
│ Core Technology Maturity [____] × 25% │
│ Team Technical Capability [____] × 25% │
│ Dependency Risk [____] × 20% │
│ Development Complexity [____] × 15% │
│ Compliance/Regulatory [____] × 15% │
│ ───────────────────────────────────────────────────────────── │
│ WEIGHTED TOTAL: [____]/10 │
│ │
│ INTERPRETATION: │
│ ├── 8-10: Highly feasible, proceed with confidence │
│ ├── 6-7.9: Feasible with some technical risk │
│ ├── 4-5.9: Challenging, requires mitigation plan │
│ └── 1-3.9: High risk, reconsider or simplify scope │
│ │
└─────────────────────────────────────────────────────────────────┘
Related guide: Extension Development Cost for detailed technical estimation.
Dimension 2: Business Model Viability {#dimension-2-business-model-viability}
🎯 Core Question: Will the Economics Work?
┌─────────────────────────────────────────────────────────────────┐
│ BUSINESS MODEL VIABILITY │
├─────────────────────────────────────────────────────────────────┤
│ │
│ The business model must generate: │
│ │
│ Revenue > Costs + Growth Investment │
│ ▲ ▲ ▲ │
│ │ │ │ │
│ Price × COGS + Marketing + │
│ Volume Operations Development │
│ │
│ KEY RATIOS TO VALIDATE: │
│ ├── LTV:CAC > 3:1 (healthy) │
│ ├── Gross Margin > 70% (scalable) │
│ ├── Payback Period < 12 months (sustainable) │
│ └── Churn < 5% monthly (retainable) │
│ │
│ IF ANY RATIO FAILS: │
│ → The business model is NOT viable in current form │
│ → Either adjust the model or don't proceed │
│ │
└─────────────────────────────────────────────────────────────────┘
💰 Revenue Model Assessment
| Revenue Model | Viable If... | Warning Signs |
|---|---|---|
| Subscription | LTV > 3× CAC, churn < 5%/mo | High churn, low expansion revenue |
| Freemium | Conversion > 2%, viral loop exists | <1% conversion, no viral component |
| One-time Purchase | Repeat rate > 20%, AOV > $50 | No repeat, low price point |
| Usage-based | Usage grows over time, margins > 50% | Usage declines, thin margins |
| Advertising | DAU > 100K, engagement > 10 min | Low engagement, ad-blocker impact |
| Marketplace | Take rate > 5%, GMV growing | Low liquidity, high leakage |
| Licensing | Enterprise buyers exist, high ACVs | Long sales cycles, customization needed |
📊 Unit Economics Calculator
┌─────────────────────────────────────────────────────────────────┐
│ UNIT ECONOMICS MODEL │
├─────────────────────────────────────────────────────────────────┤
│ │
│ REVENUE PER CUSTOMER │
│ ───────────────────── │
│ Monthly Price: $[____]/mo │
│ Average Lifespan: [____] months │
│ Expansion Revenue: $[____]/customer │
│ │
│ LTV = (Price × Lifespan) + Expansion │
│ LTV = $[____] │
│ │
│ COST PER CUSTOMER │
│ ───────────────── │
│ Customer Acquisition Cost: $[____] │
│ Monthly Serving Cost: $[____]/mo │
│ Support Cost/Customer: $[____]/mo │
│ │
│ Total Cost = CAC + (Serving + Support) × Lifespan │
│ Total Cost = $[____] │
│ │
│ PROFITABILITY │
│ ───────────── │
│ LTV:CAC Ratio: [____]:1 │
│ Gross Margin: [____]% │
│ Payback Period: [____] months │
│ Customer Profit: $[____] │
│ │
│ VIABILITY CHECK: │
│ ├── LTV:CAC > 3:1? [ ] Yes [ ] No │
│ ├── Gross Margin > 70%? [ ] Yes [ ] No │
│ └── Payback < 12 months? [ ] Yes [ ] No │
│ │
└─────────────────────────────────────────────────────────────────┘
🎯 Business Model Red Flags
┌─────────────────────────────────────────────────────────────────┐
│ BUSINESS MODEL RED FLAGS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 🔴 CRITICAL (Kill the idea): │
│ ├── Unit economics fundamentally negative │
│ ├── No clear path to profitability │
│ ├── Market won't pay the required price │
│ └── Cost structure can't be improved │
│ │
│ 🟠 SERIOUS (Major pivot needed): │
│ ├── LTV:CAC between 1:1 and 2:1 │
│ ├── Payback period > 24 months │
│ ├── Gross margin < 50% │
│ └── High customer concentration risk │
│ │
│ 🟡 CAUTIONARY (Optimize before scaling): │
│ ├── LTV:CAC between 2:1 and 3:1 │
│ ├── Payback period 12-18 months │
│ ├── Gross margin 50-70% │
│ └── Single revenue stream dependency │
│ │
│ 🟢 HEALTHY (Proceed with confidence): │
│ ├── LTV:CAC > 3:1 │
│ ├── Payback < 12 months │
│ ├── Gross margin > 70% │
│ └── Multiple revenue streams │
│ │
└─────────────────────────────────────────────────────────────────┘
Related guide: Niche Profitability Analysis for detailed economics modeling.
Dimension 3: Resource Assessment {#dimension-3-resource-assessment}
🎯 Core Question: Do We Have What We Need?
┌─────────────────────────────────────────────────────────────────┐
│ RESOURCE ASSESSMENT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ RESOURCE CATEGORIES: │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ CAPITAL │ │ TIME │ │ TALENT │ │
│ │ 💰 │ │ ⏰ │ │ 👥 │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │ │ │ │
│ Available Runway to Team skills │
│ funding milestones and gaps │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ NETWORK │ │ TECHNOLOGY │ │ ATTENTION │ │
│ │ 🔗 │ │ 🔧 │ │ 👁️ │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │ │ │ │
│ Connections Existing Founder │
│ and reach assets bandwidth │
│ │
└─────────────────────────────────────────────────────────────────┘
💰 Capital Requirements Analysis
| Phase | Typical Cost Range | Your Estimate | Gap |
|---|---|---|---|
| MVP Development | $5K-$50K | $______ | $______ |
| Initial Launch | $2K-$20K | $______ | $______ |
| First 100 Customers | $5K-$50K | $______ | $______ |
| Team Scaling | $50K-$200K | $______ | $______ |
| 6-Month Runway | Variable | $______ | $______ |
| Total Initial Need | $______ | $______ |
Funding Options Assessment:
| Source | Amount Available | Likelihood | Timeline |
|---|---|---|---|
| Personal Savings | $______ | High | Now |
| Revenue (Bootstrap) | $______/mo | Medium | 3-6 mo |
| Friends/Family | $______ | ___% | 1-2 mo |
| Angel Investment | $______ | ___% | 3-6 mo |
| VC (if applicable) | $______ | ___% | 6-12 mo |
| Grants/Competitions | $______ | ___% | 3-6 mo |
| Debt/Credit | $______ | ___% | 1 mo |
⏰ Time Budget Analysis
┌─────────────────────────────────────────────────────────────────┐
│ TIME BUDGET ASSESSMENT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ AVAILABLE TIME: │
│ ├── Full-time dedication? [ ] Yes [ ] Part-time │
│ ├── Hours per week available: [____] hrs │
│ ├── Other commitments impact: [____] hrs/week │
│ └── Realistic net hours: [____] hrs/week │
│ │
│ MILESTONES vs TIME: │
│ │
│ Milestone Est. Hours Weeks @ Your Pace │
│ ───────────────────────────────────────────────────────────── │
│ MVP Complete [____] [____] weeks │
│ First 10 Users [____] [____] weeks │
│ Revenue Start [____] [____] weeks │
│ Product-Market Fit [____] [____] weeks │
│ │
│ RUNWAY CHECK: │
│ ├── Total time to key milestones: [____] months │
│ ├── Financial runway: [____] months │
│ └── Gap (if any): [____] months │
│ │
│ ⚠️ If milestone time > financial runway → VIABILITY RISK │
│ │
└─────────────────────────────────────────────────────────────────┘
👥 Team & Talent Assessment
Current Team Capabilities:
| Skill Needed | Current Level (1-5) | Can Hire? | Can Outsource? |
|---|---|---|---|
| Product/UX Design | |||
| Frontend Development | |||
| Backend Development | |||
| DevOps/Infrastructure | |||
| Marketing/Growth | |||
| Sales (if B2B) | |||
| Customer Support | |||
| Finance/Operations |
Team Gap Analysis:
┌─────────────────────────────────────────────────────────────────┐
│ TEAM GAP MATRIX │
├─────────────────────────────────────────────────────────────────┤
│ │
│ CRITICAL IMPORTANT NICE-TO-HAVE │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ │ │
│ │ Must fill │ Fill before │ Can wait until │ │
│ │ before │ scaling │ growth phase │ │
│ │ building │ │ │ │
│ │ │ │ │ │
│ │ ____________ │ ______________ │ ________________ │ │
│ │ ____________ │ ______________ │ ________________ │ │
│ │ ____________ │ ______________ │ ________________ │ │
│ │ │ │ │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
│ FILL STRATEGY: │
│ ├── Hire: For critical, long-term needs │
│ ├── Outsource: For one-time or specialized needs │
│ ├── Learn: For skills you can develop │
│ └── Partner: For complementary expertise │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Resource Viability Score
| Resource | Available (1-10) | Required (1-10) | Gap | Fillable? |
|---|---|---|---|---|
| Capital | Yes/No | |||
| Time | Yes/No | |||
| Technical Talent | Yes/No | |||
| Business/Growth | Yes/No | |||
| Network/Distribution | Yes/No | |||
| Overall Score |
Dimension 4: Market Timing Analysis {#dimension-4-market-timing}
🎯 Core Question: Is Now the Right Time?
┌─────────────────────────────────────────────────────────────────┐
│ MARKET TIMING ANALYSIS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ "Timing is everything. Too early = no market. │
│ Too late = red ocean. Just right = opportunity." │
│ │
│ TIMING SPECTRUM: │
│ │
│ TOO EARLY EMERGING GROWING MATURE │
│ │ │ │ │ │
│ ────┼───────────────┼───────────────┼───────────────┼──── │
│ │ │ │ │ │
│ No awareness Early adopters Mass market Saturated │
│ No budget Building budget Active spend Switching │
│ Educate market Land grabbing Compete hard Differentiate │
│ │
│ IDEAL TIMING: Early in "Growing" phase │
│ ├── Market awareness exists │
│ ├── Budgets are being allocated │
│ ├── Not yet dominated by incumbents │
│ └── Clear growth trajectory │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Timing Indicators Assessment
Signs You're Too Early:
| Indicator | Present? | Evidence |
|---|---|---|
| Need to educate market on problem | ||
| No one searching for solutions | ||
| Buyers don't have budget allocated | ||
| Infrastructure not ready (platforms, APIs) | ||
| Regulatory environment unclear |
Signs You're Too Late:
| Indicator | Present? | Evidence |
|---|---|---|
| Multiple well-funded competitors | ||
| Market leaders have >50% share | ||
| Customers locked into contracts | ||
| Prices racing to bottom | ||
| Innovation slowing (feature parity) |
Signs Timing is Right:
| Indicator | Present? | Evidence |
|---|---|---|
| Search volume increasing year-over-year | ||
| New competitors entering (but not dominant) | ||
| VC money flowing into space | ||
| Industry analysts covering the category | ||
| Customers actively evaluating solutions | ||
| Platform/API maturity enabling new approaches |
🎯 Timing Score Framework
┌─────────────────────────────────────────────────────────────────┐
│ TIMING SCORE CALCULATION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ FACTOR SCORE (1-10) WEIGHT │
│ ───────────────────────────────────────────────────────────── │
│ Market Awareness [____] × 20% │
│ (Do people know they have problem?) │
│ │
│ Budget Allocation [____] × 20% │
│ (Are people spending on solutions?) │
│ │
│ Competitive Intensity [____] × 20% │
│ (10 = low competition, 1 = saturated) │
│ │
│ Enabling Technologies [____] × 20% │
│ (Are required platforms/APIs ready?) │
│ │
│ Regulatory Clarity [____] × 10% │
│ (Are rules clear and favorable?) │
│ │
│ Macro Trends [____] × 10% │
│ (Does timing align with bigger trends?) │
│ ───────────────────────────────────────────────────────────── │
│ WEIGHTED TOTAL: [____]/10 │
│ │
│ INTERPRETATION: │
│ ├── 8-10: Excellent timing window │
│ ├── 6-7.9: Good timing, proceed │
│ ├── 4-5.9: Questionable timing, validate carefully │
│ └── 1-3.9: Poor timing, wait or pivot │
│ │
└─────────────────────────────────────────────────────────────────┘
Related guide: Market Opportunity Analysis for deeper market timing research.
Dimension 5: Founder-Market Fit {#dimension-5-founder-market-fit}
🎯 Core Question: Are You the Right Person to Build This?
┌─────────────────────────────────────────────────────────────────┐
│ FOUNDER-MARKET FIT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ "The best founders are deeply connected to the problem they │
│ solve. They've lived it, understand it viscerally, and are │
│ uniquely positioned to solve it." │
│ │
│ FOUNDER-MARKET FIT SPECTRUM: │
│ │
│ LOW FIT HIGH FIT │
│ │ │ │
│ ───┼───────────────────────────────────────────────────┼── │
│ │ │ │
│ • Solving for others • Adjacent experience • Lived it │
│ • No domain expertise • Learned the domain • Deep expert │
│ • Opportunistic only • Some passion • Obsessed │
│ • No unfair advantage • Some advantages • Clear edge │
│ │
│ HIGH FIT INDICATORS: │
│ ├── You've personally experienced the problem │
│ ├── You understand customer language and mindset │
│ ├── You have unique insights others lack │
│ ├── You have relevant network and credibility │
│ ├── You're passionate beyond financial opportunity │
│ └── You'll persist when it gets hard │
│ │
└─────────────────────────────────────────────────────────────────┘
📋 Founder-Market Fit Assessment
Domain Expertise:
| Factor | Score (1-10) | Evidence |
|---|---|---|
| Problem Experience | Have you personally faced this problem? | |
| Industry Knowledge | Do you understand the market deeply? | |
| Customer Empathy | Can you speak customer language? | |
| Technical Domain | Do you understand the solution space? |
Unfair Advantages:
| Advantage | You Have? | Strength |
|---|---|---|
| Existing audience/following | ||
| Relevant network/connections | ||
| Proprietary data or insights | ||
| Technical expertise others lack | ||
| Distribution channel access | ||
| Personal brand/credibility | ||
| Prior startup experience |
Motivation Depth:
| Question | Answer |
|---|---|
| Why are you passionate about this problem? | |
| What happens if this takes 5+ years? | |
| Would you work on this without financial pressure? | |
| What unique perspective do you bring? | |
| Why will you succeed where others failed? |
🎯 Founder-Market Fit Score
┌─────────────────────────────────────────────────────────────────┐
│ FOUNDER-MARKET FIT SCORECARD │
├─────────────────────────────────────────────────────────────────┤
│ │
│ DIMENSION SCORE (1-10) WEIGHT │
│ ───────────────────────────────────────────────────────────── │
│ Problem Experience [____] × 25% │
│ Domain Expertise [____] × 20% │
│ Unfair Advantages [____] × 25% │
│ Passion/Persistence [____] × 15% │
│ Network/Credibility [____] × 15% │
│ ───────────────────────────────────────────────────────────── │
│ WEIGHTED TOTAL: [____]/10 │
│ │
│ INTERPRETATION: │
│ ├── 8-10: Excellent fit, strong foundation │
│ ├── 6-7.9: Good fit, can succeed with effort │
│ ├── 4-5.9: Weak fit, consider co-founder or pivot │
│ └── 1-3.9: Poor fit, high risk of founder burnout │
│ │
└─────────────────────────────────────────────────────────────────┘
💡 Improving Founder-Market Fit
If your score is low:
| Gap | Solution |
|---|---|
| Lack domain expertise | Spend 3-6 months immersed in the industry |
| No problem experience | Do concierge service to understand deeply |
| Missing technical skills | Find technical co-founder |
| No audience/network | Build in public, content marketing |
| Low passion | Honestly reassess if this is the right problem |
The Viability Scoring Matrix {#viability-scoring-matrix}
📊 Complete Viability Assessment
┌─────────────────────────────────────────────────────────────────────────────┐
│ COMPLETE VIABILITY SCORECARD │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ DIMENSION SCORE (1-10) WEIGHT WEIGHTED SCORE │
│ ───────────────────────────────────────────────────────────────────────── │
│ 1. Technical [____] × [__]% = [________] │
│ Feasibility │
│ │
│ 2. Business Model [____] × [__]% = [________] │
│ Viability │
│ │
│ 3. Resource [____] × [__]% = [________] │
│ Capacity │
│ │
│ 4. Market [____] × [__]% = [________] │
│ Timing │
│ │
│ 5. Founder-Market [____] × [__]% = [________] │
│ Fit │
│ ───────────────────────────────────────────────────────────────────────── │
│ TOTAL VIABILITY SCORE: [____]/10 │
│ │
├─────────────────────────────────────────────────────────────────────────────┤
│ VIABILITY THRESHOLDS: │
│ ├── 8.0-10: 🟢 HIGHLY VIABLE - Proceed with full commitment │
│ ├── 6.5-7.9: 🟡 VIABLE WITH RISKS - Address gaps, proceed carefully │
│ ├── 5.0-6.4: 🟠 MARGINALLY VIABLE - Major improvements needed │
│ └── 1.0-4.9: 🔴 NOT VIABLE - Do not proceed, pivot or kill │
│ │
│ ⚠️ ANY dimension < 4.0 = Proceed with extreme caution │
│ ⚠️ ANY dimension < 3.0 = DO NOT proceed until addressed │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
🎯 Dimension-Specific Thresholds
| Dimension | Minimum Score | Below Minimum Action |
|---|---|---|
| Technical Feasibility | 5.0 | Simplify scope or gain expertise |
| Business Model | 6.0 | Redesign economics or don't proceed |
| Resource Capacity | 4.0 | Raise capital or reduce scope |
| Market Timing | 5.0 | Wait or find better timing |
| Founder-Market Fit | 5.0 | Find co-founder or pick different problem |
📋 Quick Viability Decision Tree
┌─────────────────────────────────────────────────────────────────┐
│ VIABILITY DECISION TREE │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Start: Calculate overall viability score │
│ │ │
│ ▼ │
│ Is overall score ≥ 6.5? │
│ │ │
│ YES │ NO │
│ │ │ │
│ ▼ └─────────────────────────────────────┐ │
│ Are ALL dimensions ≥ 4.0? │ │
│ │ ▼ │
│ YES NO Is any dimension ≥ 7.0? │
│ │ │ │ │
│ ▼ ▼ YES │ NO │
│ 🟢 Address weak │ │ │
│ GO! dimensions ▼ ▼ │
│ before proceeding 🟠 MAYBE 🔴 NO-GO │
│ Fix issues Pivot or │
│ first kill idea │
│ │
└─────────────────────────────────────────────────────────────────┘
Risk Assessment Framework {#risk-assessment-framework}
🎯 Comprehensive Risk Analysis
┌─────────────────────────────────────────────────────────────────┐
│ RISK CATEGORIES │
├─────────────────────────────────────────────────────────────────┤
│ │
│ TECHNOLOGY RISKS MARKET RISKS │
│ ├── Development delays ├── Market doesn't materialize │
│ ├── Technical debt ├── Timing wrong │
│ ├── Platform dependency ├── Competition intensifies │
│ ├── Scalability issues ├── Customer behavior changes │
│ └── Security breaches └── Pricing pressure │
│ │
│ EXECUTION RISKS FINANCIAL RISKS │
│ ├── Team departure ├── Runway exhaustion │
│ ├── Founder burnout ├── Can't raise funding │
│ ├── Slow iteration ├── Revenue slower than expected │
│ ├── Poor prioritization ├── Costs higher than expected │
│ └── Quality issues └── Unit economics don't work │
│ │
│ EXTERNAL RISKS │
│ ├── Regulatory changes ├── Economic downturn │
│ ├── Platform policy change├── Key API/service discontinued │
│ └── Major competitor launch └── Partnership falls through │
│ │
└─────────────────────────────────────────────────────────────────┘
📊 Risk Matrix
| Risk | Likelihood (1-5) | Impact (1-5) | Risk Score | Mitigation |
|---|---|---|---|---|
| Development delays | L × I = | |||
| Key competitor launch | ||||
| Funding not available | ||||
| Technical scalability | ||||
| Team member leaves | ||||
| Platform policy change | ||||
| Unit economics fail | ||||
| Market timing off |
Risk Score Interpretation: - 15-25: 🔴 Critical - Must have mitigation plan - 10-14: 🟠 High - Monitor closely, plan mitigation - 5-9: 🟡 Medium - Aware, monitor periodically - 1-4: 🟢 Low - Accept, minimal attention needed
🛡️ Risk Mitigation Template
┌─────────────────────────────────────────────────────────────────┐
│ RISK MITIGATION PLAN │
├─────────────────────────────────────────────────────────────────┤
│ │
│ RISK: [Name] │
│ SCORE: [X]/25 ([Critical/High/Medium/Low]) │
│ │
│ DESCRIPTION: │
│ [What could happen and why] │
│ │
│ IMPACT IF OCCURS: │
│ [Specific consequences] │
│ │
│ EARLY WARNING SIGNS: │
│ ├── [Sign 1] │
│ ├── [Sign 2] │
│ └── [Sign 3] │
│ │
│ PREVENTION STRATEGY: │
│ [How to reduce likelihood] │
│ │
│ MITIGATION STRATEGY: │
│ [How to reduce impact if it occurs] │
│ │
│ CONTINGENCY PLAN: │
│ [What to do if risk materializes] │
│ │
│ OWNER: [Who is responsible] │
│ REVIEW DATE: [When to reassess] │
│ │
└─────────────────────────────────────────────────────────────────┘
Viability by Product Type {#viability-by-product-type}
🌐 SaaS Product Viability
┌─────────────────────────────────────────────────────────────────┐
│ SaaS VIABILITY CHECKLIST │
├─────────────────────────────────────────────────────────────────┤
│ │
│ MUST HAVES: │
│ ├── [ ] Recurring value justifies subscription │
│ ├── [ ] CAC payback < 12 months │
│ ├── [ ] Monthly churn < 5% │
│ ├── [ ] LTV:CAC > 3:1 │
│ └── [ ] Clear path to $1M ARR │
│ │
│ NICE TO HAVES: │
│ ├── [ ] Net revenue retention > 100% │
│ ├── [ ] Viral coefficient > 0.5 │
│ └── [ ] Multiple monetization levers │
│ │
│ KEY RISKS: │
│ ├── High churn (problem not ongoing) │
│ ├── Long sales cycles (high CAC) │
│ ├── Platform dependency (API changes) │
│ └── Feature creep (support burden) │
│ │
└─────────────────────────────────────────────────────────────────┘
🧩 Browser Extension Viability
┌─────────────────────────────────────────────────────────────────┐
│ BROWSER EXTENSION VIABILITY CHECKLIST │
├─────────────────────────────────────────────────────────────────┤
│ │
│ MUST HAVES: │
│ ├── [ ] Solves problem people have while browsing │
│ ├── [ ] Chrome Web Store approval path clear │
│ ├── [ ] Monetization model works (ads, premium, etc.) │
│ ├── [ ] Development cost < $5-10K │
│ └── [ ] Clear differentiation from existing extensions │
│ │
│ NICE TO HAVES: │
│ ├── [ ] Cross-browser potential (Firefox, Edge) │
│ ├── [ ] Mobile companion potential │
│ └── [ ] B2B/enterprise angle │
│ │
│ KEY RISKS: │
│ ├── Chrome policy changes │
│ ├── Low willingness to pay for extensions │
│ ├── Competition from browser built-in features │
│ └── Manifest V3 migration requirements │
│ │
│ REVENUE POTENTIAL RANGES: │
│ ├── Ad-supported: $0.01-0.10 per DAU/month │
│ ├── Freemium: 1-5% convert × $2-10/mo │
│ └── One-time: $3-30 depending on value │
│ │
└─────────────────────────────────────────────────────────────────┘
Related guide: Profitable Browser Extensions for extension-specific strategies.
📱 Mobile App Viability
┌─────────────────────────────────────────────────────────────────┐
│ MOBILE APP VIABILITY CHECKLIST │
├─────────────────────────────────────────────────────────────────┤
│ │
│ MUST HAVES: │
│ ├── [ ] Clear App Store/Play Store positioning │
│ ├── [ ] Development budget $20K-100K+ realistic │
│ ├── [ ] Ongoing maintenance budget 15-20%/year │
│ ├── [ ] Acquisition strategy beyond app store │
│ └── [ ] Retention/engagement hooks clear │
│ │
│ KEY VIABILITY METRICS: │
│ ├── Day 1 retention > 40% │
│ ├── Day 30 retention > 10% │
│ ├── Install-to-paid conversion > 2% │
│ └── Avg session > 3 minutes │
│ │
│ KEY RISKS: │
│ ├── 30% App Store commission (affects unit economics) │
│ ├── Constant updates required (OS changes) │
│ ├── High user acquisition costs ($1-5+ per install) │
│ └── App store ranking volatility │
│ │
└─────────────────────────────────────────────────────────────────┘
🏪 Marketplace Viability
┌─────────────────────────────────────────────────────────────────┐
│ MARKETPLACE VIABILITY CHECKLIST │
├─────────────────────────────────────────────────────────────────┤
│ │
│ MUST HAVES: │
│ ├── [ ] Clear chicken-and-egg strategy │
│ ├── [ ] Transaction frequency high enough │
│ ├── [ ] Take rate sustainable (5-20%) │
│ ├── [ ] Leakage prevention strategy │
│ └── [ ] Path to liquidity both sides │
│ │
│ VIABILITY REQUIREMENTS: │
│ ├── Supply side: Can you aggregate supply first? │
│ ├── Demand side: Clear user acquisition strategy │
│ ├── Transaction value: High enough to justify take rate │
│ └── Repeat usage: Ongoing need, not one-time │
│ │
│ KEY RISKS: │
│ ├── Disintermediation (users go direct) │
│ ├── Supply/demand imbalance │
│ ├── Long time to liquidity │
│ └── Winner-take-all dynamics (network effects) │
│ │
│ ⚠️ Marketplaces typically need $1M+ to reach liquidity │
│ │
└─────────────────────────────────────────────────────────────────┘
Case Studies: Viability in Practice {#case-studies}
📖 Case Study 1: Tab Manager Extension (VIABLE)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: TAB MANAGER CHROME EXTENSION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INITIAL ASSESSMENT: │
│ Hypothesis: Power users need better tab organization │
│ Validation: Strong (80% of users confirmed problem) │
│ │
│ VIABILITY SCORES: │
│ ├── Technical Feasibility: 9/10 │
│ │ └── Standard Chrome APIs, solo dev can build │
│ ├── Business Model: 7/10 │
│ │ └── Freemium model, $5/mo Pro, good conversion │
│ ├── Resource Capacity: 8/10 │
│ │ └── Solo founder, $5K budget, part-time OK │
│ ├── Market Timing: 8/10 │
│ │ └── Remote work trend = more tabs = more need │
│ └── Founder-Market Fit: 9/10 │
│ └── Developer who personally had 100+ tabs open │
│ │
│ OVERALL VIABILITY: 8.2/10 🟢 │
│ │
│ RISKS IDENTIFIED: │
│ ├── Chrome could build tab features (Medium) │
│ ├── Low willingness to pay for free alternatives (High) │
│ └── Manifest V3 migration needed (Medium) │
│ │
│ DECISION: Proceed │
│ OUTCOME: $8K MRR in 12 months, 50K users │
│ │
└─────────────────────────────────────────────────────────────────┘
📖 Case Study 2: Enterprise Analytics SaaS (NOT VIABLE for founder)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: ENTERPRISE ANALYTICS PLATFORM │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INITIAL ASSESSMENT: │
│ Hypothesis: Enterprises need better BI dashboards │
│ Validation: Strong (enterprises spending $100K+/year) │
│ │
│ VIABILITY SCORES: │
│ ├── Technical Feasibility: 5/10 │
│ │ └── Complex, needs team of 3-5 engineers │
│ ├── Business Model: 8/10 │
│ │ └── $10K-50K ACV, long sales cycles but high LTV │
│ ├── Resource Capacity: 2/10 🔴 │
│ │ └── Solo founder, $20K savings, no enterprise network │
│ ├── Market Timing: 6/10 │
│ │ └── Competitive (Looker, Tableau, etc.) │
│ └── Founder-Market Fit: 3/10 🔴 │
│ └── No enterprise sales experience, not from industry │
│ │
│ OVERALL VIABILITY: 4.8/10 🔴 │
│ │
│ VIABILITY KILLERS: │
│ ├── Insufficient capital ($500K+ needed minimum) │
│ ├── No enterprise sales skills or network │
│ ├── Competitive landscape requires differentiation │
│ └── 12-18 month sales cycles vs 6-month runway │
│ │
│ DECISION: Do not proceed │
│ ALTERNATIVE: Pivoted to SMB version with simpler sale │
│ │
└─────────────────────────────────────────────────────────────────┘
📖 Case Study 3: AI Writing Tool (PIVOT to viable)
┌─────────────────────────────────────────────────────────────────┐
│ CASE STUDY: AI WRITING ASSISTANT │
├─────────────────────────────────────────────────────────────────┤
│ │
│ INITIAL VIABILITY ASSESSMENT (General AI Writing): │
│ ├── Technical Feasibility: 7/10 │
│ ├── Business Model: 4/10 🔴 │
│ │ └── Commoditized market, low differentiation │
│ ├── Resource Capacity: 7/10 │
│ ├── Market Timing: 4/10 🔴 │
│ │ └── Too late: ChatGPT, Jasper, Copy.ai dominant │
│ └── Founder-Market Fit: 6/10 │
│ │
│ OVERALL VIABILITY: 5.6/10 🟠 - Not viable as positioned │
│ │
│ PIVOT: Narrow to legal document drafting │
│ │
│ NEW VIABILITY ASSESSMENT: │
│ ├── Technical Feasibility: 7/10 │
│ ├── Business Model: 8/10 │
│ │ └── Legal willing to pay $99-299/mo, high LTV │
│ ├── Resource Capacity: 6/10 │
│ ├── Market Timing: 7/10 │
│ │ └── Legal AI still emerging, less competition │
│ └── Founder-Market Fit: 7/10 │
│ └── Founder had legal background │
│ │
│ NEW OVERALL VIABILITY: 7.0/10 🟡 │
│ │
│ DECISION: Proceed with niche positioning │
│ OUTCOME: $15K MRR in 18 months │
│ │
└─────────────────────────────────────────────────────────────────┘
Common Viability Killers {#common-viability-killers}
❌ Top 12 Viability Killers
| # | Killer | Why It's Fatal | Detection |
|---|---|---|---|
| 1 | Insufficient capital | Can't reach milestones before money runs out | Calculate runway vs milestone timeline |
| 2 | Technical overreach | Building something team can't deliver | Honest skills assessment + spike tests |
| 3 | Wrong founder-market fit | No unfair advantage, will lose to better-fit founders | FMF score < 5 |
| 4 | Bad unit economics | Every customer loses money | LTV:CAC < 2:1 |
| 5 | Too-late timing | Market already won | 3+ dominant incumbents with >50% share |
| 6 | Too-early timing | Market doesn't exist yet | <1000 monthly searches, no budget allocated |
| 7 | Platform dependency | Success relies on platform that can change | Single API/platform critical path |
| 8 | Regulatory uncertainty | Can be killed by rule change | Unclear legal status |
| 9 | Too small market | Can't build sustainable business | TAM < $10M |
| 10 | Competitive moat impossible | Easy to copy, can't defend | No network effects, IP, or switching costs |
| 11 | Customer concentration | Depends on few large customers | Top 3 customers > 50% of revenue |
| 12 | Solo founder burnout | Too much for one person | Scope requires team, no co-founder |
🔍 Viability Killer Detection Checklist
- [ ] Runway covers 2x estimated time to revenue?
- [ ] Technical scope matches team capability?
- [ ] Founder-market fit score > 5.0?
- [ ] LTV:CAC projection > 3:1?
- [ ] Market not dominated (no single player >50%)?
- [ ] Market mature enough (real budget being spent)?
- [ ] Platform dependency mitigated?
- [ ] Regulatory path clear?
- [ ] TAM > $50M?
- [ ] Defensibility strategy clear?
- [ ] Customer diversification possible?
- [ ] Team capacity matches scope?
If ANY answer is NO, you have a potential viability killer to address.
Templates and Tools {#templates-and-tools}
📋 Complete Viability Assessment Template
# Product Viability Assessment
**Product Name:** _______________
**Date:** _______________
**Assessor:** _______________
## Executive Summary
- Overall Viability Score: ___/10
- Recommendation: [GO / CONDITIONAL GO / NO-GO]
- Key Strengths:
- Key Risks:
- Critical Actions Required:
## Dimension Scores
| Dimension | Score | Key Findings |
|-----------|-------|--------------|
| Technical Feasibility | /10 | |
| Business Model | /10 | |
| Resource Capacity | /10 | |
| Market Timing | /10 | |
| Founder-Market Fit | /10 | |
| **WEIGHTED TOTAL** | /10 | |
## Detailed Analysis
### 1. Technical Feasibility (Score: ___)
- Core technology assessment:
- Team capability gaps:
- Key dependencies:
- Development timeline estimate:
- Technical risks:
### 2. Business Model (Score: ___)
- Revenue model:
- Unit economics (LTV/CAC):
- Pricing strategy:
- Path to profitability:
- Model risks:
### 3. Resource Capacity (Score: ___)
- Capital available:
- Time commitment:
- Team composition:
- Resource gaps:
- Mitigation plans:
### 4. Market Timing (Score: ___)
- Market maturity stage:
- Competitive intensity:
- Enabling trends:
- Timing risks:
### 5. Founder-Market Fit (Score: ___)
- Problem experience:
- Domain expertise:
- Unfair advantages:
- Network/credibility:
## Risk Register
| Risk | Likelihood | Impact | Score | Mitigation |
|------|------------|--------|-------|------------|
| | | | | |
| | | | | |
| | | | | |
## Decision
**Recommendation:** [GO / CONDITIONAL GO / NO-GO]
**Conditions (if applicable):**
1.
2.
3.
**Next Steps:**
1.
2.
3.
**Review Date:** _______________
🛠️ Recommended Assessment Tools
| Tool | Purpose | Best For | Cost |
|---|---|---|---|
| Google Sheets | Custom viability calculations | All assessment types | Free |
| Notion | Documentation and tracking | Collaborative assessment | Free-$8/mo |
| NicheCheck | Automated market/competition analysis | Quick validation | Free-$29/mo |
| Miro | Visual assessment mapping | Team brainstorming | Free-$10/mo |
| Loom | Recording assessment walkthrough | Stakeholder communication | Free-$15/mo |
⏱️ Viability Assessment Timeline
| Assessment Type | Duration | When to Use |
|---|---|---|
| Quick Check | 30 min | Initial idea screening |
| Standard Assessment | 2-4 hours | Post-validation, pre-commitment |
| Deep Dive | 1-2 days | Major investment decisions |
| Team Assessment | 1 week | Funded startup pivot decisions |
FAQ {#faq}
❓ How is viability different from validation?
Validation: Confirms customers want what you're building Viability: Confirms YOU can successfully build and deliver it
An idea can be validated (customers want it) but not viable (you can't deliver it profitably). Both are required for success.
❓ What's the minimum viable score to proceed?
For bootstrapped products: 6.0+ overall, with no dimension below 4.0 For funded startups: 7.0+ overall, with no dimension below 5.0
These thresholds increase with the investment required.
❓ How often should I reassess viability?
- Monthly during early development
- Quarterly once launched
- Immediately after major market changes (competitor launch, platform changes, etc.)
Viability is not static—it changes as you learn and as markets evolve.
❓ Can a low viability score be improved?
Yes, through: - Scope reduction (simpler = more feasible) - Co-founder addition (fills capability gaps) - Raising capital (extends runway) - Pivoting (finding better-fit position) - Waiting (better timing later)
But be honest: sometimes the answer is to pick a different problem.
❓ What if I score high on validation but low on viability?
Options: 1. License the idea to someone with better fit 2. Find a co-founder who complements your gaps 3. Wait and build resources before attempting 4. Pivot the approach to something more viable for you 5. Accept the risk if you're willing to learn/fail
The worst choice: proceeding while ignoring viability gaps.
❓ How do I assess viability for something truly novel?
For innovative products: - Lean heavier on technical spikes to validate feasibility - Accept higher uncertainty in timing and market dimensions - Use analogous markets for business model estimation - Plan for longer runways (18-36 months minimum) - Weight founder-market fit higher (conviction matters more)
Novel ideas need stronger founder conviction to offset higher uncertainty.
Summary and Next Steps {#summary-and-next-steps}
📋 Key Takeaways
┌─────────────────────────────────────────────────────────────────┐
│ VIABILITY SUMMARY │
├─────────────────────────────────────────────────────────────────┤
│ │
│ THE 5 DIMENSIONS: │
│ 1. Technical Feasibility → Can we build it? │
│ 2. Business Model → Will the economics work? │
│ 3. Resource Capacity → Do we have what we need? │
│ 4. Market Timing → Is now the right time? │
│ 5. Founder-Market Fit → Are we the right team? │
│ │
│ VIABILITY THRESHOLDS: │
│ ├── 8.0+ overall: Strong go │
│ ├── 6.5-7.9: Proceed with caution │
│ ├── 5.0-6.4: Address gaps first │
│ └── <5.0: Don't proceed │
│ │
│ CRITICAL RULES: │
│ ├── Any dimension <4.0 = high risk │
│ ├── Any dimension <3.0 = don't proceed │
│ ├── Viability ≠ Validation (need both) │
│ └── Reassess regularly as conditions change │
│ │
│ WHEN VIABILITY IS LOW: │
│ ├── Reduce scope │
│ ├── Add resources (co-founder, capital) │
│ ├── Pivot positioning │
│ └── Pick a different problem │
│ │
└─────────────────────────────────────────────────────────────────┘
✅ Your Next Steps
This Week: 1. [ ] Complete the quick viability check (30 min) 2. [ ] Identify your weakest dimension 3. [ ] List 3 actions to improve that dimension 4. [ ] Assess your top 3 risks
This Month: 1. [ ] Complete full viability assessment 2. [ ] Run technical spike to validate feasibility 3. [ ] Model unit economics with real assumptions 4. [ ] Document risk mitigation strategies
Before Major Commitment: 1. [ ] All dimensions score > 5.0 2. [ ] Overall viability > 6.5 3. [ ] Risk mitigation plans documented 4. [ ] Resource gaps have clear solutions
🔗 Related Resources
- Product Validation Framework - Complement viability with validation
- Niche Profitability Analysis - Deep-dive on unit economics
- Competitive Landscape Analysis - Market timing research
- Startup Idea Checklist - Complete idea evaluation
Free tool: Quickly check if your niche is already taken with our free niche checker -- no signup required.
🚀 Ready to Assess Your Idea's Viability?
Don't waste months on something that was never going to work.
Try NicheCheck Free → and get instant viability signals: - ✅ Competition intensity analysis - ✅ Market size estimation - ✅ Revenue potential scoring - ✅ Technical feasibility indicators - ✅ GO/MAYBE/NO-GO recommendation
Make confident build decisions with data, not hope.
Ready to Validate Your Idea?
Get instant insights on market demand, competition, and revenue potential.
Try NicheCheck Free