Answer

What is usage-based pricing?

The idea is simple: price moves with consumption, so a quiet month costs less and a busy month costs more. Done well, UBP removes the friction of buying new seats and turns growth inside an account into natural, predictable revenue expansion.

Start free trial See pricing

Short answer

Usage-based pricing (UBP) is a model where customers pay based on how much they consume, like API calls, gigabytes stored, events processed, or seats actually active. Pure UBP has no fixed subscription, while hybrid UBP combines a flat base with metered overages. The model aligns revenue with the value a customer gets, lowers the cost of adopting a product, and lets accounts expand without a renewal cycle.

Key points

What matters most.

What UBP actually is, the two shapes it takes in practice, and why finance teams either love it or fight it.

Definition

Pay for what you use.

Usage-based pricing charges customers against a measurable unit of consumption: an API call, a gigabyte, an event, a message, a compute minute, or a seat that was active during the billing period. The unit is called the value metric. When consumption rises, the invoice rises. When consumption falls, the invoice falls with it.

Two shapes

Pure UBP vs hybrid.

Pure UBP has no fixed subscription, so a dormant account pays nothing. Hybrid UBP is far more common: a flat platform fee plus metered overages above an included allowance. Hybrid gives finance a predictable floor to forecast against while still letting the invoice scale with real usage.

Why vendors use it

Low entry, high ceiling.

Teams can start with a small bill, prove value, and expand consumption without buying new seats or renegotiating a contract. The friction of adoption drops, and the account can grow silently inside its existing agreement. That removes the renewal cliff that stalls traditional per-seat SaaS.

Why buyers like it

Value aligns with the bill.

A customer that uses the product more pays more, which is intuitive and defensible to their own finance team. A customer that pulls back in a slow quarter sees the invoice drop, instead of paying for seats sitting idle. The vendor only wins when the customer actually gets value, which rebuilds trust that per-seat pricing often erodes.

The hard parts

Forecasting, procurement, bill shock.

Revenue is harder to forecast because the unit of sale is variable. Enterprise procurement wants a fixed PO number, not a meter. And customers hate opening an invoice three times the size they expected, which means every UBP motion needs usage alerts, caps, and clear mid-cycle visibility.

Market shape

The model is already everywhere.

AWS prices by compute, storage, and transfer. Snowflake prices by warehouse credits consumed. Twilio prices per message and per minute. Stripe prices per transaction processed. Each is cited as a market reference, not a comparison to Strkr, and together they show UBP is the default pricing shape for infrastructure and consumption-heavy software.

How UBP works

The anatomy of a usage-based plan.

Every usage-based plan is built from the same handful of parts. The names change between vendors, but the moving pieces are consistent, and once you can read them you can read any pricing page in the category.

Value metric

The unit the meter counts.

The value metric is the single unit the invoice scales with. It should rise with the value the customer gets from the product. Common metrics include API calls, events, messages sent, gigabytes stored, compute minutes, documents processed, or seats active during the period.

Platform fee

The flat base, if any.

In hybrid UBP there is a monthly or annual platform fee that covers access, support, and an included allowance of usage. The fee gives finance a predictable floor and gives procurement a line item it can approve as a traditional subscription. Pure UBP skips the platform fee entirely.

Included allowance

What the base covers.

The number of units bundled into the platform fee before the meter starts charging. A good allowance is set at the median customer consumption so most accounts never see an overage line, and the ones that do are clearly getting outsized value from the product.

Overage rate

The price per unit above the base.

Once the included allowance is exhausted, each additional unit is billed at an overage rate. Rates often tier down with volume so the one-millionth call costs less than the first one above the allowance, which rewards expansion inside the account instead of punishing it.

Commitment tier

Prepaid units for a discount.

Enterprise plans often bundle a committed usage number for a discount off the overage rate. The customer commits to a floor of consumption, the vendor gives up some unit price, and both sides get predictability. Unused commitment typically expires at the end of the term, which is the lever that keeps commits honest.

Metering

The system that counts units.

