Usage-based pricing for SaaS, AI, and enterprise software
Charge customers for what they actually use — per API call, per token, per transaction, per compute hour. Nalpeiron is usage-based pricing software that meters and rates any usage-based model, then hands off invoice-ready usage to your billing platform, so revenue tracks the value you deliver without months of in-house engineering.
With Zenmeter, customers pay for value, not a flat fee
Usage-based pricing charges customers proportionally to what they consume — so cost matches value, and your revenue grows as customers do.
Revenue Alignment
Revenue tracks the value customers receive. As they consume more, they pay more, and your revenue grows automatically, with no upsell or renegotiation.
Lower Barrier to Entry
Customers start small and grow into your product with no large upfront commitment. A developer making 100 calls pays a fraction of an enterprise making millions, which widens your market.
Transparent Economics
Customers see exactly what they pay for, with every call, token, and transaction on the invoice. That transparency builds trust and cuts billing disputes.
Faster Deals, Easier Pilots
Buyers don't have to guess next year's needs or sign a large seat contract. They start with a small pilot, prove the value, and expand, so procurement moves faster and pilots get approved.
Better ROI Conversations
Spend maps to measurable use, so sales can talk about return instead of defending a license price. That means less discounting pressure and more trust from enterprise buyers.
More Ways to Package
Freemium, self-serve, prepaid credits, minimum commitments with overage, or subscription plus usage. The same pricing approach supports whichever go-to-market motion fits each segment.
What is usage-based pricing?
Usage-based pricing (also called consumption-based pricing) is a billing model where customers pay for what they consume rather than a fixed subscription fee. Charges are tied to a measurable unit of value: API calls, tokens, transactions, compute hours, or data stored. It dominates cloud infrastructure (AWS, Google Cloud), AI platforms (OpenAI, Anthropic), and a growing share of SaaS because it removes adoption barriers and grows revenue with customer success.
Usage-based pricing and usage-based billing often get used as if they mean the same thing, but they're two different jobs. Pricing is the structure: the metric you charge on and the rates or tiers you set. Billing is the system that meters consumption, rates it against that structure, and turns it into charges.
From event to invoice
Usage-based pricing runs on a four-stage pipeline that turns raw consumption into accurate invoices. Nalpeiron powers metering, aggregation, and rating, then hands off rated usage to your billing platform for invoicing.
Event Ingestion
Capture every billable action in real time with full metadata — customer, action, quantity, timestamp. Built for millions of events per hour at sub-second latency.
Metering & Aggregation
Deduplicate events for exactly-once accuracy, then roll them up by customer, feature, and time window — for live dashboards and each billing period.
Rating & Pricing
Apply your pricing rules — per-unit, tiers, volume discounts, credits — to aggregated usage. Update rate cards instantly, with no code changes.
Billing & Invoicing
Send rated amounts to your billing platform as invoice line items, with proration, tax, currency, and reconciliation handled by your billing system.
Every usage-based pricing model, one platform
There's no single way to do usage-based pricing. Combine these models freely to match how your customers derive value.
Pay-Per-Use
Charge for each individual action — API calls, transactions, messages, or queries. The simplest model: customers pay only for what they use. Ideal for developer tools and infrastructure.
Build pay-per-use pricingTiered Usage
Volume brackets with decreasing per-unit cost at higher tiers. The first 10,000 calls cost more per unit than the next 100,000 — rewarding growth while protecting margins.
Credit-Based
Customers pre-purchase a pool of credits that different actions consume — a simple query costs 1 credit, a complex job 10. Balances burn down live and can be shared across a B2B team.
Token-Based
Purpose-built for AI: charge per input and output token across inference, embeddings, and fine-tuning, with a different rate per model. The standard for AI products.
Explore AI token pricingHybrid
Combine a base subscription with usage overage — e.g. $500/month including 100,000 calls, then per-call above. Balances predictable revenue with consumption upside.
See hybrid pricing modelsOutcome-Based
Price on the value delivered rather than raw consumption — per successful transaction, per lead, per conversion. Maximum alignment, but needs robust attribution.
A hybrid plan in practice
Hybrid pricing is where most B2B software ends up: a subscription sets a predictable floor, and usage above the included allowance captures the upside from customers who grow. Here's how one month adds up for a customer on a plan that includes 100,000 API calls.
- Base plan (includes 100,000 calls)
- $500
- Calls used this month
- 160,000
- Overage: 60,000 calls × $0.004
- $240
- Total for the month
- $740
Usage-based pricing examples
You've almost certainly paid for something priced this way. Here's what some of the best-known usage-based companies charge on.
| Company | What customers pay for |
|---|---|
| AWS | Compute hours, storage per GB, and data transferPay-per-use |
| OpenAI | Input and output tokens, priced per modelToken-based |
| Twilio | Messages sent and voice minutesPay-per-use |
| Snowflake | Compute credits consumed, plus storageCredit-based |
| Stripe | Each successful card payment, as a percentage plus a fixed feePer transaction |
The same approach supports freemium plans, self-serve onboarding, prepaid credits, enterprise minimum commitments, overage pricing, and subscription-plus-usage hybrids.
Making usage-based revenue predictable
Pure pay-as-you-go makes revenue rise and fall with customer activity. Most companies smooth it out with one or more of these.
Minimum Commitments
Customers commit to a minimum monthly or annual spend. You get a revenue floor, and they still pay for what they use above it.
Tiered Pricing Bands
Volume brackets keep the per-unit rate steady within each band, so bills move in steps rather than swings.
Base Subscription + Usage
A fixed platform fee with an included allowance covers the baseline. Only usage above the allowance varies.
Prepaid Credits
Customers buy credits upfront and burn them down as they use the product. The cash arrives before the usage does.
Committed-Use Agreements
Enterprise customers commit to a volume over the contract term in return for a lower unit rate.
Alerts and Usage Caps
Spending alerts, soft limits, and hard caps prevent surprise invoices, which protects both the customer relationship and the revenue line.
Forecasting then moves from fixed ARR to usage patterns and customer cohorts, which is why accurate, real-time usage data matters as much as the price list.
Is usage-based pricing right for you?
How value shows up in your product matters more than your industry. Three questions decide it.
Does value grow with use?
If a customer who uses your product twice as much gets twice the value, usage-based pricing fits. If value stays flat however much they use it, a subscription may serve you better.
Can you measure it in real time?
You need to capture every billable event accurately as it happens, not tally it up at the end of the month. Otherwise you leak revenue or overcharge.
What will your pricing page look like?
Most teams end up with plans built around usage limits. That means deciding which features to meter and what the limit should be on each plan.
Startups and small businesses
Pay-as-you-go lowers the barrier for buyers with small budgets and changing demand: they start small and scale as they grow. Keep it simple, because clear usage dashboards and predictable plans matter more than clever rate cards. And have reliable metering in place before you launch.
Review your pricing regularly
Usage-based pricing isn't set-and-forget. Track unit economics, gross margin by usage tier, expansion, and the objections sales hears, then adjust rates and limits, ideally without waiting on a code release.
Usage-based pricing for AI companies
Every inference call and token consumes real GPU compute, so flat-rate pricing is unsustainable for AI. Usage-based pricing aligns revenue with the cost of serving each customer — for pure AI platforms and AI features alike.
AI Token Metering & Pricing
Track every LLM request — model, input and output tokens, latency, customer — and apply model-specific rates in real time. Traditional billing systems cannot meter at this granularity.
GPU & Compute Cost Attribution
Map infrastructure cost to each customer's usage across GPU types, regions, and providers — so you can price for a target margin per customer, model, and feature.
Multi-Model Pricing
Charge different per-token rates for different model sizes within one billing framework. The rating engine reads model metadata on every event and applies the right rate card.
AI Credit Systems
Sell pre-purchased token bundles and enterprise commitments. The platform tracks balances live, shows remaining allowance, alerts at thresholds, and stops usage when exhausted.
Usage-based pricing for SaaS platforms
SaaS companies increasingly add usage-based components alongside subscriptions to align cost with consumption and capture expansion revenue. Companies with usage-based components see meaningfully higher net revenue retention than pure-subscription peers.
API Monetization
Charge developers and partners per API call, with tiered rate limits, premium-endpoint pricing, and partner-specific rate cards. Real-time usage dashboards build trust and cut billing support tickets.
Feature-Gated Consumption
Combine feature entitlements with usage limits per tier — Free gets 1,000 calls, Pro 50,000, Enterprise unlimited. Approaching a tier limit becomes a natural upsell trigger.
Multi-Tenant Metering
Attribute compute, storage, bandwidth, and AI inference to each tenant precisely across shared infrastructure — so every customer pays for exactly their own consumption, with no cross-tenant leakage.
Get the Datasheet
Not ready for a demo? Get an overview of Zenmeter — usage metering, rating, billing, pricing and packaging delivery in one PDF.
- Every pricing model — usage, seats, credits, overages, hybrid (seats+usage)
- Meters and rates usage, feeds your billing platform
- Enterprise security, 99.9%+ SLA, GDPR, SOC 2 Type II
Explore usage-based pricing further
Dig into real-world examples, hybrid model design, and the metering infrastructure behind it all.
The platform for usage-based pricing
Zenmeter delivers every layer of the usage-based pricing stack — high-throughput event ingestion, a flexible rating engine with instant rate-card updates, real-time customer dashboards, and billing integration. It's unified with licensing and entitlements, so you can run hybrid subscription-plus-usage models from one platform, and it's built for AI-scale token metering.
Explore ZenmeterHigh-Fidelity Metering
Sub-second event ingestion with exactly-once processing
Flexible Rating Engine
Per-unit, tiered, credits, volume — update pricing instantly
Real-Time Billing Sync
Customer dashboards, spending alerts, billing-platform sync
AI-Native
Token metering, multi-model pricing, GPU cost attribution
What makes it hard — and why infrastructure matters
Usage-based pricing delivers compelling benefits, but these challenges are why it needs purpose-built infrastructure.
Revenue Predictability
Consumption-based revenue fluctuates with customer activity. Finance teams must forecast on usage patterns and cohorts rather than fixed subscription ARR.
Metering Accuracy
Every event must be captured, deduplicated, and attributed. Missed events leak revenue; duplicates overbill. Homegrown systems commonly lose 4-7% of revenue to metering errors.
Customer Bill Shock
A usage spike can produce a shock invoice that erodes trust and drives churn. You need real-time dashboards, spending alerts, and soft and hard usage caps.
Revenue Recognition
IFRS 15 revenue recognition is more complex for usage models — prepaid credits defer revenue and hybrids need price allocation. You need auditable consumption records.
Usage-based pricing FAQ
Common questions about usage-based pricing models, metering infrastructure, and billing for AI and SaaS companies.
Ready to implement usage-based pricing?
Talk to our team about the metering and rating infrastructure that powers usage-based pricing for SaaS, AI, and enterprise software — from event ingestion to your billing platform.