---
# === IDENTITY ===
id: business/startup-planning/idea-classification-framework/2026
canonical_question: "How do I classify a startup idea by type (SaaS, marketplace, hardware, services) to determine applicable playbooks?"
aliases:
  - "What type of startup am I building?"
  - "Startup business model classification taxonomy"
  - "How to categorize my startup idea by business model"
entity_type: execution_recipe
domain: business > startup-planning > idea classification framework
region: global
jurisdiction: global
temporal_scope: 2024-2026

# === VERIFICATION ===
last_verified: 2026-03-11
confidence: 0.88
version: 1.0
first_published: 2026-03-11

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: null
  next_review: 2026-09-07
  change_sensitivity: medium

# === CONSTRAINTS ===
constraints:
  - "Most startups blend models (e.g., SaaS + marketplace). Classify by primary revenue driver, not feature set."
  - "Hardware startups require 3-10x more capital than software — classification directly affects fundraising strategy."
  - "AI-native startups may not fit traditional categories — classify by delivery model (API, platform, embedded) not technology."

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "Already know business model type, need execution steps"
    use_instead: "business/startup-planning/initial-feasibility-quick-check/2026"
  - condition: "Need to evaluate idea viability, not classify it"
    use_instead: "business/startup-planning/initial-feasibility-quick-check/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: idea_description
    question: "Describe the startup idea in 2-3 sentences"
    type: text
  - key: revenue_model
    question: "How will this make money?"
    type: choice
    options: ["Subscription/recurring", "Transaction fee/commission", "One-time purchase", "Usage-based", "Advertising", "Not sure yet"]
  - key: delivery_method
    question: "How is the product delivered to customers?"
    type: choice
    options: ["Software (cloud/web/mobile)", "Physical product", "In-person service", "Digital content", "API/platform", "Hybrid"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Startup idea description"
      source: "founder"
      format: "text (2-3 sentences minimum)"
    - name: "Revenue model hypothesis"
      source: "founder"
      format: "text or selection from common models"
  outputs:
    - name: "Idea Classification Report"
      format: "JSON"
      description: "Primary type, secondary type, applicable playbooks, key metrics to track, capital requirements range"
    - name: "Playbook Routing Map"
      format: "structured list"
      description: "Ordered list of next-step knowledge cards based on classification"
  tools_required:
    - name: "Spreadsheet or text editor"
      purpose: "Document classification decision and rationale"
      tier: free
      cost: "$0"
      alternatives: ["Google Sheets", "Notion", "plain text"]
  credentials_needed: []
  estimated_duration: "30-60 minutes"
  estimated_cost: "$0"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/startup-planning/idea-classification-framework/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)"

# === RELATED UNITS ===
related_kos:
  depends_on: []
  feeds_into:
    - id: "business/startup-planning/initial-feasibility-quick-check/2026"
      label: "Feasibility check using classification-specific criteria"
    - id: "business/market-research/market-sizing-methodology/2026"
      label: "Market sizing with model-appropriate methodology"
  related_to:
    - id: "business/market-research/competitive-landscape-mapping/2026"
      label: "Competitive analysis shaped by business model type"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "YC Guide to Business Models"
    author: Y Combinator
    url: https://www.ycombinator.com/library/Gh-yc-guide-to-business-models
    type: community_resource
    published: 2024-01-15
    reliability: authoritative
  - id: src2
    title: "Conducting a Feasibility Analysis"
    author: OpenStax
    url: https://openstax.org/books/entrepreneurship/pages/11-3-conducting-a-feasibility-analysis
    type: technical_blog
    published: 2023-06-01
    reliability: authoritative
  - id: src3
    title: "10 Business Models SaaS: Top Trends for 2025"
    author: Acquire.com
    url: https://blog.acquire.com/business-models-saas/
    type: industry_report
    published: 2025-01-10
    reliability: high
  - id: src4
    title: "Startup School - The Best Online Resource for Founders"
    author: Y Combinator
    url: https://www.startupschool.org/
    type: community_resource
    published: 2024-07-01
    reliability: authoritative
  - id: src5
    title: "How to Conduct Competitor Analysis: A Strategic Framework for Startups"
    author: StartHawk
    url: https://www.starthawk.io/blog/post/how-to-conduct-competitor-analysis-a-strategic-framework-for-startups
    type: technical_blog
    published: 2025-03-15
    reliability: high
  - id: src6
    title: "Beating the odds in market entry"
    author: McKinsey & Company
    url: https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/beating-the-odds-in-market-entry
    type: industry_report
    published: 2024-05-01
    reliability: authoritative
