How many competitors should I track?

Track 3-5 direct competitors and 1-2 adjacent or non-obvious alternatives. More than 7-8 makes the analysis unwieldy and hard to maintain. Focus on competitors you actually encounter in deals, not every company in the space. Review the set quarterly and add or remove competitors as the market shifts.

How do I gather competitive intelligence ethically?

Use public sources: competitor websites, pricing pages, G2 and Capterra reviews, job postings (which reveal product direction), conference talks, blog posts, and changelogs. Your sales team is another strong source because they hear directly from prospects who evaluated competitors. Avoid anything that requires misrepresenting yourself or violating terms of service. The [Product Strategy Handbook](/strategy-guide) covers ethical competitive research methods.

How often should the competitive landscape be updated?

Review quarterly as a baseline. Do ad-hoc updates when a competitor launches a significant feature, changes pricing, raises a round, or gets acquired. The feature matrix and win/loss data should be living documents. The positioning map and strategic implications require more deliberate quarterly review.

Should I share competitive analysis with the whole company?

Share the feature matrix and positioning map broadly. Sales needs battlecards derived from this analysis. Marketing needs positioning context. Engineering benefits from understanding why certain features matter competitively. However, the strategic implications section (your planned response) should have a more limited audience. Win/loss data with deal details should be anonymized for broad distribution. The [Stakeholder Management Handbook](/stakeholder-guide) covers communication strategies for sensitive strategic information.

How do I handle competitors that are much larger than us?

Do not try to compete across every feature. Identify the 2-3 capabilities where you can be definitively better for your target segment, and invest heavily there. Large competitors have broad feature sets but often lack depth in specific workflows. Your advantage is focus and speed. Use the [RICE framework](/frameworks/rice-framework) to prioritize the features that create the most differentiation per engineering hour invested. ---

Competitive Overview Template for PMs

What This Template Is For

A competitive landscape analysis is a structured view of who you are competing against, where you win, where you lose, and where the market is heading. It goes beyond listing competitors and their features. It maps positioning, identifies gaps in the market, and surfaces the strategic moves your team should anticipate. Without one, product decisions are based on gut instinct about competitors rather than evidence.

This template is designed for PMs, product leaders, and strategy teams who need to maintain a living competitive picture. It covers competitive identification, feature comparison, positioning mapping, win/loss patterns, and strategic implications. The output is a working document your team references when making roadmap decisions, responding to sales objections, or evaluating new market entrants.

For deeper frameworks on positioning, see April Dunford's positioning methodology. The Product Strategy Handbook covers competitive positioning within the broader strategy context. If you are comparing specific frameworks for prioritization decisions, the RICE vs ICE vs MoSCoW comparison shows how to evaluate options systematically.

How to Use This Template

Identify your competitive set. Include direct competitors, adjacent products that could expand into your space, and non-obvious alternatives (spreadsheets, manual processes, internal tools).
Fill in the competitor profiles. For each competitor, document their positioning, pricing, target segment, key strengths, and weaknesses. Use their website, G2/Capterra reviews, and sales team intel.
Build the feature matrix. Compare capabilities across the features that matter most to your buyers. Rate each on a consistent scale.
Map the positioning landscape. Plot competitors on a 2x2 matrix using the two dimensions most relevant to your buyers.
Analyze win/loss patterns. Review your recent wins and losses to understand why buyers choose you (or do not).
Identify strategic implications. What does this analysis mean for your roadmap? Where should you invest? Where should you avoid competing head-on?
Set a review cadence. Competitive landscapes shift. Review and update this document quarterly.

The Competitive Overview Template

1. Competitive Set Overview

Field	Details
Product	[Your product name]
Author	[Name, title]
Date	[Date]
Market category	[e.g., Product analytics, CRM, CI/CD]
Last reviewed	[Date]

Competitive set.

Competitor	Type	Positioning	Target Segment	Pricing Model	Est. Revenue / Stage
[Competitor A]	Direct	[Their stated positioning]	[Who they target]	[Pricing model: per-seat, usage, flat]	[Est. ARR or funding stage]
[Competitor B]	Direct	[Their stated positioning]	[Who they target]	[Pricing model]	[Est. ARR or funding stage]
[Competitor C]	Adjacent	[Their stated positioning]	[Who they target]	[Pricing model]	[Est. ARR or funding stage]
[Alternative D]	Non-obvious	[e.g., "Spreadsheets + Zapier"]	[Who uses this workaround]	[Free / Low cost]	[N/A]

☐ Included at least 3 direct competitors
☐ Included at least 1 adjacent competitor (could expand into your space)
☐ Included at least 1 non-obvious alternative (manual process, spreadsheet, internal tool)

2. Feature Matrix

Rate each competitor's capability using a consistent scale: Strong, Adequate, Weak, Missing.

Feature / Capability	Us	Competitor A	Competitor B	Competitor C	Importance to Buyer
[Core capability 1]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
[Core capability 2]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
[Core capability 3]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
[Core capability 4]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
[Core capability 5]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
[Core capability 6]	[Rating]	[Rating]	[Rating]	[Rating]	Critical / Important / Nice-to-have
Integrations	[Rating]	[Rating]	[Rating]	[Rating]	[Importance]
Ease of setup	[Rating]	[Rating]	[Rating]	[Rating]	[Importance]
Pricing transparency	[Rating]	[Rating]	[Rating]	[Rating]	[Importance]
API / Extensibility	[Rating]	[Rating]	[Rating]	[Rating]	[Importance]

☐ Features are ranked by buyer importance (Critical > Important > Nice-to-have)
☐ Ratings are based on evidence (demos, reviews, customer feedback), not assumptions
☐ Include at least 8 features that buyers evaluate during purchase decisions

3. Positioning Map

