The 7 Product-Market Fit Survey Questions FitSignal Uses

The short version

A PMF survey score comes from one question:

How would you feel if you could no longer use [product]?

Among eligible respondents who answer Question 1, the percentage selecting "very disappointed" is the disappointment score.

That number cannot explain why people value the product, who gets the most value, what they would use instead, or what holds interested users back. Questions 2 through 7 provide that context. They do not create six additional PMF survey scores.

The seven FitSignal product-market fit survey questions

FitSignal uses fixed, versioned wording so results remain comparable. Replace [product] with the name of the product being measured.

1. How would you feel if you could no longer use [product]?
2. Please help us understand why you selected this answer?
3. What would you use if [product] were no longer available?
4. What is the main benefit you receive from using [product]?
5. What type of person do you think would benefit most from [product]?
6. How can we improve [product] for you?
7. What is your job title?

Question 1: measure disappointment

This is the Sean Ellis question. Respondents choose whether they would be very disappointed, somewhat disappointed, or not disappointed if the product disappeared. Asking about loss separates satisfaction from dependence, although the follow-up answers are still needed to explain that dependence.

The widely used 40% benchmark comes from Sean Ellis's survey work and was later adopted in Superhuman's process. Treat it as directional, not as a law of nature. A score of 39% does not prove that fit is absent, and 41% does not prove that it is secure. The result depends on the cohort, respondent experience, sample size, and response bias.

Question 2: understand the answer behind the score

Question 2 explains why the respondent chose that category. Two people can both choose "somewhat disappointed" for different reasons. One may depend on the core benefit but be blocked by a missing workflow. Another may find the product useful but easy to replace. Their answers should not lead to the same roadmap decision.

Use this response to interpret the rest of the survey. It explains what the respondent believes they would lose and what limits their attachment to the product.

Question 3: surface perceived alternatives

The answer could be another product, a spreadsheet, a manual process, an internal tool, or doing nothing. This is better than forcing respondents to choose from your competitor list because it captures the alternatives they recall in the moment.

Treat those answers as hypotheses, not proof of the competitive set. "No alternative" might indicate an important workflow, poor awareness, or an intention to stop doing the work. Validate repeated patterns through interviews or behavioral evidence before changing positioning or the roadmap.

Question 4: identify the main benefit

Analyze this answer first among respondents who would be very disappointed without the product. Their language shows what the product does unusually well for the people who value it most.

Look for repeated benefits rather than requested features. For example, a hypothetical response such as "I can make a decision without manually sorting every response" describes an outcome. "Great product" does not. Treat recurring benefits as constraints on roadmap changes and as input for positioning.

Question 5: describe who benefits most

People often answer this question by describing someone like themselves. Their wording can expose the role, situation, maturity, constraints, or behavior shared by users who get the strongest value.

Julie Supan's high-expectation customer is the discerning person within a target market who values the product's greatest benefit. Superhuman used this question to help describe that customer. One answer is not enough: look for recurring characteristics among very disappointed users and check whether the group shares the main benefit from Question 4.

Question 6: find the blockers worth addressing

This answer identifies what is holding a respondent back, but it is not a feature ballot. In the Superhuman process, the most relevant answers came from somewhat disappointed users who valued the same main benefit as the very disappointed group.

Feedback from other groups still matters for support, usability, market, and messaging research. Give it different weight when the roadmap question is specifically how to deepen fit for a defined audience.

Question 7: add job-title context

Job title gives you one explicit segmentation field. It lets you compare disappointment, benefits, alternatives, and blockers across roles without inferring every respondent's role from free text.

A title is not a complete persona. The same title can mean different things across company sizes and industries, so combine it with product behavior and the respondent's own description of who benefits most. An overall score can hide stronger and weaker role segments.

Why some product-market fit surveys use four questions

The historical Superhuman survey used four questions:

1. How would you feel if you could no longer use Superhuman?
2. What type of people do you think would most benefit from Superhuman?
3. What is the main benefit you receive from Superhuman?
4. How can we improve Superhuman for you?

That four-question survey extended Sean Ellis's single scoring question into a process that could inform segmentation and roadmap decisions.

FitSignal's current survey keeps those functions and adds three forms of context:

• why the respondent selected their disappointment answer
• what they would use as an alternative
• their job title

The four-question version is historically valid, but it is not FitSignal's current survey.

Who should receive the survey

Do not send the survey to every account ever created.

Survey people who have had enough exposure to understand the product's core value. The exact eligibility rule depends on the product, but it should be defined before results arrive. Useful criteria may include:

• completion of the core workflow
• a minimum period since activation
• recent meaningful activity
• exclusion of test accounts, employees, and respondents without real usage

Avoid changing the eligibility rule whenever the score is uncomfortable. That makes trend data harder to interpret and creates an easy path to selecting only favorable users.

Use newly eligible cohorts for remeasurement rather than repeatedly asking the same people. Keep the eligibility definition stable enough that changes in the score are more likely to reflect the product or market, not a different respondent mix.

How many responses do you need?

There is no universal minimum that makes a PMF survey score "valid."

A smaller sample can still produce useful qualitative themes, especially when the same benefit or blocker appears repeatedly. But the percentage itself will be uncertain.

For example, if 16 of 40 respondents select "very disappointed," the observed score is 40%. An idealized Wilson 95% interval is approximately 26.3% to 55.4%, before selection and nonresponse bias. The interval cannot correct an unrepresentative respondent pool.

Report the respondent count beside the score. When decisions are consequential, also report an uncertainty interval and the relevant cohort or segment. Do not compare a small specialist segment with a broad mixed audience as if the percentages carried the same meaning.

How to turn the seven answers into a roadmap

Use the responses in this order:

1. Preserve the baseline. Record the product version, field dates, eligibility rule, invited and respondent counts, response rate, missingness, raw numerator and denominator, survey wording, delivery channel, segment rules, and known limitations. Report raw and segmented scores side by side with their sample sizes.
2. Compare justified segments such as job title, use case, activation state, or company stage. State segment overlap and keep the raw score visible. Treat a post-hoc lift as a hypothesis to validate in a fresh cohort, not as proof that the product improved.
3. Name what the strongest users value by analyzing Question 4 within the very disappointed group. Group responses into benefits and preserve representative customer language. Cross-check Question 5 and Question 7 to understand who repeatedly receives that benefit.
4. Find aligned blockers among somewhat disappointed respondents who value the same main benefit. Analyze Question 6 for repeated blockers. Use Question 2 to understand why the blocker matters and Question 3 to see what users would do instead.
5. Choose a focused change that protects the core benefit, removes an important repeated blocker, and serves the target segment. Separate it from requests that would pull the product toward a different audience or value proposition.
6. Measure a fresh eligible cohort after shipping. Examine the score, segment mix, main-benefit themes, and blocker themes together. A score can move because the product changed, the audience changed, or both.
7. Triangulate before making a PMF claim. Compare the survey with completion of the core workflow, repeat use and retention, payment or renewal, organic pull, acquisition repeatability, and economics. The survey measures attitudinal necessity; it does not establish product-market fit by itself.

Keep the seven questions in the wording shown above. If you change one, version the survey and record the change rather than treating the old and new responses as automatically comparable.