product strategy

How to Know If You're Building the Right Product for Your Market

A modern framework for assessing product-market fit beyond Sean Ellis's 40% rule. Systematic validation for product managers who need to make build-or-pivot decisions with confidence.

Timoté Geimer · · 14 min read

The Core Answer

Product-market fit is the most important question in product, yet our primary diagnostic—Sean Ellis’s “40% very disappointed” test—is 15 years old and designed for consumer products. Modern assessment requires a spectrum view: PMF isn’t binary; it degrades over time as markets shift. Diagnose it through five signals: Pull (users coming to you), Retention (cohort analysis, not aggregate), Monetization (willingness to pay), Advocacy (organic referrals, not NPS), and Expansion (feature requests, plan upgrades). Every product rests on 5-10 core assumptions; list them explicitly and test the riskiest first. For build-vs-pivot decisions: weak Pull/Retention signals mean problem-market fit failure (wrong problem); weak Monetization means pricing/positioning failure; weak Advocacy/Expansion means product quality failure. Each failure mode requires a different fix. Track these signals weekly to catch PMF degradation before it becomes crisis.

The PMF Misconception That Kills Companies

Almost every product team gets this wrong: they treat product-market fit as binary.

You either have it or you don’t. You’ve either “achieved PMF” or you’re still searching. Once you have it, you’re set.

This is dangerous misinformation.

Product-market fit is not a destination. It’s a spectrum. More importantly, it’s not permanent. It degrades. A product that had strong PMF in 2022 can lose it by 2025 if the market shifts and you don’t evolve with it.

Real examples:

  • Instagram had strong PMF for sharing photos. TikTok shifted the market’s expectation to algorithmic video discovery. Instagram’s PMF for photos degraded until they pivoted to Reels.
  • Slack had strong PMF for team communication in tech companies. Microsoft Teams and AI integration shifted what “communication” means. Slack’s original PMF weakened.
  • Dropbox had strong PMF for file sync. Google Drive and cloud-native apps reduced the pain it solved. Dropbox had to expand into collaboration and workflow.

What’s the pattern? Markets move. User expectations evolve. Competitors ship. The product that fit perfectly becomes just adequate, then gradually inadequate.

Most PMs operate with the assumption: “We have PMF, now we scale.” This leads to the tragedy of mature products that didn’t see their own degradation until it was too late.

The solution: treat PMF as a continuous diagnostic, not a one-time achievement. Measure it. Watch it. When signals weaken, act.

The Five Signals of Product-Market Fit

These are the five signals that tell you whether you have PMF, whether you’re losing it, and what kind of PMF you have.

Not all five have to be equally strong. Different business models weight them differently. But all five should be non-zero, and they should be trending up.

Signal 1: Pull

The question: Are users coming to you, or are you pushing?

Pull is the signal that your product solves a problem so acutely that people actively seek it out. They search for it. They ask about it. They sign up because they found you, not because you paid for ads.

This is the most underrated PMF signal. Most teams obsess over retention and revenue. But if you don’t have pull, your CAC is broken, your growth is fragile, and you’re competing on price.

How to measure it:

  • Track organic signup rate. What percentage of users find you without paid acquisition?
  • Track referral rate. Do users tell others? (This is different from NPS. Real referrals = “I told my friend to use Slack.” Not “I’d recommend Slack.” One is behavior, one is survey.)
  • Track search volume. Do people search for problems you solve, or do they search for your product specifically?
  • Track inbound support questions. Are they “How do I use this?” or “Where do I find this feature?” The former is pull. The latter is discovery friction.
  • Track demo requests. Are they coming from your sales team scheduling, or from prospects requesting demos?

Red flag: If 100% of your growth is paid acquisition, you don’t have pull. Your CAC is unsustainably high. You’re competing in a market where your solution isn’t obviously necessary.

Example: A B2B SaaS that has weak pull might see: 5% organic signups, 2% referrals, 100 monthly searches for their product name, 30 inbound demo requests/month.

