Pricing density is how consistent the value of a value metric is from one unit to the next and from one customer to the next. A dense metric carries roughly the same value in every unit. A thin one hides a long tail, where a few units carry most of the value and the rest carry almost none. It is also called value density, and it is the “Consistent” test in Potio’s value metric filters.
A dollar processed through Stripe is worth the same to the merchant as the next dollar, which is why a percentage take rate sells with almost no argument. Compare a clinical software vendor charging $5 per patient record. An oncology case justifies that hundreds of times over. A routine checkup does not, and nobody can tell which is which before the record is processed.
Potio’s take: If you sell a usage model, pricing density decides whether deals close cleanly or get negotiated down every time. Low density does not show up as churn. It shows up as customers distorting their own workflow to avoid the meter, then asking for a discount anyway. The fix is structural, never just a lower unit price.
The tell is always the same: buyers game the input. With a per-record fee, hospitals stop digitising low-value records and keep a paper system alongside. With $2 per work order, dispatchers bundle unrelated jobs onto one ticket. With $0.10 per page for legal documents, firms strip boilerplate appendices before upload. The product gets less useful, the data gets worse, and the discount request arrives regardless.
Density also varies between customers. An event worth $1 to one customer and $1 million to another has no single right price. Set it high and you sell only to the big account, which still gets a bargain. Set it low and you leave most of the value on the table.
Each structural fix costs something:
| Fix | How it works | What it costs you |
|---|---|---|
| Banding | Volume grouped into stepped brackets | Customers hold usage just under each threshold |
| Prepaid credits | Different actions draw different credit amounts | Procurement may read credits as hidden markup |
| Minimum commitment | A floor that guarantees margin on small accounts | Slows trials and first deals |
| Platform fee plus usage | Fixed base for access, usage for growth | Buyers can resent paying for both |
| Spend caps | A contractual ceiling on the bill | You absorb spikes instead of the customer |
When none of those fits, the metric itself is wrong. Infrastructure vendors that sell raw compute price like a petrol station, charging the same whether the fuel goes into a Volkswagen Beetle or a Ferrari. Capturing the Ferrari’s value means moving to a metric tied to the customer’s own business.
Value density is how much value one unit of usage carries, and how much that varies across customers. Usage pricing works best when a unit is worth roughly the same to everyone who buys it.
Watch customer behaviour. Workarounds that reduce the billed number, such as batching, stripping data or bundling tickets, combined with repeated discount requests, are the clearest sign.
Partly. Credits, bands, commitments, platform fees and caps all soften it, each at a cost. If the spread in value per unit is extreme, a different metric is usually the only real fix.
More on this: SaaS Value Metric: How to Find the Right One
I'm a 3x founder and former CEO of Toggl. I work hands-on with SaaS & AI teams to fix pricing, packaging and monetization.
Book a call