RakshaSix months after launch, your startup has 400 users, a handful of paying customers, and a Slack full of feature requests. The investors are asking the question. The team is asking the question. You’re asking it yourself at 11pm on a Tuesday.
Do we have product-market fit?
The honest answer is that most founders don’t know. Not because the signals aren’t there, but because they’re looking at the wrong numbers, or interpreting the right ones too generously.
Product-market fit is not a feeling. It’s not a milestone you cross. It’s a measurable state where your product is solving a real problem for a defined group of people well enough that they keep using it, tell others, and resist alternatives. This guide covers how to measure it, what the real signals look like, and what to do with your team when you find it.
What product-market fit actually means
Marc Andreessen, who coined the term, described it simply: “Product-market fit means being in a good market with a product that can satisfy that market.”
The operative word is satisfy. Not impress. Not delighted on a demo call. Satisfy consistently at a rate that produces retention and referral.
The definition has two parts that founders routinely collapse into one. The market has to be good: large enough, underserved enough, and accessible enough to build a business on. And the product has to satisfy it: not just solve the problem, but solve it better than the alternatives users have today.
Getting one right without the other is not product-market fit. A strong product in a weak market stalls. A weak product in a strong market gets outcompeted. Both states feel, briefly, like traction.
The Sean Ellis benchmark
The most widely used quantitative test for product-market fit comes from Sean Ellis, who ran growth at Dropbox and Eventbrite before coining the framework.
Ellis’s test asks users one question: “How would you feel if you could no longer use this product?” The response options are: very disappointed, somewhat disappointed, not disappointed, and I already stopped using it.
If 40% or more of your active users answer “very disappointed,” you have a strong signal of product-market fit. Below 40%, you don’t, and the gap tells you roughly how far you are from it.
Superhuman famously used this framework to diagnose which user segments were closest to fit, then focused product development entirely on those users until the 40% threshold was crossed.
Run this survey with users who have been active in the last two weeks. Cold or churned users will skew the result toward disappointment for the wrong reasons.
Retention is the most honest signal
If the Ellis survey is the diagnostic, retention is the proof.
A product with product-market fit retains users at a rate that produces a flattening retention curve. In the first days and weeks after signup, churn is expected. Users are still deciding whether the product earns a place in their workflow. But at some point, the curve flattens. The users who stayed, stayed for good.
If your retention curve doesn’t flatten, it means the product isn’t solving the problem well enough to stick. Every cohort churns to zero eventually, and no amount of acquisition spend fixes a leaking bucket.
Benchmark retention rates vary by product category. For a B2B SaaS tool used daily, week-4 retention above 40% is a reasonable early signal. For a consumer app, Lenny Rachitsky’s benchmark research puts strong day-30 retention at 25% or above for consumer products and 35% or above for B2B.
If your numbers are below those benchmarks, the product is not retaining well enough to call it fit.
Three more metrics that signal product-market fit
Retention is the headline number. These three sit alongside it and together paint a more complete picture.
Net Promoter Score (NPS). Ask users: “On a scale of 0 to 10, how likely are you to recommend this product to a colleague or friend?” Scores of 9 and 10 are promoters. Scores of 0 to 6 are detractors. NPS is promoters minus detractors as a percentage. For a B2B SaaS product, an NPS above 30 is good. Above 50 is strong. Below 0 means more people are actively discouraging use than promoting it.
Organic referral rate. What percentage of new signups come from word of mouth, unprompted? When a product has fit, users recruit other users without being asked. If your referral rate is near zero and every new user comes from paid acquisition or founder outreach, the product isn’t generating enough pull.
Feature adoption depth. Are users discovering and using the core features regularly, or are they signing up, completing one action, and going quiet? Shallow adoption in the core workflow is a sign that the product isn’t solving the problem deeply enough to become habitual.
The qualitative signals matter too
Numbers tell you what is happening. Qualitative signals tell you why.
The clearest qualitative signal of product-market fit is unsolicited urgency. Users emailing before a scheduled downtime asking when the product will be back. Customer success calls where users explain the product to you better than you explained it to them. Support tickets that read like feature requests because the user clearly can’t imagine doing without the product.
The absence of those signals is equally informative. If users respond to a price increase by churning without complaint, the product wasn’t sticky. If no one has asked to refer a colleague, the product isn’t solving a problem worth telling people about.
Run qualitative interviews with your highest-engagement users. Ask them what they were doing before your product, what they’d do if it disappeared, and what they’d tell a colleague when recommending it. Their language will tell you more about your positioning than any survey.
Common false positives
Product-market fit is one of the most frequently misdiagnosed states in early-stage startups. These are the signals that look like fit but aren’t.
Strong demo conversion. Founders are often the best salespeople for their own product. A high demo-to-trial conversion rate says more about your ability to sell the vision than about the product’s ability to retain. Watch what happens after the demo.
Early adopter enthusiasm. The first 50 users of almost any product are unusually forgiving. They tolerate rough edges, fill in gaps with their imagination, and evangelize anyway. Their retention doesn’t predict mainstream retention.
Revenue without retention. Annual contracts paid upfront look like traction. If the users don’t renew, it’s deferred churn. Track usage and engagement from day one, not just contract value.
High engagement from a narrow segment. Ten users who love the product intensely is a signal worth paying attention to, but it’s not fit. It’s a hypothesis about which segment to target next.
What to do before you have fit
The work before product-market fit is different from the work after it. Before fit, almost everything is a hypothesis. The right response to most business questions is “we don’t know yet, here’s how we’ll find out.”
That means:
Talk to users constantly. Not through surveys alone. Direct conversations, screen shares, support calls. The founder who stops talking to users before fit is the founder who ships the wrong thing for six months.
Narrow the target, don’t broaden it. The instinct when traction is weak is to open the aperture. Try more segments, more use cases, more markets. The better instinct is to go narrower. Find the users who are closest to loving the product and build for them until the retention curve flattens.
Iterate on the core workflow, not the features around it. Before fit, most feature requests are noise. The signal is in the core action the product enables. Is it fast enough? Clear enough? Reliable enough? Fix that before adding anything.
Keep the team lean and specialist. Before fit, a small team that can move fast and change direction is worth more than a larger team locked into a roadmap. Bring in specialists for defined pieces of work rather than building a full-time org that’s expensive to restructure.
Twine matches founders with vetted specialists across UI/UX design, software development, and content, project-based, with a matched shortlist in 48 hours. The right team shape for the pre-fit sprint.
What to do when you find it
Product-market fit is not the finish line. It’s the starting gun for a different kind of work.
Before fit, the question is: does this product solve a real problem? After fit, the question is: how do we scale the thing that’s working without breaking it?
That shift changes almost everything about how the team should operate.
Double down on what’s working. Identify the user segment with the highest retention and NPS. Understand exactly what they’re using, how often, and why. Then build more of that, for more people like them.
Invest in the acquisition channels that are already converting. Before fit, you’re testing channels. After fit, you’re scaling the ones that work. Organic referral, content, paid social, outbound: the channel that is already producing your best-retained users is the one worth funding.
Hire to scale, not to explore. Post-fit hiring is about execution capacity, not discovery. You need people who can scale a known system, not people who are best at figuring out what to build.
Build the creative and content function. At scale, brand and content become acquisition channels in their own right. A content specialist, a video editor for ad creative, a designer for growth marketing assets. These roles compound in value the longer they run.
Twine has over 1 million vetted specialists across design, development, video, content, and marketing. Assemble the post-fit growth team on Twine without retainers, without agency markup, and without a six-week recruitment cycle.
The question under the question
When investors ask whether you have product-market fit, they’re asking a narrower question than it sounds. They’re asking: is there evidence that this product creates enough value for a defined group of users that it can build a business?
The answer is in your retention curve, your NPS, your referral rate, and what your highest-engagement users say when you ask what they’d do if the product disappeared.
If those numbers aren’t where they need to be, the work is clear: narrow the target, fix the core workflow, and talk to users until the signal changes.
If they are, the work is also clear: scale what’s working, build the team to support it, and don’t mistake early fit for permanent fit. Markets move. Products have to move with them.
Vicky
Twine