I made the same mistake every SaaS founder makes. I priced per user because that's what everyone else does.
It felt obvious. Simple to explain. Easy to implement. One user, one price. Stack them up as you scale.
Then I ran my first real pricing analysis and felt sick. We had enterprise customers deriving massive value from our product—thousands in outcome value per month—paying us the same as a freelancer with two team members. And when those enterprises tried to add a third seat, they pushed back hard. Not because they couldn't afford it, but because the metric didn't make intuitive sense to them.
That's when I learned about value metrics—and why Patrick Campbell (founder of ProfitWell) was right when he said 8 out of 10 companies using per-user pricing should be using something else entirely.
What Is a Value Metric, Really?
Your value metric is the unit you charge for. It's not your pricing page—it's the economic engine underneath it. It answers one question: what happens in your product that makes customers feel they've gotten their money's worth?
Per-user pricing is a proxy value metric. You're not actually selling seats—you're selling outcomes: saved hours, closed deals, resolved tickets, published articles. Seats are just an easy-to-count stand-in.
The problem with proxies: they decouple over time. A customer with five power users extracting enormous value pays the same as a customer with five casual users who barely log in. Churn becomes a mystery. Expansion revenue becomes a fight. And the customers extracting the most value feel no natural pressure to upgrade.
The Three Criteria for the Right Value Metric
Before you can pick your value metric, you need to stress-test candidates against three things.
Value alignment. Does the metric grow as the customer's success grows? If a customer gets twice the value from your product next quarter, should they naturally expect to pay more? If yes, your metric is aligned. If the answer is 'well, they'd probably add more users,' you're using a proxy.
Simplicity. Can your customer explain your pricing to their CFO in one sentence? 'We pay per API call' is simple. 'We pay per active workspace collaborator, excluding read-only viewers' is not. Complexity breeds friction at renewal time.
Measurability. You need to track it reliably—and so does your customer. If they can't self-monitor their usage, you'll get surprised support tickets every billing cycle.
How to Find Your Value Metric in Five Days
Here's the process I'd run if I were starting over.
Days one and two: map the value moments. List everything that happens in your product that a customer cares about. Not features—outcomes. Email sent. Report generated. Deal closed. Ticket resolved. For a cost-analysis tool, it might be: cost comparison run. Not the user who ran it, but the action itself.
Days three and four: interview five customers. Ask them: 'If you were explaining our pricing to your CFO next week, what would you say you're paying for?' The answer they give—not the answer you want them to give—is your value metric. Most founders skip this step and wonder why their pricing feels wrong.
Day five: score your candidates. Take your top two or three options and rate them one to five on alignment, simplicity, and measurability. The highest total score is your metric to test.
The most common outcomes: B2B productivity tools discover they should price per outcome (projects completed, reports run, campaigns sent) rather than per seat. Infrastructure tools find usage-based beats flat-rate. Vertical SaaS often discovers that per-location or per-revenue-band makes more intuitive sense than per-user.
The Revenue Math Is Not Subtle
Companies that identify and implement the right value metric see 10 to 20 percent faster revenue growth on average, according to pricing research from Pace Pricing and Chargebee's benchmark data. That's not from acquiring new customers—it's from better aligning existing revenue with value delivered.
The math is simple: if your top customer is extracting $10,000 per month in value and paying you $500 per month, you have a revenue ceiling problem, not an acquisition problem. The right value metric lets expansion revenue happen naturally through usage, rather than through awkward 'can we talk about your contract' calls.
There's also a retention effect. When customers feel like they're paying for what they get—not for a headcount that might not all use the product—churn drops. The unit that generates value is the unit on the invoice. That's a fundamentally cleaner customer relationship.
The Transition Question Everyone Asks
What about existing customers? Do you grandfather them or migrate them?
Grandfather the bottom 20 percent of accounts—low-revenue, high-noise—for 12 months. Migrate everyone else with a clear explanation of why the new pricing better reflects the value they're getting. Most customers, when you explain that the old metric was misaligned with the outcomes they're achieving, respond better than you expect. Especially if you show them the data.
The mistake is not communicating. Silent pricing changes feel like bait-and-switch. Explicit conversations about value feel like a mature vendor relationship.
One Decision, Outsized Impact
Pricing is the highest-leverage, lowest-cost growth lever you have. A 10 percent improvement in your pricing strategy produces the same revenue impact as a 10 percent improvement in acquisition—at a fraction of the effort. But almost no early-stage SaaS company spends more than a few hours on pricing before launch. They default to per-user because that's what the last ten SaaS products they used charged.
If you're pre-product-market-fit, pick a value metric now based on your best hypothesis and revisit it at 100 customers. If you're post-PMF with decent MRR, run the five-day process above and A/B test new pricing on incoming signups for 60 days before migrating.
The goal isn't perfect pricing. The goal is pricing that grows with your customers—and pushes them to succeed, because when they do, you do too.