If you asked most founders or product leaders to write down their pricing model, they'd give you something like: "we charge per seat, $50 per user per month." If you pushed them on why per seat, the answer is usually: "it's standard," or "it's easy to understand," or "Salesforce charges per seat."

Per-seat pricing is not a strategy. It's a default. And like most defaults, it works until it doesn't — and then it creates problems that are very hard to fix without changing the metric, which is painful and expensive.

Your price metric is the unit you charge on: per user, per action, per unit of output, per outcome, per month, per contract. This is one of the most consequential decisions in monetization design, and it is the one that gets the least deliberate attention. Most companies inherit their metric from convention, from a competitor, or from whatever was easiest to implement in the billing system two years ago.

That matters because the metric shapes everything.

The Per-Seat Trap

Per-seat pricing is the default because it's predictable and it maps to a plausible proxy for value. More users equals more value — usually. It makes quota math clean. It makes renewal conversations straightforward. It scales with the customer.

The trap is that per-seat pricing decouples revenue from value delivery. A customer pays the same whether they have ten active users or ten users who do nothing. The metric doesn't track usage or outcomes. Over time, this creates the "ghost user" problem: customers paying for seats they don't use because they forgot to offboard someone, or because they don't want to have the conversation about reducing spend.

The ghost user problem is a packaging failure and a metric failure simultaneously. It's a metric failure because the metric doesn't create an incentive for the customer to optimize their seat count. It's a packaging failure because there's no easy self-serve mechanism for the customer to reduce their plan as their usage changes.

Per-seat pricing also creates perverse product incentives. If revenue is per seat, the product team has a financial incentive to make the product worse for individual contributors and better for the managers who hold the budget. More managers, more seats. More seats, more revenue. The product gets shaped around the buyer, not the end user.

None of this means per-seat is wrong. It means per-seat has specific tradeoffs that need to be understood and managed, not defaulted to.

How to Choose Deliberately

The choosing process is straightforward in theory but rarely done in practice.

Start by listing every unit that correlates with value delivery in your product. This is not "things we could meter" — it's "things that actually track whether the customer is getting value." Usually there are two or three plausible candidates.

For each candidate, ask: what customer behavior does this create? If we charged on this unit, what would a rational customer do? Would they optimize for it in a way that helps or hurts both parties?

Then ask: what does this metric cost us to serve? Is there a rough correlation between the unit and our cost structure, or are we pricing blind to our own economics?

Then ask: can the buyer explain this to procurement? This is an underrated test. If your enterprise buyer cannot put this metric in a budget justification document without a paragraph of context, you have a sales friction problem that will cost you deals.

The metric you choose will shape the company for years. It will show up in your revenue model, your product roadmap, your sales playbook, and your customer success methodology. Choose it like it matters — because it does.