Product-Market Fit: How to Know If You Have It
Product-market fit is the most important milestone a startup can reach and the most poorly understood. Here is what it actually means, how to measure it, and what to do when you do not have it yet.
Marc Andreessen, who coined the term in its modern form, described product-market fit in one of the bluntest ways anyone ever has: you can always feel when you do not have it. Customers are not getting value from the product. Word of mouth is not spreading. Reviews are lukewarm. Sales cycles drag on. And you can feel when you do have it: customers are buying as fast as you can sell to them, usage grows of its own momentum, and journalists start writing about you without being asked.
That description is memorable, but it is not particularly useful if you are trying to figure out where you currently stand. The feeling Andreessen describes — the obvious, undeniable pull of a product the market genuinely wants — is real, but most teams experience something far murkier. Some customers love the product. Others churn quickly. Usage grows slowly and unevenly. You are not sure whether to keep building in the same direction or to change something fundamental.
That murky middle ground is where most early-stage companies live, and it is where clear thinking about product-market fit matters most.
What the term actually means
Product-market fit is the degree to which a product satisfies strong market demand. That sounds almost tautological, but unpacking each word reveals what founders often miss.
Product is not just the software or the service. It includes the price, the onboarding experience, the support, the positioning, the packaging — everything a customer encounters when they engage with what you sell. A technically excellent product with confusing pricing and poor onboarding may have a product-market fit problem that has nothing to do with the core technology.
Market is not everyone who could theoretically benefit from your product. It is the specific segment of people or organizations who have the problem you solve acutely enough to pay for a solution, who can actually reach your product, and who have the budget to afford it. The market that matters is almost always much narrower than founders initially assume. Trying to find fit with "small businesses" is too broad to be useful. Finding fit with "10–50 person ecommerce businesses in Southeast Asia that process more than 500 orders a month and are using Shopify" is specific enough to actually test.
Fit means the product and market reinforce each other. Customers use it because it solves a real problem well, and that usage generates the kind of organic growth — word of mouth, referrals, case studies, inbound interest — that does not require you to force it into existence through sheer marketing spend.
You do not achieve product-market fit. You discover it. And you discover it through contact with real customers, not through reasoning about what they ought to want.
Where you might be right now
Product-market fit is not binary. It is better understood as a spectrum, and knowing where you sit on it shapes the decisions you should be making.
No fit
High churn, low engagement, customers do not understand the value proposition
Weak fit
Some customers love it, most do not. Engagement is inconsistent. Growing slowly
Approaching fit
A clear segment gets real value. Retention improving. Some organic growth emerging
Strong fit
Retention is high, growth is largely organic, customers advocate unprompted
Most teams in the early stages oscillate between weak fit and approaching fit without realizing it. They have enthusiastic customers — which feels like fit — but they also have high churn among a broader population, which is the market telling them something important. The enthusiastic customers are a signal. The churned customers are an equally important signal that often gets ignored because it is uncomfortable to examine.
The signals that tell you whether you have it
Since product-market fit resists easy definition, it is worth being concrete about the signals that indicate its presence or absence. These are not perfect indicators — context matters enormously — but taken together they paint a clear picture.
Signals you have it
- Customers use the product without being prompted
- Churn is low and declining over time
- New customers arrive through referrals
- Sales cycles are shortening
- Customers push back when you raise prices
- You struggle to keep up with inbound demand
- Customers use the product in ways you did not anticipate
Signals you lack it
- Usage drops off sharply after onboarding
- Customers say they like it but do not return
- You rely heavily on sales effort to grow
- Feedback is vague or contradictory
- High churn, especially in months 2–4
- Customers struggle to explain what the product does
- Revenue comes from discounts and special deals
The most telling signal of all is retention. A product that people keep using, month after month, without being incentivized or reminded to do so, is solving a real problem in a way they find genuinely valuable. A product that people try and abandon — even if they describe it positively in conversation — has not yet found fit. What customers say and what they do are frequently different things. Behavior is the more honest signal.
How to measure it: the Sean Ellis test
In 2010, Sean Ellis — who had led growth at Dropbox, LogMeIn, and several other early-stage companies — proposed a simple survey question that has since become one of the most widely used early indicators of product-market fit. It asks one thing: how would you feel if you could no longer use this product?
The 40% threshold is a heuristic, not a law. It emerged from Ellis's observation across dozens of early-stage companies, and subsequent research has broadly supported it as a useful signal — though the exact number varies by industry and business model. What makes the question powerful is not the score itself but what it forces you to confront: do enough customers consider your product genuinely irreplaceable, or merely useful?
There is an important caveat about who you survey. Send this question only to customers who have used the product at least a few times over the past few weeks — people who have had enough experience to form a genuine view. Sending it to trial users who signed up last week and barely opened the product will produce misleadingly low scores. Sending it only to your most engaged power users will produce misleadingly high ones. The right sample is active, recent users who are neither brand new nor outliers in their engagement.
Retention curves: the most honest signal
If you have quantitative data on your product, retention curves are the single most reliable indicator of product-market fit. A retention curve plots the percentage of users who are still active at each point in time after they first signed up.
A retention curve that trends toward zero — where almost nobody is still active after twelve weeks — tells you clearly that people are not finding enough ongoing value to keep returning. A curve that drops initially but then flattens and stabilises at some level — even if that level is modest — tells you that a portion of your users have found genuine value and are staying. That flat portion is your core. Understanding who those people are, what they use the product for, and what distinguishes them from those who churned is one of the most important research exercises an early-stage team can undertake.
Finding product-market fit is fundamentally a research and coordination problem. You need to run customer interviews, track what you hear, spot patterns across conversations, and translate those patterns into product decisions — all while keeping the rest of the business running. In FabricLoop, teams building toward PMF often use a dedicated group to centralise this work: interview notes, insight threads, a Kanban board tracking what the team is testing and why, and a running document of what they believe to be true about their customer. When the whole team can see the research, the product decisions that follow from it make more sense to everyone.
The most common reasons teams miss fit
After watching many early-stage companies navigate this, the failure modes cluster into a few recurring patterns. They are worth naming plainly.
Building for the wrong customer. The product solves a real problem, but not for the customer the team originally envisioned. A tool built for enterprise procurement teams turns out to be loved by operations managers at mid-size companies. A consumer app gains traction not with young professionals but with small business owners. Teams that notice this early and deliberately shift their focus to the segment that is actually responding well move toward fit much faster than those who insist on the original vision.
Solving a problem people have but do not prioritize. This is subtler. Customers acknowledge the problem is real, they express genuine interest, they might even sign up for a trial — but when it comes to actually integrating a new tool into their workflow and paying for it month after month, they do not. The problem exists but it is not acute enough to displace their current behavior. Finding fit usually requires solving a problem that causes enough daily pain that customers are actively looking for a solution rather than merely open to one.
Mistaking politeness for enthusiasm. Customers — particularly in cultures where direct negative feedback is uncomfortable — are often much more positive in conversation than their behavior suggests. Someone who says "this is really interesting, I'd definitely use this" in a product interview and then never logs in again is not endorsing your product; they are being polite. The only reliable way to weight customer feedback is to triangulate it against actual usage data. What people do is the signal. What they say is context for interpreting it.
Raising a large round and hiring aggressively before you have found product-market fit is one of the most reliable ways to destroy a startup. You hire salespeople who cannot sell because the product is not ready. You hire marketers who cannot generate sustainable demand because the retention is not there. You burn cash solving a distribution problem when the real problem is the product. Find fit first. Scale after.
When to pivot and when to persist
If the signals clearly indicate you do not have fit, the question becomes: what do you change? There is a spectrum between small iterations — adjusting onboarding, repositioning for a different customer segment, changing the pricing — and full pivots, where you fundamentally change what the product does or who it is for. Deciding which end of that spectrum to act on is one of the hardest calls in early-stage building.
| Signal | What it suggests |
|---|---|
| Some customers love it but they are a small, specific segment | Narrow your focus to that segment. Double down on them, not on the broader market you originally targeted. |
| Customers use it once then do not return | Likely an onboarding or habit formation problem. Improve the path to the first moment of value. |
| Customers like it but say the price is too high | Either wrong market (they cannot afford it) or wrong value articulation (they do not see enough benefit). Test both. |
| Nobody is really enthusiastic — responses are uniformly lukewarm | The problem you are solving may not be acute enough. Consider whether the core premise needs to change. |
| Customers use it, but not for what you intended | Pay very close attention. This is often where fit is hiding. Follow the actual use case, not the original vision. |
| Sales require enormous effort and heavy discounting | Value proposition is unclear or unconvincing at the current price point. Rethink positioning before hiring more salespeople. |
The general principle is: before changing the product, make sure you understand why customers behave as they do. A pivot made without that understanding is just a guess dressed up as strategy. The teams that find fit fastest are typically those that talk to customers relentlessly, pay close attention to what they observe rather than what they hope to find, and are willing to serve a much narrower market than they originally imagined.
What happens after you find it
Finding product-market fit changes the problems worth solving, but it does not make the work easier — it just makes it different. Before fit, the question is whether you have something the market wants. After fit, the question is how to scale what is working without breaking it. That transition introduces its own challenges: hiring quickly without diluting the culture that made the product good, managing the operational complexity that comes with rapid growth, and staying close to customers even as the distance between founders and users increases.
It is also worth saying that product-market fit is not permanent. Markets shift. Competitors emerge. Customer expectations evolve. Companies that achieved strong fit in one era — with one version of their product, for one configuration of the market — have to find it again as circumstances change. Treating fit as a destination you reach once and then hold forever is a category error. The work of staying close to what customers actually need is ongoing, not a phase you eventually graduate from.
The teams that sustain product-market fit over time are usually the ones that have built organizational habits around staying close to customers — not just a quarterly survey or an annual review, but ongoing conversations, visible research, and product decisions that are clearly traceable back to what real customers said and did. FabricLoop is built around the idea that work and context should stay connected. When customer research lives in the same place as the tasks it generates and the discussions it starts, those habits become easier to sustain as a team grows.