Competitive Analysis for Heads of Product: template, structure and example

A Head of Product's Competitive Analysis is a competitor intelligence document that reads the market at strategy level: ICP and buyer context, competitor segmentation, positioning and claims, and win-loss evidence. It decides where the product can credibly differentiate and defend, and what product, GTM and investment actions should follow across the portfolio.

Reviewed by Gensudo Team · Last reviewed 24 July 2026

When to use it

Create it in Discover, ahead of the Customer Segmentation Report, when a product, positioning, pricing, sales or investment decision needs a defensible read of the competitive landscape. Reach for it when you must explain not just what is happening in the market but why a given direction is the right one, and when senior leadership needs confidence before funding or strategic commitment. It is the right document when the decision spans the portfolio rather than a single feature.

When not to use it

If the question is feature-level or workflow-level, how a specific journey compares step by step, the Product Manager's Competitive Analysis fits better. If the landscape is already understood and the next need is to define and size the segments you serve, move on to the Customer Segmentation Report. Skip it when there is no strategic, pricing or investment decision at stake.

What you need before you start

Recommended structure, section by section

  1. Executive SummaryThe decision-ready view of the competitive position: category context, highest-risk threats, credible differentiation, recommended product and GTM actions, and decisions required.
  2. Purpose, Decision Context and Success MetricsThe product, portfolio, positioning, pricing, sales or investment decisions this analysis will inform, plus the metrics it should influence.
  3. Market, ICP and Buyer ContextTarget market, customer segments, priority use cases, category maturity, buying committee, budget owner, procurement drivers and adoption influencers.
  4. Competitive LandscapeDirect competitors, indirect competitors, substitutes, emerging entrants, incumbents, open-source alternatives, services-led alternatives and adjacent threats.
  5. Competitor SegmentationCompetitors grouped by market position, customer segment, pricing model, GTM motion, product maturity, enterprise readiness and likely buyer consideration set.
  6. Evaluation Criteria and WeightingThe comparison criteria, their relative importance and why they matter, covering differentiation, enterprise readiness, integrations, compliance, adoption, pricing and GTM strength.
  7. Comparison MatrixA side-by-side comparison of your product against key competitors across strategic, commercial, product, operational, security, compliance and GTM criteria.
  8. Competitor ProfilesPositioning, target customers, use cases, strengths, weaknesses, pricing signals, proof points, GTM model, partnerships, roadmap signals and likely strategic direction.
  9. Pricing, Packaging and Value Metric ComparisonHow competitors monetise, package capabilities, use trials or freemium, structure tiers, apply value metrics and signal ROI.
  10. Positioning, Messaging and Claims AnalysisHow competitors frame their value proposition, which proof points they use, which claims are defensible, and where your product can credibly differentiate.
  11. Customer, Sales and Win/Loss EvidenceEvidence from sales calls, lost deals, churn reviews, RFPs, customer interviews, review sites, support themes and customer success feedback.
  12. Threat and Opportunity AssessmentThreat level and opportunity level by competitor, with likely impact on pipeline, retention, expansion, pricing power and market perception.
  13. Differentiation, Market Gaps and DefensibilityWhere the product can win, where gaps are material, and which advantages can become defensible through workflow depth, data, integrations, compliance or ecosystem position.
  14. Product, GTM and Sales Enablement RecommendationsRoadmap implications, GTM recommendations, pricing considerations, objection handling, battlecards, sales enablement needs and investment decisions.
  15. Monitoring Signals and Review TriggersThe competitor moves, customer signals, pricing changes, analyst signals or win/loss shifts that should trigger an update before the standard review cadence.
  16. Evidence, Assumptions and ConfidenceSources, dates, evidence quality, confidence levels, assumptions, contradictory signals and areas requiring further validation.
  17. Ownership and Review CadenceWho owns the analysis, who contributes updates, when it is refreshed, where the source evidence lives and how changes are communicated.

What good looks like

It is strong when another product lead can grasp the competitive position without a long verbal briefing, and can see that the read rests on evidence rather than personal preference. The executive summary gives the decision-ready view: category context, highest-risk threats, credible differentiation and the product and GTM actions required. Threat and opportunity are assessed by competitor, differentiation is tied to what can become defensible, and a new reader can name the recommended next step, see who approved it and know what would trigger an update.

Quality checklist

Who creates it, and when

In Gensudo this document is a governed template for:

Where it sits in the flow

Before this document: Market Research Report for Heads of Product

This unblocks: Persona Document for Product Managers · Opportunity Assessment for Product Managers · Product Strategy Document for Heads of Product

Writing one from scratch? Read the step-by-step guide: How to Write a Competitive Analysis: Steps, Examples and Checklist.

Frequently asked questions

How is the Head of Product version different from the PM version?

This one works at market and strategy level: ICP and buyer context, competitor segmentation, positioning and claims analysis, win-loss evidence, defensibility, and GTM and sales enablement across the portfolio. The Product Manager version works at feature and workflow level, comparing user journeys step by step to drive backlog and MVP decisions.

What decisions is this analysis meant to inform?

Portfolio direction, positioning, pricing and packaging, sales enablement and investment. It should be explicit about which of these decisions it serves and the metrics it aims to influence, so senior leadership can act on it with confidence.

How does win-loss evidence fit in?

It is central. Evidence from sales calls, lost deals, churn reviews, RFPs, customer interviews, review sites and customer success feedback grounds the threat and opportunity assessment and keeps the competitive read anchored in what buyers actually do, not what the market claims.

Who signs it off?

Final sign-off normally sits with the Head of Product, with senior leadership endorsement where funding, risk or strategic direction is affected. Do not request sign-off until current competitor evidence, weighted criteria and differentiation risks are set out, the recommendation and ownership are clear, and open questions are visible.

When should it be refreshed?

Ahead of the standard cadence when monitoring signals shift: a material competitor move, a pricing change, an analyst signal or a swing in win-loss. The Monitoring Signals and Review Triggers section should name these in advance so the analysis stays current between reviews.

Create this document in Gensudo

The governed template, role-specific guidance and AI drafting grounded in cited evidence.

Get started