Product-Market Fit Explained: Origins, Signals and Myths

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Product-market fit, usually shortened to PMF, is the idea that a startup succeeds when it's in a good market with a product that satisfies that market. That sounds almost too obvious to need a name. But the name stuck because it points at something founders routinely get backwards: they pour effort into the team, the product, the brand and the fundraising, while the one thing that decides most outcomes is whether enough people actually want what they've built.

This article covers a plain definition, where the phrase came from, why people describe it as pull rather than push, the signals practitioners use to judge it, and the myths that cause the most damage. It's the general explainer. For the software-specific version, with staged thresholds and SaaS metrics, see product-market fit for SaaS.

A working definition

The most quoted definition comes from the person who popularised the term. In his 2007 essay The only thing that matters, Marc Andreessen wrote that product/market fit means being in a good market with a product that can satisfy that market.

Two halves, then. The market is a group of real potential customers with a need strong enough that they'll pay to have it met. The product is whatever you ship that meets the need well enough. Fit is the relationship between them, not a property of either one alone.

That distinction matters in practice. Andreessen separates the quality of a product from the size of a market and uses a blunt example: the world's best software application for an operating system nobody runs. A great product can sit in a tiny or indifferent market and go nowhere. A merely adequate product can sit in a hungry market and take off.

Where the term came from

Andreessen published the essay on his blog in June 2007, as part of a series of posts on startups. It's now preserved at pmarchive.com. His argument was that when you look across a broad set of startups, the team, the product and the market all vary wildly in quality, and the question is which one correlates most with success. His answer was the market.

The idea wasn't entirely his. In the same essay he credits Andy Rachleff, formerly of Benchmark Capital, with crystallising the formulation, and names two principles after him. Rachleff's Law of Startup Success says the number one company-killer is lack of market. The corollary says the only thing that matters is getting to product/market fit. So when you read that Rachleff "coined" PMF, the fairest reading of the primary source is that Andreessen named and spread it, and Rachleff supplied the thinking behind it.

Andreessen also split the life of any startup into two parts: before product/market fit and after it. His advice for the first part was to focus obsessively on getting there, and to do whatever's required, including changing people, rewriting the product, or moving into a different market.

Why it's described as pull, not push

The best-known image in the essay is the one about pull. Andreessen writes that in a great market, the market pulls the product out of the startup. The market needs to be fulfilled and will be fulfilled by the first viable product that comes along. In his words, the product doesn't need to be great, it just has to basically work.

Compare the two modes:

Mode What it feels like Where the energy comes from
Push You chase prospects, explain the value, discount to close, and chase again Your team's persuasion
Pull Customers find you, ask for access, and complain when something breaks The customers' own need

His description of the pull side is vivid. Customers are buying the product as fast as you can make it, or usage grows as fast as you can add servers. The main goal becomes answering the phone and replying to all the emails from people who want to buy.

And the opposite is just as telling. Andreessen lists the signs that fit isn't happening: customers aren't quite getting value from the product, word of mouth isn't spreading, usage isn't growing fast, the sales cycle takes too long, and lots of deals never close. He adds that you can always feel the difference.

Those are felt signals from a practitioner, not measurements. They're useful as a sanity check, but a team that relies on feel alone will be fooled by a few warm conversations. That's why people have tried to turn the feeling into numbers.

The signals people use

No single number proves product-market fit. What practitioners offer instead is a set of signals, each attributed to someone, each with its own blind spots. Lenny Rachitsky collected many of them in a roundup titled How to know if you've got product-market fit, quoting founders and investors on what they look for. The ones below come from that collection and from the primary sources it points at.

1. Retention that flattens

Take a group of customers who joined in the same period and track how many are still active over time. Brian Balfour is quoted in that roundup saying that if the retention curve flattens off at some point, you've probably found product/market fit for some market or audience. Casey Winters, in the same piece, describes the shape: a deep drop in the first month is fine, and what you want to know is whether the curve flattens somewhere. If it does, a group of customers is finding value, which means you have PMF, at least for those customers.

The flip side is a curve that keeps sliding toward zero. Every cohort leaves, just a little slower or faster. That's a product people try but don't keep.

2. The "very disappointed" survey

Sean Ellis proposed asking users how they'd feel if they could no longer use the product. According to a First Round Review piece by Rahul Vohra, after benchmarking nearly a hundred startups, Ellis found that companies that struggled to find growth almost always had fewer than 40% of users answer "very disappointed," while companies with strong traction almost always exceeded that. The detail of how to run it and read it belongs in a separate guide: see the Sean Ellis test.

3. Organic demand

Several of the people in the roundup point at demand you didn't pay for. Sam Altman is quoted asking whether any users love the product so much they spontaneously tell other people to use it. Andy Rachleff is quoted describing exponential organic growth driven by word of mouth for consumer apps. For enterprise products, Rachleff and Doug Leone are quoted on a harsher test: at the end of a free trial, pull the trial, and if the customer doesn't scream, you don't have PMF.

4. Sales cycle friction

This one goes back to Andreessen's own list. If sales cycles drag and deals stall, the pull isn't there yet. If prospects arrive already convinced and the work is mostly logistics, it probably is. It's a softer signal than retention, but it's available early, before you have months of cohort data.

