6.4 Product-Market Fit Survey

At a Glance
Other names Sean Ellis Test · PMF Survey
In Brief
The Product-Market Fit Survey is a single multiple-choice question that asks existing users, “How would you feel if you could no longer use this product?” with four answer options ranging from “very disappointed” to “no longer use it.” If 40 percent or more of qualified respondents pick “very disappointed,” that is a strong quantitative signal that the product has found product-market fit for that segment. The output is a percentage score you can track over time, plus follow-up questions that reveal what users value and where the product falls short.
Common Use Case
You have a few hundred active users and your investors are asking whether it is time to spend heavily on marketing. Before committing budget, you want a quick quantitative check on whether your core users truly depend on the product or are casually trying it out.
Helps Answer
- Are enough customers deeply attached to this product to justify scaling?
- Which customer group would miss this product the most?
- What is the single benefit users would not want to live without?
- What is missing for the people who are only somewhat disappointed?
Description
The Product-Market Fit Survey is a single multiple-choice question, sent to people who already use your product, that asks how they would feel if they could no longer use it. The answer options run from “very disappointed” to “I no longer use it.” The headline result is the share of qualified respondents who pick “very disappointed”: if 40 percent or more do, that is a strong signal the product has found product-market fit for the segment you surveyed. A short battery of open-ended follow-ups runs alongside the multiple-choice question so the score comes with the reasons behind it.
The survey turns product-market fit — the otherwise fuzzy sense that you are in a good market with a product that satisfies it — into a number you can track. A high “very disappointed” share is a proxy for the value hypothesis: the assumption that customers will keep using the product because it solves a real problem for them. Below the 40 percent threshold, spending heavily on acquisition tends to be inefficient, because most users would not miss the product if it disappeared; above it, growth efforts are more likely to compound.
The 40 percent figure is a heuristic, not a hard cutoff. Treat the score as a starting point, not a verdict. The real value is in the follow-ups: comparing what “very disappointed” respondents say they value against what “somewhat disappointed” respondents say is missing tells you which segment to build for and what to build next. The “very disappointed” group also defines your high-expectation customer — the segment whose standards you design toward, because meeting them tends to pull the rest of the audience along.
The survey is a leading indicator, not a finish line. Run it on people who have genuinely used the product, re-run it as the product and audience change, and read it alongside retention and engagement data rather than on its own. This page covers the survey itself: how to qualify respondents, run the question, and read the score.
How to
Prep
- Define the user qualification filter. Sean Ellis’s original guidance is to send the survey only to users who have (a) experienced the core of the product, (b) used it at least twice, and (c) used it in the last two weeks. Surveying casual or lapsed users contaminates the score with people who never had a chance to depend on the product. If your analytics platform doesn’t track these conditions, define them as best you can — first-week churn is normal and you don’t want to count it as “not disappointed.”
- Decide standalone or embedded, then pick the channel and tool. A standalone single-question survey (in-app intercept, email link, or a dedicated form) keeps the PMF question uncontaminated by surrounding questions. Embedding it in a longer customer survey is fine if you place the PMF question early. Common channels: in-app prompt, email to active users, in-product chat. Common tools: a free form builder, an in-app survey platform, or a dedicated PMF survey template (see Tools).
- Set a target sample size. Aim for at least 30 qualified responses before treating the score as anything more than directional, and 100+ before treating it as a real signal. Below 30, a handful of answers swings the percentage by 10+ points.
- Draft the follow-up questions. Three follow-ups turn the score from a number into a roadmap: What type of person do you think would benefit most from this product? (a segmentation cue that surfaces your high-expectation customer), What is the main benefit you receive from this product? (the value proposition in your users’ words), and How can we improve this product for you? (the missing-feature gap, especially valuable from “somewhat disappointed” respondents). Add a fourth — Why did you choose that answer? — so you can read the qualitative pattern under the quantitative score.
- Pre-commit to segmentation analysis. Decide before launch which segments you’ll cut by (acquisition channel, plan tier, role, company size, signup cohort). The headline percentage often masks one segment well above 40 percent and another well below — the high-expectation customer segment is typically the one to build for. Choosing the cuts upfront prevents post-hoc data dredging.
Execution
-
Filter the respondent list. Apply the qualification criteria from prep — you want users who have actually used the core product at least twice in the last two weeks. AI-powered customer analytics tools can help identify which users meet the criteria when your database doesn’t have clean behavioral filters.
-
Send the survey. The single quantitative question is:
How would you feel if you could no longer use this product?
- Very disappointed
- Somewhat disappointed
- Not disappointed (it isn’t really that useful)
- N/A — I no longer use the product
Followed by the prep-drafted follow-ups (main benefit, type of person who would benefit most, what’s missing, why this answer).
Send via any of:
- Email link to qualified users
- In-app intercept (survey platform or custom)
- A form-builder link
- A dedicated PMF survey template (see Tools)
-
Run a tight collection window. Two weeks is usually enough — open windows drag and let new behavioral signals contaminate the cohort. Send one reminder; do not send two.
-
Do not coach respondents. If a user replies asking what “very disappointed” means or which option to pick, do not steer the answer. The point is their unprompted reaction. Note the confusion as a signal that the question itself may need a small rewording for your audience, but do not change it mid-collection.
Analysis
If 40 percent or more of qualified respondents picked “very disappointed,” that is the threshold that tends to correlate with a startup able to scale acquisition and grow. Below 40 percent, the product is not yet a “must have” for enough of the surveyed segment, and pouring marketing budget on top is likely to be inefficient.
That percentage is an estimate from a sample, so it carries a margin of error: at around 30 responses the true figure can sit roughly 15 points either side of what you measured, which is why 30 is only directional and 100+ is defensible. Read 38 and 42 percent as the same number, and treat a change between waves as real only when it is larger than that margin rather than ordinary sampling noise.
The headline number is the start of the analysis, not the end:
- Read the qualitative follow-ups by quantitative bucket. Compare the language “very disappointed” users use to describe the main benefit, against the language “somewhat disappointed” users use. The very-disappointed cohort tells you what the product really is in users’ minds; the somewhat-disappointed cohort tells you what’s missing for them to cross over.
- Segment. Cut the score by the segments you pre-committed to in prep. A 28 percent overall score that hides a 55 percent segment is a different problem than a uniform 28 percent — the first calls for narrowing the target customer; the second calls for fundamental product change.
- Identify the high-expectation customer. The segment that scores highest on “very disappointed” is the segment whose expectations you should design for. Building for the median user dilutes the product; building for the high-expectation segment tends to lift the median anyway.
- Plan the next roadmap. A roughly 50/50 split works well: half the roadmap doubling down on the benefits the very-disappointed cohort named, half closing the gaps the somewhat-disappointed cohort named.
- Track over time. Re-run quarterly. Product-market fit is not a single moment but a series of measurements that should hold, and ideally rise, as the product and audience evolve.
Paste the raw responses into an LLM to auto-categorize the open-ended follow-ups and surface the language patterns that distinguish “very disappointed” respondents from “somewhat disappointed” ones. That language analysis directly informs your positioning and marketing copy.
- Order effect If the PMF question sits inside a longer survey, earlier questions can prime the answer. Place this question early or run it as a standalone.
- Threshold worship Forty percent is a heuristic, not a physical constant. Treat 38 percent and 42 percent as the same number; treat the trend across quarters and the segment-level scores as more informative than the headline.
- Selection bias in respondents Users who bother to complete a survey skew positive. If your response rate is under 10 percent, your “very disappointed” share is probably overstated.
- Conversational-AI administration bias Administering the PMF question via a chatbot or conversational AI breaks the standardized format the 40% benchmark was calibrated against; AI-generated preamble or dynamic follow-up questioning shifts how respondents interpret the question, making the resulting score incomparable to the published threshold.
Learn more
Case Studies
Superhuman: PMF engine
Rahul Vohra’s First Round account lifts the Sean Ellis “very disappointed” score from 22% to 33% to 58% via a four-step loop — segment, analyze, split roadmap 50/50, repeat — aimed at a high-expectation-customer persona named “Nicole.”
Further reading
- The Pmarca Guide to Startups, part 4 — Marc Andreessen, 2007
- The Startup Pyramid — Sean Ellis (archived)
- How Superhuman Built an Engine to Find Product/Market Fit — Rahul Vohra, First Round Review 2018
- The Never Ending Road To Product Market Fit — Brian Balfour
- The Lean Product Playbook — Dan Olsen, Wiley 2015
Got something to add? Share with the community.