The Product Market Fit Checklist: 20 Signals to Check Before You Build

Most founders check product-market fit too late.

They build. They launch. Then they find out whether the market wanted it. By that point, months are gone and, in some cases, savings are too.

This checklist runs the test in reverse. It gives you the signals to verify before you write a line of code. Twenty checkpoints across five categories. Pass enough of them and you have evidence that PMF is achievable. Fail too many and you know that now, before the commitment, not after.

What Is a Product Market Fit Checklist?

A product market fit checklist is a structured evaluation tool used to verify, before building, whether a specific product has a viable market. Rather than waiting for launch results to reveal whether PMF exists, it identifies leading indicators that predict market acceptance. The output is a decision: go, wait, or kill, backed by evidence rather than enthusiasm.

A product market fit checklist is an evidence-gathering framework that addresses five dimensions of market viability: problem severity, demand evidence, willingness to pay, buyer specificity, and distribution fit.

The underlying logic comes from Marc Andreessen’s original PMF definition: “being in a good market with a product that can satisfy that market.” Before you have a product, you can still evaluate the market. And before you have the full product, you can test whether early signals support building the rest.

The checklist covers five evidence categories:

Each section below provides the specific checkpoints and explains what a pass or fail means for your decision.

Is the Problem Real Enough to Build Around?

Problem severity is the first filter in any product market fit checklist. A problem clears this filter when at least five people have described it in their own words without prompting, it recurs at least monthly, and those people have already tried to solve it themselves. Problems that fail this filter rarely produce products the market pays for, regardless of how elegant the solution.

Most failed products failed not because of poor execution but because the founder assumed a problem was painful enough to motivate payment, based on friendly conversations and personal intuition, without checking. The problem was real. It just was not real enough.

The gap between “yes, that frustrates me sometimes” and “I have spent weeks trying to fix this” is where most ideas die. This section helps you identify which side of that gap your idea sits on.

Use this checklist for each candidate idea:

• At least five people have described this problem to you unprompted, without your framing or leading
• The problem recurs for them at least monthly, not once a year or occasionally
• At least three of them have tried to solve it themselves, even with a clunky workaround
• You can find at least three forum threads, Reddit posts, or community discussions where people ask for help with this exact problem

The clearest indicator of a real problem: unsolicited, vivid language from strangers. When someone you have never met describes the problem you are planning to solve in exactly the words you would have used, that is a signal worth paying attention to. When your only validation comes from friends who say “yeah, that sounds annoying,” the problem might not be severe enough to motivate a purchase.

Rob Fitzpatrick’s approach in The Mom Test gives the most reliable rules for running these conversations honestly: ask about past behavior, not future intentions. “Tell me about the last time you dealt with this” produces real answers. “Would a tool that did X help you?” produces socially desirable agreement that tells you nothing.

Related: Customer Interview Scripts for Idea Validation

Does Demand Evidence Exist in the Market?

Demand evidence is proof that people are actively looking for what you are planning to build. The strongest signals are competitor products with paying customers, measurable search volume for problem-related keywords, and community discussions where people explicitly request solutions. Two or more of these signals confirm a real market. Zero signals typically means the market has not formed, or others investigated and walked away.

There is a critical difference between a problem people acknowledge and one they actively try to solve. Demand evidence measures the second condition. It tells you whether the frustration is strong enough to motivate action.

Check each signal:

• At least one keyword related to the core problem has measurable search volume
• At least one competitor product exists and has paying customers
• You can find at least one community where this problem is regularly discussed and people ask for solutions
• People in your interviews confirmed they currently spend money on imperfect alternatives

One clarification worth making explicit: competitor existence is a positive signal. It confirms that real buyers have already handed over money for an imperfect version of what you are planning to build. No competition is the riskier scenario. Either you have found a genuine gap, or (more commonly) others investigated and walked away. Competitor reviews are one of the most underused research methods available. Real buyers describe exactly what they wish the current solution did differently, which is free briefing material for your positioning.

