Usage-Based Pricing

Usage-based pricing means you pay for how much you use, such as API calls, requests, messages or compute time, instead of a flat fee per seat. Your bill moves with your usage, so it can be hard to predict.

What is usage-based pricing?

Under usage-based pricing (also called metered or pay-as-you-go pricing), the vendor measures something you do and charges per unit. The unit might be requests served, messages sent, records stored or AI credits spent. Some plans are fully metered. Others mix a flat base fee with metered charges on top.

Vendor terms often use the pay-as-you-go wording. HubSpot's terms bill usage above your HubSpot Credits limit "on a Pay-as-You-Go basis," and Cloudinary's pricing documentation lists $0.45 per credit beyond the monthly allotment on its Pro pay-as-you-go plan.

It can be fair: you pay for what you use. The catch is that the vendor decides what counts as a unit, and its terms decide how that counting can change.

A real change we caught

Venpo flagged a change that shows how much the definition of a billable unit matters. Our article Cloudflare removed its promise not to bill for bad bot requests covers how a promise that bad bot traffic would not be billed was taken out. Nothing replaced it, so the terms no longer say whether those requests are billed, which is worth asking about.

Other changes we covered show usage billing spreading. Atlassian added usage-based billing to its paid plans, on by default. JumpCloud's terms now allow usage-based pricing. And Kustomer now adds a 20% fee to WhatsApp on usage-based plans.

Why it matters to you

  • Bills you cannot predict. A traffic spike, a bot attack or a runaway script can multiply a monthly bill, much like overage charges on a flat plan.
  • The vendor sets the meter. If the terms let the vendor change what is counted or the rate, your cost can rise with no change in what you do.
  • Default settings. When metered billing is switched on by default, you may start paying before anyone decides to.
  • Harder budgeting. Finance teams plan in fixed numbers. Metered costs need monitoring, not just a yearly approval.

What to check

  • Exactly what unit is billed, and whether invalid, bot or failed traffic counts. The definition often sits in the billing terms or a product page, not the main contract.
  • Whether you can set a spending limit or hard cap, and what happens when you reach it.
  • Whether the vendor sends usage alerts, and to whom.
  • How much notice you get before rates or the definition of a unit change. See price change notice.
  • Whether metered features are on by default, and how to turn them off.
  • Whether a committed spend gets a discount, and what you owe if you use less. See minimum commitment.

How Venpo helps

Venpo watches your vendors' terms of service and billing pages and emails you when usage rules change, such as a new metered fee, a changed unit definition or a removed billing promise. The Fine Print Scan also answers, for each vendor, whether it can raise your prices.

Start for free

Frequently asked questions

Is usage-based pricing cheaper than per-seat pricing?

It can be if your use is low or steady. If your use grows or spikes, it can cost more than a flat plan, so compare a few realistic months before you switch.

How do I control costs on a usage-based plan?

Set spending limits and usage alerts where the vendor offers them, review usage each month, and watch the vendor's terms for changes to rates or what counts as a unit.

Related terms

Sources

Last reviewed