Competitive Analysis

Competitive Analysis

Overview

Competitive analysis isn't about building a feature comparison spreadsheet — it's about understanding where you win, where you lose, and where the market is going. This skill guides you through strategic competitive analysis using frameworks like Porter's Five Forces, competitive positioning maps, and feature impact matrices.

When to Use

• Entering a new market or segment
• Positioning a new product or major feature
• Preparing for a strategy review or board deck
• Evaluating an acquisition or partnership
• Don't use for: daily feature-level tracking (use lightweight monitoring instead), one-off competitor curiosity

Instructions

1. Identify Your Competitors

Three tiers:

• Direct — Same problem, same solution approach
• Indirect — Same problem, different solution approach
• Adjacent — Different problem, but could move into yours

2. Build Competitive Profiles

For each competitor, document:

• Product: Core offering, key features, pricing model
• Positioning: What do they say about themselves? What segment do they target?
• Distribution: How do they reach customers? (Sales-led, product-led, channel)
• Funding/Size: Revenue range, funding, employee count (indicates staying power)
• Strengths: Their unfair advantages
• Weaknesses: Where they're vulnerable

3. Map the Competitive Landscape

Create a positioning map with 2 key axes (e.g., ease of use vs. power, price vs. features). Plot each competitor. Where is there white space? Where is it crowded?

4. Apply Porter's Five Forces

1. Threat of new entrants — How hard is it to enter this market?
2. Bargaining power of suppliers — Do suppliers control your costs?
3. Bargaining power of buyers — Do customers have leverage?
4. Threat of substitutes — What non-obvious alternatives exist?
5. Industry rivalry — How intense is competition?

5. Feature Analysis

• List the top 15-20 features/capabilities in the market
• Score each competitor: 0=absent, 1=weak, 2=comparable, 3=market-leading
• Identify where you must match vs. where you can differentiate
• Highlight features you should deliberately NOT build

6. Strategic Recommendations

• Where to compete — Segments where your strengths matter most
• How to differentiate — Capabilities competitors can't easily copy
• Risks to monitor — Competitor moves that could disrupt you
• White space — Unserved needs or underserved segments

Sample Output

A competitive analysis for a team task manager might reveal:

• Direct: Asana (power), Trello (simplicity), Linear (developer-focus)
• Indirect: Notion (all-in-one), GitHub Issues (code-coupled)
• White space: Teams that want simple but structured — not as rigid as Asana, not as loose as Trello
• Strategic recommendation: Focus on async status updates + AI summaries (competitors ignore this)
• Don't build: Advanced resource management (Asana already owns this, low differentiation)

Common Pitfalls

1. Spreadsheet trap — 50-row feature matrices obscure strategy. Focus on the 10 things that matter
2. Confirmation bias — Cherry-picking competitors that make you look good
3. Static analysis — Competitors change. Revisit quarterly
4. Ignoring indirect competitors — The biggest threats often come from adjacent spaces
5. Paralysis by analysis — Done is better than perfect. A good competitive analysis takes 2-3 days

Verification Checklist

• [ ] Identified direct, indirect, and adjacent competitors
• [ ] Built a positioning map with 2 strategic axes
• [ ] Documented strengths/weaknesses per competitor
• [ ] Identified 3+ strategic recommendations
• [ ] Flagged 2-3 risks to monitor

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: uthumany
• Source: uthumany/uthy-legacy-os
• License: MIT
• Homepage: https://uthumany.github.io/uthy-legacy-os/

Install and usage instructions live in the source repository linked above.