Will People Pay Before You Have a Product?

Willingness to pay separates validated ideas from interesting ones. The definitive test is whether a real potential buyer will complete a payment action before you have built anything. A strong result requires at least one concrete payment commitment: a card entered into a pre-sell landing page, a deposit for a reserved spot, or money exchanged for a manual version of the service you plan to automate.

This is the most important section in the checklist. It is also the most commonly skipped.

Founders skip it because it is uncomfortable. Asking for money before you have a product feels presumptuous. But the discomfort is exactly what makes the signal valuable. Polite enthusiasm is easy to generate. Real payment behavior is not.

Three methods for testing willingness to pay before you build:

Method 1: The current-spend question. During customer interviews, after establishing the problem is real, ask: “What do you currently spend to deal with this?” Past spending is an honest proxy for future willingness to pay. If three people tell you they spend between $50 and $200 per month on imperfect workarounds, you have confirmed that a budget line already exists.

Method 2: The pre-sell page. Build a simple landing page describing the product at a specific price. Drive real traffic from communities where your target buyer spends time. If people enter payment details, that is strong demand evidence. If nobody converts after meaningful exposure, that result is equally valuable. Pre-selling as a validation method is one of the most reliable techniques documented in the Indie Hackers community for separating validated ideas from interesting ones.

Method 3: The manual offer. Offer to solve the problem as a service before automating it. Charge for your time. If someone pays you to do this manually, they have confirmed both that the problem is worth solving and that the outcome is worth paying for. Paul Graham describes this as the canonical early-stage validation path: get one person to pay for the outcome before you build the tool that delivers it at scale.

Willingness-to-pay checklist:

• At least three people gave a non-zero answer to “what do you currently spend to deal with this?”
• At least one person indicated price willingness without being led to a number by your suggestion
• You have described the product at a specific price to at least five people, and at least two responded with genuine interest beyond polite agreement
• Someone has completed a payment action before you built anything (pre-sell, deposit, or manual service payment)

Is your idea getting polite encouragement or real demand signals? The Idea Validation Scorecard runs 15 checkpoints across problem, demand, and founder fit. It takes about 20 minutes and produces a clear go, wait, or kill recommendation. Run the scorecard

Do You Know Exactly Who Your Buyer Is?

Buyer specificity means you can describe the ideal buyer in one sentence: their situation, their specific problem, and the trigger that makes them look for a solution now. Without this, you cannot find them, cannot reach them, and cannot write marketing that resonates. With it, you know where to look, what to say, and how to prioritize your first outreach.

A vague buyer definition is one of the most predictable paths to a failed launch. “Small business owners who need help with marketing” describes potentially millions of people, none of whom you can find, message, or convert at a reasonable cost. “Freelance graphic designers with 10 to 50 clients who spend more than three hours per week on invoice follow-up” describes a real person you can find in specific communities and speak to directly.

Buyer specificity checklist:

• You can describe the ideal buyer in one sentence (situation plus specific problem plus trigger)
• You can name at least 10 specific people who match that description right now
• You know where these people spend time online (specific subreddits, newsletters, communities, or professional associations)
• You know how they currently solve the problem without you, and what they dislike about that solution

The “can you name 10” test is more revealing than it sounds. If you can write 10 actual names or handles of people who match your buyer description, you have a real testing pool. If you cannot, buyer acquisition will cost more time than building the product itself.

Related: How to Evaluate a Business Idea: The Complete Framework

Can You Reach Your First Buyers Without a Budget?

Distribution fit is the gap most solopreneurs discover after launch, not before it. Building the right product for a market you cannot reach produces the same outcome as building the wrong product. Before committing to build, verify that you can reach your first 20 buyers through community access, existing relationships, or platform presence, without needing a paid advertising budget.

Product-market fit requires both a product that fits and a market you can reach. Most pre-build checklists focus entirely on the product side and ignore distribution. This section addresses market access.

