Value Metric Examples for SaaS Pricing

A value metric is the unit your pricing is based on. It determines how a customer's bill changes as they use more of your product. Common value metrics include users or seats, contacts, projects, API calls, transactions and storage. A customer on a per-user plan pays more as they add people; a customer on a per-contact plan pays more as their database grows.

Choosing the right value metric is one of the most consequential pricing decisions a SaaS company makes. A good one makes pricing feel fair, because customers pay more only when they get more. It supports expansion revenue, because successful customers naturally grow into higher bills. And it aligns the company's growth with customer success. A poor choice can discourage adoption, push customers to find workarounds or leave significant revenue unclaimed. This article explains what makes a good value metric, walks through common options with their fits and risks, and explains how to choose, test and change one.

As an example, we will follow the founders of a company that sells a customer support platform to online businesses. They currently charge per support agent, but they are questioning whether that is the best fit.

What makes a good value metric

A good value metric is aligned with value. As the metric increases, the customer should be getting more value from the product. If customers can get much more value without the metric changing, or if the metric grows without delivering more value, pricing feels disconnected from what customers care about.

It is easy to understand. Customers should be able to predict what they will pay. A metric that requires a calculator or a technical explanation creates uncertainty and slows buying decisions.

It grows with customers. Successful customers should naturally use more of it over time, which creates expansion revenue without the company needing to push upgrades.

It is measurable. You need to track it accurately and transparently, so both you and the customer can see usage and understand bills.

And it is hard to game. Customers should not be able to avoid paying more while still getting more value, for example by sharing logins or deleting data.

No metric is perfect on every criterion. The goal is to find the one that balances them best for your product and customers.

Users or seats

Pricing per user or seat charges for each person with access to the product. It fits collaboration tools, CRMs, design tools and other products where value grows with the number of people using them. It is simple to understand and predictable, and it grows as customer teams grow.

The risk is that customers limit seats to save money. They may restrict access to a few people, share logins or avoid inviting colleagues who would benefit. That reduces adoption and can make the product less valuable, which increases churn risk. Per-seat pricing can also feel unfair for products where most value comes from a few power users while many others need only occasional access.

For the customer support platform, per-agent pricing has a clear logic, since more agents handle more tickets. But the founders notice that some customers keep agent counts artificially low, routing tickets through a few accounts, which hides the product's real usage and limits expansion.

Active users

Pricing per active user charges only for users who actually use the product during a billing period. It fits products where usage varies across teams, so customers can invite many people without paying for those who rarely log in. It encourages broad adoption, since there is no penalty for inviting someone who might only use the product occasionally.

The risk is that costs become harder to predict. Customers may not know in advance how many people will be active in a given month. Clear definitions of what counts as active, and caps or alerts, help manage this.

Contacts or records

Pricing by contacts or records charges based on the size of the customer's database. It fits email marketing tools, CRMs and customer data platforms, where the number of contacts is a reasonable proxy for the scale of the customer's business and the value they get.

The risk is that customers delete data to save money, sometimes removing contacts who could have been valuable. Some customers also feel penalized for growing their audience. Pricing that counts only active or engaged contacts can address this, though it adds complexity.

Usage volume

Pricing by usage volume charges for how much of the product's core function the customer uses, such as messages sent, emails delivered, API calls or transactions processed. It fits infrastructure products, communication tools and other products where usage directly corresponds to value delivered.

Usage-based pricing aligns cost with value closely and lets customers start small. The risk is unpredictability. Customers may worry about unexpected bills, especially if usage spikes. Clear pricing tiers, usage alerts, spending caps and committed-use discounts help address that concern.

Projects, workspaces or entities

Pricing by projects, workspaces, locations or other entities charges for the number of distinct units the customer manages. It fits agency tools priced per client, multi-location businesses priced per location and project tools priced per active project.

This metric is often easy to understand and maps well to how customers think about their business. The risk is that customers combine entities to save money, such as putting several clients into one workspace, or that the metric does not reflect very different sizes of entity.

Outcomes or value delivered

Some companies price based on outcomes, such as revenue processed, leads generated or resolutions achieved. This aligns pricing very closely with value, which can be compelling. The risk is complexity and disputes. Outcomes can be hard to measure, attribute and agree on, and customers may resist paying a share of value they feel they created themselves.

Feature-based tiers

Some companies use flat tiers that differ by features rather than a single scaling metric. Customers pay more to unlock advanced capabilities. Feature tiers are simple and predictable, but on their own they do not grow with customer usage, which limits expansion. Many companies combine feature tiers with a value metric, such as tiers that each include a certain number of users or contacts.

How to choose a value metric

Start with how customers get value. Ask what increases when a customer gets more from the product. Interviews with your best customers, usage data and analysis of which customers expand and which churn all help answer this.

Then test candidate metrics against the criteria. Is the metric aligned with value? Can customers predict their costs? Does it grow naturally as customers succeed? Can you measure it accurately? Can customers game it?

Look at how competitors price, not to copy them but to understand buyer expectations. If every competitor prices per user and you price per outcome, buyers will need more explanation. That can be a point of differentiation, but it requires clear communication.

Consider your customers' budgets and buying processes. Larger customers often prefer predictable costs for budgeting, while smaller customers may prefer to pay only for what they use.

For the customer support platform, the founders analyze their data and find that the number of resolved conversations correlates more strongly with customer value and expansion than the number of agents. They consider pricing by resolved conversations, with tiers and caps to keep costs predictable, and unlimited agents so customers have no reason to restrict access.

Test before switching

Changing a value metric is a significant decision, so test it before committing. Model how the new metric would affect existing customers' bills, identifying who would pay more, who would pay less and by how much. Talk to customers and prospects about the new approach and listen for confusion or concern. Consider offering the new pricing to new customers first, or as an option alongside the old pricing, before migrating everyone.

Change value metrics carefully

If you change your value metric, plan the transition carefully. Communicate clearly and early with existing customers, explaining the change, the reasons and how it affects them. Consider grandfathering existing customers on their current pricing for a period, or offering transition discounts. Make sure billing systems, usage tracking and invoices reflect the new metric accurately. Train sales and support teams to explain it.

Pricing pages and content need updating too. Buyers often research how pricing works before they talk to sales, and clear explanations of your value metric, including pages that answer the cost questions buyers search for, help them understand it before the first conversation. That kind of pricing content is something our SEO growth service builds for SaaS companies.

Avoid the common mistakes

The mistakes in choosing value metrics are predictable. Companies choose metrics that are easy to bill but disconnected from value. They choose metrics customers cannot predict. They choose metrics that discourage adoption, such as strict per-seat pricing for products that benefit from broad access. They ignore gaming and workarounds. They copy competitors without considering their own product's value. They change metrics without modeling the impact on existing customers. And they fail to communicate changes clearly.

Bringing it together

A value metric is the unit your pricing is based on, and the right one aligns what customers pay with the value they receive. Good value metrics are aligned with value, easy to understand, grow with customers, measurable and hard to game. Common options include users or seats, active users, contacts or records, usage volume, projects or entities, outcomes and feature-based tiers, each with its own fit and risks. Choose by understanding how customers get value, testing candidate metrics against clear criteria and modeling the impact before switching. For the customer support platform, moving from per-agent pricing toward resolved conversations, with unlimited agents, removes the incentive to restrict access and ties revenue more closely to the value customers actually receive.