Product-market fit is the moment when that question gets answered. It’s when a specific group of people genuinely needs what you built, uses it repeatedly, and would be noticeably worse off without it.
The problem is that most founders are bad at judging their own progress toward product-market fit. A spike from a Product Hunt launch feels like traction. Encouraging feedback from early users feels like validation. A flattering tweet from someone with 50K followers feels like a signal. But these are vanity metrics, and they’re especially dangerous because they feel real enough to stop you from asking harder questions.
At Solvee, we see this pattern in almost every early-stage founder we work with. They come in with engagement numbers that look decent on the surface, and within a week of actually measuring retention or running a survey, the picture looks completely different. The frameworks below are the same ones we use to cut through the noise.
You need a repeatable product-market fit framework - a structured way to separate signals from flattery. This guide covers five of them. Pick the one that fits where you are right now.
Why Most Founders Get Product-Market Fit Wrong (And How Frameworks Fix It)
Declaring product-market fit too early is one of the most expensive mistakes in the startup playbook, and it’s almost always caused by the same thing: measuring the wrong things.
Total registered users is a vanity metric. App downloads are a vanity metric. Social media impressions, press mentions, waitlist size - all vanity metrics. They trend upward, they feel good, and they tell you almost nothing about whether people find ongoing value in your product.
Think about the apps on your phone right now. How many did you download, open once out of curiosity, and then quietly forget about for the next six months? Those apps technically have “users.” They do not have product-market fit.
A structured product-market fit framework removes emotion from the evaluation. Instead of debating whether the latest batch of feedback was “positive enough,” you look at a product-market fit checklist with binary answers. It tells you whether to keep building or to change direction - and it tells you before you’ve burned through your runway, finding out the hard way.
Framework 1 — The Sean Ellis Test (The 40% Rule)
If you want the fastest, honest signal available, the Sean Ellis test is where to start. The question it asks is deliberately uncomfortable: not “do you like this product?” but “how would you feel if you could no longer use it?”
The product-market fit survey has one core question: “How would you feel if you could no longer use [Product]?”
- Very disappointed
- Somewhat disappointed
- Not disappointed
- I no longer use it
The benchmark for the Sean Ellis test is 40%. If 40% or more of active users choose “very disappointed,” you have a real signal worth building on.
One of the most instructive product-market fit examples of this in practice is Superhuman. When they first ran the Sean Ellis test, they weren’t at 40%. Instead of ignoring the result, they broke down the data: who specifically was in the “very disappointed” group, what those users had in common, and which features they valued most. They doubled down on those features for that specific segment and watched their product-market fit score climb to 58%.
One critical detail: run the Sean Ellis test only on active users - people who’ve used the product at least twice in the past two weeks. Responses from casual or lapsed users introduce noise that can make your product-market fit score look worse than it is, or, occasionally, better than it actually is.
Framework 2 — The Retention Curve (Flattening = PMF)
Surveys tell you what people say. Retention tells you what people actually do. To understand how to measure product-market fit with behavioral data rather than self-reported opinions, cohort retention is the most honest tool available - and one of the core product-market fit metrics worth tracking from day one.
Picture a graph with the Y-axis showing the percentage of users still active and the X-axis showing time since signup. Most early products show a curve that heads steadily toward zero, meaning everyone who tries the product eventually leaves. That’s a retention curve with no floor - and it means you don’t have product-market fit yet, regardless of what your signup numbers look like.
For consumer products, seeing 25-30% of users still active at 90 days is a meaningful foundation. For B2B SaaS, the product-market fit metrics target is higher, and you want that line to stabilize at 40% or above. If the curve never stops declining, acquiring more users won’t fix the underlying problem - it just means you’ll find out the product isn’t working at a larger and more expensive scale.
Framework 3 — The “Pull” Test (Are Users Coming to You?)
This framework is less quantitative than the others. Still, it captures something that the numbers often miss - the overall texture of how the business feels to operate day to day, and whether that texture is changing.
Before product-market fit, everything feels like pushing. You’re doing manual outreach to get a single signup, offering discounts to nudge free users toward a paid plan. Every new user requires deliberate effort on your end to acquire and onboard, and the whole process feels like trying to move something that doesn’t want to move.
After product-market fit, the dynamic starts to reverse. The market begins pulling the product forward rather than you pushing it.
A practical product-market fit checklist for pull signals worth tracking regularly:
- Are more than 30% of new signups coming through organic or word-of-mouth channels?
- Are users asking for new features - meaning they’re actively using what you’ve already built?
- Do users escalate or complain when there’s downtime? Frustration about outages is actually a good sign because it means people depend on you.
- Are people using the product in ways you didn’t design or anticipate?
One of the clearest product-market fit examples of pull working at scale is Slack. There was no massive advertising push in the early days. Teams started using it because it solved the problem of chaotic email threads better than anything else available, and word-of-mouth did most of the growth work from there. The pull was the strategy.
At Solvee, we use a version of this checklist as a gut-check before recommending any paid acquisition investment. If the pull signals aren’t present yet, spending money on ads just surfaces the retention problem faster and more expensively.
Framework 4 — The Unit Economics Test (Would They Pay More?)
Revenue is the most honest signal in any product-market fit framework, because it removes the ambiguity of self-reported surveys and the lag time in retention data. The question this framework really asks is simple: if you raised your price, who would stay?
If you doubled the price and half your users left immediately, your product-market fit might be built on affordability rather than genuine value. If your core users stayed at a higher price point - or if the price increase barely moved your churn rate - you’ve found something people consider a necessity rather than a convenience.
The product-market fit survey can include a pricing section to explore this before making changes: what do users consider a fair price, and at what point would the product become too expensive? This surfaces your value-based price - what people would actually pay if they had to, rather than what they currently pay because it’s easy.
The product-market fit metrics to track here are LTV and CAC. In a business with real product-market fit, LTV should be at least 3x CAC. If you’re spending $100 to acquire a customer who pays you $80 total before churning out, the unit economics are broken - and scaling that model will make the problem significantly larger rather than solving it.
How to measure product-market fit through pricing: Raise your price with the next cohort of new users, then track what happens to conversion and retention over the following 60 days. The response tells you more about perceived value than any survey question can.
Framework 5 — The “One Metric That Matters” Test (Pick Your PMF Signal)
.jpg)
Every business has a different North Star - the single metric that proves a user got genuine value from the product. For a marketplace, it might be the number of transactions completed. For a SaaS tool, it might be the core workflow action that creates the habit of returning. For a subscription business, it’s often net revenue retention.
The job of this PMF framework is to identify that metric first, then use it as the anchor for evaluating everything else.
A final product-market fit checklist to work through before making any serious scaling decisions:
- Sean Ellis Test: Is your product-market fit score at or above 40%?
- Retention: Does your cohort curve flatten and stabilize after 30 days?
- Pull: Is organic growth increasing month-over-month without a corresponding increase in paid spend?
- Unit economics: Is your LTV:CAC ratio above 3x?
- North Star: Is your core value metric growing faster than your overall user count?
Four out of five, and you have a strong product-market fit worth scaling. Two or fewer means more iterations are needed - which is not a failure; it’s just the honest answer at most early stages, and it’s better to know now than six months from now.
How to measure product-market fit is not a one-time exercise you run before a fundraising round. Markets shift, competitors arrive, and the fit that existed six months ago can erode gradually without obvious warning signs. The PMF framework only works if you run it on a regular cadence - not just when growth slows, or an investor asks for the data.
How to measure product-market fit consistently is what turns these frameworks from useful tools into a real feedback system for the business. One of the most common product-market fit examples of this done well is a founder who runs the retention analysis monthly, catches a cohort degradation early, and adjusts the onboarding flow before churn becomes a pattern rather than a data point.
This is why at Solvee we build measurement habits from week one, not as a post-launch audit. By the time most founders realize they don’t have product-market fit, they’ve already spent months building in the wrong direction. The frameworks above give you the early warning system to catch it before it costs you a runway.
