Usage-Based Billing: A Practical Guide for SaaS Founders

You’ve shipped your product. Users love it. Now you need to figure out how to charge them — and if your product’s value scales with how much your customers use it, flat per-seat pricing leaves money on the table.

Usage-based billing charges customers according to actual consumption: API calls, storage used, messages sent, compute time consumed. Instead of a flat $49/month regardless of usage, you bill $0.001 per API call or $0.10 per gigabyte stored.

This guide covers what usage-based billing actually is, when it makes sense, the technical pitfalls that trip up founders, and how to implement it without spending weeks writing your own metering infrastructure.

What Is Usage-Based Billing?

Usage-based billing (also called consumption-based billing or metered billing) is a pricing model where customers pay according to their actual product usage rather than a fixed subscription fee. Stripe’s own definition: “charge customers based on how much they use your product or service” [2].

The bill varies each billing cycle based on measurable events: API calls processed, gigabytes stored, minutes of compute time, messages routed, or any quantifiable unit of consumption.

The core mechanics are simple in theory:

  1. Track usage events — every time a customer consumes a unit of your service, log it
  2. Aggregate and bill — at the end of each billing period, sum up usage and calculate charges
  3. Collect payment — process the invoice through your payment processor

The execution is where founders bleed time and money.

Real-World Examples

  • AWS charges per gigabyte of S3 storage, per million Lambda invocations, per hour of EC2 uptime
  • Twilio charges per SMS sent, per minute of voice call, per API request
  • OpenAI’s API charges per million tokens of input and output, with rates varying by model
  • Vercel charges per GB of bandwidth and per build minute beyond free tier limits

These companies didn’t build their billing systems from scratch. They leveraged existing infrastructure — but as a SaaS founder, the choices are fewer and the stakes are higher.