Plot competitors on a 2x2 matrix. Choose the two dimensions that matter most to your target buyers.

Suggested axis pairs (pick the most relevant):

Ease of use vs. Depth of features
Price vs. Functionality
SMB-focused vs. Enterprise-focused
Self-serve vs. Sales-assisted
Point solution vs. Platform

Axis X: [Dimension] (Low to High)

Axis Y: [Dimension] (Low to High)

Quadrant	Position	Competitors
Top-right (High X, High Y)	[What this position means]	[Competitors in this quadrant]
Top-left (Low X, High Y)	[What this position means]	[Competitors in this quadrant]
Bottom-right (High X, Low Y)	[What this position means]	[Competitors in this quadrant]
Bottom-left (Low X, Low Y)	[What this position means]	[Competitors in this quadrant]

Where we sit: [Your current position on the map]

Where we want to be: [Your target position and why]

4. Win/Loss Analysis

Deal	Won / Lost	Competitor	Primary Reason	Secondary Reason	Segment
[Deal 1]	Won	[Competitor]	[e.g., Faster time to value]	[e.g., Better integrations]	[Segment]
[Deal 2]	Lost	[Competitor]	[e.g., Missing enterprise SSO]	[e.g., Higher price]	[Segment]
[Deal 3]	Lost	[Competitor]	[e.g., Incumbent relationship]	[e.g., Fear of migration]	[Segment]
[Deal 4]	Won	[Competitor]	[e.g., Pricing]	[e.g., Modern UX]	[Segment]

Win rate by competitor.

Competitor	Win Rate	Sample Size	Trend
[Competitor A]	[X]%	[N deals]	Improving / Stable / Declining
[Competitor B]	[X]%	[N deals]	Improving / Stable / Declining
[Competitor C]	[X]%	[N deals]	Improving / Stable / Declining

☐ Reviewed at least 10 recent deals (last 2 quarters)
☐ Identified the top 3 reasons buyers choose us
☐ Identified the top 3 reasons buyers choose competitors

5. Strategic Implications

Where we have an advantage. [2-3 sentences on where you consistently win and why.]

Where we are vulnerable. [2-3 sentences on where you consistently lose and the structural reasons behind it.]

Competitive moves to anticipate. [What are competitors likely to do in the next 6-12 months?]

Competitor	Anticipated Move	Evidence	Our Response
[Competitor A]	[e.g., Launch AI features]	[e.g., Job postings, conference talks]	[How we should respond]
[Competitor B]	[e.g., Move downmarket with free tier]	[e.g., Pricing page changes]	[How we should respond]

Roadmap implications.

☐ [Investment area 1: e.g., Close the SSO gap to stop losing enterprise deals]
☐ [Investment area 2: e.g., Double down on integration advantage]
☐ [Investment area 3: e.g., Build competitive battlecards for sales]

Filled Example: FlowBoard (Project Management Tool)

Competitive Set Overview

Competitor	Type	Positioning	Target Segment	Pricing Model	Est. Revenue
Asana	Direct	"Work management for teams"	Mid-market, 50-500 employees	Per-seat, $10.99-24.99/mo	$600M+ ARR
Linear	Direct	"Issue tracking for high-performance teams"	Engineering-led startups, 20-200	Per-seat, $8/mo	$30M+ ARR est.
Notion	Adjacent	"All-in-one workspace"	Startups, solopreneurs, small teams	Freemium, $8-15/mo per seat	$300M+ ARR
Spreadsheets + Slack	Non-obvious	"Free, familiar, no learning curve"	Early-stage, <20 people	Free	N/A

Feature Matrix

Feature	FlowBoard	Asana	Linear	Notion	Buyer Importance
Task management	Strong	Strong	Strong	Adequate	Critical
Sprint planning	Strong	Adequate	Strong	Weak	Critical
Custom workflows	Strong	Strong	Adequate	Weak	Important
Roadmap views	Strong	Adequate	Adequate	Weak	Important
Real-time collaboration	Adequate	Strong	Adequate	Strong	Important
Reporting / Analytics	Strong	Adequate	Adequate	Missing	Important
API / Integrations	Adequate	Strong	Strong	Adequate	Important
Ease of onboarding	Adequate	Adequate	Strong	Strong	Critical
Enterprise (SSO, SCIM)	Missing	Strong	Adequate	Adequate	Critical (enterprise)
AI features	Adequate	Adequate	Adequate	Strong	Nice-to-have (growing)

Win/Loss Summary

Top 3 reasons buyers choose FlowBoard: (1) sprint planning and roadmap views in one tool, (2) reporting depth, (3) pricing 30% below Asana.

Top 3 reasons buyers choose competitors: (1) missing enterprise SSO (lost to Asana), (2) Notion's flexibility for non-engineering teams, (3) Linear's speed and developer experience.

Strategic Implications

Invest in: Enterprise readiness (SSO, SCIM, audit logs) to stop losing deals over $50K ACV. Double down on reporting advantage. Ship AI sprint planning summaries to match market expectations.

Avoid competing on: Notion's "everything workspace" breadth. Focus on project-to-roadmap workflow, not general-purpose docs.

Key Takeaways

Track direct competitors, adjacent threats, and non-obvious alternatives (manual processes, spreadsheets)
The feature matrix only matters when features are ranked by buyer importance. A feature you rate "Strong" that buyers rate "Nice-to-have" is not an advantage
Win/loss analysis provides the most actionable intelligence. What prospects tell you in deal reviews is more reliable than what competitors say about themselves
Update the analysis quarterly and after any significant competitive event
Translate analysis into specific roadmap implications. Competitive intelligence without action is just research

About This Template

Created by: Tim Adair

Last Updated: 3/4/2026

Version: 1.0.0

License: Free for personal and commercial use

Competitive Overview Template for PMs