competitive analysis matrix

Feature matrices answer 'what does the competitor have?' That is the wrong question. The right questions are: where are customers leaving them and why, what can they structurally not do, and how much pain does it cost someone to switch?

From the Competitive Analysis page, PM Manual

This is the template. No download, no email gate. Copy the markdown, paste it into Notion or a Google Sheet, fill in your rows, and use it in the next roadmap meeting where someone asks “what are our competitors doing?”

What follows the template is an explanation of why each column exists — because a template you fill in mechanically without understanding it is a template that produces wrong decisions.

The template

Copy everything between the horizontal rules.

# Competitive Analysis Matrix
**Product area:** [The specific area you are analyzing — e.g., "onboarding flow", "pricing page", "mobile app checkout"]
**Analysis date:** [Date — this goes stale fast, always date it]
**Decision this informs:** [The specific product or roadmap decision this analysis will feed. If you cannot name it, stop and find it first.]

---

## Competitors in scope

| # | Competitor | Type | Why included |
|---|-----------|------|-------------|
| 1 | [Your product] | Baseline | — |
| 2 | [Direct competitor A] | Direct | [One sentence — same buyer, same problem, similar approach] |
| 3 | [Direct competitor B] | Direct | [One sentence] |
| 4 | [Indirect competitor] | Indirect | [Different approach to the same problem] |
| 5 | [Emerging entrant] | Signal | [New, small — but directionally interesting] |

*Limit to 4-5 competitors. A matrix with 10 rows is not more thorough — it is less actionable.*

---

## Dimension scoring

**Scale:** 0 = does not exist, 1 = exists but weak, 2 = solid, 3 = best-in-class
**Source:** List where you got the score (review site, trial, customer interview, sales call notes)

### Dimension 1: Core job-to-be-done

*What is the primary thing a user comes to this product to accomplish? Score how well each competitor does that specific job.*

| Dimension | Your Product | Competitor A | Competitor B | Indirect | Emerging |
|-----------|:---:|:---:|:---:|:---:|:---:|
| **Core JTBD execution** | | | | | |
| Source | | | | | |
| Notes | | | | | |

### Dimension 2: Onboarding and time-to-value

*How long before a new user gets their first meaningful outcome? Lower friction = higher score.*

| Dimension | Your Product | Competitor A | Competitor B | Indirect | Emerging |
|-----------|:---:|:---:|:---:|:---:|:---:|
| **Time-to-first-value** | | | | | |
| **Documentation quality** | | | | | |
| **Setup complexity** | | | | | |
| Source | | | | | |
| Notes | | | | | |

### Dimension 3: Pricing and packaging

*Is the pricing legible? Does it match how the buyer thinks about value? Score legibility and alignment, not just price.*

| Dimension | Your Product | Competitor A | Competitor B | Indirect | Emerging |
|-----------|:---:|:---:|:---:|:---:|:---:|
| **Pricing legibility** | | | | | |
| **Entry price accessibility** | | | | | |
| **Value-metric alignment** | | | | | |
| Source | | | | | |
| Notes | | | | | |

### Dimension 4: Ecosystem and integrations

*What does the product connect to? For B2B products, integrations are switching costs — both for gaining customers and for losing them.*

| Dimension | Your Product | Competitor A | Competitor B | Indirect | Emerging |
|-----------|:---:|:---:|:---:|:---:|:---:|
| **Core integrations** | | | | | |
| **API access** | | | | | |
| **Marketplace / partner ecosystem** | | | | | |
| Source | | | | | |
| Notes | | | | | |

### Dimension 5: Structural constraints

*What can each competitor structurally NOT do — because of their business model, funding, sales motion, or installed base?*

| Competitor | Constraint | Why it exists | Time to unwind |
|-----------|-----------|---------------|---------------|
| Competitor A | [e.g., Cannot serve SMBs profitably] | [Enterprise sales motion requires $50K+ ACV] | [3-5 years to restructure go-to-market] |
| Competitor B | | | |
| Indirect | | | |
| Emerging | | | |

*This table is the most important one in the matrix. Fill it before filling anything else.*

---

## Customer voice (what customers say publicly)

*Pull this from G2, Capterra, App Store reviews, Reddit, and Twitter. Not the 5-star reviews — the 2-star and 3-star ones. These are from people who tried the product and found it only partially worked. That friction is your opportunity.*

