/product-analysis

Competitive Niche Boundary Framework

The Problem

Competitive analysis fails at its foundation when we misidentify who we're competing with.

The Category Tax Error: Assuming products in the same analyst category (e.g., "project management," "note-taking," "CRM") are competitors. Categories are labels, not markets. Customers don't say "I need a project management tool"—they have a job to do and evaluate options that might do it.

The Feature Similarity Error: Assuming products with similar features compete. Notion and Excel both have tables, but they rarely compete for the same customer in the same moment. Same features ≠ same competition.

The consequences of boundary errors:

1. False Competition: Treating surface-similar products as competitors when they serve different markets → wasted analysis effort, wrong positioning
2. Missed Substitutes: Ignoring indirect competitors that customers actually switch to → blindsided by real competition
3. Platform Confusion: Treating sprawling platforms as single competitors → paralysis or irrelevant comparisons
4. Feature Mimicry: Copying features from "competitors" who aren't actually competing for your customers → building the wrong things

The only valid definition of competition: Products are competitors if customers actually substitute between them for the same job.

Core Principles

1. Jobs-to-be-Done Primacy

Competition is defined by what job the customer hires the product to do, not by product category labels or feature sets.

Two products with identical features can serve completely different jobs. Two products with no feature overlap can compete intensely for the same job.

Example: A whiteboard (physical), Miro (digital), and a spreadsheet may all compete for the job "help my team think through a problem visually"—despite having almost no feature overlap.

2. Substitution Reality Test

Products are in the same competitive space if and only if customers actually substitute between them.

• "Would they?" is theoretical
• "Do they?" is competitive reality

Evidence of switching behavior trumps category logic. If you can't find evidence of customers switching between two products, they probably aren't competitors—regardless of how similar they look.

3. Context Collapse

The same product exists in different competitive contexts for different customer segments.

A product isn't "in a niche" universally—it occupies different niches for different customers. Competitive analysis must be segment-specific.

Example: Slack competes with Microsoft Teams for enterprise IT decisions, but competes with Discord for gaming community coordination. Same product, completely different competitive sets.

4. Adjacent Possibility

Competition includes not just current substitutes but adjacent products one feature-release away from competing.

Platforms that could trivially extend into your space represent latent competitive pressure. Products with strong distribution that could add your capability are threats even before they act.

Competitive radius: How many feature releases, partnerships, or acquisitions away is a product from competing directly?

5. Value Chain Position

Where the product sits in the customer's value chain determines who it competes with.

Products that are complements in one configuration become substitutes in another. A tool that integrates with your workflow is a complement—until it expands to replace the thing it integrated with.

Example: Calendly was a complement to calendar apps until it started adding scheduling features that compete with the calendars themselves.

Key Vocabulary

Process

Phase 1: Job Extraction

Input: Product to analyze Output: Candidate job definitions

Articulate the job(s) the product gets hired to do. Use the format:

"When [situation], I want to [motivation], so I can [expected outcome]."

Generate multiple candidates by asking:

1. What do existing customers actually use it for?
2. What do they stop using when they adopt it?
3. What would they use if this didn't exist?
4. What triggers the moment of "hiring" the product?
5. What emotional job does it serve beyond the functional one?

Warning signs of Category Tax:

• If your job statement reads like a category label ("project management," "note-taking"), you haven't found the job
• If the job could describe 50+ products equally well, it's too broad
• If you can't name a specific moment when the customer "hires" the product, dig deeper

Output template:

## Job Candidates for [Product]

### Candidate 1: [Job Statement]
- **When**: [Trigger situation]
- **Want**: [Core motivation]
- **So that**: [Expected outcome]
- **Evidence**: [Where you observed this]

### Candidate 2: [Job Statement]
...

Phase 2: Substitution Evidence Gathering

Input: Job candidates Output: Verified substitutes with evidence

For each job candidate, find substitution evidence:

Where to find substitution evidence:

1. Customer interviews: "What were you using before?" "What would you use if we didn't exist?"
2. Cancellation data: Where do churned customers go?
3. Review sites (G2, Capterra): Filter for reviews mentioning migration
4. Reddit/forums: Search "[Product A] vs [Product B]" and "migrating from [Product A]"
5. Comparison blog posts: What products do content creators compare?
6. Sales conversations: What alternatives are prospects also evaluating?

The substitution test: "If this product didn't exist, what would the customer actually use?"

• If the answer is "nothing"—you're not in a competitive market (or it's a truly new category)
• If the answer is "something completely different"—follow that thread; that's your real competition

Output template:

## Substitution Evidence for [Job]

