PMF Feels Like a Phone Call, Not a Chart

There's a long tradition of trying to define product-market fit with metrics. Sean Ellis's '40% would be very disappointed' survey. Cohort retention curves flattening. Organic growth rate exceeding some threshold.

These metrics are real. They're also lagging. By the time the metrics show PMF, the team has known for a month from a different signal entirely: users started behaving differently.

That behavior change is what PMF actually feels like. The metric confirmation comes later.

Three behaviors mark the transition.

**Users reach out unprompted.** Before PMF, users are passive. They use the product when prompted, they fill out surveys when asked, they answer support tickets when issues arise. After PMF, users contact you. They have feature requests. They report bugs proactively. They ask when X is coming.

This is the cheapest PMF signal to measure. Count unsolicited inbound from users this week vs. last week. When the slope changes, something happened.

**Users explain you to other users.** Before PMF, the only people who can explain your product are you and your closest customers. After PMF, random users in your community can explain it to newcomers. They've internalized the value prop. They can recommend you and have the conversation stick.

This is detectable in support tickets where users reference each other ('I saw [other user] solve this using X — does that work?'). It's also detectable in any community forum your product spawns.

**Pricing conversations get easier.** Before PMF, every pricing conversation is friction. Users push back, demand discounts, churn over rounding errors. After PMF, pricing becomes background. Users grumble but pay. The conversation moves on quickly.

This isn't because users like paying more. It's because they perceive value strong enough that the pricing question becomes a small one.

Pre-PMF, every conversation is about the product. Post-PMF, every conversation is about what to do next.

Most teams track lagging metrics and have planning conversations like 'are we at PMF yet?' The conversation cycles for months. The team can't agree because the lagging metrics give ambiguous answers.

If you track behavior signals instead, the answer is usually clear. Either the inbound is increasing, users are recommending you, and pricing is getting easier — or it's not. The team can have a one-meeting conversation about which one is true and act accordingly.

This matters because pre-PMF and post-PMF require different operating modes. Pre-PMF, the team should keep iterating on the core, talking to users, narrowing the wedge. Post-PMF, the team should shift to scaling — hiring, expanding channels, deepening the feature set. Confusing the two is expensive. PMF teams that don't shift to scaling burn the moat. Pre-PMF teams that try to scale burn capital on growth that won't compound.

For most products, the answer is 18-30 months of focused work. Not weeks. Months. Plural.

This is unsatisfying. Investors want PMF by month 6. Founders want it by month 4. The actual timeline is longer because PMF requires not just building the right thing, but building it for the right segment, finding that segment, and developing the marketing language that lets the segment recognize you.

The shortest path to PMF is honesty about which of those three things is the current bottleneck. Many teams are building the right thing for the wrong segment, which they could fix in months if they admitted it. Other teams have the right segment but the wrong product, which is a longer fix. Diagnosing the bottleneck correctly is the highest-leverage 0→1 skill.