A B2B SaaS with strong pull might see: 35% organic signups, 15% referrals, 5,000 monthly searches for problems they solve, 200 inbound demo requests/month from prospects (not just sales outreach).

Signal 2: Retention

The question: Do users stay? Does this matter to them?

Retention is the truth serum. If users retain, the product matters. They use it. It solves something real. If they churn, they’ve concluded the problem either isn’t acute enough or your solution isn’t good enough.

Here’s the nuance: aggregate retention is useless. “We have 85% month-to-month retention” is meaningless. Cohort retention matters.

How to measure it:

  • Build cohort analysis by signup date. Track what percentage of users from each cohort return in Week 2, Week 4, Month 3, Month 6, Month 12.
  • Look for the “retention curve.” Does it drop off a cliff after one week? (Bad. Users tried it, didn’t get value.) Does it flatten after Month 2? (Good. Users who stay past Month 2 stay long-term.)
  • Segment by user type. Maybe SMB cohorts have 60% M1 retention. Enterprise cohorts have 95%. Power users have 90%. This tells you who has PMF and who doesn’t.
  • Calculate median lifetime (time until 50% of a cohort has churned). If it’s 6 months, you have some PMF. If it’s 18 months, you have strong PMF. If it’s 3 weeks, you don’t.

Red flag: If M1 retention is below 25%, you don’t have PMF. Users tried it. They left. Something’s wrong with the product itself or with your positioning (they signed up for the wrong reason).

Example: A fintech app with weak retention: M1 = 22%, M3 = 8%, M6 = 3%. Users try it, most leave. Something about the core experience isn’t compelling.

A fintech app with strong retention: M1 = 50%, M3 = 35%, M6 = 25%, M12 = 15%. Users are sticking around. The curve is gradual, which is normal (some people move on). But enough stay long-term that the product has value.

Signal 3: Monetization

The question: Will users pay? Are they willing to pay?

Monetization is where willingness-to-pay meets ability-to-pay. You can have strong retention and zero monetization (your users love the product but don’t have budget). You can have monetization and weak retention (users will try it, but not enough stay).

The gap between “would you pay?” and “will you pay?” is enormous.

How to measure it:

  • Track conversion to paid. Of your free users, what percentage move to paid plans? B2B should be 2-5%. B2C should be higher (depends on category, but 10-25% isn’t unusual if you have strong PMF).
  • Track net revenue retention (NRR). Of your customers from last year, how much are they spending this year (accounting for churn, downgrades, and upsells)? B2B with strong PMF should have NRR > 110% (customers expand faster than they churn). Anything above 100% is good. Below 90% is weak.
  • Track willingness-to-pay surveys. Ask users: “If we removed this free version, would you pay $X/month?” Price at multiple points. The point where 40%+ say yes is your target price. If no price point gets 40%, you have a positioning problem or a PMF problem.
  • Track revenue per user by cohort. New customers from 2025 should be worth more than new customers from 2024 (because your product has improved). If older customers are worth more, you’ve lost positioning or you’re competing on price.

Red flag: If willingness-to-pay is zero (users say “I wouldn’t pay for this”), you have a free product, not a paid product. That’s fine—but you need a different monetization model (ads, marketplace, data). If conversion to paid is below 1%, you have a positioning problem (users don’t see value) or a pricing problem (price doesn’t match value perception).

Example: A project management tool with weak monetization: 30% free-to-paid conversion, NRR = 85%, willingness-to-pay survey shows only 20% would pay at $15/month. Users see value, but don’t see enough value to pay. Problem: either your core feature isn’t differentiated (they can get it free elsewhere) or your positioning isn’t clear (they don’t understand what problem you solve).

A project management tool with strong monetization: 8% free-to-paid conversion (small but qualified), NRR = 125%, willingness-to-pay survey shows 65% would pay at $29/month. Users move to paid when they’re serious. They expand as they grow. They see clear value.

Signal 4: Advocacy

