Definition
Usage-based pricing charges customers based on consumption (for example API calls, GB processed). It can align price with value but can increase revenue variability.
How to use it
- Use clear value metrics and predictability guardrails (caps, tiers).
- Track retention and expansion by cohort; bill shock can increase churn.
Measured as
Measure Usage-based Pricing on the same customer segment, time window, and revenue basis each time you review it.
Operator takeaway
- Use clear value metrics and predictability guardrails (caps, tiers).
- Track retention and expansion by cohort; bill shock can increase churn.
- Keep Usage-based Pricing consistent by cohort, segment, and period before you use it as a decision signal in planning or reporting.
- Interpret the metric alongside retention, margin, or payback so one ratio does not hide the real operating trade-off.
Next decision
- Read Pricing guardrails: payback-based minimum price and max discount if the decision depends on interpretation, policy, or trade-offs beyond the raw formula.
- Decide whether Usage-based Pricing is a growth, retention, or efficiency signal before you set targets around it.
Where to use this on MetricKit
Guides
- Pricing guardrails: payback-based minimum price and max discount: A practical guide to pricing guardrails: compute minimum ARPA (or max discount) from CAC, margin, and a target payback to avoid breaking unit economics.
- Unit economics hub: CAC, LTV, payback, and runway (a practical stack): A practical hub for unit economics: CAC, fully-loaded CAC, LTV, payback, margin impacts, burn multiple, and runway planning.