Quick Research Snapshot

A tight, one-dollar orientation on a topic: what is broadly established, the numbers people quote and how much to trust them, the common misconception, and the three questions worth actually researching. Sized to drop into a larger deliverable.

A Markdown snapshot under 350 words containing: (1) an opening line on the knowledge-cutoff constraint, flagging if the topic is a poor fit; (2) 'What is broadly established' with four to six bullets; (3) 'Figures people cite' with two or three numbers, each with a high/medium/low confidence marker and a reason; (4) 'Common misconception'; (5) 'Worth actually researching' with three questions and where each would be answered.

_Recalled from training data with a knowledge cutoff and not verified. Pricing-model adoption statistics move quickly and are usually produced by vendors with an interest in the answer, so treat every figure here as a starting point._

## What is broadly established
- Pure usage-based pricing is most common where consumption maps cleanly to a unit the customer already understands — API calls, compute, storage, messages sent.
- Hybrid models (a platform fee plus usage) are the more common enterprise shape, because a pure usage model makes revenue hard to forecast for both sides.
- The hardest migration problem is not technical, it is commercial: existing seat customers experience a move to usage as a price change, whatever the intent.
- Bill shock is the dominant churn risk. Caps, spend alerts and a grandfathering period are the standard mitigations.
- Usage pricing requires metering you can defend in a dispute. Instrumentation that is 'approximately right' becomes a credit request and then a lost renewal.
- Sales compensation usually breaks before the pricing does: quota and commission built around a contract value do not survive a model where revenue arrives later and varies.

## Figures people cite
- **Around 40-50% of SaaS companies now have some usage component.** Confidence: low. The number depends entirely on how 'some usage component' is defined and most published versions come from vendor surveys.
- **Hybrid models show higher net revenue retention than pure seat models.** Confidence: medium on direction, low on any specific multiple. The direction is widely reported; the magnitude is not comparable across sources.
- **Usage adoption is highest in infrastructure and data tooling.** Confidence: medium. Consistent with how the model works, but I cannot give you a current share.

## Common misconception
That usage-based pricing is inherently cheaper for the customer and therefore easier to sell. It is not a discount, it is a transfer of forecasting risk from the buyer to the seller — and buyers with procurement processes frequently prefer a predictable invoice to a lower expected one.

## Worth actually researching
1. **What your own customers' usage distribution looks like.** Only your data answers it, and it determines whether a usage model raises or lowers revenue.
2. **How your three closest competitors currently price.** Their live pricing pages, checked this week — not recall.
3. **What your largest ten accounts would pay under the new model.** A back-test on last year's usage, before you commit to anything.