NPS tells you how users feel about you. The disappointment survey tells you whether they would miss you if you disappeared. Different questions, different uses, and most NPS tools do not compute a product-market fit score even though they can ask the question. This is the difference, the overlap, and why running both is usually worth it.

Plenty of teams start with NPS because it is the metric a board or an investor asked for. It answers a real question, but it is not the question of whether the market needs you. That is when adding a disappointment survey starts to pay off.

Quick Answer: What Is the Difference Between PMF and NPS?

The disappointment survey asks whether your product is a need or a nice-to-have, using Sean Ellis's question "How would you feel if you could no longer use [product]?", with 40% "very disappointed" as the benchmark to aim for. NPS measures how the relationship is going on a 0 to 10 scale using "How likely are you to recommend [product] to a friend?", tracked over time. The rough division: the disappointment survey asks whether people would miss you, and NPS asks how the relationship is going. Neither one settles anything on its own.

What NPS Actually Measures

NPS was created by Fred Reichheld at Bain & Company in 2003. One question, one number:

"How likely are you to recommend [product] to a friend or colleague?" (0 to 10)

Scores of 9 or 10 are promoters. Scores of 7 or 8 are passives. Scores of 0 to 6 are detractors. Your NPS is the percentage of promoters minus the percentage of detractors, yielding a number between -100 and +100.

What NPS is good at:

Tracking customer sentiment over time
Flagging drops that correlate with product or support issues
Comparing against industry benchmarks
Driving customer success workflows (follow up with detractors, get referrals from promoters)

What NPS is not good at:

Telling you whether you have product-market fit
Distinguishing "loyal but replaceable" from "would miss deeply"
Predicting retention at the pre-PMF stage
Giving you a clear go/no-go signal on whether the product is worth building more of

What PMF Actually Measures

The score comes from Sean Ellis, who ran early growth at Dropbox and was on the founding team of LogMeIn, and who published the survey in 2009. One question, one percentage:

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

Very disappointed

Somewhat disappointed

