The Goal Behind Every Other Goal
If a Product Manager could only optimise for one thing in the early life of a product, it would be Product-Market Fit. Marc Andreessen popularised the term in a 2007 essay, where he wrote that the only thing that matters is getting to product-market fit, and that everything else is secondary. He was largely right. Without product-market fit, no amount of marketing, sales effort, design polish, or feature investment will save a product. With it, almost everything else becomes easier.
Despite its centrality, the concept is regularly misunderstood. Many teams claim product-market fit when they have something less. Some teams have it and do not realise it, leaving growth on the table. Some teams chase it down a path that cannot reach it because the underlying market is not there. Getting the diagnosis right is one of the most important judgments a PM ever makes.
This article is our practical view of what product-market fit actually is, how to know whether you have it, what to do before you have it, and what to do after. It draws on Andreessen, on Sean Ellis's practical work, on Rahul Vohra's structured approach at Superhuman, and on hard-won experience across teams that found it, almost found it, and lost it.
Why It Feels Like a Gradient and Behaves Like a Threshold
One of the most disorienting things about product-market fit is that it feels gradual on the way up and absolute once you have it. Teams typically work for months or years thinking they are getting closer, with metrics improving slowly, and then at some point something shifts. Users start arriving without paid marketing. Support tickets become more about wanting more than complaining about what is broken. Sales conversations get noticeably easier. Internally, the team feels less like they are pushing the product and more like the product is pulling them. Andreessen described this as the difference between push and pull. Before fit, you push: every user is acquired through deliberate effort, every conversion is hard-won. After fit, you pull: word spreads, demand outpaces supply, the company's problem becomes scaling rather than convincing. The transition is rarely a single moment but it is rarely subtle either. People who have lived through it tend to recognise it when they see it again.
The threshold quality is important. Many teams optimise for incremental metrics improvements, expecting that gradual growth in numbers will eventually amount to fit. It often does not. The underlying behaviour either crosses a threshold of love and necessity for users or it does not, and that crossing is what produces the change in trajectory. Pre-fit, growth is often linear and dependent on inputs. Post-fit, growth tends to compound.
Signals That You Have It
There are several signals to look for. None is sufficient on its own. Together, they form the picture.
Quantitative Signals
- Strong organic growth. A meaningful share of new users arrives through word of mouth, referrals, or unaided organic channels. If turning off paid marketing would collapse growth, you do not yet have fit.
- High retention. Users who try the product keep using it. Cohort curves flatten rather than decay to zero. The specific thresholds depend on category, but in consumer software a flattening retention curve above thirty to forty percent at the relevant time horizon is a strong signal.
- Net Promoter Score or equivalent advocacy. Users actively recommend the product. The advocacy is unprompted. They use the product's name in conversations about the broader problem space.
- Decreasing customer acquisition cost over time. As the product's reputation builds, paid acquisition becomes more efficient because more users come pre-warm.
- Revenue or usage growth that is hard to stop. When you try to reduce activity to focus elsewhere, demand persists anyway. The product has its own gravity.
Qualitative Signals
- The Sean Ellis test. When you ask users how would you feel if you could no longer use this product , more than forty percent answer very disappointed . This is a remarkably reliable signal across categories.
• Users describe the product to others using your language. Not because they were
trained to, but because the framing has become the natural way to think about the problem.
- Customer support contacts shift in nature. Less this is broken , more can you add this, can you do that . Users are projecting the product into more of their workflow.
- Sales feels like order-taking. Prospects come in pre-convinced because someone they trust referred them. Closing motion becomes lighter.
- The team can feel it. The mood shifts. People stop asking will this work? and start asking how do we keep up?
Signals That You Do Not Have It (Yet)
It is sometimes easier to identify lack of fit than presence of it. These are the patterns we see most often when teams think they have fit but do not.
- Growth depends on continuous paid acquisition. Stop the spend, growth stops. Word of mouth is minimal.
- Retention curves bleed continuously rather than flattening. Users sign up, try the product for a week or two, and disappear.
- Customers struggle to articulate what the product is for. They use vague language and seem to be guessing at the value.
- Sales requires heavy lift on every deal. Each customer needs to be convinced from cold; nobody is referred in.
- Support tickets are dominated by confusion about basic flows and complaints about what does not work, rather than questions about how to get more out of the product.
- The team is constantly debating new features as the way to fix engagement, rather than refining what already works.
If most of these descriptions match your situation, you do not have fit. The good news is that this is the right diagnosis for most products at most points in their life. Lack of fit is the default state. Fit is the exception that takes deliberate effort to achieve.
How to Find Product-Market Fit
There is no formula. There is a process, and the process is broadly the same across products that have found fit, even though the specifics differ enormously.
Step One: Choose a Specific Customer
Before you can find fit, you must pick which fit you are looking for. Most teams pick too broad a target. Small businesses is not a customer; it is a market segment containing thousands of different sub-segments with different needs. Email marketing managers at e-commerce companies with under fifty employees is a customer. The narrower your target, the easier it is to know whether you have served them well.
Step Two: Identify a Specific Problem
Within the target, find one problem that is significant, frequent, and poorly served by current alternatives. Not three problems. One. Most products that fail do so because they tried to solve many small problems instead of one big one, and ended up doing all of them mediocre.
Step Three: Build Something That Solves It Better
Significantly better, not slightly better. The threshold for users to switch from their current solution to yours is high. They have habits, sunk cost, integrations, and risk aversion. Your product must deliver an order-of-magnitude better experience on the core problem to overcome that inertia.
Step Four: Get It in Front of Users and Watch
Not surveys. Not focus groups. Real users using it in real contexts. Watch what they do, not what they say they will do. Their behaviour is the only evidence that matters. If they use it obsessively and tell others, you are close. If they use it occasionally and forget about it, you are not.
Step Five: Iterate Based on Behaviour
Iterate the product, the target customer, or both, based on what the behaviour shows. Sometimes you keep the customer and change the product. Sometimes you keep the product and change the customer. Sometimes you change both. The discipline is to update based on data, not based on attachment to original ideas.
The Trap of False Positive Fit
Many teams convince themselves they have fit when they do not, usually for one of three reasons:
- 1. Vanity metrics. The team watches signups, page views, or downloads, all of which are easy to inflate without genuine fit. Only behavioural metrics that show retention, advocacy, and organic growth tell the real story.
- 2. Friend-and-family base. Early users are friends, colleagues, or people in the team's network who use the product out of goodwill. Their behaviour does not predict how cold users will behave.
- 3. Subsidised acquisition. Heavy discounts, free trials, or paid placement create usage that disappears the moment the subsidy stops. Real fit shows up in willingness to pay full price after experiencing the product.
What to Do Before You Have It
Pre-fit, the operating principles are different from post-fit. Most teams confuse the two and do post-fit work prematurely.
- Stay small. Fewer engineers, fewer designers, smaller budget. More people make iteration slower, not faster.
- Talk to users constantly. The PM should be in user conversations multiple times per week, not once a quarter.
- Resist scaling activities. Marketing campaigns, sales team builds, partnership pursuits all assume the product is ready to scale. Pre-fit, they waste resources and create commitments that constrain pivots.
- Be willing to throw things away. Pre-fit, the team's attachment to its work is the biggest risk. Half of what you build will be wrong. The teams that find fit are the ones who discard wrong work quickly rather than defending it.
• Watch the qualitative signals more than the quantitative. Numbers are noisy at small
scale. The depth of love or indifference among early users is a better leading indicator.
What to Do After You Have It
Post-fit, the priorities flip. The risk is no longer that you are building the wrong thing. The risk is that you fail to capitalise on the thing you have.
- Scale the engine that produced fit. Sales, marketing, distribution, channels. The fit makes these efforts work; before fit, they were waste.
- Hire ahead of demand. The product will pull harder than you can serve it. If you wait until you are overwhelmed, you are already losing customers.
- Protect the core experience. Many companies lose fit by expanding into adjacent products that dilute the team's focus or by changing the core product in ways the original users dislike.
- Listen for fit erosion. Markets change, competitors arrive, user expectations shift. Fit is not permanent. The same Sean Ellis surveys that helped you measure fit should be run periodically to detect erosion early.
- Plan for the next fit. Most large companies grew by finding multiple fits over time, in adjacent markets or with new products. Once one fit is established and scaling, the cycle of finding the next one begins.
Common Mistakes in the Search
Mistake One: Picking the Wrong Customer
Many teams pick a customer because they understand them well or have access to them, even when those customers do not have the problem the team wants to solve. The result is years of effort for a customer base that does not need the product. Before committing, validate that the chosen customer experiences the problem acutely and frequently enough to justify changing their behaviour.
Mistake Two: Over-Listening to Early Users
Early users have feature requests. Many of them are useful. Many of them, if implemented, will spread the product thin and make it less special, not more. The PM's judgment is essential here. Listen to early users for problems and patterns, not for feature specifications. The shape of the right product is rarely the sum of the requests.
Mistake Three: Confusing Fit With a Working Demo
A demo that gets gasps in a sales meeting does not predict fit. Buyers are evaluating an unfamiliar artefact in a contrived situation; their reaction is shallow. Fit shows up in repeated use over weeks, not in initial reactions over minutes.
Mistake Four: Scaling Marketing Before Fit
When unit economics depend on cold acquisition working, the team is essentially betting that paid channels can substitute for fit. They cannot. Pre-fit marketing scaling produces brief usage spikes followed by churn, with the company's budget burned in the process.
Mistake Five: Declaring Fit Too Early
The team has a few enthusiastic users, organic word of mouth, and celebrates fit. They begin scaling activities and find that the growth was a small initial wave that does not sustain. Better to underclaim fit until the signals are unambiguous than to celebrate early and have to walk it back.
Measuring Fit Rigorously
If you want a single rigorous measurement, run the Sean Ellis survey systematically. Send it to users who have used the product at least twice in the past two weeks. Ask: how would you feel if you could no longer use this product? with options of ' very disappointed , somewhat disappointed , not disappointed , and not applicable .
Calculate the percentage of respondents who answered very disappointed , ignoring those who chose not applicable . Above forty percent is strong fit. Twenty-five to forty percent is approaching fit; significant work is still needed. Below twenty-five percent is no fit. Track this over time. Watch for changes.
Then ask the very-disappointed segment a follow-up: what is the main benefit you get from this product? Their answers, in their words, become your positioning. They are telling you the shape of the fit you have. Use this language in marketing and sales material; it is the message that resonates.
Combine this with retention curves and organic growth share. The three together are far more reliable than any one alone, and they produce both a measurement and a roadmap for what to do next.
A Note on Different Categories
Product-market fit looks different across categories. The underlying principle (genuine pull from a well-defined market) is the same, but the metrics that detect it vary.
Category Strong Fit Signals
Consumer mobile app Daily active to monthly active ratio above thirty percent, organic install
share rising, day-thirty retention above twenty-five percent.
B2B SaaS, mid-market Net revenue retention above one-hundred-twenty percent, customer
acquisition cost payback under twelve months, organic referrals.
B2B SaaS, enterprise Multi-year contracts, expansions inside accounts, named reference
customers willing to advocate publicly.
Marketplace Liquidity in core categories, repeat usage by both sides, declining cost
to acquire each new participant.
Developer tools Adoption by individual developers leading to team and then company
adoption, GitHub stars rising organically, community contributions to the product itself.
A Final Word
Product-market fit is the closest thing to a single goal in early product work. Hit it, and most other things become possible. Miss it, and most other things are unavailable to you, no matter how well executed. The reason it is so important is also the reason it is so hard to fake: it is genuine pull from a real market, and there is no shortcut to producing that pull other than actually doing the work.
If you take only one thing from this article, take this: be honest about whether you have it. Most teams who claim it do not. Most teams who do not claim it could not pass the Sean Ellis test. Run the test, look at the retention curves, listen to the advocacy, and tell yourself the truth. Then either pour resources into scaling what works or pour time into discovering what would actually work. Do not split the difference. The split is where most products quietly die.
Key Takeaways
- Product-market fit is genuine pull from a well-defined market: organic growth, high retention, advocacy, and willingness to pay.
- It feels gradual on approach and threshold-like on arrival. Pre-fit, you push; post-fit, you pull.
- The Sean Ellis test (forty percent or more would be very disappointed without the product) is the single most reliable measurement.
- Pre-fit and post-fit are different operating modes. Scaling activities pre-fit waste resources and constrain pivots.
- Most teams who claim fit do not have it. Be honest about the diagnosis. The penalty for misjudging is enormous.