When Usage-Based Billing Makes Sense (And When It Doesn't)

Use it when:

Customer value scales with usage. If a customer who uses your product 10x more gets 10x more value, flat pricing feels unfair to heavy users and leaves revenue on the table.

Your product has variable cost structures. AI inference, data processing, and cloud compute all have per-unit costs. Usage-based pricing naturally covers marginal costs. This is critical for AI SaaS products where inference costs fluctuate with model pricing and usage volume.

You want frictionless adoption. Zero-base pricing removes the barrier to entry. A developer can try your API with a free tier of 1,000 calls and only pay when they exceed it. This is why usage-based billing dominates developer tools.

Don't use it when:

Customers need budget predictability. Enterprise procurement teams hate variable costs. Pure usage-based billing slows sales cycles as finance departments struggle with approval workflows for unpredictable invoices.

Usage is sporadic or hard to measure. If your product delivers value through insights, strategy, or qualitative outputs rather than quantifiable units, usage-based pricing feels arbitrary.

Your unit economics don’t support it. If each unit of usage costs you nearly as much as you’d charge, thin margins amplify the pain of failed payments and churn.

The Hybrid Model: What Most SaaS Founders Actually Need

Pure usage-based billing works for AWS and Twilio. It rarely works as a standalone model for early-stage SaaS.

The practical approach is hybrid pricing: a base subscription fee that covers your fixed costs and gives customers budget predictability, plus usage-based overage charges beyond included thresholds.

Example: $49/month base + $0.001 per API call after 10,000 included calls.

This gives you:

  • Predictable recurring revenue (MRR) from the base fee
  • Upside from high-usage customers through metered overages
  • A frictionless free tier (0 base fee, pay-per-use only) for acquisition
  • Enterprise-friendly budgeting with configurable hard limits

How to Implement Usage-Based Billing: The Technical Reality

Here’s what no pricing guide will tell you: implementing usage-based billing correctly is a full-time engineering problem.

The Three Systems You Need

1. Event Tracking Infrastructure

Every usage event must be captured, attributed to the correct customer account, and stored with a timestamp. This sounds simple until you need to handle:

  • High-volume bursts (a customer fires 10,000 API calls in a minute)
  • Offline events (customer usage during a payment processor outage)
  • Multi-tenant attribution (sub-accounts, teams, projects under one account)
  • Event deduplication (idempotent API calls shouldn’t double-charge)

You’ll need a reliable event pipeline — typically webhook handlers, message queues (Redis Streams or Kafka), and a time-series database for aggregation.

2. Metering and Aggregation Engine

Raw events need to be rolled up into billable quantities:

  • Summing events per billing period
  • Applying volume discounts (1-10K at $0.01, 10K-100K at $0.008, 100K+ at $0.005)
  • Handling partial billing periods (mid-cycle plan changes, upgrades, downgrades)
  • Prorating credits for service outages or billing disputes

3. Billing and Collection System

This is where you generate invoices, process payments, handle failures, and manage dunning. Stripe’s metered billing handles the collection layer, but you still need to push usage records in real time and handle webhook reconciliation.

The DIY Approach: What It Actually Costs

Building all three systems in-house means:

  • 2-4 weeks of engineering time for event tracking and metering
  • 1-2 weeks for billing integration (Stripe, Chargebee, or custom)
  • Ongoing maintenance for edge cases (failed payments, mid-cycle changes, audit compliance)
  • Hidden costs: tax calculations, invoice generation, customer self-service portals, usage analytics dashboards

For a solo founder or small team, that’s 4-8 weeks of billing-focused development — time you could spend on product features your customers actually care about.

As Paul Copplestone, CEO of Supabase, put it when describing why his team adopted a dedicated billing platform: “We didn’t want to build a billing system. Billing is not our core product and we didn’t want to deal with the level of complexity that building our own system would require.”

— Paul Copplestone, CEO, Supabase (via Orb case study)

Usage-Based Billing Platforms: Options for SaaS Founders

Stripe Usage-Based Billing

Stripe offers two usage-based billing paths, and which one you should use changed in January 2026. Metronome is now part of Stripe and is described in Stripe’s own docs as “Stripe’s primary usage-based billing platform and the recommended starting point for all new integrations.” Basic usage-based billing, built on the Meters API, is “a lower-level primitive that remains fully supported for existing integrations” [2].

Stripe’s guidance is explicit: unless you’re maintaining an existing Meters integration, use Metronome — including for new integrations, adding usage-based pricing to existing flat-rate subscriptions, prepaid credits, enterprise contracts, dimensional or composite pricing, real-time usage visibility, and high-volume ingestion [2].

Strengths

  • One vendor for payments and billing — if you already run payments on Stripe, metered invoicing, dunning, and payment collection come from the same integration, with no new webhook stream or data sync to maintain
  • Well-documented API with SDKs for Python, Node, Ruby, and Go, plus the largest example-and-community ecosystem in the category
  • Handles the money side for you — invoice generation, payment retries, dunning, and Stripe Tax for sales tax and VAT sit inside the same platform
  • Supports volume-based, tiered, and per-unit pricing on subscriptions, with the Meters API covering raw-event metering [2]
  • Zero switching cost if you are already on Stripe — payment methods, billing history, and invoicing carry over
  • Adjacent compliance tooling — Stripe Revenue Recognition is explicitly built for ASC 606 and IFRS 15 [1]

Weaknesses

  • Billing is now a priced product, not a free add-on — Stripe Billing starts at $620.00 per month on a 1-year contract, or 0.7% of Billing volume pay-as-you-go [1]. Basic usage-based billing features remain available via the Meters API as part of Billing pricing, with up to 100M events per month included [1]
  • You still build the event tracking and aggregation layers yourself — Stripe meters the events you send; producing, deduplicating, and storing them is your problem
  • No built-in customer-facing usage dashboards at the level the dedicated platforms offer
  • Limited flexibility for complex billing models — hybrid seat + usage, custom proration, and retroactive repricing get awkward fast on the basic Meters path; Stripe routes those cases to Metronome [2]
  • Webhook reconciliation is your problem — Stripe doesn’t guarantee delivery, and you need to handle retries and idempotency
  • No auth, user, or organization management — Stripe bills customers; identity, roles, org hierarchy, and account portals remain your problem

Stripe’s usage-billing capability is actively consolidating around Metronome following the January 2026 acquisition. Stripe’s own docs recommend migrating new integrations there and offer a migration path [2]. Re-check this section before relying on it.

Stripe Billing Documentation

Chargebee Usage-Based Billing

Chargebee is a mature subscription billing platform that has expanded into a bundled suite — Billing, CPQ, RevRec, and Growth — each priced separately, which makes its pricing page one of the harder ones in this category to evaluate.

Strengths

  • Published entry pricing with a genuine $0 option — the Flow plan is $0 + 0.80% of monthly invoicing volume, or $99/mo + 0.65%, on a $0–$500K invoicing band; Chargebee’s own page marks the breakeven between the two at roughly $66K
  • 100M usage events/month included in the entry band, extendable to 500M via paid add-on
  • 40+ payment gateway integrations — Stripe, Adyen, Braintree, PayPal Commerce, GoCardless, Checkout.com, Authorize.net, Mollie, Worldpay, EBANX, dLocal and others
  • Serious usage-billing depth — metered or real-time ingestion via API, CSV or S3; near-real-time aggregation; schemaless usage data; custom SQL meters; tiered, stair-step, volume and block pricing; included-usage entitlements with thresholds and overages
  • Tax and accounting coverage built in — US sales tax, EU VAT and global tax with multiple tax profiles and regions; Avalara and Anrok integrations; Xero, QuickBooks, NetSuite and Intacct
  • Multi-entity and hierarchy support — account hierarchies up to 30 levels deep, and up to 100 business entities at the enterprise tier
  • Revenue recognition as a first-class module — point-in-time and ratable recognition, GAAP reports, journal entry mapping, multi-currency
  • Established customer base — Zapier, LegalZoom, Brevo, Condé Nast, CodeRabbit, Phrase

Weaknesses

  • Pricing is fragmented across four products — RevRec’s Performance plan is available only to Chargebee Billing customers and shows “Book a demo and request pricing”; Growth’s Enterprise tier is quote-based
  • Percentage-of-invoicing costs compound — the 0.65–0.80% take continues to apply as revenue scales, on top of gateway fees
  • Suite breadth over developer speed — the platform is feature-dense, and CPQ, RevRec and Growth are add-on surfaces most pre-seed teams will never open
  • No auth, user, or organization management — Chargebee manages subscriptions, not identities. Customer hierarchy is a billing construct, not an application role model

Chargebee Usage-Based Billing

Zuora Usage-Based Billing

Zuora is the enterprise-grade subscription management platform in this category, and the clearest example of a vendor whose pricing is invisible to both buyers and crawlers. Zuora does not publish list pricing; everything is quote-based.

Strengths

  • Deepest financial-compliance capability in the set — advanced revenue recognition with ASC 606 / IFRS 15 compliance, financial close automation, and sophisticated collections workflows
  • Modular by design — Billing, Revenue, Collect, CPQ and Analytics as separate products
  • Usage-based billing is native, not bolted on — metered usage, tiered pricing, overages and hybrid subscription-plus-usage, included in Scale and Enterprise editions
  • Three-tier maturity ladder — Growth, Scale, Enterprise
  • Enterprise deployment options — single-tenant private cloud available, which most of this category doesn’t offer
  • Established integration ecosystem — pre-built connectors for Salesforce, NetSuite, Microsoft Dynamics, QuickBooks and major payment gateways

Weaknesses

  • Priced for enterprise, not startups — Vendr’s transaction data puts the median buyer at $170,000/year, across a range of $26,883 to $696,804
  • Cost fragments across modules — Revenue, Collect, CPQ and Analytics each carry separate quote-based fees
  • Single-tenant premium — roughly 40–60% above comparable multi-tenant configurations
  • Renewals escalate — standard increases of 5–12% annually without negotiation; price-protection caps of 3–5% must be negotiated into the original contract
  • Implementation is a major line item — professional services commonly run 15–25% of annual platform fees for basic setups, 25–40% for moderate complexity, and 50–75% for complex multi-entity or legacy migrations; overall often 20–50% of first-year total cost
  • Long sales cycle — 60–90 days for mid-market, longer for enterprise
  • No auth, user, or organization management

Zuora Usage Billing

Metronome

Metronome is a usage-based billing platform whose positioning is “start free, scale confidently — never outgrow your billing infrastructure” — though its published pricing grid starts at a paid Startup tier rather than a free plan. As of January 2026, Metronome is part of Stripe: the acquisition completed on January 13, 2026, and Metronome now appears in Stripe’s product lineup as its usage-based billing platform [1][2]. Stripe’s docs describe it as the recommended starting point for all new usage-based billing integrations [2].

Like Orb, it bills on raw ingested events rather than pre-aggregated usage, using SQL-based billable metrics so pricing definitions can change without re-instrumenting your product.

Strengths

  • Published, self-serve-friendly pricing — the Startup tier bills $0.04 per 1,000 ingest events plus 0.8% of billing volume [1]
  • Deep Stripe alignment — now part of Stripe’s stack, so payments, invoicing, and metering come from one vendor rather than a third-party bridge; embeddable billing dashboards can be surfaced inside your own product
  • Full pricing-model coverage from day one — usage-based, seat-based, subscription, and hybrid, supporting both scaled self-serve and custom enterprise contracts
  • Real-time metering with low-latency alerting — streaming billable metrics used to guard against fraud and abuse
  • Pricing-change machinery built in — centralized rate cards, commits and credit models; per-customer discounts, overwrites and amendments; updates applied instantly, on a future date, or retroactively
  • Deepest AI/infrastructure reference base in the category — OpenAI moved off a homegrown manual billing system to Metronome; Replicate launched prepaid credits in two weeks; Anyscale credits Metronome with making self-serve possible at all
  • Named customer roster — OpenAI, Anthropic, NVIDIA, Hugging Face, Together, Cockroach Labs, Confluent, Fly.io, AssemblyAI, Cribl, DataStax, Starburst, LangChain, Anyscale, Redpanda, Kong, Temporal, Astronomer, mParticle, Salad

Weaknesses

  • Cost scales with your revenue — the 0.8% billing-volume charge means your bill rises as you grow, independent of engineering effort saved [1]
  • Data export is gated to custom plans — $0.03 per 1K standard exports and $0.05 per 1K premium exports, available only on Custom tier [1]
  • Finance-stack integrations are gated — Salesforce, NetSuite and cloud marketplace invoicing (AWS, Azure, GCP), warehouse/BI exports, a dedicated account manager and enhanced SLAs sit behind the Custom tier, which has no published price
  • Acquisition uncertainty — folding into Stripe may mean roadmap, pricing, and packaging changes over the coming years
  • No auth, user, or organization management — Metronome is a billing and metering engine only; identity, roles and customer account management remain your problem
  • Enterprise-leaning proof points — customer stories skew to infrastructure and AI companies with large event volumes, not solo founders shipping a first paid plan

Metronome Pricing

Orb

Orb is a usage-based billing platform positioned explicitly for high-growth and enterprise companies “where billing is mission-critical,” not for early-stage founders. Its defining architectural choice is billing on raw ingested events rather than pre-aggregated usage, so billable metrics can be redefined at any time without re-instrumenting your product.

Strengths

  • Raw-event billing, not metered aggregation – events stay queryable, so pricing models change without re-sending data
  • Proven at extreme scale – ingestion is stress-tested to 250,000+ events/second via API and S3, with idempotency guarantees
  • Hybrid pricing in a single plan – combine usage-based, fixed platform fees, and per-seat charges; adjust quantities mid-cycle
  • Native invoicing on every tier – invoice generation, payment collection, dunning and delivery built in, or integrate with QuickBooks, Bill.com, or Stripe
  • Deep finance-stack integrations – NetSuite and Salesforce on Advanced and above; tax via Avalara, Anrok, Numeral, Sphere, Stripe Tax, or TaxJar
  • Reference customers at infrastructure scale – Vercel, Supabase, Replit, Redis, Neo4j, LaunchDarkly, Pinecone, Alchemy, Glean, Fal
  • Quantified outcomes – Supabase processes 1.5M invoices/month through Orb; Vercel ran a 70% load test and went live in 3 weeks; Replit implemented in one month; Jasper grew usage 4x; Stytch cut billing and invoicing time by 75%
  • Evidence of the Stripe ceiling – Supabase began on Stripe Billing and moved to Orb after usage-based pricing required constant engineering work, producing billing inaccuracies and lost revenue; switching to Orb Invoicing alone cut fees by roughly 0.4% of total revenue

Weaknesses

  • No published pricing – all three tiers (Core, Advanced, Enterprise) display “Custom pricing” with a Contact Sales CTA
  • Sales-led, not self-serve – no free tier and no trial; you cannot begin integrating without a sales conversation
  • Cost scales with your billings – pricing is based on total invoice value issued through Orb plus event volume, with an added platform fee on Advanced and Enterprise
  • Key capabilities are tier-gated – customer hierarchy, data warehouse sync, Salesforce/NetSuite, and contractual SLAs require Advanced or Enterprise; SLAs appear only “In MSA” at Enterprise
  • No auth, user, or organization management – Orb is a billing engine
  • Not built for pre-seed speed – packaging targets teams whose billing is already mission-critical
  • Acquisition uncertainty – Orb announced it is joining Adyen, which may create roadmap and pricing uncertainty for new customers

Orb Pricing

Paddle

Paddle is a Merchant of Record purpose-built for SaaS, apps and digital products. The MoR model is the whole proposition: Paddle becomes the legal seller, absorbing sales tax, VAT, fraud, chargebacks and buyer support, so you don’t build or buy a compliance layer.

Strengths

  • Single all-inclusive rate — 5% + 50¢ per checkout transaction, with no monthly fees, migration fees, or hidden extras
  • Compliance fully offloaded — global sales tax and VAT collection, filing and remittance, plus international payment regulation
  • Risk transfer included — fraud protection, bad-faith chargeback defense, fraudster screening, and buyer-facing billing support in the base price
  • Migration is free and included — no lock-in periods, with your data portable to another provider
  • Genuine self-serve start — signup with no sales gate, plus a developer sandbox and quickstart guides
  • Free subscription analytics — ProfitWell Metrics bundled at no cost
  • Developer surface is current — API reference, changelog, and a Docs MCP server so AI assistants can retrieve up-to-date Paddle knowledge
  • Credible in the developer/indie segment — Tailwind Labs, n8n, Laravel Spark, GeoGuessr, removebg, MacPaw, Fortinet, Daylite, GetBlock
  • The tax argument is quantified by a customer — Tailwind’s CEO cites ~3.5% with Stripe and ~4.5% with PayPal on cross-border payments, concluding the nominal saving wasn’t worth the admin burden or tax scrutiny

Weaknesses

  • Effective cost is high on small transactions — 5% + 50¢ against Stripe’s 2.9% + 30¢ for domestic cards [1]; on a $10 sale the fixed 50¢ alone is 5%
  • Low-value pricing requires negotiation — sub-$10 products need bespoke pricing via a custom tier
  • You don’t own the checkout relationship — Paddle’s hosted/branded checkout is the transaction surface; customization is narrower than a direct Stripe integration
  • Invoicing, advisory and implementation are add-ons — listed separately behind a demo booking
  • No auth, user, or organization management — Paddle handles selling and billing, not identity, roles, or multi-tenant account structure

Paddle Usage Billing

Serial Subscriptions

Serial Subscriptions handles usage-based billing natively as part of a unified platform combining authentication, billing, user and organization management, and usage tracking in one integration — on top of your own Stripe account.

Strengths

  • Bring Your Own Stripe — link your existing Stripe account in test or live mode; you keep payouts, disputes, and analytics. Not a merchant of record, so none of Paddle’s 5% + 50¢ effective cost applies
  • Auth and organization management included — signup flows, email verification, password resets, org invites, and owner/admin/billing/readonly roles. This is the layer every other platform on this page leaves to you
  • Usage metering via a lightweight library — log usage events (AI credits consumed, API calls, custom actions) with a few lines of code rather than a heavy SDK
  • Plan builder covers the models above — free trials, user limits, monthly AI credits, usage-based overages, base fee plus bill-for-credits, and “Call for Pricing” for enterprise. Supports account-based and project-based subscriptions. Pricing model changes require no code rewrite
  • Self-service customer portal on your own domain — fully branded pricing pages, dashboards, invoices, and onboarding
  • ASC 606-aware invoicing — itemized invoices with legal entity, tax jurisdiction, and terms
  • Published pricing with a free developer tier — see the pricing page
  • Data portability — full export, no lock-in on your billing data

Weaknesses

  • Smaller ecosystem than the incumbents — no 40+ gateway marketplace, no Salesforce/NetSuite integration library, no analyst coverage
  • Stripe-only payment processing — if you need Braintree, Adyen, or a merchant-of-record model for tax reasons, this isn’t the fit
  • Younger company — fewer public case studies at enterprise scale than Zuora, Chargebee, or Metronome
  • SSO on the enterprise tier — social login is included; enterprise SSO is tier-gated

Choosing the Best Usage-Based Billing Software for Your Stage

Pre-Seed to Seed (0-100K ARR)

You need speed. Stripe’s basic usage-based billing is the fastest path if you’re already on Stripe — but note that Stripe Billing itself is now a priced product starting at $620/month or 0.7% of Billing volume [1], which changes the “it’s free because you already use Stripe” assumption. Stripe’s own docs now route new usage-based integrations to Metronome [2].

Seed to Series A (100K-500K ARR)

Complexity hits. You need usage analytics, customer self-service, dunning, and hybrid pricing. Chargebee handles these natively — though weigh its suite-breadth trade-off if developer speed is your priority. Alternatively, unified platforms like Serial Subscriptions consolidate authentication, billing, usage tracking, and subscription management in a single integration, eliminating the Stripe + auth vendor + custom code stack most startups inherit.

Series A+ (500K+ ARR)

You need ASC 606 compliance, sophisticated reporting, multi-currency, and dedicated billing operations. Zuora is the enterprise standard but expect significant implementation costs. Stripe Revenue Recognition covers ASC 606 and IFRS 15 starting at $25/month [1], which compresses part of Zuora’s historical advantage here.

Common Pitfalls

1. Webhook Reconciliation Failures

Payment processors send webhooks but don’t guarantee delivery. Build idempotent handlers with retry logic and maintain an audit trail.

2. Mid-Cycle Plan Changes

Upgrades and downgrades require prorating both fixed fees and usage charges. Most founders get this wrong — double-charging or under-charging. Test this edge case before launch.

3. Usage Data Loss During Outages

If your processor is down but your product is running, you lose usage events. Buffer locally and sync when the connection restores.

4. Customer Budget Shock

Usage-based billing without caps causes support tickets. Implement hard limits or alerts at 50%, 80%, and 100% of estimated monthly spend. Stripe’s own docs support setting alerts for when a customer exceeds a usage threshold [2].

5. Tax and Compliance Complexity

Variable invoice amounts complicate tax. VAT, GST, and sales tax rules differ by jurisdiction.

Implementing Usage-Based Billing: A Practical Checklist

  • Define your unit of measurement (API calls, GB stored, minutes processed)
  • Build event tracking with idempotency and deduplication
  • Implement aggregation with volume tiers and thresholds
  • Set up mid-cycle proration for plan changes
  • Configure usage alerts at 50%, 80%, and 100% of estimated spend
  • Build webhook handlers with retry logic and audit trails
  • Test edge cases: failed payments, outages, rapid churn, zero-usage
  • Implement customer-facing usage dashboards
  • Set up tax calculation for all target jurisdictions
  • Build dunning and retry workflows for failed payments

Fact Check

Vendor pricing and capability claims on this page were verified against the vendor’s own published pages on 15 October 2026. Vendor pricing changes frequently — treat figures as a snapshot, not a quote.

Verified against vendor sources:

  • Stripe Billing pricing: starting at $620.00/month on a 1-year contract, or 0.7% of Billing volume pay-as-you-go — stripe.com/pricing.
  • Stripe standard card rate: 2.9% + 30¢ per successful domestic card transaction — stripe.com/pricing.
  • Basic usage-based billing is built on the Meters API; Usage Records is documented as legacy — docs.stripe.com/billing/subscriptions/usage-based.
  • Metronome is Stripe’s primary usage-based billing platform and the recommended starting point for all new integrations — Stripe docs.
  • Up to 100M events per month included in Billing pricing via the Meters API — stripe.com/pricing, footnote 2.
  • Metronome Startup tier: $0.04 per 1K ingest events plus 0.8% of billing volume; Custom tier is quote-based; data export ($0.03/$0.05 per 1K) available only on custom plans — stripe.com/pricing and metronome.com/pricing.
  • Stripe Revenue Recognition supports ASC 606 and IFRS 15; $25/month or starting at $190/month on a 1-year contract — stripe.com/pricing.
  • Stripe usage threshold alerts are a documented feature — Stripe docs, “Monitor usage.”
  • Metronome is part of Stripe — acquisition confirmed complete 13 January 2026 by Metronome CEO Scott Woody (metronome.com/blog/our-next-chapter-metronome-is-now-part-of-stripe).
  • Chargebee Flow breakeven (~$66K/mo invoicing) — derived from Chargebee’s published rates: $0 + 0.80% versus $99/mo + 0.65%. Solving 0.0080x = 99 + 0.0065x gives x = $66,000.
  • Chargebee entry band $0–$500K monthly invoicing, 100M usage events/mo included — chargebee.com/pricing.
  • Paddle 5% + 50¢ per checkout transaction — paddle.com/pricing.
  • Orb ingestion stress-tested to 250,000+ events/second — withorb.com/pricing FAQ.
  • Orb tiers (Core, Advanced, Enterprise) show “Custom pricing” — withorb.com/pricing.
  • OpenAI API priced per million tokens, varying by model — openai.com/api/pricing.
  • Orb is joining Adyen — confirmed by Orb’s own announcement (withorb.com/blog/orb-next-chapter).
  • Supabase processes 1.5M+ invoices/month via Orb; Orb Invoicing switch cut fees by ~0.4% of total revenue — withorb.com/customers/supabase.
  • Copplestone build-vs-buy quote — quoted in Orb’s Supabase case study, not a Supabase-published channel; attribution reflects that.

Third-party benchmark, not a vendor figure:

  • Zuora median $170,000/year (range $26,883–$696,804) — Vendr anonymized transaction data, 149 purchases, guide updated February 2026. Zuora publishes no list pricing, so this is the best available benchmark rather than an official rate.

This page’s own estimates, not vendor claims:

  • 4–8 weeks of engineering time to build usage-based billing in-house — an estimate based on typical scope for event tracking, metering, and billing integration. Varies with billing complexity and team experience.

Unverified — treat as directional:

  • AWS, Twilio, Vercel consumption examples — described generically; see linked pricing pages for current rates.
  • Stripe “doesn’t guarantee webhook delivery” — standard distributed systems guidance, not a quoted Stripe statement.

Sources

  1. Stripe Pricing — https://stripe.com/pricing
  2. Stripe — Basic usage-based billing — https://docs.stripe.com/billing/subscriptions/usage-based
  3. Stripe Billing Documentation — https://stripe.com/docs/billing
  4. Chargebee Pricing — https://www.chargebee.com/pricing/
  5. Chargebee Usage-Based Billing — https://www.chargebee.com/recurring-billing-invoicing/metered-usage-billing/
  6. Zuora Pricing — https://www.zuora.com/pricing/
  7. Zuora Usage Billing — https://www.zuora.com/resources/products/usage-billing/
  8. Zuora pricing benchmarks (Vendr, Feb 2026) — https://www.vendr.com/marketplace/zuora
  9. Metronome Pricing — https://metronome.com/pricing
  10. Metronome — “Our Next Chapter: Metronome is Now Part of Stripe” (Jan 13, 2026) — https://metronome.com/blog/our-next-chapter-metronome-is-now-part-of-stripe
  11. Metronome Customer Stories — https://metronome.com/customer-stories
  12. Paddle Pricing — https://www.paddle.com/pricing
  13. Paddle Billing — https://www.paddle.com/billing
  14. Orb Pricing — https://www.withorb.com/pricing
  15. Orb Customers / Case Studies — https://www.withorb.com/customers
  16. Orb customer case study — Supabase — https://www.withorb.com/customers/supabase
  17. Orb announcement — “Orb is joining Adyen” — https://www.withorb.com/blog/orb-next-chapter
  18. AWS Pricing — https://aws.amazon.com/pricing/
  19. Twilio Pricing — https://www.twilio.com/en-us/pricing
  20. OpenAI API Pricing — https://openai.com/api/pricing/
  21. Vercel Pricing — https://vercel.com/pricing

    22. All sources accessed 15 October 2026.