Methodology · 6 min read

Sean Ellis 40% Test (PMF Survey)

A segment-level signal of product-market fit.

Sean Ellis and Morgan Brown · View sources ↓

At a glance

Use this when
You need to assess how strongly a customer segment depends on your product.
What you will work towards
A segment-level signal of product-market fit.
Bring to the reading
A specific decision from your work and the customer evidence you have so far.

What it is

The Sean Ellis Test, also called the 40% test or the PMF survey, is a single-question survey that gives an early, standardised read on product-market fit. Active users are asked one question: "How would you feel if you could no longer use [product]?", with four fixed answers: Very disappointed, Somewhat disappointed, Not disappointed, and N/A (no longer use it). Sean Ellis, founder of GrowthHackers and Qualaroo, first published the test on his startup-marketing blog around 2009-2010 and later documented it fully in Sean Ellis & Morgan Brown, Hacking Growth (2017); across dozens of startups he advised, he found that products crossing roughly 40% "Very disappointed" tended to have found genuine product-market fit and could sustain aggressive growth spend, while products below that threshold burned growth budget on a leaky bucket no amount of distribution could fix. The test is product-owned in the sense that matters most: product management runs the survey, decides what a "Very disappointed" result implies for the roadmap, and owns the underlying go or no-go call on scaling growth investment. PMM's role is narrower and explicitly supporting, in the same way this knowledge base scopes MEDDIC/MEDDPICC to a sales-owned discipline: PMM contributes segment-level survey design so the result can be cut by the same personas STP already defined, then translates whatever the segmented result says into positioning and messaging decisions, not into product bets.

When to use it

  • Product leadership is deciding whether to shift from "find fit" to "scale growth spend". An external, standardised benchmark beats an internal gut check on whether the underlying product can support the growth a scaling plan assumes.
  • Usage metrics look reasonable but growth spend is not compounding. The team suspects the constraint is fit, not distribution, and wants a fast, cheap read before diagnosing further.
  • Customers describe the product as merely "convenient" rather than essential. Recurring soft language like this in sales calls or reviews is a flag that a formal PMF read is overdue, not just a messaging problem.
  • You are about to write growth-stage messaging (a T2D3-style scaling plan, a new paid-channel commitment) and want confirmation the product itself, not just the current message, will support the growth those plans assume.
  • A repositioning or new-segment launch has just gone live. An early, low-cost PMF read on the new segment catches a fit problem before a full messaging or GTM budget is committed to it.

How to run it

  1. Recruit from active users only, never free-trial signups or one-time visitors. Product typically defines "active" as having used a core feature within the last two weeks; surveying a lapsed or one-time user about disappointment produces a meaningless answer that drags the topline number down for the wrong reason.
  2. Send the single question with the four standard answers, plus one open-ended "why do you feel that way?" follow-up and a persona or segment identifier field. Keep the survey to that; adding more questions produces fatigue without improving the result, and the segment field is what lets PMM cut the data usefully afterwards.
  3. Collect at least 30 to 40 responses per segment before drawing any conclusion. A handful of responses from one vocal segment can distort the topline percentage badly, especially in an early-stage product with a small active-user base.
  4. Calculate the Very-disappointed percentage overall and, separately, by segment. A product can sit below 40% in aggregate while one specific segment sits comfortably above it, and that segment-level cut is almost always the more actionable finding than the blended number.
  5. Read the open-ended responses from the Very-disappointed group closely. The specific, unprompted language customers use about what they would miss is genuine PMM raw material, even though the go or no-go verdict itself stays product's call.
  6. Hand the segmented result and the raw quotes to product. Product owns the interpretation and the resulting roadmap or growth-investment decision; PMM's role stops at translating a Very-disappointed segment's language into that segment's positioning and messaging.
  7. Re-run on a cadence rather than treating one reading as permanent. Product-market fit moves as the market, competitors, and the product itself change, so a score from eighteen months ago tells you little about today.

Cadence & ownership

Product management owns the survey instrument, the go or no-go interpretation of the result, and any resulting roadmap decision; this stays explicitly outside PMM's remit, mirroring the "PMM's supporting role" framing this knowledge base already applies to MEDDIC/MEDDPICC. PMM's scope is limited to contributing the segment or persona field on the survey so results align to STP's segments, reading the qualitative "why" responses for messaging language, and translating a segment's Very-disappointed result into that segment's positioning, without owning the underlying PMF verdict. Run the survey every two quarters as a standing check once a product has a meaningful active-user base, and treat a major repositioning, a new-segment launch, or a significant feature release as an automatic trigger for an off-cycle run, in addition to the standing cadence.

Example

Fictional field-service scheduling SaaS Fieldloop ran the 40% test eighteen months after launch, surveying 340 active users across its two segments: solo contractors and small field-service teams of 5 to 20 people. The aggregate Very-disappointed score came back at 34%, below the 40% benchmark, and the initial instinct from leadership was to pull back growth spend across the board. Cutting the result by segment told a different story: solo contractors scored only 22% Very disappointed, while small teams scored 51%, comfortably above the benchmark. Reading the qualitative responses from the small-team segment, PMM found the same unprompted phrase recurring: "I'd go back to double-booking jobs by accident", a specific, vivid pain the existing "all-in-one scheduling" positioning never named directly. Product used the segmented result to redirect the next two quarters of roadmap investment toward the small-team segment rather than pausing growth spend entirely, while PMM rewrote that segment's homepage messaging around the double-booking pain and deliberately deprioritised further messaging investment in the weaker solo-contractor segment. Re-run two quarters later, the small-team segment's score held at 54%, and its self-serve trial-to-paid conversion rose from 11% to 17%, which the team read as the new messaging compounding a fit that was already real, rather than manufacturing fit that had not existed.

Pitfalls

  • Surveying all users instead of only active ones. Including lapsed trial users or one-time visitors drags the Very-disappointed percentage down for reasons that have nothing to do with whether the product has found fit with the people who actually use it. Recovery: define "active" concretely (a specific feature used within a specific recent window) before a single survey goes out, and exclude anyone who does not meet it.
  • Reading the aggregate score and stopping there. A blended score across two very different segments can sit just below 40% while masking one segment well above it and another nowhere close, leading leadership to the wrong company-wide decision. Recovery: always cut the result by the segments STP already defined before anyone acts on the topline number.
  • PMM treating the result as a mandate to redesign the product. Because the survey feels like a marketing instrument, being a single easy-to-run question, PMM sometimes over-reaches into interpreting what the score means for the roadmap, which is product's call, not PMM's. Recovery: keep the deliverable to a segmented score, the raw qualitative quotes, and a messaging recommendation; hand the go or no-go verdict to product explicitly, the same boundary this knowledge base draws around MEDDIC/MEDDPICC.

How the ideas connect

Choose where to go next

Make it useful

Bring it back to your work.

Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.

Check your understanding

Practise applying Sean Ellis 40% Test (PMF Survey) in five short scenarios.

5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.

Sources

  • Sean Ellis & Morgan Brown, Hacking Growth (2017), Chapter 2, which documents the test and the roughly 40% "very disappointed" benchmark drawn from Ellis's work advising dozens of startups.

← All entries in Market & Customer Understanding · Try the category quiz