Every UBP motion depends on an event stream, a counter, and a reconciliation step that lands those counts in the invoice. The metering pipeline must be correct, auditable, and fast enough that both the customer dashboard and the finance system agree on the number. Mistakes here poison trust immediately.

The upside

Why usage-based pricing keeps spreading.

Teams move to UBP for three reasons that reinforce each other: it aligns incentive with value, it eliminates the friction of expansion, and it lets revenue grow at the same curve the customer grows at. Together those pull against the natural stall of flat subscriptions.

Value alignment

Pay more when you win more.

Per-seat subscriptions charge whether the product is used or not, which erodes trust over time. UBP ties the invoice to the thing the customer actually came to the product for. The pricing then feels fair in the slow quarters and defensible in the busy ones, and the vendor only wins when the customer wins.

Zero-friction expansion

Growth without a renewal cycle.

In per-seat SaaS, expansion means buying new licenses, which usually means approvals, procurement, and a conversation with the account owner. In UBP, expansion happens automatically as the customer sends more events or stores more data. The vendor captures the growth without ever reopening the contract.

Lower barrier to entry

Easy to try, cheap to start.

A new team can adopt the product at a tiny bill, prove value inside their org, and scale up as internal usage spreads. The land-and-expand motion that per-seat pricing fakes with free trials is native to UBP, which is why product-led companies lean on it.

Growth with the customer

Revenue curves with their business.

When the customer's own business grows, their usage grows, and the vendor's revenue grows with it. The relationship compounds instead of plateauing at the ceiling of their seat count. Net revenue retention climbs because every successful customer is also an expanding one.

Honest value signal

Usage data is a feedback loop.

The meter is also a measurement of product-market fit. Rising consumption means the product is working. Flat or falling consumption is an early churn signal weeks before the customer cancels. Teams that watch usage closely spot the problem while there is still time to fix it.

Pricing power

Room to charge for new capabilities.

Adding a feature to a flat subscription is almost always free to existing customers. In UBP, a new high-value action can be priced on its own meter. The pricing surface stays elastic as the product grows, instead of forcing every improvement into the same bundle at the same price.

The trade-offs

The hard parts nobody writes on the pricing page.

UBP is not free. It introduces real complexity in forecasting, procurement, and customer experience that teams underestimate when they first move off flat subscriptions. The playbook below is what mature UBP companies spend their first two years learning.

Harder forecast

Revenue is a variable, not a given.

In per-seat SaaS, closed revenue is a stable number for the year. In UBP, closed revenue is a bet on how much a customer will consume. Finance needs new models that mix a committed floor with a usage estimate, and every forecast has a confidence interval instead of a single number.

Procurement pushback

Variable invoices scare enterprise buyers.

Enterprise procurement is built around fixed POs and multi-year commitments. A variable invoice violates those norms, so UBP deals often convert to a committed-usage tier at the enterprise level. The pricing stays usage-based in spirit, but the contract looks closer to a traditional subscription.

Bill shock

The invoice that ended a relationship.

An unexpectedly large bill is the single fastest way to lose a UBP customer. Every mature motion includes real-time usage dashboards, forecast-to-bill estimates, soft caps, hard caps, and threshold alerts so the finance contact at the customer is never surprised when the invoice arrives.

Metric choice

Pick the wrong unit, break the model.

The value metric has to rise with value from the customer's perspective, not the vendor's. A metric that goes up for reasons unrelated to outcome, like retried API calls or logging events, feels extractive. Teams often iterate on the value metric two or three times before it settles.

Sales compensation

Comp plans need a rewrite.

Per-seat comp pays on the signed amount at the close date. UBP comp has to pay on expected consumption, actual consumption, or a mix of both. Pay too early and the rep collects on usage that never materializes. Pay too late and the rep stops caring about new logos.

Operational load

The meter is a product too.

The metering pipeline, usage dashboards, alerting system, invoice reconciliation, and dispute workflow are collectively a product the finance and engineering teams own. Teams that treat metering as a side project ship invoices that customers do not trust, and trust is the whole motion.