The question: Do users tell others? Not in a survey, in real behavior.

This is different from NPS. NPS is sentiment (“I’d recommend this”). Advocacy is behavior (“I told someone to use this”).

The most underrated signal in product.

If users are telling others, they’ve concluded the product is good enough that they’re willing to stake their reputation on it. That’s strong signal. If they’re not telling others, it means the product is fine but not remarkable.

How to measure it:

  • Track referral rate. Of your new signups, what percentage came from user referrals? (Not referral campaigns. Organic referrals where users tell other users.)
  • Track referral quality. Referral users typically have higher LTV. If they don’t, you have a selection bias (friends of power users are still power users, but referrals are selecting for quantity, not quality).
  • Track Net Promoter Score (NPS), but use it correctly. NPS is a lagging indicator. It tells you how people feel, not if they act. But it gives you a population to interview. Interview your promoters (9-10 rating). Ask: “You said you’d recommend us. Have you actually told anyone? Who? Did they sign up?” This tells you if sentiment = behavior.
  • Monitor social proof. Are users mentioning you on Twitter, in blogs, in reviews? Cold hard evidence that they care enough to talk about you publicly.
  • Track logo velocity. How fast do new logos (companies using you) grow? This is partly sales (they drive adoption), but fast logo velocity also signals that users are spreading the word internally.

Red flag: If referral rate is below 5%, users aren’t organizers talking about you. They’re not advocates. You’re not generating word-of-mouth. Either the product isn’t good enough for them to stake reputation on, or you don’t have distribution mechanism for sharing.

Example: A Notion template marketplace with weak advocacy: 2% referral rate, NPS = 40 (respectable, but no word-of-mouth). Users like templates. They don’t tell friends.

A Notion template marketplace with strong advocacy: 18% referral rate, NPS = 65, users mention templates on Twitter constantly, they’re featured in Notion community channels. Word-of-mouth is organic.

Signal 5: Expansion

The question: Do users want more? Do they try new features? Upgrade plans? Recommend you for different use cases?

This is often the difference between a good product and a great product. Users tried you for one use case (time tracking). They like it. Do they now want time tracking + reports + integrations + team management? If yes, expansion signal is strong.

How to measure it:

  • Track feature adoption. Of your new features launched in the last quarter, what percentage of users have tried them?
  • Track plan upgrades. Of your free users who convert to paid, how many upgrade plans within 12 months? (If nobody upgrades, your pricing is wrong, or your top tier isn’t valuable.)
  • Track expansion revenue. What percentage of growth comes from existing customers (upsells, cross-sells) vs new customers? Strong PMF should see expansion revenue = 30-50% of new customer revenue.
  • Track feature requests. Are customers asking for specific features (good) or just saying “we need X” (weak)? Specific feature requests signal they’re imagining use cases beyond what you’ve built.
  • Track use case expansion. Are customers using you for the primary use case, or have they found secondary use cases? (Slack was designed for team messaging. Teams found it valuable for customer support, HR, finance notifications, etc.)

Red flag: If feature adoption is below 15% for new launches, your product isn’t showing up as a solution to new problems. If plan upgrades are below 10% annual, your pricing isn’t matching value growth. If expansion revenue is below 10% of growth, you’re not creating value that makes users want more.

Example: A customer feedback tool with weak expansion: users collect feedback, they don’t upgrade to analyze it, they don’t integrate with product roadmap tools, no feature requests for analysis/prioritization. They’re using you as a feedback bucket, not a decision-making tool.

A customer feedback tool with strong expansion: users collect feedback, 25% upgrade to analysis tier, 40% integrate with Jira, consistent requests for prioritization frameworks, customers finding use in product strategy meetings. You’ve become part of their decision process.

The Assumption Stack: What Needs to Be True

Every product rests on 5-10 core assumptions about the market, the user, the problem, and the solution.