| Competitor | Top praise (what works) | Top complaint (what fails) | Source |
|-----------|------------------------|--------------------------|--------|
| Your Product | | | |
| Competitor A | | | |
| Competitor B | | | |
| Indirect | | | |

---

## Switching cost map

*For a customer to leave Competitor A and come to you, what do they have to give up? This determines where you should attack and where you should not.*

| From → To | Data migration effort | Retraining effort | Contract lock-in | Net switching cost |
|-----------|:---:|:---:|:---:|:---:|
| Competitor A → You | [Low / Med / High] | [Low / Med / High] | [None / 6mo / 12mo+] | [Low / Med / High] |
| Competitor B → You | | | | |
| You → Competitor A | | | | |

---

## The decision

*Fill this section last. If you cannot write one or two specific decisions that follow from this analysis, the analysis is not done.*

**What this analysis tells us to do:**
1. [Specific action — e.g., "Do not build feature X — Competitor A has a 3-year head start and we have a structural advantage in segment Y instead"]
2. [Specific action — e.g., "Prioritize onboarding reduction — we are a 2 vs Competitor B's 3 on time-to-value, and that is where churn happens in month 1"]
3. [Specific action]

**What this analysis does NOT tell us:**
- [The question this analysis cannot answer — and what you need to find out to answer it]

**Review date:** [When to revisit — competitive analyses older than 90 days are usually wrong about something important]

How to fill each section

Start with the decision, not the competitors

Before you write a single competitor name, write the decision this matrix will inform. Be specific. “Understand the competitive landscape” is not a decision. “Should we prioritize checkout speed or payment method breadth in Q3?” is a decision. “Should we price by seat or by usage for the SMB segment?” is a decision.

The decision determines which dimensions belong in the matrix. If you are evaluating a pricing decision, Dimensions 2 and 3 matter most. If you are evaluating whether to build an integration, Dimension 4 is the whole analysis. If you are making a positioning call, customer voice and structural constraints are the inputs. A matrix without a named decision collects every dimension equally and produces nothing actionable.

Choosing your competitors

Four to five competitors is the right number. Beyond five, the matrix becomes a documentation exercise. Less than three and you are not capturing enough competitive surface area.

Include at least one structural constraint you do not have, and at least one competitor targeting a different segment with a different approach. The direct competitors tell you where to fight. The indirect one tells you where the market is going. The emerging signal tells you where smart people are placing bets.

Label each competitor by type before you score them. Direct competitors require a thorough response. Indirect and signal competitors require a posture, not a response.

Scoring honestly

The most common mistake in competitive matrices is inflation. PMs score their own product generously and competitors conservatively because they are presenting to leadership and the matrix feels like a report card.

This destroys the analysis. If your product gets a 2 and the competitor deserves a 2, write 2 for both. If you genuinely believe your product is weaker on a dimension that matters, write the lower number. That is the point — to find where the actual gaps are.

A useful calibration: score each dimension from the customer’s perspective, not from what you believe internally. “We have an API” is not a 3 — a 3 is “customers consistently choose us over alternatives because of our API quality and documentation.” Check your scores against your G2 and Capterra reviews. If customers are not mentioning a dimension as a positive, you probably scored it too high.

The structural constraints table

This is the most important section and the one most teams skip. A feature can be copied in a quarter. A structural constraint takes years to unwind.

Structural constraints come from four places:

Business model. A freemium product with 10 million free users cannot remove the free tier without losing their distribution. An enterprise product with a direct sales motion cannot serve SMBs — the unit economics do not work at that deal size.

Funding and burn. A startup burning $3M per month cannot afford to chase a six-month sales cycle with a small customer. A public company cannot sacrifice NRR this quarter to win positioning next year.

Installed base. A competitor with a large legacy customer base cannot make breaking changes even when those changes are obviously right. They are hostage to backward compatibility.

Go-to-market motion. A company that sells through partners cannot build a product-led growth motion without destroying their partner relationships. A company that sells direct cannot pivot to PLG without reducing perceived sales deal value.

For each competitor, find the constraint. Then ask: can we win in the space this constraint creates? If yes, that is where to focus. If no, find a different angle.

Customer voice is primary data

Do not fill the customer voice table from your assumptions. Fill it from what customers actually say.

