How to Succeed with Usage-Based Pricing

Why usage-based pricing works

With usage-based pricing (UBP), customers pay for what they consume. Revenue scales with adoption. Customers who get more value pay more, and those who are just starting out aren't locked into contracts they can't justify. That alignment between cost and value is why UBP has gone from niche to mainstream. According to OpenView's 2023 report, 61% of SaaS companies have adopted or are testing some form of usage-based pricing.

But switching to UBP isn't just a pricing change. It touches your billing system, your sales motion, your forecasting, and how customers experience your product. Here's what you need to get right.

Three decisions before you switch

1. Pick the right metric

The billable metric is the most important decision in UBP. It should:

• Scale with customer value. If you run an email platform, emails sent maps directly to value. If you run a data pipeline tool, rows processed or compute time might be better.

• Be easy to understand. Customers need to predict their spend. API calls work for developers. For non-technical buyers, something like "reports generated" or "active contacts" is clearer.

• Align with your cost structure. If the metric you charge for doesn't correlate with your costs, margins degrade as usage grows.

If your customers can't explain the metric to their finance team in one sentence, it's too complicated.

2. Decide how much of your business transitions

UBP doesn't have to be all-or-nothing. Many companies start with a hybrid model: a base subscription plus usage-based components. This keeps some revenue predictable while letting the usage component capture upside.

You'll need to decide whether UBP applies to all customers or specific segments, and whether it's the primary structure or a supplement. Testing with one segment before rolling out broadly reduces risk.

3. Plan for the operational impact

UBP changes more than pricing. It changes how your teams operate:

• Finance needs to forecast with variable revenue inputs. Monthly cash flow becomes less predictable, especially early on.

• Support will field more billing questions. Customers with fluctuating charges need clear answers.

• Sales shifts from selling a fixed price to selling a model. Reps need to explain how pricing works, what customers should expect to pay, and why that's fair.

If your org isn't prepared for these changes, the pricing switch will create internal friction before it creates growth.

How to implement it

Track usage accurately

Before you can bill on usage, you need a system that tracks consumption in real time and at scale. Manual tracking breaks down fast. You need metering infrastructure that ingests events, aggregates them into billable metrics, and feeds them into your invoicing workflow.

Meteroid's metering engine is built in Rust for high-throughput event ingestion. It transforms raw events into billable metrics without pre-aggregation, so you can define and adjust metrics without re-instrumenting your pipeline.

Make pricing transparent

Customers should always know where they stand. That means clear invoices with usage breakdowns, and ideally a self-serve portal where they can monitor consumption in real time. Meteroid's customer portal gives customers visibility into their usage, subscriptions, and upcoming charges.

Transparency reduces billing disputes and builds the trust that makes customers comfortable scaling their usage.

Adjust your sales motion

Instead of pitching a fixed annual price, your sales team now sells flexibility: "Pay only for what you use. Start small, scale as you grow." That message works well for prospects who are cautious about large upfront commitments, which is most of them.

Monitor and iterate

Once live, watch how customers respond. Are some segments using less than expected? Are there complaints about unpredictability? Use that data to tune your pricing tiers, introduce commit-discount structures, or add usage alerts and budget caps.

Real-world examples

• Twilio charges per API call. Developers pay only for the messages, calls, or lookups they make. The metric maps directly to the value delivered.

• AWS bills per second of compute, per GB of storage, per request. The entire platform is usage-based, which lets customers start small and scale without contract renegotiation.

Both companies chose metrics that are intuitive, measurable, and correlated with the value customers receive.

How Meteroid helps

Meteroid is an open-source billing platform built for usage-based and hybrid pricing. It supports any pricing model out of the box: per-unit, tiered, volume, package, capacity commitments, matrix pricing, and any combination of these.

The platform is API-first, so it plugs into your existing stack. Plans are version-controlled, which means you can iterate on pricing without disrupting existing subscribers. And because it's open-source, your team has full visibility into how every charge is calculated.

Book a demo to see how Meteroid handles usage-based billing.