---

# Startup Idea Classification Framework

## Purpose

This recipe produces a formal classification of a startup idea into one of 12 primary business model types, with secondary type identification for hybrid models. The output determines which downstream playbooks, metrics, capital requirements, and go-to-market strategies apply. Misclassification wastes months pursuing wrong benchmarks and investor expectations.

## Prerequisites

- [ ] **Startup idea description** (minimum 2-3 sentences describing what the product does and for whom)
- [ ] **Revenue hypothesis** (even rough — "we'd charge monthly" or "we'd take a cut of transactions")
- [ ] **Target customer segment** (B2B, B2C, B2B2C, or B2G)

## Constraints

- Most startups blend 2-3 models. Classify by primary revenue driver, not feature list. A SaaS tool with a marketplace feature is still SaaS if subscriptions drive >60% of revenue. [src1]
- Hardware startups require 3-10x more capital than pure software. This classification directly affects fundraising strategy and investor targeting. [src6]
- AI-native startups should be classified by delivery model (API service, embedded AI, platform), not by the technology itself. "AI startup" is not a business model. [src3]
- Classification is not permanent. Many startups pivot model types (e.g., Slack started as a gaming company). Revisit classification after each major pivot. [src4]
- Do not conflate pricing model (subscription, usage-based, freemium) with business model type. Pricing is a subset of the model, not the model itself. [src1]

## Tool Selection Decision

```
Which path?
├── Founder has clear idea description + revenue model
│   └── PATH A: Direct Classification — decision tree + scoring
├── Founder has idea but unclear revenue model
│   └── PATH B: Revenue Model Discovery — guided questionnaire first
├── Founder has multiple ideas to compare
│   └── PATH C: Batch Classification — score all, rank by fit
└── Agent is auto-classifying from a pitch deck or description
    └── PATH D: Automated Extraction — parse text, extract signals
```

| Path | Tools | Cost | Speed | Output Quality |
|------|-------|------|-------|---------------|
| A: Direct Classification | Text editor | $0 | 15 min | High (founder input is clear) |
| B: Revenue Discovery | Questionnaire + text editor | $0 | 30 min | Medium-high (discovery adds clarity) |
| C: Batch Classification | Spreadsheet | $0 | 45 min | High (comparative scoring) |
| D: Automated Extraction | LLM + structured output | $0.01-0.05 | 5 min | Medium (depends on input quality) |

## Execution Flow

### Step 1: Gather Idea Signals

**Duration**: 10 minutes
**Tool**: Text editor or form

Collect these 8 signals from the founder or idea description:

