Product-market fit: how to know when you've found it
How to recognise product-market fit: which signals count, how to measure retention and demand, what the Sean Ellis test tells you and when to scale up.
In short: You have product-market fit when a clearly defined group of users uses your product regularly, would miss it and brings others to it without constant pushing from you. The most reliable sign is a retention curve that flattens at a stable level after the initial drop. Surveys such as the Sean Ellis test and qualitative interviews add to that data, but they do not replace it.
What product-market fit means
The term was popularised by investor Marc Andreessen. It describes the state in which a product has found a market that really wants it. Before that point everything feels like hard work: every customer has to be convinced individually, users try the product and do not come back. After it, the market pulls: enquiries arrive on their own, customers recommend the product, and the team struggles to keep up with support and development.
Product-market fit is not a one-off event. It applies to a specific audience with a specific problem. When you enter new markets or customer segments, you have to find it there again.
The most reliable signals
Retention that levels off
Look at cohorts: all users who started in a given week are tracked together. How many are still active after one, four and twelve weeks? For almost every product the curve drops at first. What matters is whether it eventually flattens. A curve that keeps sliding towards zero shows the product is not essential to anyone over time. A curve that settles at a stable level shows a core of users who get real value.
What "active" means depends on the product. For accounting software it is monthly use, for a messaging app it is daily use. Choose the action that reflects the core benefit instead of just counting logins.
The Sean Ellis test
Growth adviser Sean Ellis proposed a simple question: "How would you feel if you could no longer use this product?" with the answers "very disappointed", "somewhat disappointed" and "not disappointed". As a rule of thumb, Ellis suggested that around 40 percent of active users surveyed should answer "very disappointed". The threshold is a heuristic from experience, not a law of nature. The follow-up questions are often worth more than the number: who answers "very disappointed", and which benefit do those people name?
Demand that arrives on its own
Watch where new customers come from. If a growing share arrives through referrals, word of mouth or people searching for your name directly, that is a strong signal. So is a shorter sales conversation, because prospects already know the problem and have asked for you. With B2B products, fit often shows in customers renewing without long negotiations and adding further departments.
Typical signs you are not there yet
- Growth comes almost entirely from paid advertising and stops when the budget does.
- Users praise the product in interviews but barely use it afterwards.
- Every customer wants something different, and the roadmap is a list of individual requests.
- You keep explaining what the product is actually good for.
None of these is a reason to give up. They show that the audience, problem or solution needs sharpening. We describe how to gather feedback systematically in user feedback loops: building products users actually love.
What this means for the technology
Before product-market fit, learning speed is what counts. A lean MVP that is easy to change is worth more than a perfect architecture for users who do not exist yet. Deliberate technical debt is often sensible at this stage. Our post on technical debt in startups explains when to pay it down.
After fit, the focus shifts. Now it pays to invest in stability, scalability, testing and monitoring, because outages affect more people. Our post on MVP vs. full product covers when to make that move.
Frequently asked questions (FAQ)
How long does it take to find product-market fit?
There is no general answer. Some products find it after a few iterations, others only after a significant change of audience. What matters is how fast you learn: short cycles of shipping, measuring and adjusting shorten the search.
How many users do I need to measure it?
For cohort analysis you need enough users per cohort that individual outliers do not distort the picture. In the early phase, in-depth conversations with a few well-chosen users often tell you more than statistics. As numbers grow, the weight shifts towards the data.
Does this apply to internal software too?
In principle, yes. An internal tool can also miss the actual need. The questions are the same: do employees use it voluntarily, would they miss it, and do other departments ask for it? If people keep maintaining spreadsheets in parallel, that is a clear warning sign.
Conclusion
Product-market fit shows up in your users' behaviour first and in revenue later. Measure retention by cohort, listen to the users who would miss the product most and align your technical investment with the phase you are in. If you want to build an MVP quickly and develop it further based on real feedback, we can help with web application development.
Related posts
- MVP development: from idea to launch in 8 weeks
How to build an MVP in about eight weeks: set the scope, test a prototype, build, launch. With a week-by-week plan, a sensible tech stack and the usual mistakes.
- How to validate your startup idea before writing code
How to validate a startup or product idea without code: customer interviews, landing pages, fake door tests, concierge MVPs and pre-sales. Plus notes on GDPR.
- MVP vs. Full Product: When to Scale Your Development
How to tell your MVP is ready to grow into a full product: real usage signals, technical limits, common mistakes and a step-by-step path to scaling up.
- Technical Debt in Startups: When to Pay It Down
Technical debt in startups: which shortcuts are fine, how to spot the dangerous kind, and when paying it down is worth more than shipping new features.