How to conduct competitive analysis: build a competitor intelligence system that goes beyond feature matrices to understand positioning, pricing strategy, growth signals, and the strategic bets your competitors are making — so you can make product decisions with full market context.
Most competitive analyses are outdated before they're finished. A product team spends two weeks building a feature comparison spreadsheet, presents it to leadership, and files it in Confluence where it slowly becomes fiction. The solution is not a bigger spreadsheet — it's a continuous competitive intelligence system.
This guide shows product managers how to build competitive analysis that informs decisions rather than archives information.
Step 1 — Define Your Competitor Set
Not all competitors are equal. Segment your competitor set into four types:
H3: Competitor Tiers
| Tier | Definition | Example | |------|-----------|--------| | Direct | Same customer, same job-to-be-done | Same product category | | Indirect | Same customer, different approach to the same job | Adjacent tools that solve the same problem differently | | Emerging | Same job, early stage or different geography | Startups gaining traction in your segment | | Potential | Large platform players who could enter your space | Microsoft, Salesforce, Google adding your feature |
For deep analysis, focus on 2-4 direct competitors. Monitor emerging and potential competitors at lower frequency.
Step 2 — Build Your Research Stack
H3: Free Intelligence Sources
- G2, Capterra, Trustpilot: Customer review sentiment and recurring complaint themes
- LinkedIn: Hiring velocity by function (rapid engineering hiring signals product investment; heavy sales hiring signals GTM push)
- Job boards: Specific job descriptions reveal product roadmap priorities ("Hiring ML engineer to work on recommendation system" = they're building recommendations)
- App Store / Play Store reviews: Patterns in 1-3 star reviews reveal friction and unmet needs
- Changelog / release notes: What they're shipping and at what cadence
- Pricing pages: Pricing model changes signal strategic pivots
H3: Paid Intelligence Sources
- SimilarWeb: Traffic trends, channel mix, geographic distribution
- Semrush / Ahrefs: Keyword targeting, content strategy, organic growth signals
- BuiltWith: Technology stack (reveals infrastructure investment and migration signals)
- PitchBook / Crunchbase: Funding rounds and investor thesis signals
According to Lenny Rachitsky's writing on competitive strategy, the most valuable competitive intelligence comes from job postings — not for talent, but as a window into what competitors are building six to twelve months from now. Job descriptions are the closest thing to a competitor's internal roadmap.
Step 3 — Build the Feature Matrix
A feature matrix is the baseline, not the output.
H3: Feature Matrix Structure
| Feature Area | Your Product | Competitor A | Competitor B | Competitor C | |-------------|-------------|-------------|-------------|-------------| | Core Feature 1 | ✓ Full | ✓ Full | ✓ Basic | ✗ None | | Core Feature 2 | ✓ Full | ✗ None | ✓ Full | ✓ Basic | | Differentiating Feature | ✓ Unique | ✗ | ✗ | ✗ |
Code cells as: ✓ Full (complete implementation), ✓ Basic (partial), ✗ (absent), 🔜 (announced/roadmap).
The feature matrix answers: where are we behind, where are we ahead, where do we uniquely lead?
Step 4 — Build the Positioning Map
A positioning map plots competitors on two axes relevant to your customers' decision criteria.
H3: Choosing Your Axes
Axes should reflect what your target customers actually use to decide: ease-of-use vs. power, SMB vs. enterprise focus, breadth vs. depth, self-serve vs. high-touch sales. The map is most useful when the axes reveal a white space — a position no current competitor occupies that aligns with customer needs.
According to Gibson Biddle on Lenny's Podcast discussing competitive positioning, the goal of a positioning map is not to show where you are today but to identify where you want to move — the empty quadrant where the right customers are underserved.
Step 5 — Extract Strategic Insights
The feature matrix and positioning map are inputs. The output is strategic insight: what should we do differently because of what we learned?
H3: Three Questions for Strategic Insight
- Where is the market converging? (All competitors adding the same feature signals a table-stakes requirement)
- Where is the market diverging? (Competitors making opposite bets signals an unresolved strategic question)
- What are competitors avoiding? (White spaces in the feature matrix may reveal under-served segments or dismissed opportunities)
H3: Building a Continuous Intelligence System
Rather than quarterly competitive audits, build a system:
- Weekly: Review competitor changelogs, app store reviews, and LinkedIn hiring
- Monthly: Refresh feature matrix and pricing data
- Quarterly: Full competitive landscape review with positioning map update
- On trigger: Immediate analysis when a competitor raises funding, launches a major feature, or changes pricing
According to Shreyas Doshi on Lenny's Podcast, the most common competitive intelligence mistake is building a system optimized for comprehensiveness rather than speed to insight. A lightweight weekly review beats an exhaustive quarterly audit because markets move faster than audit cycles.
FAQ
Q: How do you conduct competitive analysis as a product manager? A: Define your competitor tiers, build a multi-source research stack covering reviews, job posts, changelogs, and traffic data, construct a feature matrix and positioning map, then extract strategic insights about where the market is converging, diverging, or leaving white spaces.
Q: What sources should you use for competitive analysis? A: G2 and Capterra for customer sentiment, LinkedIn and job boards for roadmap signals, competitor changelogs for shipping cadence, SimilarWeb for traffic trends, and Semrush for content strategy.
Q: How often should you update your competitive analysis? A: Weekly lightweight reviews of changelogs and hiring signals, monthly feature matrix refreshes, quarterly full landscape reviews with positioning map updates, and immediate analysis triggered by competitor funding, major launches, or pricing changes.
Q: What is a competitive positioning map? A: A two-axis chart plotting competitors on dimensions relevant to your customers' decision criteria — used to identify white spaces where the right customers are underserved and where you could move to win.
Q: How do you turn competitive analysis into product decisions? A: Ask three questions: where is the market converging (table-stakes requirements), where is it diverging (unresolved strategic bets), and what are competitors avoiding (potential white spaces). Answers directly inform roadmap prioritization.
HowTo: Conduct Competitive Analysis
- Define your competitor set by tier — direct, indirect, emerging, and potential — and prioritize two to four direct competitors for deep analysis
- Build a research stack using free sources including G2, LinkedIn job posts, changelogs, and app store reviews plus paid sources like SimilarWeb and Semrush
- Construct a feature matrix scoring each competitor as full implementation, basic, absent, or roadmap across all core and differentiating feature areas
- Build a positioning map on two axes reflecting your customers' actual decision criteria to identify white spaces no competitor currently occupies
- Extract strategic insights by asking where the market is converging, where it is diverging, and what all competitors are avoiding
- Replace the quarterly competitive audit with a continuous system: weekly changelog and hiring reviews, monthly matrix refreshes, and quarterly full landscape updates