```
1. DELIVERY: How does the customer use the product?
   [ ] Cloud software (browser/app)  [ ] Downloaded software
   [ ] Physical product               [ ] In-person service
   [ ] API/developer tool             [ ] Content/media
   [ ] Platform connecting two sides   [ ] Hardware + software

2. REVENUE: How does money flow?
   [ ] Monthly/annual subscription    [ ] Per-transaction fee/commission
   [ ] One-time purchase              [ ] Usage-based (per API call, per GB)
   [ ] Advertising                    [ ] Licensing/royalties
   [ ] Professional services          [ ] Freemium + premium tier

3. CUSTOMER: Who pays?
   [ ] Businesses (B2B)    [ ] Consumers (B2C)
   [ ] Both sides (B2B2C)  [ ] Government (B2G)

4. SUPPLY: What creates the product?
   [ ] Software only (team builds and maintains)
   [ ] Third-party suppliers/creators (marketplace)
   [ ] Physical manufacturing required
   [ ] Human labor per engagement (services)

5. NETWORK EFFECTS: Does the product get better with more users?
   [ ] Yes, directly (each user adds value)
   [ ] Yes, indirectly (more supply attracts demand)
   [ ] No (value is independent of user count)

6. MARGINAL COST: What does it cost to serve one more customer?
   [ ] Near zero (software, digital)
   [ ] Low ($1-50 per customer)
   [ ] Medium ($50-500 per customer)
   [ ] High ($500+ per customer, or custom work required)

7. SWITCHING COST: How hard is it for customers to leave?
   [ ] Very easy (cancel anytime, data portable)
   [ ] Moderate (some data lock-in, learning curve)
   [ ] High (deep integration, workflow dependency)

8. MOAT TYPE: What makes this defensible?
   [ ] Technology/IP          [ ] Network effects
   [ ] Data accumulation      [ ] Brand/trust
   [ ] Regulatory barriers    [ ] Economies of scale
```

**Verify**: All 8 signals have at least one selection
**If failed**: If founder cannot answer, mark as "unknown" and use Path B for revenue model discovery

### Step 2: Apply Classification Decision Tree

**Duration**: 10 minutes
**Tool**: Decision tree below

Apply this classification tree using the signals collected:

```
START: What is the primary delivery method?
│
├── Cloud software / downloaded software
│   ├── Revenue = subscription/usage-based → SaaS
│   ├── Revenue = per-transaction + two-sided → TRANSACTIONAL MARKETPLACE
│   ├── Revenue = advertising + content → MEDIA/CONTENT PLATFORM
│   └── Revenue = licensing/API → DEVELOPER TOOLS / API BUSINESS
│
├── Physical product
│   ├── Supply = own manufacturing → HARDWARE / D2C
│   ├── Supply = third-party + curation → E-COMMERCE / RETAIL
│   └── Supply = third-party + logistics → LOGISTICS / SUPPLY CHAIN
│
├── Platform connecting two sides
│   ├── Revenue = commission on transactions → MARKETPLACE
│   ├── Revenue = subscription from one/both sides → PLATFORM-AS-SERVICE
│   └── Network effects = strong → NETWORK/SOCIAL PLATFORM
│
├── In-person or human-delivered service
│   ├── Marginal cost = high + custom work → PROFESSIONAL SERVICES / AGENCY
│   ├── Marginal cost = medium + standardized → PRODUCTIZED SERVICE
│   └── Scaling via technology → TECH-ENABLED SERVICES
│
├── API / developer tool
│   ├── Revenue = usage-based → API-FIRST / INFRASTRUCTURE
│   └── Revenue = subscription → DEVELOPER SaaS
│
└── Content / media
    ├── Revenue = advertising → AD-SUPPORTED MEDIA
    ├── Revenue = subscription → SUBSCRIPTION MEDIA
    └── Revenue = transactions → DIGITAL COMMERCE
```

**Verify**: Classification maps to exactly one primary type
**If failed**: If idea maps to 2+ types equally, proceed to Step 3 for hybrid scoring

### Step 3: Score Hybrid Model Fit

**Duration**: 10 minutes
**Tool**: Scoring matrix

For ideas that span multiple types, score each candidate type 1-5 on these dimensions:

```json
{
  "scoring_dimensions": [
    {"dimension": "revenue_alignment", "weight": 0.30, "question": "How much of revenue comes from this model type?"},
    {"dimension": "operational_alignment", "weight": 0.25, "question": "How much of daily operations match this model?"},
    {"dimension": "investor_expectation", "weight": 0.20, "question": "Which model type do target investors expect?"},
    {"dimension": "scaling_path", "weight": 0.15, "question": "Which model defines the scaling strategy?"},
    {"dimension": "competitive_positioning", "weight": 0.10, "question": "Which model defines competitive dynamics?"}
  ]
}
```

