Product Discovery

Product-Market Fit (PMF)

Marc Andreessen famously described product-market fit as 'the only thing that matters' in the early stages of a startup. He was right — and most teams are worse at recognising when they have it, or don't have it, than they think.

What is Product-Market Fit?

Product-market fit (PMF) is the degree to which a product satisfies strong market demand. In practical terms, it's the point at which a meaningful segment of users loves the product enough to keep using it, pay for it, and tell others about it — without being pushed.

The classic description comes from Marc Andreessen: you can feel it when it's happening. Customers are buying as fast as you can make the product. Usage is growing with minimal marketing. Support requests are about edge cases, not core functionality. The company is cash-flow positive before it was supposed to be.

How to Measure Product-Market Fit

Two methods are most widely used:

Sean Ellis test. Survey your active users: "How would you feel if you could no longer use this product?" If 40% or more answer "very disappointed," you're in PMF territory. Below 40%, you're not — and the open-ended follow-ups tell you why.

Retention curves. A product with PMF shows a retention curve that flattens rather than trending to zero. Users keep coming back. The curve never reaches 100%, but if it levels out above a meaningful threshold and holds, that's a strong PMF signal.

Qualitative signals are equally important: unprompted referrals, users who use the product even when it breaks, customers who resist your attempts to raise prices. These are data points that surveys don't capture.

Before and After Product-Market Fit

PMF divides startup life into two fundamentally different modes:

Before PMF: the only goal is to find it. Every other activity — scaling, hiring, optimising — is premature and potentially fatal. Teams should do whatever is necessary: talk to users obsessively, ship fast, kill features that don't work, pivot without ego.

After PMF: the goal shifts to capturing the opportunity as efficiently as possible. This is when scaling sales, investing in marketing, and building operational infrastructure makes sense. Scaling before PMF destroys companies. Scaling after PMF creates them.

Common PMF Mistakes

Confusing activity for fit. High sign-up rates, positive feedback in demo calls, and strong trial engagement can all exist in the absence of genuine PMF. The test is whether users return and stay — not whether they're initially impressed.

Declaring PMF too early. Early adopters are forgiving by nature. Their enthusiasm can create a false sense of fit. True PMF requires validation from users who look like your long-term mainstream customer — not just the most technically sophisticated or change-hungry early adopters.

Thinking PMF is permanent. Markets change, competitors emerge, user expectations evolve. Companies that dominated their category and lost (BlackBerry, Myspace) are evidence that PMF can decay. Continuous listening and product iteration are how you keep it.

Frequently Asked Questions

Is 40% on the Sean Ellis test the definitive threshold?
It's a useful benchmark, not a law. A 38% score in a large market is probably fine; a 52% score in a tiny niche that doesn't scale may not be meaningful. Use the 40% threshold as a directional signal, not an absolute gate.
Can you have PMF in one customer segment but not another?
Absolutely — and this is very common. A product might have strong PMF with solo practitioners and weak PMF with enterprise teams. Segment-level PMF analysis is often more useful than aggregate PMF scoring.
How long does it take to find product-market fit?
It varies enormously. Some products find it in months; many don't find it in years. Research by CB Insights suggests the median time from founding to PMF for successful SaaS startups is 2–3 years. Faster is better — but the more important variable is the quality of learning per iteration, not the calendar time.

Build and validate onboarding around your PMF

Kompassify helps product teams experiment with onboarding flows, measure activation rates, and continuously improve the path to user value — at every stage of product development.

Start for free →