TL;DR
- The value metric is the unit on which price scales. If that unit is wrong, even a smart price point will still feel arbitrary.
- The fastest useful test is the Value Metric Trinity: does the metric scale with value, stay easy to understand, and feel predictable to the buyer?
- Most failures are structural, not cosmetic: the metric discourages rollout, creates budget anxiety, or rewards the wrong customer behavior.
- Choose the metric first, then decide whether the right architecture is flat-rate, per-seat, usage-based, tiered, or hybrid.
Most SaaS pricing teams spend too much time on the number and not enough time on the unit.
Should the plan be $49 or $79? Should annual billing get a discount? Should enterprise be quote-only? Those questions matter, but they are downstream. The deeper question is: what exactly are customers paying more for as they get more value?
If your product creates more value as more people collaborate, a seat-based metric can make sense. If value rises with API calls, transactions, or records processed, usage or transaction-based pricing may be more honest. If the product stays roughly the same in value no matter how many people touch it, forcing a per-seat model into place can quietly damage adoption and expansion for years.
"You can set the perfect price on the wrong metric and still lose."
— ProductQuant pricing workbook
That is why value-metric selection belongs before packaging polish. A bad metric creates negotiation, rollout friction, and customer distrust even when the page copy looks clean. A good metric makes expansion feel normal because the bill rises when the customer's value rises too.
The Value Metric Trinity
The repo source material keeps returning to 3 tests. They are simple enough to use in a workshop and hard enough to expose bad assumptions quickly.
| Test | What good looks like | Failure signal |
|---|---|---|
| Scales with value | When the customer gets more value, the bill rises for a reason the buyer can defend. | The metric grows while customer value stays flat, or customer value grows without any pricing upside. |
| Easy to understand | A buyer can explain the metric to finance in one sentence. | The model needs a calculator, caveats, or repeated sales explanation to feel fair. |
| Predictable for the buyer | The customer can forecast cost well enough to budget against it. | The metric creates bill shock, procurement anxiety, or internal pressure to limit usage. |
Most weak pricing models fail one of these tests. Per-seat pricing often fails the first test when the product is effectively single-player. Pure usage pricing often fails the predictability test when customers cannot estimate future consumption. Outcome pricing can fail the clarity test if the outcome is hard to define or easy to dispute.
If the model is structurally wrong, the team usually compensates with discounts, exceptions, or plan sprawl. None of those fix the original mismatch.
5 Common Metric Patterns and What They Assume
The point is not to memorize 12 textbook variants. It is to understand what each metric assumes about the product underneath it.
Per seat
This works when the product is collaborative enough that more users create more value. Slack and many team workflow products fit this logic. The failure mode is charging by seat on a tool where one admin does most of the meaningful work and everyone else is peripheral.
Usage-based
This works when consumption is measurable and tightly connected to value. Stripe's billing documentation and many infrastructure tools are useful examples of systems designed to support variable consumption. The failure mode is turning usage into a billing event before the customer can forecast it with confidence.
Per contact or record
This can work for CRM and marketing systems where database scale reflects business scale. HubSpot's marketing-contacts pricing is a good example of pricing on a unit the buyer already understands. The failure mode is charging for stored objects that do not really reflect value, like stale records or inactive contacts.
Flat-rate
Flat pricing can be strategically correct when simplicity is part of the value proposition. It is not automatically unsophisticated. The tradeoff is obvious: the easier the model is to buy, the more likely you are to undercapture value in larger accounts unless the product itself stays relatively uniform.
Hybrid
Hybrid models make sense when one metric prices access and another prices scale. They are strongest after the primary value logic is already clear. They are weakest when they are used to paper over uncertainty by charging on multiple axes "just in case."
Choose the value metric before choosing the pricing model.
The model architecture should express the underlying metric, not invent it. If your team is debating tiers, seats, or usage before the value unit is clear, start further upstream.
How to Pick the Right Metric
A usable selection process is narrower than most teams think.
- List realistic candidates. Start with the 5 to 8 metrics that could plausibly fit the product. If a metric obviously breaks buyer understanding or product behavior, do not keep it in the room for politeness.
- Score against the Trinity. Use the 3 core tests first, then add adoption risk and expansion potential as secondary modifiers.
- Pressure-test failure modes. Ask what the metric would encourage customers to do. Good metrics reinforce healthy product behavior. Bad metrics encourage gaming, seat hoarding, or suppressed usage.
- Validate with customers. Ask whether the metric feels fair, forecastable, and connected to value. Do not settle for "I guess that works." Look for clear acceptance or clear friction.
- Match the model to the metric. Only after the metric survives should the team decide whether the architecture is flat, tiered, seat-based, usage-based, or hybrid.
| Score range | Interpretation | Recommended move |
|---|---|---|
| 13-15 | Strong fit across the Trinity | Validate with customers and move into packaging design. |
| 10-12 | Plausible but uneven | Address the weak dimension before locking the model. |
| 7-9 | Weak fit | Test an alternative metric or a narrower segment-specific version. |
| Below 7 | Structural mismatch | Reject it and restart from the value event, not the pricing page. |
What Usually Goes Wrong
The metric prices access instead of value
This is the classic seat-pricing mistake on a product that is valuable to one operator but visible to many stakeholders. The company bills on the visible count because it is easy, not because it is economically honest.
The metric punishes adoption
A metric can look elegant in a spreadsheet and still create the wrong customer behavior. If every additional user, workflow, or event feels like a penalty, the customer starts optimizing for a lower bill instead of a better outcome.
The metric is impossible to forecast
Some buyers can live with variable spend. Many cannot. If finance or procurement cannot estimate next quarter's cost well enough to trust it, the model becomes a buying-motion problem even when the product value is real.
The metric is copied from the category leader
This is usually the most expensive shortcut. A category leader may have a more collaborative product, a different buyer, stronger network effects, or better tolerance for complexity. Copying the visible pricing model imports all of those hidden assumptions for free.
What to Do After Choosing the Metric
The metric decision is not done when the team picks a winner in a workshop. It is done when the chosen metric survives reality.
- Run customer interviews. Ask whether the metric feels fair, whether spend feels controllable, and whether paying more really means getting more value.
- Compare against expansion data. Check whether the metric rises in healthy accounts at the same time retention and expansion rise.
- Design packaging around the metric. Plan tiers, fences, and enterprise logic only after the core unit is proven.
- Document the anti-patterns. Note the conditions under which the chosen metric becomes dangerous so the team does not forget them during sales pressure.
If the metric is still fuzzy, do not start redesigning the pricing page.
The clean next move is a pricing audit that forces alignment between product structure, expansion logic, and the unit the bill will scale on.
FAQ
What is a value metric in SaaS pricing?
The value metric is the unit on which price scales. Seats, usage, contacts, transactions, and flat subscription tiers are all ways of converting product value into a billing axis.
How do I know if a value metric is wrong?
The strongest signals are buyer confusion, forecast anxiety, pricing workarounds, slow rollout, and expansion that depends on negotiation instead of naturally increasing with value.
Should we choose the same metric as our competitor?
Only if the product structure is genuinely similar. Copying a category leader's metric imports its assumptions about collaboration, usage, and buyer tolerance whether they fit your product or not.
Can hybrid pricing be the right answer?
Yes, but only after the primary value metric is clear. Hybrid models work when one component prices access and another prices consumption or scale, and both are still understandable to the buyer.
Sources
About the Author
Jake McMahon writes about pricing strategy, product structure, and the systems underneath growth decisions in B2B SaaS. ProductQuant helps teams separate pricing-page tweaks from structural pricing problems that are really about value delivery, adoption, and expansion.
Pick the metric that makes expansion feel earned, not negotiated.
When the bill rises on the same axis as customer value, pricing gets simpler to explain, easier to forecast, and harder for the team to undermine with exceptions.