When UBP fits

The shapes of business that make UBP work.

Usage-based pricing is not the right answer for every product. It fits best when consumption varies widely between customers, when the value metric is easy to measure, and when expansion inside the account is the real growth engine. The checklist below is how teams decide whether to adopt it.

Variable consumption

Customers use it very differently.

If one customer uses ten times what another uses, flat pricing either overcharges the small account or undercharges the big one. UBP makes the invoice match the shape of the actual usage, which is why infrastructure, messaging, and data platforms adopted it first.

Clear value metric

The unit is obvious and measurable.

The product has a natural counter that lines up with customer value: a transaction, a message, a document, an event. If the obvious unit does not correlate with value, UBP will feel arbitrary. If it does, the pricing explains itself.

Expansion motion

Growth happens inside accounts.

If most revenue growth comes from existing customers doing more, UBP captures that growth automatically. If most growth comes from new logos, the expansion benefit is smaller and the forecasting pain is larger, which pushes some teams back toward hybrid or flat.

Product-led adoption

Users land before buyers do.

Products that spread bottom-up, where a developer or operator tries the tool before procurement is involved, benefit from a cheap entry price and automatic expansion. UBP is a near-perfect fit for product-led growth motions and a tougher fit for sales-led enterprise motions.

Low marginal cost

Serving more usage does not break margin.

UBP works best when serving another unit of consumption is close to free. When marginal cost is high, a usage spike can wipe out gross margin on a given customer. Teams in that position often cap usage per plan or move to committed-usage contracts to protect unit economics.

Honest meter

The counter the customer trusts.

The customer must be able to see what they are being billed for, in real time, with enough resolution to argue. Without a trustworthy meter, UBP collapses the moment a dispute lands in a finance team's inbox. The dashboard is as important as the pricing page.

CRM role

How a CRM makes usage-based pricing operable.

UBP sounds like a billing problem, but in practice it is a revenue operations problem. The CRM is where usage data has to land so forecasts, invoices, and commission plans all speak the same language. The jobs below are the ones teams underestimate until the first UBP close looks nothing like their old SaaS motion.

Usage on the record

Consumption lives on the customer.

The CRM pulls usage from the metering system onto the account and contact timeline, so every account manager opens a record and sees the actual consumption curve, not a static ARR number. Usage becomes a first-class field alongside stage, close date, and amount.

Forecast fed by usage

Pipeline weighted on real signal.

Forecasts stop depending on the rep's gut and start depending on usage trend. A deal with a trial already producing production traffic is weighted differently from a deal with a dormant workspace. The pipeline review becomes a conversation about consumption, not just stage movement.

Expansion signals

Early warnings before renewal.

Rising consumption near a plan ceiling triggers a workflow that routes the account to the right owner for an expansion conversation. Falling consumption triggers a save motion weeks before the renewal date, when there is still time to fix the problem instead of just losing the account.

Commissions aligned

Reps paid on usage, not just signatures.

Commission plans in UBP depend on actual consumption, not booked amount. The CRM has to carry the compensation rules, the usage data, and the attribution logic in one place so a monthly commission statement is reproducible and auditable instead of hand-built in a spreadsheet.

Invoice-ready records

The data billing already needs.

Billing systems need clean account hierarchies, correct tax jurisdictions, consistent product codes, and reliable usage events. The CRM is the system of record for everything except the raw meter, so the handoff between CRM and billing is where UBP motions quietly succeed or fail every month.

Customer visibility

Shared view across teams.

Account managers, finance, support, and the customer themselves all look at the same consumption numbers. Disagreements about the invoice stop being three teams holding different spreadsheets and start being a conversation grounded in one shared record. That is the whole point of a CRM in a usage-based motion.

Run usage-based pricing without losing the thread.

Strkr pulls usage onto the customer record, feeds forecasts from real consumption, and keeps commissions, renewals, and expansion workflows aligned to the same numbers. One tool, one record, one invoice conversation.

Start free See the platform

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.