### Verified Substitutes
| Product | Evidence Type | Specific Evidence | Strength |
|---------|--------------|-------------------|----------|
| [Product A] | Observed switching | [Quote/data] | High |
| [Product B] | Stated consideration | [Quote/data] | Medium |

### False Positives (looked like competitors, aren't)
| Product | Why it seemed like competition | Why it isn't |
|---------|-------------------------------|--------------|
| [Product C] | Same category | No switching evidence, different job |

Phase 3: Context Segmentation

Input: Verified substitutes Output: Context-specific competitive maps

The same product competes with different alternatives for different customers. Segment by hiring context:

Process:

1. List the major segments where your product/category is used
2. For each segment, re-evaluate the substitution evidence
3. Note which competitors matter in which segments
4. Identify segments where you have no real competition (opportunity or warning?)

Output template:

## Context-Specific Competitive Maps

### Segment: [Segment Name]
**Characteristics**: [What defines this segment]

| Competitor | Role in This Segment | Our Position |
|------------|---------------------|--------------|
| [Product A] | Primary alternative | [Strong/Weak/Not competing] |
| [Product B] | Secondary option | [Strong/Weak/Not competing] |
| [Build own] | Viable for some | [Strong/Weak/Not competing] |

### Segment: [Segment Name]
...

Phase 4: Adjacent Threat Assessment

Input: Current competitive map Output: Latent competition inventory

Identify products one move away from competing:

For each adjacent threat, assess:

1. Motivation: Why would they move here?

   • Revenue opportunity
   • Customer requests
   • Strategic positioning
   • Defensive move

2. Capability: How hard would it be?

   • Technical difficulty
   • Distribution challenge
   • Brand/positioning stretch

3. Signals: Any indication they're considering it?

   • Job postings
   • Acquisitions
   • Partnership announcements
   • Feature beta tests

Output template:

## Adjacent Threat Assessment

