SABER Product-Market Fit Engine
Segment users, analyze needs, build improvements, and repeat toward product-market fit.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 99%
SABER turns product-market fit into an optimization loop. Survey users after they have experienced the product's core benefit several times, asking how disappointed they would be without it, who benefits most, what benefit matters most, and what should improve. Segment the responses to identify the users who would be very disappointed, then analyze what those users value and which adjacent users could also become highly dependent. Build improvements around the valued core experience rather than trying to satisfy every request. Repeat the survey after each meaningful iteration and track the percentage of users who would be very disappointed. Rahul Vohra uses 40% as the benchmark for initial product-market fit, while scores around 15% to 25% may still offer a viable path through sustained iteration.
Origin
Rahul Vohra developed the engine at Superhuman after searching for an actionable way to show his team how close the company was to product-market fit. It combines Sean Ellis's very-disappointed metric with Superhuman's segmentation and roadmap process.
Core principles
- 01Measure product-market fit through user dependency, not enthusiasm alone.
- 02Survey users only after they have experienced the product's core benefit.
- 03Focus first on the users who would be very disappointed without the product.
- 04Let desired benefits and improvement requests shape the roadmap.
- 05Repeat measurement after each meaningful product iteration.
How to run it
- 1
Survey Experienced Users
Survey users only after they have experienced the product's core benefit two or three times, typically after about two weeks. Ask the four dependency, audience, benefit, and improvement questions.
Pro tip Use a lightweight form that makes free-text responses easy to submit and analyze.
Watch out Surveying users before they experience the core benefit will produce weak or misleading signals.
- 2
Segment the Responses
Separate users by their answer to the dependency question and examine the group that would be very disappointed. Identify which user types appear most often in that group.
Pro tip Use respondents' descriptions of who benefits most to refine the segment in their own language.
Watch out Do not average all users together and assume every segment has equal product potential.
- 3
Analyze the Core Benefit
Determine the main benefit that highly dependent users consistently receive. Compare it with the requests from less-satisfied users to identify improvements that preserve the product's core appeal.
Pro tip Prioritize improvements that help somewhat-disappointed users obtain the benefit already loved by very-disappointed users.
Watch out Blindly implementing every request can dilute the experience that makes the product indispensable.
- 4
Build the Roadmap
Translate the analysis into focused product changes that reinforce the core benefit and remove obstacles for promising adjacent users. Keep the roadmap tied to measurable hypotheses.
Pro tip Choose changes likely to move a defined segment from somewhat disappointed to very disappointed.
Watch out Do not treat the score as a substitute for understanding the qualitative responses behind it.
- 5
Repeat and Recalibrate
Run the survey again after users have experienced the changes. Compare segments and the overall very-disappointed percentage, then begin another SABER cycle.
Pro tip Track cohort and segment changes as well as the headline score.
Watch out A single favorable measurement does not remove the need for continuing retention and growth analysis.
In the wild
After segmenting its users, Superhuman recorded a product-market-fit score in the 15% to 25% range. Rather than launching broadly, the team used survey responses to understand the users who valued the product most, generate its roadmap, and keep iterating toward the 40% benchmark.
→ The company developed a measurable path toward stronger product-market fit while controlling access and preserving product quality.
A hypothetical workflow startup surveys experienced users and discovers that agency project managers are far more dependent on the product than occasional freelancers. Their main benefit is rapid client approval, while their largest obstacle is fragmented feedback. The team prioritizes consolidated approval controls and surveys the next cohort after release.
→ The roadmap targets a specific mechanism that can convert promising users into highly dependent users.
Common mistakes
Surveying Before Users Reach Value
New or inactive users cannot reliably judge whether losing the product would disappoint them. Include people who have completed the core workflow multiple times.
Building for Every Respondent
Treating all feedback equally can weaken the benefit loved by the strongest segment. Use segmentation to determine whose feedback should shape the core roadmap.
Treating 40% as the Whole Business
The benchmark indicates initial product-market fit, not guaranteed success. Runway, team cohesion, execution, retention, and distribution still determine whether the company survives.
Is it for you?
Best for
It is best for startup teams with active users, enough runway to iterate, and uncertainty about which roadmap will deepen product-market fit.
Not ideal for
It is not ideal for products without enough users who have genuinely experienced the core benefit or teams with no capacity to iterate.
From the transcript
“And the four steps that you go through are number one, segment, number two, analyze, number three, build, and number four, repeat.”
“You simply ask your users, how would you feel if you could no longer use the product, and you let them answer either I would…”
“And what he found is that the companies that struggled to grow almost always had less than 40% very disappointed. And the companies that grew…”
From the episode
Superhuman (with CEO Rahul Vohra)
Rahul Vohra