Your PMF score is a filter on people, not a verdict on your product. It asks engaged users one question and reports the share who'd be devastated to lose what you built. Change the price, and you change who shows up on the other side of that filter, before a single feature moves.

So the honest answer to "do I need to re-survey" isn't yes or no. It's: did this price change plausibly swap out the population you were measuring?

What a price change actually does to your sample

Three groups of users subtly change composition the moment you move price:

None of this is new usage data contaminating your retention curve or your feature logs. It's new people contaminating the comparison between your old score and whatever you'd measure next. That's the same root issue covered in when your PMF score and your revenue disagree: the two metrics can diverge because they're sampling different populations, not because one of them is lying.

A price change is a filter change. Your score didn't get better or worse. The population answering the question did.

Three signals it's time to re-run, not wait for the next cycle

  1. The change is 20% or larger. Small adjustments (currency rounding, a 5-10% bump) rarely move who clears the bar enough to matter. A jump from $49 to $79, or a launch price expiring, usually does.
  2. You added or removed a tier. Restructuring plans changes which feature set a given price buys, which changes what "the product" even means to the person answering. Score it like a new product line, not a patch.
  3. The change targets a different buyer. Moving from self-serve to a sales-assisted higher tier, or the reverse, brings in a meaningfully different ICP. Combine this with segment-level PMF rather than one blended number.

If none of these apply, your existing survey cadence from how often to run the PMF survey is still the right rhythm. Don't manufacture urgency a 5% price tweak doesn't warrant.

See whether your score moved for a real reason

Run the Sean Ellis survey inside your product. PMFtracker tracks the score over time and shows the response count behind every reading, so a jump or dip after a price change is read against its sample, not taken at face value.

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

What carries over, and what doesn't

This is the same question PMF score after a pivot answers for a much bigger change, and the logic transfers directly, just with a smaller blast radius:

Practically: don't throw out your historical trend line. Add a marker on it for the price change, the same way you would for a major feature launch, and read the next data point knowing the sample underneath it shifted.

Segment legacy users from new-price users

If you grandfathered existing customers at the old price, don't blend them into a single survey result with new-price signups. They are answering with a different filter already applied; they never had to decide whether the new price was worth it. Score the two cohorts separately, the same way segment-level PMF recommends cutting by plan tier or channel. A blended number here hides exactly the information you're trying to get: whether the new price is still clearing the bar for new buyers.

Read your next score against the right sample

PMFtracker holds back the survey score until 40+ responses sit behind it, so you don't act on a new-price number before the sample can carry it.

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