Revenue is the metric everyone trusts by default. It's real money, it's hard to fake, and it's the number on the board slide. But revenue is a lagging and confirming signal, it tells you what already happened, filtered through pricing, sales effort, and acquisition spend. Your PMF score is closer to a leading signal: it tells you how your currently engaged users actually feel, independent of how much you spent to get them or what you charge.

Most of the time these two move together, and that agreement is reassuring but not that informative. The moments that actually teach you something are when they disagree. There are exactly two ways they can, and each one means something specific.

Revenue tells you what happened. Your PMF score tells you whether it will keep happening.

Case 1: revenue rising, PMF score falling

This is the more dangerous combination, because it looks like good news on the dashboard everyone actually checks. Revenue is one of the weaker PMF signals precisely because paid acquisition can grow it while fit quietly erodes underneath.

What's usually happening: you've turned on or scaled a paid channel, and the new cohort it brings in is lower-intent than your organic or referral users. They sign up, some convert, revenue climbs. But this cohort is less likely to be a genuine fit, so as they become a larger share of your active base, the percentage of all engaged users who'd be "very disappointed" to lose you drifts down, even though the absolute number of happy users hasn't shrunk.

The tell is a leaky bucket: you're filling the top of the funnel faster than fit-driven retention can hold it. Revenue keeps climbing because you keep pouring more in, not because what's already in the bucket is staying.

What to do: split your PMF survey by acquisition source, paid vs organic vs referral, rather than reading one blended score. If the paid cohort scores meaningfully lower, you have a targeting or qualification problem in that channel, not a product problem. Slow the specific leak (tighter targeting, a stronger qualification step, honest positioning in the ads) before pouring in more spend. Cross-check against a retention curve by cohort: if newer cohorts retain worse than older ones, that confirms the leak independently of the survey.

See the score behind the revenue

PMFtracker lets you segment PMF survey results by how users found you, so you can tell a genuine fit signal from paid growth that's quietly propping up the top line.

Measure your PMF score free → 14-day free trial · No credit card

Case 2: PMF score strong, revenue flat

This is the frustrating combination, but the far better one to have. Users are telling you, unprompted, that they'd be genuinely upset to lose the product. That's real signal, not a fluke. And revenue still isn't moving.

This is a monetization or distribution problem, not a fit problem, and treating it like a fit problem (rebuilding the product, chasing more feature requests) wastes time on the wrong lever. The usual causes:

The instinct in this case is to keep building. Resist it. A rising or already-strong PMF score with flat revenue is the survey doing exactly what it's supposed to: telling you the product isn't the constraint. The constraint is getting the product in front of more people, or charging appropriately for the value it already delivers.

Confirm it's not a fit problem before you rebuild anything

PMFtracker tracks your PMF score over time alongside your segments, so when revenue stalls you can see immediately whether the product is the bottleneck or something else is.

Start Tracking PMF → Set up in 5 minutes · No credit card required

The diagnostic in one table

PatternLikely causeFix first
Revenue ↑, PMF score ↓Leaky bucket, paid growth masking weak retentionQualify the paid channel, slow the leak
Revenue flat, PMF score strongMonetization or distribution gapFix pricing or reach, not the product
Both rising togetherHealthy, genuine growthKeep the cadence, don't over-diagnose
Both flat or falling togetherReal fit problemBack to segments and open-ended answers

The two disagreement cases are the ones worth stopping for. When they agree, in either direction, the story is usually simpler than founders assume, either it's working or it genuinely isn't. It's the disagreement that hides a specific, fixable problem, if you know which of the two you're looking at.