Key Facts: Product-Market Fit

  • Andreessen's 2007 essay defines product/market fit as being in a good market with a product that can satisfy that market (source).
  • The same essay credits Andy Rachleff, then at Benchmark Capital, with crystallising the idea that market matters most (source).
  • Andreessen's argument: in a great market, the market pulls the product out of the startup (source).
  • Sean Ellis found, after benchmarking nearly a hundred startups, that the dividing line was 40% of users answering "very disappointed" (source).
  • Practitioners quoted by Lenny Rachitsky treat a retention curve that flattens as a sign of PMF for at least one group of customers (source).

A spectrum, not a switch

Most explanations treat PMF as a line you cross. Real data looks more like a dial.

The clearest example comes from Rahul Vohra's account of Superhuman, in the First Round piece cited above. When the team first ran Ellis's survey in 2017, 22% of respondents answered "very disappointed," so the company clearly hadn't reached the 40% mark. After focusing on the users who loved the product most, the number moved to 33%, and within three quarters of product work, Vohra reports, the score nearly doubled to 58%. The company wasn't at zero fit before, and it wasn't done afterwards. The point of the exercise was to keep measuring and keep improving.

Two related ideas follow from that.

Fit is often segment-specific. Winters's quote above says PMF "at least for those customers." A product can fit one niche tightly and be a poor fit for the wider market. That's useful to know early, because it tells you which group to serve first, and it's why the jump from early fans to a mainstream audience is its own challenge, discussed in crossing the chasm.

Fit can erode. Customers change, competitors arrive, and markets shift. That's reasoning rather than a cited statistic, but it follows from what fit is: a relationship between a product and a market, and both sides move. A company that stopped measuring after its first good quarter may not notice until retention slips.

Common myths

Myth 1: PMF is a one-time milestone

Andreessen's "before and after" framing invites this reading, and it's a fair simplification for a company's first years. But the Superhuman numbers show the score can be tracked and pushed higher, and the logic above shows it can slip. Treat it as something you keep checking, not a trophy.

Myth 2: Revenue equals PMF

Money coming in is a good sign, and Andreessen lists "money from customers is piling up in your company checking account" among the signs of fit. But revenue alone can mislead. A founder who personally sells every account, or who discounts heavily, can generate revenue without any pull. The better question is how the revenue behaves: do customers renew, expand and refer others without a push? Revenue plus a flat retention curve says far more than revenue alone.

Myth 3: A few enthusiastic users mean you've found it

Early fans are essential, and they're the starting point. But a handful of passionate users is a sign of a promising niche, not proof of a market. The questions to ask are how many of them there are, whether more like them exist, and whether you can reach them at a sensible cost. Ellis's survey is built to catch this: it looks at the share of users who'd be very disappointed, not the intensity of the loudest ones.

Myth 4: A great team or a great product guarantees it

Andreessen argues the opposite. His line, attributed to Rachleff, is that when a great team meets a lousy market, the market wins. That doesn't mean teams and products don't matter. It means neither can rescue a market that isn't there.

Myth 5: You can plan your way to it

You can't schedule it. Finding fit is mostly a search: form a guess about a customer and a problem, test it, and adjust. That's the logic behind customer discovery, the minimum viable product, and the build-measure-learn loop in the Lean Startup method.

What comes before and after

PMF doesn't appear out of nowhere. A common sequence runs like this:

  1. Problem-solution fit. You've confirmed that a real problem exists and that your proposed fix addresses it, usually with a small number of customers. See problem-solution fit.
  2. Product-market fit. The product, in a real market, shows pull: retention holds, demand arrives on its own, and the sales cycle shortens.
  3. Scaling. Only after fit does heavy investment in sales, marketing and hiring make sense, because you're amplifying something that works.

Founders who skip step one often discover they've built a polished answer to a problem nobody has. Founders who scale before step two burn money pushing a product the market doesn't pull.

And what if the signals say no? That's often the moment to consider a pivot: keep what you've learned, and change the customer, the problem or the product. Andreessen's own advice for the stage before fit includes moving into a different market or rewriting the product.

A short checklist for judging your own fit

Use these as questions, not scores. None of the cutoffs below is a rule from the sources.

  • Do customers who stay beyond the first weeks keep staying? Does the retention curve flatten for any group?
  • If you ran the "very disappointed" survey on people who've really used the product, what share would answer yes, and which segment do they come from?
  • Where does new demand come from? How much arrives without you chasing it?
  • Is the sales cycle getting shorter, or are deals stalling at the same stage?
  • Would customers complain loudly if the product disappeared tomorrow?
  • Which segment fits best, and have you written down who they are?

If most answers are uncertain, that's useful information too. It means the next job is learning, not scaling.

About the author

Brian Tr

Brian Tr

Co-Founder & COO

Brian Tr is Co-Founder and COO of Rework, with 12+ years in B2B go-to-market and operations. Brian scaled Rework from 0 to 10,000+ B2B customers across CRM and productivity tools. Brian writes for founders and owner-CEOs: startup fundamentals, founder-led and family businesses, partnerships, and how SaaS, marketplace, AI and EdTech companies grow.