| Dimension | Weight | Type A Score | Type B Score |
|-----------|--------|-------------|-------------|
| Revenue alignment | 0.30 | _/5 | _/5 |
| Operational alignment | 0.25 | _/5 | _/5 |
| Investor expectation | 0.20 | _/5 | _/5 |
| Scaling path | 0.15 | _/5 | _/5 |
| Competitive positioning | 0.10 | _/5 | _/5 |
| **Weighted Total** | | **_/5.00** | **_/5.00** |

Highest score = primary type. Second highest = secondary type.

**Verify**: Primary type scores at least 1.0 higher than secondary type for clean classification. If gap < 1.0, flag as "true hybrid" requiring dual-playbook execution.
**If failed**: If all scores are within 0.5, the idea may be too unfocused. Recommend the founder narrow the initial wedge.

### Step 4: Map to Applicable Playbooks and Metrics

**Duration**: 10 minutes
**Tool**: Reference table below

Based on classification, assign the correct downstream playbooks and KPIs:

| Business Model Type | Primary Metric | Key Playbooks | Capital Requirement | Typical Timeline to Revenue |
|---------------------|---------------|---------------|--------------------|-----------------------------|
| SaaS | MRR / ARR | Pricing, PLG or sales-led GTM | $50K-$500K | 3-12 months |
| Marketplace | GMV, take rate | Supply acquisition, trust/safety | $100K-$2M | 6-18 months |
| Hardware / D2C | Units shipped, COGS | Manufacturing, supply chain | $500K-$5M | 12-24 months |
| Professional Services | Revenue per consultant, utilization | Hiring, delivery process | $10K-$100K | 1-3 months |
| Productized Service | MRR, delivery cost per unit | Standardization, automation | $25K-$250K | 2-6 months |
| Tech-Enabled Services | Revenue, automation rate | Technology + ops balance | $100K-$1M | 3-12 months |
| API / Infrastructure | API calls, revenue per call | Developer experience, docs | $200K-$2M | 6-18 months |
| E-Commerce / Retail | AOV, CAC, LTV | Inventory, logistics, brand | $50K-$500K | 2-6 months |
| Media / Content | MAU, engagement, ARPU | Content creation, distribution | $50K-$500K | 6-24 months |
| Network / Social | DAU/MAU ratio, virality | Growth loops, retention | $500K-$5M | 12-36 months |
| Subscription Media | Subscribers, churn | Content quality, retention | $100K-$1M | 6-18 months |
| Developer SaaS | Developers using, expansion rev | Developer community, docs | $100K-$1M | 6-18 months |

**Verify**: At least 3 applicable playbook references identified for the primary type
**If failed**: If type is novel or doesn't map well, create a custom playbook list combining elements from the two closest types

### Step 5: Generate Classification Report

**Duration**: 5 minutes

Compile the final classification output:

```json
{
  "classification_report": {
    "idea_summary": "{2-3 sentence description}",
    "primary_type": "{type}",
    "primary_type_confidence": 0.85,
    "secondary_type": "{type or null}",
    "hybrid_flag": false,
    "customer_segment": "{B2B|B2C|B2B2C|B2G}",
    "revenue_model": "{subscription|transaction|usage|advertising|one-time}",
    "key_metrics": ["{metric1}", "{metric2}", "{metric3}"],
    "capital_requirement_range": "{$XK-$YK}",
    "timeline_to_revenue": "{N-M months}",
    "applicable_playbooks": [
      "{playbook1 card path}",
      "{playbook2 card path}",
      "{playbook3 card path}"
    ],
    "classification_rationale": "{Why this type — 2-3 sentences}",
    "risks_from_misclassification": "{What goes wrong if classified differently}"
  }
}
```

**Output files**:
- `idea_classification_report.json` — Complete classification with playbook routing
- `classification_rationale.md` — Human-readable summary for founder review

