Usage-Based Pricing for SaaS
Usage-based pricing means the invoice changes with what a customer actually consumes — API calls, tokens, gigabytes, messages, compute minutes — rather than a fixed recurring fee. It is the default model for AI products, developer tools, and infrastructure, and the wrong model for almost everything else.
This cluster separates four questions people collapse into one. Pick the page that matches where you are:
Start here
Should I use it at all?
Usage-Based Billing: What It Is and When to Use It — a scored framework for deciding, the failure modes that arrive after you’ve committed, and how fit maps by product category. No code, no vendors.
What are the actual models?
Consumption-Based Pricing Models for SaaS: The Complete Taxonomy — ten models defined by how they bill, with verified examples from Stripe, Twilio, and Datadog. Includes the graduated-vs-volume cliff, worked in arithmetic, and Datadog’s high-watermark percentile exclusion.
Once you've decided
How does it work under the hood?
Usage-Based Billing for SaaS: How It Works — the five-stage pipeline: capture, ingest, aggregate, rate, invoice. Idempotency keys, aggregation immutability, invoice finalization grace periods, dimension cardinality limits, and the specific ways metering systems lose revenue silently. The most technical page in the cluster.
What should I charge per unit?
Usage-Based Pricing: How to Price SaaS by Consumption — value metric selection, marginal cost, margin targets, tier design, minimums and caps, and why passing token costs through 1:1 makes you a commodity reseller.
Build it or buy it?
Usage-Based Billing: A Practical Guide for SaaS Founders — what it costs to build metering yourself, and how Stripe, Chargebee, Zuora, Metronome, Orb, and Paddle compare on usage billing specifically.
Terminology, settled once
Three terms describe the same model and this cluster uses them interchangeably:
- Usage-based billing — what SaaS companies and developers say
- Consumption-based pricing — what infrastructure vendors say (AWS’s term)
- Metered billing — what billing systems and payment APIs say
The distinction some draw — that “usage” means product activity while “consumption” means infrastructure resources — is semantic, not structural. Pick one term for your own marketing and use it consistently.
What this cluster does not do
It does not treat usage-based pricing as obviously correct. The most successful products in the category — Slack, Notion, Figma — remain per-seat, because their value is a team having access to a shared workspace. If your product’s value comes from availability rather than throughput, the right answer is usually not to meter it.