Why Every Other PMF Metric Fails
Your app has 100K MAU. Your engagement is 30%. Your retention curve flattens week-three. You're fundraising, and your deck looks impressive.
None of this tells you if users actually need you.
Paul Graham wrote: "Do things that don't scale." What he meant: talk to ten users who depend on you instead of ten thousand who tolerate you. The 40% rule operationalizes that insight.
Sean Ellis, who scaled Dropbox and Eventbrite, ran experiments on growing products. He asked a single question to users who'd spent time with the product: "How would you feel if you could no longer use this product?"
Responses: Very disappointed. Somewhat disappointed. Not disappointed. Neutral.
Products with 40%+ "very disappointed" responses had predictable viral growth. Products below 20% flattened despite marketing spend. The correlation was mechanical.
Why 40%? Because it signals you're solving a problem so acute that the absence of your solution creates genuine pain. Not inconvenience. Pain.
The Measurement Framework
This is where most founders fail. They run the test once, celebrate or despair, and move on.
Do this instead:
Timing is Everything. Run the question at the point where users have formed a habit: typically week 2-4. First-week answers reflect novelty, not dependency. If you run on day one, you're measuring excitement, not PMF.
Sample Size Discipline. Ellis tested 40-50 weekly active users per cohort. Not hundreds. Not thousands. You need enough depth to detect patterns, not enough to hide signal in noise. Indian founders often ask 500 people and assume statistical rigor. You don't need that. You need honest answers from power users.
Segment by Acquisition Channel. Paid users report differently than organic. Enterprise buyers differ from SMBs. Cohort your responses by how they found you. You might have 42% PMF in SMB but 18% in free tier. That's actionable—it tells you where to double down.
Track Over 12 Weeks Minimum. One measurement is noise. Monthly tracking over three months reveals whether you're climbing or declining. Scott Belsky calls this "the messy middle"—the grinding phase where you're testing, learning, and iterating. Your 40% number will jump around. That's normal. Look for direction.
How to Actually Ask
The question sounds simple. Execution matters.
Use one sentence, not a survey. Surveys introduce bias and friction. In-app tooltip. Exit email. Direct Slack message. The medium that gets fastest, most honest response wins.
Offer four explicit options:
- Very disappointed
- Somewhat disappointed
- Not disappointed
- It doesn't matter to me
Don't ask yes/no. Don't ask if they'd recommend it. Neither correlates with PMF. The disappointment question directly measures whether absence hurts.
Follow up with one open-ended question. "What would you miss most?" One sentence answer. This is where you find your moat. If 40% say they'd miss your specific feature and nothing else comes close, you know your north star.
What Ellis's Data Actually Showed
Dropbox hit 40%+ "very disappointed" at month 2.
Groups of products plateaued at 15-20% and couldn't scale past it.
But here's the non-obvious insight: products that hit 40% didn't suddenly succeed. They already had product-market fit traction for 3-4 months. The 40% rule didn't create PMF. It validated PMF that already existed.
This changes how you interpret your own number. If you're at 12%, it's not a signal to pivot. It's a signal to keep iterating on core value prop. If you're at 32% and staying flat, your retention mechanics are broken. Fix those before building features.
For Indian Founders Specifically
B2B SaaS founders in India consistently hit 40%+ faster than global peers. Why? Acute pain. A 50-person fintech startup using your automation tool doesn't have alternatives. They're very disappointed without you by week one.
Consumer app founders typically bottom out at 25-30% even with 100K users. This doesn't mean failure. It means you're solving a convenience problem, not a necessity. Your path to scale is different: unit economics, retention mechanics, viral loops. The 40% rule isn't a ceiling—it's a diagnostic.
The mistake: comparing your B2C number to a B2B benchmark and panicking.
The Actionable Framework
1. Run the test this week. Pick 50 weekly active users. Ask the one-sentence question.
2. Segment responses. Organic vs. paid. Early adopters vs. later adopters. Geography if relevant.
3. Interview the 40%. Not a survey. A call. "What would you miss?" Get specific.
4. Track monthly. Plot it. Is it rising, flat, or declining? Direction matters more than absolute number.
5. Fix before pivoting. If you're at 22%, iterate. Tweak onboarding. Remove friction. Don't jump to new product.
The Final Truth
The 40% rule cuts through noise because it measures something binary: does the user fundamentally depend on you?
Not like you. Depend on you.
That distinction is everything.
Most startups die measuring MAU and retention curves. A few survive because they obsessed over whether users would genuinely suffer without them.
Measure the right thing. Everything else follows.