## Output Schema

```json
{
  "output_type": "idea_classification_report",
  "format": "JSON",
  "columns": [
    {"name": "idea_summary", "type": "string", "description": "2-3 sentence idea description", "required": true},
    {"name": "primary_type", "type": "string", "description": "Primary business model classification", "required": true},
    {"name": "primary_type_confidence", "type": "number", "description": "Confidence score 0-1 for primary classification", "required": true},
    {"name": "secondary_type", "type": "string", "description": "Secondary model type for hybrid ideas", "required": false},
    {"name": "hybrid_flag", "type": "boolean", "description": "True if idea is a true hybrid requiring dual playbooks", "required": true},
    {"name": "customer_segment", "type": "string", "description": "B2B, B2C, B2B2C, or B2G", "required": true},
    {"name": "applicable_playbooks", "type": "array", "description": "Ordered list of relevant playbook card paths", "required": true},
    {"name": "capital_requirement_range", "type": "string", "description": "Estimated capital needed for this model type", "required": true}
  ],
  "expected_row_count": "1",
  "sort_order": "N/A (single document)",
  "deduplication_key": "idea_summary"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Signal completeness (8 questions answered) | > 6/8 | 8/8 | 8/8 with detailed notes |
| Classification confidence gap (primary vs secondary) | > 0.5 | > 1.0 | > 2.0 |
| Playbook mapping completeness | >= 3 playbooks | >= 5 playbooks | >= 7 playbooks with sequencing |
| Founder agreement with classification | Acknowledged | Agreed | Enthusiastically validated |

**If below minimum**: Re-gather signals from founder with more specific questions. Classification with <6 signals answered produces unreliable results.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Idea maps to 3+ types equally | Idea is too broad or unfocused | Ask founder to define the initial wedge product, classify that |
| No matching type in decision tree | Novel business model or unusual combination | Classify by closest analog, document deviations |
| Founder disagrees with classification | Founder has different mental model of their business | Review signals together, re-score with founder's weighting |
| Classification changes after pivot | Normal startup evolution | Re-run classification, update playbook routing |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| Classification framework | $0 (this card) | $0 | $0 |
| Research validation (optional) | $0 (web search) | $50-100 (industry report) | $500+ (custom research) |
| Founder workshop facilitation | $0 (self-serve) | $200-500 (consultant) | $2,000+ (strategy firm) |
| **Total** | **$0** | **$50-500** | **$500-2,500** |

## Anti-Patterns

### Wrong: Classifying by technology instead of business model
Calling it an "AI startup" or "blockchain startup" tells you nothing about go-to-market, metrics, or capital needs. OpenAI is an API business. A chatbot SaaS using GPT is a SaaS business. The technology is an implementation detail. [src1]

### Correct: Classify by delivery and revenue model
Use the 8-signal framework to determine how value is delivered and how money flows. Technology choices follow from the business model, not the other way around.

### Wrong: Forcing a single classification on a true hybrid
Classifying Airbnb as "just a marketplace" ignores the trust/safety, payments, and content platform elements that require different operational playbooks. [src6]

### Correct: Identify primary and secondary types
Score both types, flag as hybrid if the gap is <1.0, and pull playbooks from both model types. Assign primary for investor communication and metrics tracking.

## When This Matters

Use this recipe as the first step in any startup planning pipeline. Every downstream decision — market sizing methodology, competitive analysis framework, financial model structure, and fundraising strategy — depends on correct business model classification. Skipping this step or getting it wrong cascades errors through the entire planning process.

## Related Units

- [Initial Feasibility Quick Check](/business/startup-planning/initial-feasibility-quick-check/2026) — Next step: validate the classified idea's viability
- [Market Sizing Methodology](/business/market-research/market-sizing-methodology/2026) — Size the market using model-appropriate methods
- [Competitive Landscape Mapping](/business/market-research/competitive-landscape-mapping/2026) — Map competitors within the classified model type