Product-Market Fit Assessment

Evaluate PMF using multiple frameworks

analysisadvancedSean Ellis TestRetention AnalysisNorth Star Metric1600-2200 words
Customize Your Prompt
Fill in the variables to generate your personalized prompt
Preview
See how your prompt will look with the current variables
You are a Senior Product Manager assessing product-market fit for [Product Description] with metrics: [Current Metrics (Optional)]

Conduct PMF assessment:

## 1. SEAN ELLIS TEST
### Survey Question: "How would you feel if you could no longer use [product]?"
Survey heuristic, to assess alongside behavior:
- Very disappointed: 40% or more meets the Sean Ellis heuristic; it does not prove PMF
- Somewhat disappointed: [%]
- Not disappointed: [%]

### Analysis:
- Use actual survey responses; do not infer a disappointment score from unrelated metrics
- Segments showing strongest attachment
- Reasons for disappointment/attachment

## 2. RETENTION ANALYSIS
### Cohort Retention Curves
- Day 1: [%] (benchmark: [industry standard])
- Day 7: [%] (benchmark: [industry standard])
- Day 30: [%] (benchmark: [industry standard])
- Day 90: [%] (benchmark: [industry standard])

### Retention Quality:
- Flattening point: [When curve stabilizes]
- Power user threshold: [Usage frequency]
- Natural frequency: [Expected usage pattern]

## 3. GROWTH INDICATORS
### Organic Growth Signals:
- Word of mouth coefficient: [>1 indicates viral growth]
- Organic vs paid acquisition: [Ratio]
- User-generated content: [Volume and sentiment]
- Community engagement: [Metrics]

### Economic Signals:
- CAC Payback: [Months]
- LTV/CAC Ratio: [X:1]
- Gross margins: [%]
- Pricing power: [Evidence]

## 4. QUALITATIVE SIGNALS
- **Strong PMF Indicators:**
- [Signal 1: e.g., Users hack together solutions]
- [Signal 2: e.g., Strong emotional response to downtime]

**Weak PMF Indicators:**
- [Signal 1: e.g., Low engagement after signup]
- [Signal 2: e.g., Feature requests all over the map]

## 5. MARKET RESPONSE
### Demand Indicators:
- Sales cycle length: [Trend]
- Win rate: [%]
- Competitive wins: [Frequency]
- Inbound interest: [Volume]

### Customer Feedback:
- NPS score: [X], with respondent count and survey context; no universal NPS cutoff establishes PMF
- Support ticket sentiment: [Positive/Negative]
- Feature request patterns: [Focused/Scattered]

## 6. PMF SCORE CALCULATION
| Dimension | Weight | Score (1-10) | Weighted |
|-----------|--------|--------------|----------|
| Retention | 30%    | [X]          | [X]      |
| Growth    | 25%    | [X]          | [X]      |
| Economics | 20%    | [X]          | [X]      |
| Satisfaction | 25% | [X]          | [X]      |
| **Total** | 100%   |              | **[X/10]** |

**Assessment:** [Evidence for fit, concerns, and unknowns]. The custom weighted score organizes the discussion; it has no validated PMF cutoff.

## 7. PATH TO (STRONGER) PMF
### If No PMF:
1. **Pivot considerations:** [What to change]
2. **Segment focus:** [Narrow target market]
3. **Core value prop:** [What to strengthen]

### If Approaching PMF:
1. **Double down:** [What's working]
2. **Fix blockers:** [What's preventing adoption]
3. **Expand carefully:** [Next segments]

### If Strong PMF:
1. **Scale triggers:** [When to accelerate]
2. **Market expansion:** [Adjacent opportunities]
3. **Defensive moats:** [How to maintain advantage]

Provide specific, actionable recommendations based on PMF status.

## Web research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Web research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.
What Makes a Good PMF Assessment
  • • Review survey results, retention, and economics, including where the signals disagree.
  • • Cohorts over averages: flattening point, natural usage frequency, and where the curve actually stabilizes.
  • • Segment truth: PMF can be strong for one segment and weak elsewhere—say it out loud.
  • • Metrics with baselines: payback, LTV/CAC, win rate, and pipeline quality.
  • • A clear “what now”: if no PMF, narrow; if close, fix blockers; if strong, scale with guardrails.
Common PMF Assessment Mistakes
  • • Declaring PMF on top‑line growth while cohorts quietly decay.
  • • Using averages that hide power users vs. tourists; segment or you’ll fool yourself.
  • • Surveying only happy users; selection bias turns everything into a victory lap.
  • • Hand‑waving economics: “We’ll make it up in volume” is not a plan.
  • • An assessment without a decision or a plan to resolve uncertainty.
Questions PMs Actually Ask (PMF Assessment)

What’s the quickest sanity check for PMF?

Review the Sean Ellis survey, cohort retention, and unit economics together. The 40% very-disappointed threshold is a heuristic, not proof of fit. Match retention windows and payback expectations to your product. See the Superhuman founder’s account for an example of the survey approach.

Our top‑line is growing fast. Is that PMF?

Growth can come from acquisition even when retention is weak. Compare cohorts and acquisition sources before drawing a conclusion about fit.

How do I run the Sean Ellis survey without bias?

Define eligible users before sampling, seek responses beyond your strongest advocates, and report the response count. Add a follow-up asking why and compare segments.

What’s a good Day‑30 retention number?

Use the product’s natural usage frequency and a clearly defined cohort. Day-30 retention for a daily product is not directly comparable with a weekly or occasional-use product.

Our NPS is 60 but retention stinks. What gives?

An NPS of 60 and weak retention can coexist. Check who answered the survey, when they answered, and whether their subsequent behavior matches the score.

What economics scream “not ready to scale”?

Review payback against available cash, retention trends, discounting, and dependence on a few large accounts. A single threshold cannot determine readiness to scale.

Do I need PMF for every segment?

You can start with one segment where the evidence for value and retention is strong. Report its results separately instead of assuming they apply to every segment.

What if we’re “close” to PMF—what’s the play?

Identify the gaps in activation or repeat use and test focused changes. Expand to other segments when the evidence supports doing so.

Executive wants to scale now. Should we?

Show the survey results, retention cohorts, unit economics, and remaining uncertainty. Compare the risks of scaling with the evidence that further research or product work could provide.

How do we present PMF credibly without a 40‑slide deck?

One‑pager: survey result + why, cohort chart with flattening point, 3 economics bullets, and a call—no PMF/approaching/strong—with 3 concrete next steps, owners, dates. That’s it.

How to use this prompt

When to use it

Evaluating readiness to scale

Before you use the output

  • •Fill in the variables with the facts and constraints you have.
  • •Check the output against your source material and revise any mistakes.
  • •Enable web search where available and check the dates and sources it returns.

Expected output

PMF assessment with recommendations

Quick Info
Categoryanalysis
Output Length1600-2200 words
Web SearchSupported
Frameworks
Sean Ellis TestRetention AnalysisNorth Star Metric
Try PM Toolkit Calculators

Use the calculators to check the numbers behind a proposed product decision.