How Should a Founder Assess Product-Market Fit?

Founders often want one number that tells them they have product-market fit.

There is no universal number that works across every business.

YC's Michael Seibel describes stronger product-market fit through a recognizable pattern: customers are using and buying the product at a rate that creates real pressure on the founding team, with demand and customer pull becoming difficult to keep up with. He also warns founders not to confuse funding, hiring or enthusiasm with product-market fit.

That gives founders a better starting point: look for evidence of pull.

"Do people like this?" is too broad.

Instead ask:

• Which customer are we serving?
• Which problem are they trying to solve?
• How often does the problem occur?
• What do they do today instead?
• Why would they switch?
• What behavior would show that the solution is becoming important?

YC's founder guidance repeatedly emphasizes defining the customer and problem clearly, then learning from actual customer behavior rather than relying on founder confidence.

If the customer definition keeps changing, the evidence is difficult to interpret.

Early interest can be useful. It is not enough.

Depending on the business model, look at:

• repeat purchase
• continued usage
• renewal
• expansion
• referrals
• activation
• frequency of the problem
• willingness to pay
• customer effort required to keep using the product

The right measure depends on the business.

For a subscription product, retention and renewal may matter greatly. For an infrequent purchase, repeat purchase may take too long to be useful, so other signals such as paid conversion, referrals and customer pull can matter more.

The principle is simple:

Measure the behavior that demonstrates the customer is receiving continuing value.

That is unsafe.

A B2B product sold annually, a consumer subscription, a marketplace and a one-time service do not produce the same behavioral data.

Instead of asking, "Have we crossed the magic number?" ask:

1. Is the same type of customer repeatedly experiencing the problem?
2. Are customers choosing the product without extraordinary persuasion?
3. Is the product becoming part of the customer's workflow or purchasing behavior?
4. Are customers staying, renewing, buying again or expanding where those behaviors apply?
5. Is demand creating pressure to improve capacity, reliability or distribution?

The pattern is more informative than any isolated threshold.

Interviews are valuable for understanding why customers behave as they do.

They are weaker when used as substitutes for behavior.

Ask customers about what they actually did:

• What happened the last time you had this problem?
• What did you use?
• What did it cost?
• What was frustrating?
• What changed after using our product?
• What would you do if our product disappeared tomorrow?

Then compare those answers with observed product and commercial data.

YC's Segment discussion describes a similar approach: understand the customer's problem deeply, qualify the situation, and use customer conversations to test whether the product is actually a fit for the problem.

Fit is not a permanent certificate.

Markets change. Customer needs change. Distribution changes. Competitors change. Products change.

A founder should therefore establish a recurring review of the evidence rather than treating product-market fit as a one-time milestone.

A quarterly review can ask:

• What customer segment is producing the strongest evidence?
• Which customers are staying or expanding?
• Where are customers dropping away?
• Which use cases are becoming more important?
• Which new competitors or substitutes have appeared?
• What evidence has weakened since the last review?

The point is not to manufacture certainty.

It is to notice when the relationship between product and market is strengthening or weakening.

Build a small dashboard around the behavior that matters for your model.

No single row proves product-market fit.

Together, they give the founder a more defensible evidence base.

Do not immediately respond by adding features.

First identify where the evidence breaks.

Maybe the customer segment is wrong.

Maybe the problem is too weak.

Maybe the product solves the problem inconsistently.

Maybe customers value the outcome but cannot justify the price.

Maybe acquisition is reaching the wrong people.

YC's product-market-fit guidance emphasizes returning to the market and problem when the evidence is weak, rather than assuming that more spending or more people will solve the underlying issue.

That is the useful discipline: diagnose the broken link before increasing the scale of the system.

You do not need to announce that you have product-market fit.

You need to know what evidence is getting stronger, what evidence is still missing, and what experiment will reduce the uncertainty next.

If customers repeatedly experience the problem, repeatedly choose the solution, and their behavior creates genuine demand, you have a much stronger basis for scaling.

If those signals are weak or inconsistent, keep learning before treating growth as proof.

Product-market fit is best treated as an evidence discipline, not a finish line.

Related reading: \2 · \2

Y Combinator — Before You Grow. YC cautions against focusing on growth before a product is loved and retained. Y Combinator — The Real Product Market Fit. YC describes product-market fit as a state where customer demand and usage overwhelm the company's ability to keep up.

Evidence boundary: These sources support the underlying principles and context; they do not prove that one universal tactic works for every founder, market or company. SOE separates source evidence from editorial synthesis.

Build the evidence dashboard for the business model before choosing a growth decision. Separate customer behaviour from founder interpretation, review the evidence by segment and time period, and decide what experiment would reduce the largest remaining uncertainty.