Is Major Cooked? Free AI risk score + roast for your college major
Solo Era solo activities, solo maxxing, sidequests, challenge
Keepsake Project Management, Freelancers, DesignersProduct market fit: what it means and how to measure it
Product market fit means being in a good market with a product that can satisfy that market. Marc Andreessen coined the framing in a 2007 essay. For a small app you can measure it with the Sean Ellis survey: ask active users how they would feel if they could no longer use the product, and check whether at least 40% answer “very disappointed”. Forty respondents is enough to see a direction.
What is product market fit?
Most explanations of product market fit quote the same line. It comes from Marc Andreessen’s June 2007 essay The only thing that matters, and it reads: “Product/market fit means being in a good market with a product that can satisfy that market.” Two things are packed into that sentence. There has to be a market, meaning a group of people who really have the problem. And the product has to be good enough for that group to use it.
The essay’s argument is that of the three things a startup is made of (team, product and market), the market matters most. In a great market, he writes, the market pulls the product out of the startup. The product does not need to be great, it just has to basically work. In a bad market, no team and no product rescues you. That is useful for anyone building alone: before you polish anything, check that enough people want the thing.
Andreessen also describes what it feels like. When fit is missing, customers are not quite getting value, word of mouth is not spreading, and usage is not growing fast. When it is present, customers buy as fast as you can make the product, or usage grows as fast as you can add servers. That description is vivid, but it is a trailing signal. By the time you feel it, you already have fit. The rest of this page is about earlier, smaller signals you can check as a solo builder.
What are the signs of product market fit?
No single number proves fit. Look for several signals pointing the same way, and be honest about which ones come from strangers and which come from people who feel obliged to be kind. The table pairs each signal with what it looks like in a small app, and the weak version of the same signal.
| Signal | Strong version | Weak version |
|---|---|---|
| Repeat use | The same people come back without a reminder, week after week | A burst of visits in the first two days after launch |
| Word of mouth | Strangers arrive saying a specific person sent them | Friends share it once because you asked |
| Disappointment if it vanished | Users say they would be annoyed or stuck without it | Users say it is “nice” or “interesting” |
| Unprompted requests | Users email asking for a feature or a bigger plan | Users only answer when you message them first |
| Willingness to pay | A stranger pays without a discount or a long conversation | Verbal “I would pay for that” |
| Who the users are | A recognisable group (same job, same situation) dominates the active users | A scatter of unrelated people, each using it for something different |
Repeat use is the signal most builders can read directly. Plot, for each week you launched, how many of that week’s new users were still active in later weeks. If the line drops and then flattens above zero, some people have made the product part of their routine. If it keeps sliding to zero, you have visitors, not users. Many founders treat a flattening retention curve as the earliest hint of fit, though how high it must flatten depends on the kind of product.
Willingness to pay is the hardest to fake. If your product is free, a small paid tier, even a modest one, tells you more than a hundred nice replies. The guide to pricing a micro SaaS covers how to test it.
What is the Sean Ellis product market fit test?
Sean Ellis, author of Hacking Growth, looked for a leading indicator of fit. His idea: ask users one question, “How would you feel if you could no longer use this product?”, with three answers: very disappointed, somewhat disappointed, not disappointed. Then count the share who say “very disappointed”.
The benchmark is 40%. Rahul Vohra, founder of the email app Superhuman, explains in First Round Review that Ellis benchmarked nearly a hundred startups with this survey. Companies that struggled to find growth almost always had fewer than 40% of users answer “very disappointed”. Companies with strong traction almost always exceeded it. The 40% line is a rule of thumb drawn from that comparison, not a law, and it is a signal about your current users rather than a guarantee of future growth.
Two published examples show how the number behaves. According to the same article, Hiten Shah asked Ellis’s question of 731 Slack users in a 2015 open research project, and 51% said they would be very disappointed without it. Superhuman’s first survey produced 22%, so by that measure it had not yet reached fit. After Vohra’s team narrowed its audience to the people who loved the product and rebuilt the roadmap around them, the score reached 58% within three quarters. The lesson is that a low first score is a starting point, not a verdict.
How do you measure product market fit for a small app?
You do not need a data team. You need a list of people who have really used the product and a four-question form. These steps follow the approach Vohra describes, scaled down for a solo project.
- Pick who to ask. Include only people who have experienced the core of the product. Vohra, following Ellis’s advice, polled users who had used it at least twice in the previous two weeks. Do not send it to every sign-up, since people who never got going cannot tell you what they would miss.
- Send the four questions. Use any form tool, or plain email. Keep the order below, with the disappointment question first so later questions do not bias it.
- Wait for about 40 answers. Vohra notes that results become directionally correct around 40 respondents, which is fewer than most people expect. With fewer users than that, treat the survey as a structured interview and talk to every person who answers.
- Compute one number. Divide the people who chose “very disappointed” by everyone who answered the first question.
- Read the “very disappointed” answers separately. What they say is the main benefit (question 3) and who they are (question 2) is your real product and your real market. The others are noise until you have found the first group.
1. How would you feel if you could no longer use [product name]? ( ) Very disappointed ( ) Somewhat disappointed ( ) Not disappointed 2. What type of person do you think would benefit most from [product name]? 3. What is the main benefit you get from [product name]? 4. How could we improve [product name] for you?
| Answer | People | Share |
|---|---|---|
| Very disappointed | 14 | 30% |
| Somewhat disappointed | 19 | 41% |
| Not disappointed | 13 | 28% |
These numbers are an illustration, not a real product. Fourteen of 46 is about 30%, under the 40% line. The next move is not to add features for everyone. It is to read the 14 answers to question 3, find the benefit most of them name, and check what the 19 “somewhat disappointed” users say is missing. Vohra’s method splits the next roadmap roughly in half: one part doubles down on what the happy group loves, the other part removes what holds the in-between group back. Then you run the survey again.
If you cannot yet reach 40 users, you can still use the question in interviews. Ask it out loud after someone has used the product for a week, and write down the exact words they use for the benefit. Those words are also your best landing page copy.
How do you test for fit before you build anything?
The survey needs users, so it cannot help on day one. Before anything exists, you are testing the market half of the sentence: do enough people have this problem, and do they already do something about it? The cheapest checks are conversations and a page that describes the outcome. The guide to validating an app idea lays out a week of such checks, and the free Validate App Idea planner turns your idea into interview questions.
Once you have a first version, keep it small. The MVP guide explains why the first release exists to produce evidence, not to impress. MVP examples show how others kept theirs minimal, and the scoping guide helps you cut the build to one workflow.
If you are still looking for something worth testing, browse the ideas posted on the board. Each has a ready-made build prompt, so you can have a rough version in front of ten people quickly.
What mistakes do people make when measuring fit?
- Asking the wrong people. Friends, family and people who signed up but never used the product will skew the result in both directions.
- Reading a launch spike as fit. A day on a launch directory brings traffic. The question is who is still there a month later.
- Chasing the average. Building for every respondent produces a product no group loves. Pick the group that already does.
- Surveying too early. With five users, a percentage means nothing. Interview them instead.
- Treating 40% as a finish line. Fit in one small segment does not mean the market is big. It tells you the segment is worth serving; how many such people exist is a separate question.
- Confusing fit with a paying customer base. You can have users who love a free tool and still lack a business. Test the price separately.
What should you do once you see signs of fit?
Do not rush to scale. First write down who the product is for and what the main benefit is, using the words your happiest users used. Then work out how to reach more of exactly those people. A narrow, repeatable channel beats a broad one. The guide to launching without an audience and the guide to marketing an app cover the next step.
If you decide the idea is not for you to pursue, that is also a result. You can post it on the submit page for a builder who sees what you do not, and move on to the next one.
Frequently asked questions
What is product market fit in simple terms?
Product market fit means a real group of people wants your product enough to keep using it and to be upset if it went away. Marc Andreessen’s 2007 wording is being in a good market with a product that can satisfy that market. In practice you see steady repeat use and referrals you did not ask for.
What is the Sean Ellis 40% rule?
The Sean Ellis rule says a product likely has fit when at least 40% of surveyed users say they would be “very disappointed” if they could no longer use it. Ellis derived the benchmark from comparing nearly a hundred startups. Treat it as a rule of thumb and survey only people who actively use the product.
How many users do you need to measure product market fit?
About 40 survey responses give a directionally useful result, according to Rahul Vohra of Superhuman, who ran the Ellis survey on a base of 100 to 200 users. With fewer users, run the same question as interviews and read every answer yourself instead of computing a percentage.
How do you know if you have product market fit?
You have it when retention flattens above zero, new users arrive by recommendation, people complain when the product breaks, and a clear group says they would be very disappointed without it. No single signal is enough. Check several, and note which come from strangers.
Can you have product market fit without revenue?
Yes, a free product can have strong usage and recommendation without revenue, but revenue is the strongest proof that the need is real. Test willingness to pay early, even with a small paid tier, so you do not mistake enthusiasm for a business.
What comes first, product market fit or an MVP?
The MVP comes first. You build the smallest version that lets real people try the core idea, then look for fit in how they use it. Fit is not something you declare before launch. It is evidence that appears, or does not, after people use the product.
Created with AI assistance and edited for this site. Examples are illustrative and do not represent customer research. About the publisher.