If you cannot answer “how do I get my first 20 buyers?” before you build, you are likely to answer it the expensive way: by launching, then discovering the distribution problem while your runway is shrinking.

Distribution checklist:

• You can describe a specific, non-paid channel for reaching your first 20 buyers (community posting, direct outreach, an existing audience, or a professional network)
• You have access to at least one community where these buyers spend time and where you can contribute credibly
• You know the language they use to describe their problem, so your outreach reads as relevant rather than generic
• You have a credible reason to discuss this problem publicly (work experience, documented research, or demonstrated familiarity with the space)

Related: The One-Week Idea Test: Validate Any Idea Before Writing Code

How Do You Score Your PMF Checklist Results?

Score your results by counting confirmed signals across all five categories. A total of 16 or more out of 20 is a strong pre-build case. A total between 12 and 15 has identifiable gaps worth addressing before committing. Below 12, the evidence base is too thin. The distribution across categories matters as much as the total: failing the willingness-to-pay section is a critical gap regardless of your overall score.

After running all five sections, count your confirmed signals:

The hard cases are the middle scores. A score of 14 feels like a go because most signals are green. But in most cases, the red signals become the launch problem. Two focused weeks on the weakest category is a better investment than six months building toward a problem you already suspected was weak.

When to run this checklist again:

Run the same checklist when you substantially change the idea, including a different buyer segment, different price point, or different problem framing. PMF evidence is specific to the version of the idea you tested. A different positioning requires fresh validation.

Related: The Idea Validation Framework: A Four-Phase Approach for Solopreneurs

Frequently Asked Questions

What is a product market fit checklist?

A product market fit checklist is a structured set of evidence-gathering criteria used to assess, before building, whether a specific product has viable market demand. It covers problem severity, demand evidence, willingness to pay, buyer specificity, and distribution fit. Each category produces a pass or fail signal, and the total score informs a go, wait, or kill decision backed by actual evidence.

How many checklist signals do you need confirmed before building?

A strong pre-build case requires at least 16 of the 20 signals confirmed across all five categories. A score of 12 to 15 justifies continuing validation work on the weakest category before committing. Below 12, the evidence base is too thin to support a confident build decision. Category distribution matters as much as total score: failing willingness to pay is a critical gap regardless of how well the other categories score.

How is a PMF checklist different from idea validation?

Idea validation is the broader process of testing whether a business idea is worth pursuing. A PMF checklist is one component of that process, focused specifically on whether the market will accept the product once built. Idea validation also covers founder fit, competitive landscape, and go-to-market feasibility. The checklist is best used as a focused tool within a fuller validation process, not a replacement for it.

What does product-market fit look like before you launch?

Before launch, PMF evidence is indirect by definition. The closest pre-launch signals are: at least one genuine payment commitment from a potential buyer (pre-sell or deposit), five or more customer conversations confirming the problem is real and recurring, and documented current spending on imperfect alternatives. None of these prove PMF. They confirm that the conditions for PMF are present, which is the most you can demonstrate before shipping a product.

Can you check for PMF without talking to potential customers?

Demand signals and competitive research can be done without customer conversations. Willingness-to-pay tests can run with a landing page and traffic. But problem validation cannot be done remotely. The goal of customer conversations is to confirm whether the problem is real, recurring, and painful enough to motivate payment. That requires actual conversation, not inference. Skipping interviews means skipping the phase where most weak ideas get eliminated at the lowest cost.

Ready to Run Your Idea Through a Full Evaluation?

The checklist above tells you whether the conditions for PMF exist.

The Idea Validation Scorecard takes you through 15 structured checkpoints and produces a clear go, wait, or kill recommendation based on your specific idea. It covers everything above plus founder fit, competitive positioning, and timing.

Run the Idea Validation Scorecard

Keep Reading

• The Idea Validation Framework: A Four-Phase Approach for Solopreneurs
• The Mom Test Summary: How to Run Customer Conversations Without Leading the Witness
• The One-Week Idea Test: Validate Any Idea Before Writing Code