Use Rahul Vohra's Superhuman PMF Engine. (1) Survey active users with the Sean Ellis question 'how would you feel if you could no longer use this?'. (2) Segment respondents by 'very disappointed' / 'somewhat disappointed' / 'not disappointed'. (3) Profile your fans (the very disappointed) to find your real ICP. (4) Build a roadmap that's half doubling-down on what fans love and half closing the on-the-fence blockers. (5) Re-run quarterly. The score should rise.
The fast version
PMF doesn’t appear by accident. It appears by running the Superhuman PMF Engine, a four-step quarterly loop:
- Survey active users with one question: “How would you feel if you could no longer use this product?” Three options: very disappointed / somewhat disappointed / not disappointed.
- Segment respondents. The “very disappointed” are your fans (your real ICP). The “somewhat disappointed” are the conversion opportunity. The “not disappointed” are not your customer; ignore them.
- Profile your fans. What do they have in common? Industry, role, team size, use case? That’s your real ICP, narrower than your stated one.
- Build the half-and-half roadmap. Roughly 50% of engineering effort on deepening features your fans already love (you ask them: “what’s the main benefit?”). Roughly 50% on closing the on-the-fence blockers (you ask them: “what would you need to upgrade to ‘very disappointed’?”).
Re-run quarterly. The percentage of active users who answer “very disappointed” is your PMF score. 40%+ is the rough heuristic for likely PMF.
Why “very disappointed” beats every other PMF metric
NPS asks would-you-recommend. People can recommend a product they barely use. They cannot honestly say they would be very disappointed to lose a product they don’t depend on. The Sean Ellis question demands the user has integrated the product into a workflow they would mourn losing. That’s a structurally stronger signal than recommendation.
This is also why the PMF score is harder to game. You can manufacture an NPS spike with a great support interaction. You cannot manufacture “very disappointed” without actually being load-bearing in the user’s day.
Common mistakes
1. Surveying the wrong audience. Active users only. Not signups, not trialists, not churned users. Active = completed the core product action in the last 14-28 days.
2. Treating 40% as binary. It’s a directional heuristic. Movement matters more than the absolute number.
3. Optimizing for the not-disappointed group. They are not your customer. Building for them dilutes the experience for your fans and lowers your overall score.
4. Running the survey once. Quarterly cadence or you cannot tell whether you are getting closer to PMF or further.
5. Confusing PMF score with NPS. Different questions, different signals. Use both, but don’t substitute.
How ShipFit relates
ShipFit’s 9-step playbook is structured to maximize the probability of finding PMF before you commit engineering resources. Stages 1-4 identify a buyer segment with a real, painful problem and a defensible angle. Stages 5-7 scope the smallest product that could plausibly hit PMF for that segment. Stages 8-9 take the validated package and ship it.
After launch, the Superhuman PMF Engine is the canonical measurement loop. ShipFit’s stage 7 (Will They Pay?) gives you the pre-launch behavioral evidence that increases your PMF odds; the engine itself runs after you have 40+ active users.
Further reading
- The Superhuman PMF Engine framework, full breakdown of the loop.
- What is product-market fit?, the wider definition + why most claimed PMF is wishful thinking.
- Rahul Vohra’s First Round Review article (2018), the source.
Related
Superhuman PMF Engine
Rahul Vohra's framework for measuring and engineering product-market fit. The 40% rule, the high-expectations customer, and the four-step loop to actually move the score.
The Lean Startup
Eric Ries's Lean Startup, stripped of consultant fluff. Validated learning, Build-Measure-Learn, MVP, pivot or persevere. What it means and where it gets misapplied.
Idea Validation
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Product-Market Fit
The state in which a product satisfies a strong market demand such that demand pulls the product through the company. Coined by Marc Andreessen in 2007. Most rigorous measure: 40%+ of active users would be 'very disappointed' to lose the product (Sean Ellis test).
Frequently asked questions
How long does it take to find PMF?
Can I find PMF before launch?
What if my PMF score is below 40%?
Should I survey churned users too?
Is hitting 40% enough?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
Rahul Vohra's framework for measuring and engineering product-market fit. The 40% rule, the high-expectations customer, and the four-step loop to actually move the score.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.
Does each customer make you money? Or cost you money?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.
If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.