Product-market fit is not a feeling you confirm in a board meeting — it is a sequence of measurable thresholds you either clear or fail. For early-stage SaaS, the practical answer is a three-stage validation process: first confirm problem-solution fit with the Sean Ellis survey (40% of users "very disappointed" without your product), then validate engagement with leading behavioral indicators, and finally confirm business viability with lagging metrics such as a 3:1 LTV:CAC ratio and a flattening retention curve. Each stage gates the next, so you learn exactly where your product is weak — sentiment, engagement, or unit economics — before you spend on scaling.
Beyond Intuition: The Need for Data-Driven PMF
Most teams that believe they have product-market fit have only reached problem-solution fit, and the difference matters because fit is a spectrum rather than a switch: you can have strong fit in one segment and none in another. That warning comes from Sara Detrik's SaaS PMF guide, which argues that no single metric is definitive and that the Sean Ellis threshold, retention curves, and organic referrals each tell part of the story.
Heap's framing reinforces the same point from a different angle: PMF is not a static condition but "the iterative process of adapting to customer needs as they evolve." In other words, even a validated fit can decay — feature bloat, moving upmarket too fast, and losing touch with core users erode what you have built, so measurement must be permanent, not a one-time gate. The framework below turns that philosophy into an ordered set of checks, moving deliberately from qualitative signals to quantitative benchmarks so that each stage produces evidence the next stage can build on.
