Market Research Report for Heads of Product: template, structure and example

A Market Research Report is the Head of Product's evidenced view of the market before product choices are made: market size, trends, competition, buyer economics and external forces, interpreted into implications. It gives leaders a reliable basis for portfolio direction, so strategy is set from evidence rather than assumption or opinion.

Reviewed by Gensudo Team · Last reviewed 24 July 2026

When to use it

Create it early in Discover, when you need to start broad and understand the market before committing to a solution or investment. Use it to establish market size, dynamics, customer demand and competitive context, and to inform strategic or investment decisions across the portfolio. It works best when written for readers who were not part of the original conversations.

When not to use it

Do not use it to make the funding decision itself; once the market is understood, a Business Case carries the investment case. If you are narrowing to how a single trend reshapes the market, an Industry Trends Report is the natural next step rather than this broad scan.

What you need before you start

Recommended structure, section by section

  1. Executive SummaryThe market opportunity, evidence strength, segment attractiveness, major risks, recommended decision and decisions required from leadership.
  2. Purpose, Decision Context and Success MetricsWhy the research was commissioned, which strategic or investment decisions it informs, and which product or commercial metrics may be affected.
  3. Research Scope and MethodMarkets, segments and questions in scope, methods used, sample, data sources, time period, exclusions and known limitations.
  4. Market Definition and BoundariesThe market category, boundaries, adjacent categories, substitutes and assumptions used to define the opportunity.
  5. Market Sizing and ModelTAM, SAM and SOM or equivalent sizing, calculation method, key assumptions, sensitivity ranges and confidence level.
  6. Market Dynamics and TrendsGrowth drivers, headwinds, regulatory shifts, technology shifts, budget shifts and structural changes shaping the market.
  7. Customer Segments and DemandPriority segments, needs, urgency, frequency, willingness to pay, buying triggers and evidence of real demand.
  8. Buyer Economics and Procurement ContextBudget owner, economic buyer, approval process, procurement friction, ROI expectations and likely buying cycle.
  9. Competitive and Substitute LandscapeWho else serves this demand at a market level, including direct competitors, substitutes, incumbents, services, internal tools and doing nothing.
  10. Opportunity Sizing and AttractivenessThe most attractive opportunities, their value, timing, accessibility, strategic fit and the criteria used to rank them.
  11. Strategic Implications and RecommendationsWhat the research means for product strategy, portfolio direction, investment, positioning, pricing and GTM, with the recommended next step.
  12. Risks, Constraints and No-Go SignalsThe market, legal, regulatory, commercial, operational or technical risks that could reduce attractiveness, plus signals that should stop or reshape investment.
  13. Evidence, Assumptions and ConfidenceSources, dates, data quality, assumption log, confidence level, triangulation and areas needing further validation.
  14. Ownership and Review CadenceWho owns the report, when it is refreshed, which decisions it informs and how findings are communicated into planning.

What good looks like

A strong Market Research Report lets another product lead understand the issue without a long verbal explanation. Data is interpreted, not just presented, and the reader can see the link between the evidence and the decision it informs. Sources, dates and limitations are stated. A new reader can describe the purpose, understand the recommended next step, see who has approved it and identify what would make the report need updating.

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: Product Discovery Brief for Product Managers

This unblocks: Competitive Analysis for Product Managers · Opportunity Assessment for Product Managers · Business Case for Heads of Product

Prefer to see one finished? Read a complete, cited Market Research Report for Heads of Product example for a early-years edtech product.

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

Frequently asked questions

How is this different from a Business Case?

This report builds the market understanding that comes first; it does not ask for funding. It sizes the opportunity and interprets external conditions so that a later Business Case can make the investment decision on solid evidence.

What makes it a Head of Product's report rather than a team's?

It reads across the portfolio. The findings connect to product strategy, positioning, pricing and go-to-market, and are framed around the strategic and investment decisions leadership needs to make, not a single feature area.

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. Coordinate input from Product Directors, finance, commercial, customer insight and executive sponsors.

How much certainty should it claim?

Only as much as the evidence supports. State the confidence level, log assumptions, show where findings were triangulated and flag the areas needing further validation, so leaders can weigh the market view honestly.

Create this document in Gensudo

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

Get started