### [Adjacent Product]
- **Adjacency type**: [Feature extension/Market pivot/etc.]
- **Competitive radius**: [# releases/quarters away]
- **Motivation**: [Why they'd move]
- **Capability**: [How hard it would be]
- **Signals**: [Evidence of intent]
- **Threat level**: [High/Medium/Low/Watch]

### [Adjacent Product]
...

Phase 5: Boundary Articulation

Input: All previous outputs Output: Explicit niche boundary documentation

Document the boundary with precision:

## Competitive Niche Boundary: [Product/Category]

### Job Boundary
[The primary job, in hiring language]

### We Compete With
| Product | Evidence | Context | Threat Level |
|---------|----------|---------|--------------|
| [Direct substitute] | [Substitution evidence] | [Which segments] | Active |
| [Adjacent threat] | [Capability + motivation] | [Which segments] | Latent |

### We Do NOT Compete With (Despite Appearances)
| Product | Why It Looks Like Competition | Why It Isn't |
|---------|------------------------------|--------------|
| [False positive] | [Category overlap, feature similarity] | [Different job, no switching] |

### Segment-Specific Variations
| Segment | Primary Competitors | Our Position |
|---------|---------------------|--------------|
| [Segment A] | [Competitors] | [Assessment] |
| [Segment B] | [Competitors] | [Assessment] |

### Boundary Stability Assessment
- **Likely to expand when**: [Conditions that would bring new competitors in]
- **Likely to contract when**: [Conditions that would remove competitors]
- **Key signals to monitor**: [What to watch]

### Analysis Metadata
- **Analyst**: [Name]
- **Date**: [Date]
- **Confidence level**: [High/Medium/Low]
- **Evidence gaps**: [What's missing]
- **Next review trigger**: [When to update]

Anti-Patterns

1. Category Tax Thinking

Pattern: Assuming products in the same analyst category are competitors.

Signs:

• Competitive analysis starts with "other [category] products"
• Feature matrices comparing products that don't substitute
• No evidence of actual switching between "competitors"
• Analysis cites Gartner/Forrester categories as competitive definitions

Why it fails: Categories are labels, not markets. Customers don't buy categories; they hire solutions to jobs. A "project management" label encompasses products serving completely different jobs.

The test: Can you find 5 instances of customers switching between these products for the same job?

Fix: Start from substitution evidence, not category labels. If you can't find switching behavior, you're not competing—regardless of what analyst reports say.

2. The Demo Day Fallacy

Pattern: Defining competitors as products that look similar when demoed.

Signs:

• "They have the same features"
• Side-by-side screenshots as competitive analysis
• No consideration of who actually buys each product
• Competitor definitions based on pitch deck positioning

Why it fails: Features are visible; jobs are invisible. Products that look identical can serve completely different customers with different needs. A Porsche and a minivan both have four wheels and an engine.

The test: Do the customer bases actually overlap? Would these customers ever consider both products?

Fix: Ask who actually uses each product and what they were using before. If the customer bases don't overlap, neither does the competition.

3. Platform Blindness

Pattern: Treating a platform as a single competitor rather than recognizing it spans multiple niches.

Signs:

• "We compete with Notion/Salesforce/Microsoft"
• Comparing your focused product to a sprawling platform's entire feature set
• Strategic paralysis because "they do everything"
• No segmentation of where the platform actually competes

Why it fails: Platforms don't compete everywhere they exist. They compete specifically where their capabilities match customer jobs well enough. A platform's presence in a space is not the same as competitive threat in that space.

The test: In your specific job context, how do customers actually evaluate the platform? Do they even consider that part of the platform?

Fix: Analyze the platform's offering in your specific job context. What do they actually provide for your job? How strong is their implementation? What's their attention on this segment?

4. Static Boundary Assumption

Pattern: Treating competitive boundaries as permanent rather than constantly shifting.

Signs:

• Competitive analysis is a one-time exercise
• Surprise when an adjacent product moves into your space
• No monitoring of adjacency signals
• "That's not a competitor" dismissals that age poorly

Why it fails: Every product with motivation and capability can expand. Complement-substitute flips happen regularly. Platform sprawl is accelerating. Today's non-competitor is next quarter's primary threat.

The test: When did you last update your competitive boundary assessment?

Fix: Maintain an adjacency watch list. Set competitive radius estimates. Treat boundary monitoring as ongoing, not one-time. Define triggers for reassessment.

5. Segment Flattening

Pattern: Treating competitive position as uniform across all customer segments.

Signs:

• Single competitive positioning for all customers
• Confusion when feedback varies wildly by customer type
• "We compete with X" without "for whom"
• Marketing messages that resonate with some segments, alienate others

Why it fails: The same product occupies different competitive positions for different segments. You might dominate one context and be invisible in another. Aggregating obscures strategic insight.

The test: Does your competitive assessment change when you filter by segment?

Fix: Segment competitive analysis by hiring context. Create separate competitive maps per segment. Accept that competitive position is segment-specific.

Boundaries

Assumes

Not For

Degrades When

Complementary To

Worked Example: Task Management Space

Phase 1: Job Extraction

Product to analyze: A new task management tool targeting teams

Job Candidates:

1. "When I need to coordinate work across my team, I want to see who's doing what and when, so that work doesn't fall through cracks and we hit deadlines."

   • When: Team coordination moment
   • Want: Visibility into commitments
   • So that: Execution reliability
   • Evidence: Common in team productivity interviews

2. "When I'm overwhelmed by too many things to do, I want to capture and organize my tasks, so that I can focus without worrying about forgetting something."

   • When: Personal overwhelm
   • Want: Cognitive offload
   • So that: Mental peace and focus
   • Evidence: Personal productivity content

3. "When my manager asks for a status update, I want to quickly show progress on initiatives, so that I don't spend time on status reports."

   • When: Reporting requirement
   • Want: Automatic status visibility
   • So that: Time savings
   • Evidence: Enterprise buyer interviews

Analysis: These are three different jobs. A product optimized for #1 (team coordination) competes differently than one optimized for #2 (personal task capture) or #3 (status reporting).

Phase 2: Substitution Evidence

For Job #1 (team coordination):

False positives identified:

• Todoist: Same category, but serves personal task capture (Job #2), not team coordination
• Obsidian: Has task features, but serves knowledge management job
• Slack: Has workflow features, but serves communication job

Phase 3: Context Segmentation

Insight: "Task management" isn't one market. Engineering teams almost never consider the tools marketing teams use, and vice versa.

Phase 4: Adjacent Threats

Phase 5: Boundary Articulation

Competitive Niche: Team Task Coordination for Marketing/Operations Teams

• Job Boundary: "Coordinate work across team so nothing falls through cracks"
• NOT: Personal productivity, engineering workflow, status reporting to executives

We compete with: Asana, Monday.com, Trello (for smaller teams), spreadsheets (for migrations)

We do NOT compete with (despite appearances):

• Jira (engineering job, different buyers)
• Todoist (personal job, different context)
• Notion (knowledge management first; task features secondary)

Boundary stability: Watch Notion closely—they're one major release from being a primary competitor.

Success Indicators

Leading Indicators

Lagging Indicators

Evolution

Review Triggers

• Time: Review every quarter minimum
• Market event: Major competitor release, acquisition, or pivot
• Signal detection: Adjacent threat shows intent
• Win/loss surprise: Lost deal to unexpected competitor
• Customer feedback: "Why don't you compare to X?"

Changelog