Chapter 6: Product-Market Fit

What PMF actually is

Product-market fit is when your product solves a real problem for a specific market so well that customers pull it from you — you stop pushing.

PMF is not a binary state. It's a spectrum. You can have "soft PMF" (some pull) or "strong PMF" (organic growth, low churn, customers advocating for you).

How to know if you have PMF

The Sean Ellis test Ask users: "How would you feel if you could no longer use this product?" - **> 40% say "Very disappointed"** = PMF - 25-40% = Getting close - < 25% = Not there yet

Observable signals

| Signal | Pre-PMF | Post-PMF | |--------|---------|----------| | Growth | Pushed (outbound, ads) | Pulled (word of mouth, organic) | | Churn | High (> 8%/month) | Low (< 5%/month) | | Sales cycle | Long, lots of objections | Short, "when can I start?" | | Feature requests | All over the place | Converging on a theme | | Support | "How does this work?" | "Can you add X?" |

The retention curve Plot your cohort retention over time. If it flattens (stops dropping), you have PMF for that cohort. If it keeps dropping to zero, you don't.

The path to PMF

Step 1: Talk to customers (not build) Before writing code, have 20 conversations with your ICP. Not surveys — real conversations.

Ask: 1. "Tell me about the last time you dealt with [problem]." 2. "What did you do about it?" 3. "What was frustrating about that?" 4. "If you could wave a magic wand, what would change?"

Step 2: Build the minimum viable thing Not an MVP with 50 features. The minimum thing that solves the core problem for your ICP.

Rule: If you're not embarrassed by V1, you launched too late.

Step 3: Measure the right thing Don't measure signups. Measure: - Activation rate (do they experience the value?) - Retention (do they come back?) - NPS or Sean Ellis score (would they miss it?)

Step 4: Iterate on the feedback loop Weekly: talk to 3-5 users. Monthly: review metrics. Quarterly: decide if you need to pivot, persevere, or double down.

Common PMF traps

1. Premature scaling Adding sales, marketing, and features before PMF is the #1 startup killer. You're scaling a leaky bucket.

Rule: Don't hire, don't run ads, don't build features for edge cases until retention curve flattens.

2. Vanity PMF 1,000 signups is not PMF. 100 daily active users who would be "very disappointed" without you is PMF.

3. Founder-market confusion You think the problem is painful because you experienced it. But your experience may not generalize. Validate with 20+ people who aren't you.

4. Moving the goalposts "We'll have PMF when we add this feature" — and then the next one, and the next one. PMF is about the core value, not the feature set.

Pivoting vs. persevering

When to pivot - Sean Ellis score < 25% after 6 months of iteration - Every conversation reveals a different problem - You can't find 50 people who care about your solution

When to persevere - Sean Ellis score is 25-40% and trending up - Users give specific, converging feedback - Retention curve is starting to flatten for a subsegment

How to pivot Don't throw everything away. Pivot on one dimension: - **Customer pivot**: Same product, different market - **Problem pivot**: Same market, different problem - **Solution pivot**: Same problem, different approach

PMF by MRR stage

$0 (Pre-product) You're in discovery mode. Talk to people. Validate the problem. Don't build yet.

$0-1K MRR You have something. But is it PMF or just early adopter enthusiasm? Track retention. Run the Sean Ellis test.

$1-5K MRR If retention is strong and customers refer others organically, you likely have soft PMF. Time to optimize, not pivot.

$5-15K MRR If growth is still purely outbound, you may not have PMF despite revenue. True PMF shows up as organic pull.

Action items

• [ ] Run the Sean Ellis test with your current users
• [ ] Plot your 30-day cohort retention curve
• [ ] List the top 5 feature requests — do they converge?
• [ ] Have 3 conversations with users this week (calls, not surveys)