Example assumptions for a project management tool:

  1. Teams need better visibility into who’s doing what
  2. Asynchronous work is becoming normal (not everyone in the office)
  3. Teams will adopt a tool if it saves 5+ hours/week
  4. Price elasticity is such that teams will pay $10-30/user/month
  5. Teams prefer tools with strong API access (not spreadsheets)
  6. Mobile project management is important (not just web)
  7. Integration with Slack/email is table stakes
  8. Our UI is intuitive enough that teams don’t need training

Some of these are about the market (assumption 2). Some about the user (assumptions 3, 4). Some about your solution (assumptions 6, 7, 8). Some about the competitive landscape (assumption 5).

Your job: List your assumptions. Rank by risk. Test the riskiest first.

How to test assumptions:

  • Talk to users: “Do you agree that [assumption]?” Don’t sell. Don’t defend. Just listen.
  • Look at usage data: “Do users actually do [behavior we assumed]?” Assumption 3 (save 5+ hours/week) is falsifiable. Look at time savings.
  • Run surveys: “Would you prefer [feature we assumed is important]?” Run it against alternatives.
  • Build an MVP: If the assumption is core and uncertain, sometimes you need to build a minimal version to test it.

The goal: find which assumptions are weakest. Test those. If they’re wrong, your whole product direction is wrong. Fix early.

The Build-vs-Pivot Decision: Diagnostic Framework

Here’s the moment of truth: your PMF signals are weak or degrading. Should you fix the product (build more), or should you fundamentally change direction (pivot)?

The answer depends on which signals are failing.

Pull and Retention Failing → Problem-Market Fit Issue

If users aren’t coming to you and they’re leaving when they do arrive, you’re solving the wrong problem.

The market doesn’t need what you’re building. Or you’re positioning it as a solution to the wrong problem.

Fix: Don’t iterate the product. Go back to customer discovery. What problems are they actually trying to solve? What solutions are they cobbling together today? Where’s the real pain point you’re missing?

Example: A “productivity AI” tool that promised to summarize emails. Nobody signed up (weak pull). People who tried it left immediately (weak retention). The assumption was “people have email overload.” The reality: people don’t mind email overload. What they mind is sorting through irrelevant emails. The product solved the wrong problem. A pivot to spam filtering would have been smarter.

Monetization Failing → Pricing or Positioning Issue

If users love you (pull, retention, advocacy are strong) but won’t pay, your pricing or positioning is broken.

You’re solving a real problem. They value it. But they don’t see it as a “paid product” problem.

Fix: Don’t change the product. Change the positioning or pricing. Maybe you’re targeting the wrong buyer (you’re selling to users, but should sell to teams). Maybe your price point is wrong. Maybe you’re competing on feature set, but should compete on speed/ease/support.

Example: A design tool that had strong retention and advocacy but low monetization. Users used it regularly. They told friends. But conversion to paid was 1%. The problem: the product was designed for solopreneurs, but priced for teams. When they repositioned as “professional design for creators” and adjusted pricing to $5/month instead of $15/month, conversion jumped to 12%. Same product. Different market fit.

Advocacy and Expansion Failing → Product Quality or Experience Issue

If users retain and pay, but they don’t expand and don’t advocate, you have a functional product that isn’t remarkable.

You’re solving the problem. It’s not delighting them.

Fix: Improve the product. Speed it up. Simplify the interface. Add the features they keep requesting. Make it so good they can’t help but tell others.

Example: A note-taking app with 60% M3 retention and 8% free-to-paid conversion. Users stayed and paid. But nobody upgraded plans (weak expansion) and referral rate was 3% (weak advocacy). The product solved the problem but felt like a commodity. They invested in design, speed, and collaborative features. Referral rate went to 15%. Expansion revenue became 40% of growth. Same PMF on retention and monetization. Better product changed advocacy and expansion.

The Continuous PMF Dashboard

You need to measure PMF continuously. Not quarterly. Weekly. Monthly at minimum.

