
You've got 50 active users, your retention looks decent and someone on your team asks the question you've been avoiding: "Do we actually have product-market fit?" Turning that gut feeling into a measurable number requires a specific survey methodology that most founders either skip or run incorrectly.
This guide covers the core product-market fit (PMF) survey question, how to build and segment a full survey and how to connect your score to fundraising readiness.
The product-market fit survey centers on Sean Ellis's framework, known as the "very disappointed" test. The methodology revolves around a single question designed to measure dependency, not satisfaction. How the question works and who should answer it determine whether your score is useful.
The question reads: "How would you feel if you could no longer use [product]?"
Respondents choose from four options: very disappointed, somewhat disappointed, not disappointed or N/A (I no longer use this product). The N/A option filters out inactive users who can't meaningfully evaluate what losing the product would feel like.
You calculate your score by dividing the number of "very disappointed" responses by total qualifying responses, excluding anyone who selected N/A. Companies struggling to grow tend to score below 40 percent, while companies gaining strong traction tend to exceed it. Framing around loss rather than preference often produces more honest responses because people react more strongly to losing something than to rating how much they like it.
Timing and audience selection determine whether your score reflects reality or noise. Respondents should have used your product more than once, experienced the core offering and engaged recently. For software as a service (SaaS) products, restricting the survey to customers who have remained active for a meaningful period generally produces more reliable data.
A commonly used benchmark is that 40 percent or more of active users say they would be "very disappointed" if they could no longer use the product. At around 100 responses, your results are generally more stable and less likely to be overly influenced by a few outliers. If you have fewer than 40 qualifying users, that gap tells you something on its own: focus on acquiring and activating more users before drawing conclusions from survey data.
The core disappointment question produces a single score. Follow up questions tell you what to do with that score. A well designed product-market fit survey doubles as a customer segmentation study, surfacing who your best users are and what stops everyone else from joining them.
Effective follow up questions split into three jobs: defining your ideal customer, identifying your real value proposition and surfacing your highest priority roadmap items. Product-market fit starts with pull from the right users. The survey questions below help you determine whether that pull exists and where it concentrates. Your complete survey, including the core question and all follow ups, should stay short enough that people actually finish it.
These questions work best in a fixed order because each one plays a different part in interpreting the score. Together, they help you connect the headline percentage to positioning, roadmap choices and competitive context. Keep the list tight so respondents finish the survey and so each answer has a clear use.
After the core question, ask these follow up questions sequentially:
That set gives you a workable dataset: who your best users are, what they value, what holds others back and where your competitive position stands. It also keeps the survey tied to decisions you can actually make in positioning, roadmap planning and competitive analysis.
Adding more questions rarely improves the signal. Net Promoter Score and customer satisfaction questions are redundant, as they merely mirror your PMF score without adding new information. "How did you find us?" questions produce unreliable data because users often can't accurately recall their discovery channel.
Frequency of use questions waste respondent attention on data your product analytics should already capture. The goal is a survey short enough that people finish it and structured enough that responses map cleanly to product decisions. Branching logic helps here, since you shouldn't ask users who selected "not disappointed" to explain your value proposition because they don't think you have one.
An aggregate product-market fit score can mislead you. Consider a startup scoring 30 percent overall that might score 55 percent among a specific user type. The aggregate number hides exactly the insight you need most.
Superhuman's approach to measuring product-market fit is a well-documented public case study of this methodology. When founder Rahul Vohra first ran the Ellis survey, the score came in at 22 percent, well below the 40 percent benchmark. After segmenting responses by user persona, the score improved even before product changes shipped. The company then used the survey to focus product work on deepening what its top users already loved and addressing what held "somewhat disappointed" users back.
Segmenting your survey by company size, persona or use case can reveal sharply different scores across groups. An aggregate score may clear the Ellis threshold while still concealing a targeting problem that only appears once you break the data apart. Once you isolate your highest fit segment, the path forward becomes obvious: rebuild acquisition around that group, sharpen positioning toward their language and reorder the roadmap around their unmet needs. The mechanics of cutting customer segments by behavior and attribute are well documented across product analytics work.
This pattern shows up across companies that scaled from a sharply defined early audience. Vercel built deep adoption among frontend developers working with Next.js before expanding into broader web infrastructure, and that early concentration made the survey signal useful. Founders who try to interpret aggregate scores without segmenting often misread the data and end up broadening the product when they should be deepening it.
Each response category in the Ellis survey drives a different part of your product and business decisions. Treating all responses the same collapses the most useful distinctions into a single number. Your "very disappointed" respondents, your "somewhat disappointed" respondents and your indifferent users each guide separate parts of your roadmap. Each group guides a different set of decisions.
The distinctions below are most useful when you review them side by side. They help you decide whose feedback belongs in positioning, whose feedback belongs in the roadmap and whose feedback should not drive core product choices.
Separating your data into these three groups turns a single percentage into a product roadmap, a positioning document and a resource allocation framework. The segmented view also helps you avoid the common mistake of building features for indifferent users at the expense of deepening value for the users who already depend on the product.
The most damaging mistake is surveying the wrong people. Including churned users or signups who never activated can deflate your score by mixing people who self-selected out of your product with people who depend on it. Surveying during onboarding captures reactions to your signup flow, not to the core product itself. Both errors produce data that looks like a product-market fit measurement but answers a completely different question.
The second-most common error is treating the survey as a one-time event. A single score is a snapshot, not a full system for learning. Running the survey repeatedly and comparing the results with product changes makes it a more useful diagnostic tool. 42 percent of startups failed due to a lack of market need, a problem often described as poor product-market fit.
Product-market fit measurement and fundraising readiness connect directly, but the evidence investors expect varies between stages. A score above 40 percent works well in a seed conversation, while Series A investors need that score backed by quantitative business outcomes. Knowing what each stage demands helps you prepare the right data before investor meetings begin.
At seed stage, investors weigh qualitative signals heavily alongside your score. Most seed stage investors look for evidence of market validation alongside early signs of customer pull. Your product-market fit survey score above 40 percent combined with segmentation data showing which user type scores highest gives you a specific story to tell. Verbatim quotes from your top respondents serve double duty: the language they use to describe the problem your product solves becomes your positioning copy and your investor pitch simultaneously. We've seen founders build strong fundraising narratives directly from this qualitative data because it grounds the story in customer language rather than founder assumptions.
Series A evaluation shifts toward quantitative confirmation that the survey signal has translated into business outcomes. Series A benchmarks include meaningful annual recurring revenue (ARR), strong year-over-year growth and solid unit economics. Your product-market fit survey score still contributes to the narrative, but it needs to sit alongside retention cohort data and unit economics. A high PMF score paired with strong retention and revenue momentum makes a compelling case. Founders who can connect these signals to a clear path toward Series A readiness tend to find the right investor partnerships faster.
Product-market fit measurement gives founders a concrete way to replace gut feelings with data and sharpen their focus at each stage. Your score, your segmentation data and your respondents' own words give you the raw material for every product and fundraising decision ahead. If you're an early stage founder looking for a partner who will help you interpret your product-market fit signals and build toward a Series A, reach out to us to see if we'd be a good fit.
Your score needs cautious interpretation in the context of your sample quality and representativeness. At around 100 responses, the data generally becomes more stable, and a small number of outlier answers are less likely to shift a percentage score by double digits. If you have fewer than 40 active users who meet the criteria, treat any results as preliminary and supplement with qualitative interviews.
Yes. Surveying users during their first session or within their first week captures reactions to your onboarding experience, not to the core product. Users need to have completed your core workflow more than once and engaged recently. Sending the survey too early inflates response volume at the cost of data quality.
A score in this range is promising but not yet a clear signal. Your responses need segmenting by user persona, company size and acquisition channel before you draw conclusions because your aggregate is likely masking a higher-fit group. The highest-scoring segment deserves your full focus: rebuild your customer acquisition approach around that group and plan to re-survey after your next meaningful set of product changes.
The 40 percent threshold comes from Sean Ellis and works as a heuristic rather than a hard rule. The benchmark works best as a floor rather than a target, and the direction of your trend across repeated surveys carries as much weight as any single number.