Usage-based pricing
Usage-based pricing applies a price rule to measured consumption; the billing quantity, customer-value evidence, delivery cost, and accounting treatment remain separate questions.
The operating requirement is a reproducible meter with identity, source events, period, corrections, exclusions, pricing version, and dispute path. A disputed invoice can reflect metering, mapping, pricing, contract, presentation, or customer-understanding problems; investigate before assigning a cause.
Minimum commitments, tiers, credits, caps, and overages are design options rather than universal requirements. Choose them from customer fit, economics, cash exposure, capacity, risk, and forecast needs, then test actual behavior against the declared model.
Where it breaks
Usage revenue is annualised from a peak month, so ARR describes a level the base has never sustained.
Related terms
- Unit Map
- The Unit Map distinguishes how the customer evaluates benefit, how price is calculated, what is billed, what the customer may access, and what drives delivery work.
- Annual recurring revenue (ARR)
- ARR is the annualized value of contracted recurring revenue at a point in time, a management metric, not a GAAP one.
- Revenue model
- A revenue model is the mechanism by which value delivered converts into money received, subscription, consumption, transaction fee, licence, service, or a defined combination.
- Expansion revenue
- Expansion revenue is additional revenue from existing customers through seat growth, tier upgrade, usage increase or new product attachment.
Field notes on this
- Your pricing is a list, not a logic
A price list says what things cost today. It cannot say what to charge the deal in front of you, which is why realised price drifts and nobody owns the drift.