Not disappointed (it isn't really that useful)

N/A, I no longer use it

Your score is the percentage of respondents who say "very disappointed." The 40% benchmark comes from Sean Ellis, who arrived at it by comparing results across nearly 100 startups and described the line itself as "a bit arbitrary." The pattern he reported is asymmetric: companies that struggled were always below it, while most with strong traction were above it. Treat it as the target to aim for rather than a line that certifies anything.

What PMF is good at:

Telling you whether your product is a need versus a nice-to-have
Informing decisions about whether to scale, raise, or narrow your focus
Identifying which user segments have fit even when overall does not
Focusing your roadmap on the users who would actually miss you

What PMF is not good at:

Continuous sentiment tracking
Industry benchmarking (PMF data is sparsely published)
Predicting short-term churn from passive unhappiness
Measuring support or UX quality directly

The Core Difference in One Sentence

NPS asks "How do you feel about the product you already have?" PMF asks "Is this product a need or a nice-to-have?"

Those sound similar. They are not. A user can rate you 10 on NPS (they love recommending you) and still say they would be "not disappointed" if you disappeared, because a competitor is one click away. Conversely, a user who rates you 6 on NPS (too buggy, too expensive, frustrating UX) can absolutely say they would be "very disappointed" without you, because the core thing you do is irreplaceable for them.

The first user is loyal but replaceable. The second is grumpy but hooked. PMF catches the second. NPS does not.

Two Examples That Make This Concrete

Example 1: SaaS With NPS 60 But PMF 22% (Loyal But Replaceable)

Take a hypothetical project management tool. Suppose NPS is 60, genuinely high. Users like the interface, the onboarding is smooth, support responds in under an hour. They would recommend it to a friend.

But when you ask "how would you feel if this product disappeared," only 22% say "very disappointed." The rest say "somewhat disappointed" or "not disappointed," because Notion, Asana, Linear, Trello, and five more tools do roughly the same thing. The switching cost is low. The loyalty is real but shallow.

This is where NPS alone can mislead you. You look at 60 and conclude the product is in good shape. It may well be. But the survey is telling you that most of these users have alternatives they would be comfortable moving to, which is worth knowing before you spend heavily on acquisition.

Example 2: SaaS With NPS 35 But PMF 52% (Polarizing But Essential)

Now flip it. Take a hypothetical compliance tool for indie SaaS founders dealing with EU VAT. Suppose NPS is 35. Users complain about the UI, the dashboard is ugly, some workflows are clunky.

But 52% say they would be "very disappointed" if the product disappeared. Because no one else solves this specific problem at this price point. The alternative is spending $400/month on a tax accountant or getting it wrong and paying penalties.

This is where NPS alone also misleads you. You look at 35 and think you are failing. You are not. You have strong product-market fit with a polarizing user experience, which is a fixable problem. If you only measured NPS, you would be tempted to rebuild the UI. If you measured PMF, you would realize the UI is fine enough, and you should invest in widening the wedge.

Why Most NPS Tools Cannot Measure PMF (Even Though They Look Like They Could)

Both surveys are single-question tools sent to users. Both produce a number. Both claim to measure "customer love." So can any survey tool run either?

Technically yes. Practically no.

An NPS tool can build the Sean Ellis question as a custom survey. What it cannot do:

Calculate the PMF score automatically. NPS tools calculate promoters-minus-detractors. They do not understand "very disappointed = positive signal." You end up calculating PMF in a spreadsheet.
Segment by high expectation customer. Julie Supan originated that framework and Rahul Vohra applied it to survey data at Superhuman. It depends on reading the main-benefit and who-benefits-most answers within your very-disappointed group, which NPS tools are not built to do.
Track your score against the 40% benchmark. NPS tools chart a trend line for a different metric on a different scale. They will not show you your disappointment percentage against the line you are aiming for, or the confidence around it.
Support the two-lane roadmap. Splitting effort between deepening what your core loves and removing what blocks the almost-convinced requires reporting on what each group actually wrote. That is a different report from a promoter breakdown.

Delighted, which shut down on June 30, 2026, was a common example. It could run the Sean Ellis question, but the product was primarily built around NPS workflows. Teams using it for PMF still had to treat PMF as a custom measurement workflow.

When to Use Each

Use NPS when

You already have confirmed PMF and are optimizing customer experience
Your business model relies on referrals (consumer apps, freemium SaaS)
You need continuous sentiment tracking, not a gate
Investors or boards require NPS specifically
You have a customer success team that acts on per-response feedback

Use PMF when

You are pre-PMF and need to know if you should keep building
You are early-PMF and trying to strengthen it
You are deciding between product iterations and need user-value signal
You are picking which segment to double down on (PMF by segment is often revealing)
You want a retention leading indicator rather than a sentiment lagging one

Use both when

You have enough users to get a readable response count and you intend to act on what comes back
You want both the current-state thermometer (NPS) and the depth-of-need gate (PMF)
You want to catch the "loyal but replaceable" and "grumpy but hooked" cases above
You have investors asking about NPS but know PMF is the number that actually predicts your business

Most indie developers benefit from running both from the start. They are not expensive, they are not redundant, and together they tell a complete story that neither one tells alone.

How to Run Both Without Doubling Your Survey Load

The mistake is sending two separate surveys to the same users every month. Survey fatigue kills response rates.

Better approach:

Send the disappointment survey to users with enough experience to have an opinion. How often to repeat it depends on how often people actually use your product. A first reading is a state, not a baseline, so decide deliberately whether a later reading is measuring newly eligible users or re-asking the same ones, and keep that choice stable.
Send the NPS survey on a trigger: after a completed onboarding, after 30 days of activity, after hitting a key feature usage milestone. That gives you continuous sentiment data without hammering users.
Ask the same "what is the main benefit" open-ended follow-up on both. Over time, the qualitative responses converge and tell you which value props are loadbearing for retention versus which just drive recommendations.

Done this way, a given user sees the disappointment survey rarely and the NPS survey on specific triggers, which keeps the total number of interruptions low.

PMF and NPS in the Same Tool

Historically you needed two tools. NPS specialists (SatisMeter, Delighted) were strong on NPS but weak on PMF. PMF measurement was usually a custom setup in Typeform or Google Forms, which meant manual segmentation and no integration.

That is why FitSignal was built. The disappointment survey is the primary object: the score is computed against the 40% line with its trend, distribution and a stated confidence level, and the free-text answers are broken down by persona and segment. Licensed NPS surveys run in the same account, on the same customers and personas, and are included in every plan.

If you already run NPS elsewhere and want to add a disappointment survey, FitSignal's free plan collects 250 responses a month through an in-app widget or a share link, which is enough to get a real reading without changing your existing setup.

Best For / Not Best For

This article is best for: Indie developers, early-stage SaaS founders, and growth-stage PMs who run NPS (or are about to) and want to understand what they are missing. Also useful for anyone confused by the "NPS is dead" vs "NPS is gospel" debate. Both camps are wrong because they are pointing at the wrong metric.

This article is not best for: Large enterprise ops teams with established NPS programs running through CX platforms (the tool switch cost outweighs the tooling gains), or consumer apps where referral loops are the whole business (NPS alone is probably the right call for you).

Bottom Line

These are not competing metrics. NPS gives you an ongoing read on the relationship. The disappointment survey tells you whether people would feel the loss. Without the first you miss emerging quality problems. Without the second you can spend heavily acquiring users who are comfortable leaving.

Run both, send NPS on triggers, and pay attention when the two disagree. The disagreements are usually where the useful product insight sits.

If you want both in one place, FitSignal runs them on the same customers and personas, with licensed NPS included in every plan. Or keep your existing NPS setup and add the disappointment survey alongside it. What matters is having both readings, not where they live.