G2 and Capterra have review filters that let you see customers who switched from a specific competitor. Those reviews are gold — someone who left Competitor A for something else will tell you exactly what broke the relationship. Read fifty reviews per competitor before writing a single word in the customer voice table.

App store reviews work especially well for consumer-facing products in India. Regional language reviews surface pain points that English-language review sites miss. A competitor with 4.1 stars overall might have 2.7 stars in Hindi reviews because a critical flow breaks on older Android devices with regional fonts.

Reddit threads are underused for B2B analysis. Search the competitor name plus “alternative” or “leaving” or “migrating from.” These threads have specific, honest evaluations from people who have used the product under real conditions — not the polished use cases the competitor puts on their website.

Switching cost map

This table prevents you from attacking the wrong target. High switching cost means customers are locked in even if they are unhappy. They will not switch even when your product is objectively better, because the migration pain is too high. Low switching cost means a superior product actually wins.

Attacking a high-switching-cost competitor head-on is usually a losing strategy. A better move is to win at the top of the funnel — new customer acquisitions where switching cost does not yet exist — and let the locked-in base churn out over time.

For the reverse direction (you → competitor), be honest. If switching away from you is easy, your retention strategy needs work before your feature strategy.

// exercise: · 90 min

Fill the matrix for your current competitive threat

Pick the competitive situation that is most live for you right now. A specific competitor your sales team mentions in every deal, or a segment you are trying to enter where an established player dominates.

Work through the matrix in this order:

Write the decision first. Name the specific product or roadmap decision this analysis will inform. If you cannot write it in one sentence, stop and figure it out before continuing.
Fill the structural constraints table before anything else. For each competitor, identify one structural thing they cannot do. If you can only find feature differences, go deeper — find the business model or motion that creates them.
Pull fifty customer reviews. G2, Capterra, or App Store — real reviews, not the marketing copy. Find the top three complaints. Write them in the customer voice table verbatim (paraphrase, but stay close to the customer’s actual words).
Score every dimension from the customer’s perspective. After scoring, sanity-check by asking: “Would a customer who tried both products score us this way?” If the answer is uncertain, you are probably scoring yourself too generously.
Fill the decision section. If you cannot write two or three specific actions that follow from the matrix, the matrix is not done — you have information but not analysis. Go back and look for the pattern.

After you complete it, bring it to one colleague who was not involved and ask: “Based on this matrix, what would you prioritize next quarter?” If they come to a different conclusion than you, that is a gap in your reasoning, not their reading.

// interactive:

The Sales Team Escalation

Your head of sales, Vikram, walks into your Slack at 11am on a Tuesday. A deal you have been trying to close for two months — a 120-seat B2B account in the logistics sector — just went to a competitor. Vikram's message: 'Competitor X won it. They have a WhatsApp integration. We don't. I need that on the roadmap by next quarter or we are going to keep losing these deals.' You have a competitive matrix but it does not include WhatsApp integration as a dimension. You have a sprint planning session in two days.

Vikram has named a specific feature. He has a real loss to point to. Your sprint is in two days. What do you do in the next four hours?

When to update the matrix

A competitive matrix has a shelf life. Here is when it goes stale and what to do.

Update immediately when:

You lose a deal and the stated reason is a feature gap you do not have in the matrix
A competitor announces a funding round or acquisition (structural constraint changes)
A competitor changes their pricing model (dimension 3 resets entirely)
A new entrant raises a seed round targeting your exact segment

Update quarterly when:

G2 or Capterra review patterns shift — this shows product-market changes before public announcements
Your own NPS or support tickets surface a new complaint category that is not reflected in your matrix scores
Your sales team’s win/loss ratio changes by more than 10 percentage points in either direction

Do not update reactively for:

Competitor blog posts or press releases about new features (wait to see if customers actually use them)
Conference announcements (features announced at conferences take 6-12 months to reach general availability)
Anything a competitor’s sales rep says in a competitive deal (assume favorable self-representation)

Competitive Analysis — the analysis approach behind this template: the three questions that actually matter, and how to turn findings into strategy
PRD Template — once competitive gaps become roadmap items, this is how you specify them for engineering
Market Research Template — for the upstream research that populates the customer voice and structural constraints sections
Prioritization Frameworks — once the matrix surfaces two or three opportunities, this is how to sequence them