Weekly metrics:

  • Organic signup rate (are users still finding you?)
  • Daily active users (trend—is it up or down?)
  • Free-to-paid conversion (are people still willing to pay?)

Monthly metrics:

  • Cohort retention (do new cohorts retain at the same rate as old ones?)
  • NPS and referral rate (are users still advocating?)
  • Feature adoption for new launches (is expansion signal strong?)
  • Churn analysis (why are people leaving? If reasons change, you’ve lost PMF on something.)

Quarterly metrics:

  • Full cohort analysis (how many of each cohort from 12 months ago are still here?)
  • Net revenue retention (customers expanding or contracting?)
  • Willingness-to-pay surveys (has value perception changed?)
  • Win/loss analysis (why do we win new customers? Why do we lose deals?)

When any signal drops more than 15% month-to-month, investigate immediately. You might be losing PMF.

PMF for B2B vs B2C

These frameworks work differently in B2B vs B2C.

B2B PMF

Pull is more important. B2B companies should have inbound pipeline (pull). If you’re pure outbound, CAC is broken.

Retention is measured by cohort, but accounts matter too. (Customer A might have 3 users. Customer B might have 300. Aggregate retention misses this.)

Monetization matters enormously. Your unit economics need to work. If CAC is $50k and LTV is $30k, you don’t have PMF regardless of retention.

Advocacy happens at the user level (individual contributors tell peers), but purchase happens at the buyer level (manager, director, exec). You need both signals.

Expansion is the highest-leverage signal. Most B2B revenue comes from existing customers. If expansion is weak, your PMF is fragile.

B2B red flags:

  • Organic signup rate < 5%
  • M1 retention < 50%
  • Free-to-paid conversion < 2%
  • NRR < 100%
  • Logo churn > 15% annually

B2C PMF

Pull is critical. If users aren’t finding you organically, your unit economics don’t work.

Retention is measured by cohort, and it matters more. One bad cohort (people who signed up in October have 15% M3 retention, everyone else has 40%) tells you something changed—in product, in marketing, or in your market.

Monetization can take different forms: ads, freemium, premium, subscriptions. But whatever form, there needs to be a clear unit economics story.

Advocacy and expansion are often the same signal (users who pay are users who advocate, and advocacy drives new cohorts).

B2C red flags:

  • Organic signup rate < 30%
  • M1 retention < 30%
  • Willingness-to-pay < 30% of users
  • Referral rate < 8%
  • Cost per install > 30% of LTV

When to Pivot: The Decision Framework

You’ve diagnosed PMF. The signals are weak. Should you stay the course, iterate, or pivot?

Stay the course when:

  • At least three of the five signals are strong and stable
  • You’re losing momentum but not cratering
  • You have runway (18+ months) to improve
  • The fixes are product improvements, not market shifts

Iterate hard when:

  • Two signals are strong, three are weak
  • The weak signals require product changes (not repositioning)
  • You understand the fix (retention is weak because of Y feature being broken)
  • Customer feedback is consistent on the problem

Pivot when:

  • Pull and retention are both weak (you’re solving the wrong problem)
  • You’ve iterated on product, and signals haven’t improved
  • Your team has high confidence in a different market or product direction
  • You have customers who want something different than what you’re building

Pivots are hard. But pivoting while you have runway is faster than iterating on the wrong thing for two years.

How Dualoop Coach Helps

Assessing product-market fit requires structured thinking across multiple dimensions: market signals, user behavior, assumptions, competitive position, and long-term viability. Dualoop Coach helps PMs systematize this analysis—moving beyond hunches to rigorous diagnosis.

Rather than debating whether you have PMF based on one metric (retention or NPS), you run structured analysis across all five signals. You map your assumptions explicitly and stress-test them. You diagnose what kind of PMF failure you might have (problem-market, pricing, or product quality) so your fix is precisely targeted.

For product leaders facing build-or-pivot decisions, a rigorous PMF framework turns uncertainty into actionable diagnostics. That’s the difference between iterating productively and spinning wheels.