When I talk to early-stage SaaS founders about pricing, the conversation almost always goes the same way. I ask how they charge, and they say "per seat." I ask why, and they say "because that's how everyone does it."
That is the wrong reason to pick a pricing metric. And in a surprising number of cases, it is quietly capping your revenue growth without you realizing it.
What a value metric actually is
A value metric is the unit you charge for. Seats. API calls. Contacts. Invoices. Gigabytes. Revenue processed. It is the answer to the question: what increases as your customers get more value from your product?
The reason this matters more than most founders think is that your value metric determines how your revenue scales with your customers. Pick the right one and your MRR grows automatically as customers succeed. Pick the wrong one and you are leaving most of the value you create on the table.
Three tests a good value metric must pass
Before you settle on a metric, run it through three questions.
First: does it scale with the value the customer gets? If a customer goes from managing ten projects to managing a hundred, and your product saves them more time and money as a result, does your metric capture that? Per-seat pricing would only capture it if they added team members. If the value scales independently of seats, you are leaving revenue behind.
Second: can the customer predict their bill? A metric that creates anxiety is a metric that creates friction. "Per API call" sounds logical until a prospect's engineering team realizes they cannot estimate next month's invoice. Predictable does not mean flat — it means the customer can see the relationship between their usage and their cost and plan accordingly.
Third: does it get easier to justify as the customer grows? The best value metrics have a natural story: as you get more value, you pay more. If a customer has to explain to their CFO why they are paying more this quarter, you want that explanation to be self-evident. "We processed 40% more revenue through the platform, so the fee went up" is a much easier conversation than "we added three users."
The per-seat trap
Per-seat pricing is the most common SaaS model for a simple reason: it is easy to implement and easy to explain. But simple and optimal are not the same thing.
The core problem with per-seat pricing is that it conflates users with value. For some products — project management tools, communication software, code editors — value genuinely does track with headcount. Every additional person who has access creates additional value. In those cases, per-seat pricing is correct.
But for a lot of products, value scales along a completely different axis. If you build invoicing software, the relevant axis is invoices processed, not accountants logged in. If you build analytics software, it is data volume or events tracked. If you build a sales tool, it is contacts reached or deals managed.
When you charge per seat for a product where value scales differently, you are creating a ceiling for yourself. Your best customers — the ones getting the most value — are not paying proportionally more. You are essentially giving away your highest-value usage for free.
There is also a secondary problem: per-seat pricing gives customers an incentive to consolidate. If five sales reps are sharing one login to avoid paying for five seats, you already know the product is valuable enough to use — you just made it easy for them to undermine your revenue.
Common alternatives and when to use them
Usage-based pricing ties charges to a unit of consumption: API calls, emails sent, events tracked, rows synced. This works well when usage is measurable, when value clearly scales with that usage, and when customers can predict their consumption with reasonable accuracy. The risk is unpredictable bills — mitigate it by publishing usage calculators and offering commitment discounts for high-volume customers.
Outcome-based pricing — a percentage of revenue generated, or a fee per transaction — is the strongest alignment with customer value. If your product directly drives revenue or saves a quantifiable amount, charging a fraction of that outcome is often the most defensible model. The challenge is that it requires either trust or technical integration to verify the outcome. This model works best when you can instrument results directly rather than relying on self-reporting.
Feature-tiered pricing keeps the model simple and predictable but separates customers by what they need rather than how much they use. It works well when different customer segments have genuinely different requirements and when usage patterns are hard to measure. The risk is that you price features incorrectly and inadvertently put high-value features in the wrong tier, either blocking adoption or giving away capabilities that should be premium.
The decision framework
Here is the simplest version of the framework I use when working through this with founders.
Start by answering one question: what does a customer have more of when they are getting significantly more value from your product?
If the answer is "more users," per-seat pricing is probably right. If the answer is "more of some measurable action" — calls, transactions, data volume, contacts — usage-based pricing is likely stronger. If the answer is "they have unlocked certain capabilities they did not have before," feature-tiered pricing may fit. If the answer is "they are making more money or saving more money," a revenue-share or outcome-based model deserves serious consideration.
Once you have a hypothesis, pressure-test it against the three questions above. If it fails any of them, keep iterating. Do not go live with a metric just because it is familiar or because your biggest competitor uses it.
How to validate before you commit
The fastest way to validate a value metric is to talk to your five best customers and ask them how they would explain the cost to their team. The language they use naturally will point you toward the right metric. If they say "we pay based on how many invoices we run through it," they are already thinking in usage terms. If they say "we pay for our team to have access," they are thinking in seat terms.
The second test is correlation. Pull your customer data and check whether the customers paying the most are also the ones who report the highest value or show the strongest retention. If your highest-paying customers are churning and your lowest-paying ones are your most engaged, your metric is backwards. The customers who are getting the most value should be the ones paying the most.
Your first metric is not permanent
Most companies change their pricing model at least once in the first three years. The goal right now is not to find the perfect metric — it is to find one that aligns with how your best customers describe the value they get, and then watch whether it actually tracks their success.
If you find that your happiest, most engaged customers are not paying proportionally more than your least-engaged ones, that is a clear signal your metric is wrong. Fix it before it becomes a structural constraint on your growth.
Pricing is not a one-time decision and your value metric is not a permanent identity. It is a hypothesis about how your customers experience value. Test it. Refine it. And if the data says you got it wrong, change it before the wrong metric locks you into a growth ceiling you built yourself.