Decision #300AcceptedTrack · Pricing & Monetization4 min read
Pricing on Value Metrics Cuts Churn Up to 75%, ProfitWell Data Shows
Value-metric pricing cuts churn up to 75% versus feature tiers, with outcome-based metrics adding another 40% cut, according to ProfitWell CEO Patrick Campbell.

Context
Value metrics deliver up to 75% less churn than feature-differentiated pricing, per ProfitWell CEO Patrick Campbell.
Outcome-based value metrics reduce churn by an additional 40%.
Value metrics generate at least 30% more expansion revenue; outcome-based models reach nearly 50%.
Per-user pricing is the most common SaaS pricing model despite rarely aligning with value, per the Pacific Crest Survey.
A valid value metric must be understandable, aligned with received value, and grow with usage.
Value-metric pricing cuts churn by up to 75% compared with feature-differentiated pricing, and outcome-based value metrics strip out a further 40%, according to Patrick Campbell, CEO of ProfitWell. For expansion revenue, the gap is just as stark: value metrics deliver at least 30% more expansion revenue than feature-based tiers, and outcome-based metrics push that to nearly 50%. Those numbers are the strongest argument available for rebuilding your pricing around what customers actually consume.
A value metric is the unit in which you measure the exchange of value in your product. It is the linchpin of a product-led go-to-market strategy because it aligns your revenue model with your acquisition model. Concretely:
- Wistia, a video platform, could price on the number of videos uploaded.
- Slack could price on messages sent — and in practice prices per active user.
- PayPal could price on the amount of revenue it generates for customers.
What are the two types of value metrics?
Campbell splits them into two families. Functional value metrics price on a function of usage, such as per user or per 100 videos. Outcome-based value metrics price on the result itself: how many views a video received, or how much money you made your customer.
Outcome-based pricing performs best on the data, but most teams cannot use it. Measuring exactly how much money a customer gained, or what the time you saved them is worth, is often technically impossible. The practical lesson is to get as close to the customer's realized value as your instrumentation allows.
Value metrics also answer two questions product managers already own: what does the ideal customer want from a product like ours, and how much are they willing and able to pay? They explain why free users stay free, and why paying users downgrade. They complement — not replace — customer lifetime value and customer acquisition cost.
What makes a good value metric?
Campbell's test has three conditions, and a candidate metric must pass all of them:
- Easy for the customer to understand. A visitor to your pricing page should immediately know what they are paying for and where they fit. If not, pick another metric.
- Aligned with the value received. A live-chat vendor tracks conversations; a churn-prevention vendor tracks automated recovery emails sent and revenue saved. Many teams measure this internally with product-qualified leads (PQLs), users who have demonstrated readiness to buy through usage.
- Grows with usage of that value. Charge more when customers get more value, less when they do not. Slack's fair billing policy — you pay only for active users — is the canonical example.
In established markets, check how competitors charge. Email marketing tools mostly price on contact count, so contacts is a defensible metric there. In emerging categories like AI, you need a data-driven discovery process instead.
Why does per-user pricing fail?
Per-user pricing is the most common trap, and the Pacific Crest Survey found it remains the most common pricing model despite the damage. Campbell said: "The reason per-user pricing kills your growth and sets you up for long-term failure is that it's rarely where the value is ascribed to your product."
Charging per user discourages sharing the product across a team, which throttles the very expansion a product-led motion depends on. Slack is the exception because messaging has network effects — more users make the product more valuable. Conditions where per-user pricing does make sense include differentiated per-user value (LinkedIn Recruiter), a standardization requirement (Salesforce), network effects (Slack), buyers who need budget predictability (DocuSign), less sophisticated buyers (Evernote), and commoditized usage metrics (GitHub).
Campbell also explained why bad pricing persists: "It's counterintuitive, but because pricing touches on every single part of your business, it's often ignored. That's because it's at the intersection of marketing, sales, and product — so nobody in the organization owns it."
How do you find and validate your metric?
Start with subjective analysis. List every candidate metric, then run each through Campbell's three-condition scratchpad. If nothing passes, keep brainstorming before touching pricing. Then validate with data. Segment your users into churners, minimal users, power users, and high-LTV users, and compare behaviors:
- What do best customers do regularly, and never do?
- Which features did they try first in onboarding?
- What demographics, team structure, or ability predicted success?
- For churned users: which activities and outcomes differed, and were they even in your target market?
Segmentation carries a real tradeoff: optimizing onboarding for perfect-fit customers may lower your signup-to-activation rate while raising free-to-paid conversion. That is usually the right trade.
Finally, stress test with a relative preference analysis — a statistical method that forces respondents to choose the most and least preferred pricing dimensions, such as analytics versus premium support versus SSO. A scratchpad reflects your judgment; preference analysis reflects your customers'. Campbell's Chapter 6 of The Product-Led Playbook then covers turning the metric into a pricing matrix and setting the actual price.
Small companies can test several hypotheses and get the metric wrong first; the failure mode is never testing at all. As pricing ownership continues to migrate from sales into product teams, the PMs who can instrument customer value — not just feature usage — will set the packages everyone else copies.
via paddle.com (Original)
More from Marcus Bennett
Show full bio
Market editor covering regulation, policy and their impact on product management at Roadmap File.
44 articles