Product-Market Fit Assessment for Product Managers: template, structure and example

A Product Manager's Product-Market Fit Assessment judges whether a product has genuine, durable pull in its market, and recommends whether to scale, improve fit, or rethink. It weighs demand, retention and customer-value evidence, shows the segments where fit holds and where it does not, and separates evidence from opinion so the reader sees how the verdict was reached.

Reviewed by Gensudo Team · Last reviewed 24 July 2026

When to use it

Create it in the Validate phase when you need to decide whether real, repeatable demand exists before committing further investment. Use it when usage, retention and willingness-to-pay signals need to be read together across segments rather than in isolation. It helps senior stakeholders challenge the thinking early, and it sets up the more focused Validation Findings Report that follows.

When not to use it

If you are reporting on a specific validation exercise and the decision it drives, use the Validation Findings Report instead. If the product has no live usage or retention data to assess, earlier discovery and validation work should come first. Do not use this assessment to justify scaling on demand signals you cannot yet evidence.

What you need before you start

Recommended structure, section by section

  1. Summary and VerdictThe product-market fit verdict, the evidence behind it, the segments where it holds, and the recommended scale, improve, or rethink decision.
  2. Purpose and ScopeThe purpose of the assessment, the boundaries and exclusions of its scope, the audience it serves, and the decisions and outcomes it is meant to inform.
  3. Definition of Fit HereWhat product-market fit means specifically for this product and segment, and the bar that defines it.
  4. Demand and Pull SignalsThe signals of genuine demand, such as usage, retention, referral, organic growth, and willingness to pay.
  5. Retention and Engagement EvidenceThe retention, engagement, and repeat-use evidence broken down by cohort, segment, and tenure.
  6. Customer Value EvidenceThe evidence that customers get the value, recognise it, would miss it if gone, and would recommend it.
  7. Segments Where Fit Is StrongestWhere fit is strongest and weakest across segments, use cases, and account sizes, and the reasons behind the differences.
  8. Gaps and Barriers to FitWhat holds fit back, where the product falls short, the barriers to deeper adoption, and the unmet needs.
  9. Risks and AssumptionsThe principal risks to the assessment, the assumptions it depends on, their likelihood and impact, the early-warning signals, and the mitigation or validation each requires.
  10. Evidence and ConfidenceThe evidence base behind the assessment, the quality and recency of its sources, the coverage and consistency it provides, the contradicting signals, and the confidence level in the conclusions.
  11. Recommended Next StepsWhether to scale, improve fit, or rethink, the accountable owner, the conditions, and the next action.
  12. Ownership and ReviewWho owns the assessment, the accountable owners and contributors, where the source evidence lives, the review rhythm and decision rights, and the events that trigger a revisit.

What good looks like

A strong assessment is specific, in plain English, and decision-ready for the Product Manager. The verdict is supported by evidence rather than personal preference, assumptions are explained, agreements are shown, and trade-offs are visible. A new reader can describe the assessment's purpose, understand the recommended next step (scale, improve or rethink), see who has approved it, and identify what would make it 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: Opportunity Assessment for Product Managers · Jobs to Be Done Analysis for Product Managers

This unblocks: Validation Findings Report for Product Managers · Business Case for Heads of Product

Writing one from scratch? Read the step-by-step guide: How to Run a Product-Market Fit Assessment: Steps, Examples and Checklist.

Frequently asked questions

What is the headline decision this assessment produces?

Whether to scale, improve fit, or rethink. The verdict should state the segments where fit holds, the evidence behind it, the accountable owner, the conditions, and the next action, so the reader is left with a clear recommendation.

Why assess fit by segment rather than overall?

Fit is rarely uniform. Breaking demand, retention and value evidence down by cohort, segment and account size shows where it is strongest and weakest, and why. That is what tells you where to scale and where to keep improving.

What evidence best signals genuine fit?

Signals of real pull such as usage, retention, referral, organic growth and willingness to pay, alongside evidence that customers recognise the value, would miss it if it were gone, and would recommend it. Interpret these together, not one in isolation.

How does this relate to the Validation Findings Report?

This assessment reaches a broad verdict on market pull; it precedes the Validation Findings Report, which tests specific questions and records the decision that follows. Together they build the Validate-phase evidence base before you commit significant delivery effort.

Create this document in Gensudo

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

Get started