Usage-based pricing is now the dominant billing model for SaaS companies — from cloud infrastructure to API platforms to AI tools. Instead of a flat monthly fee, customers pay based on what they consume: API calls, storage, seats, transactions, or compute hours. The model aligns cost with value, and customers generally prefer it.
The problem is your contract. Most SaaS agreements are written for flat-rate subscriptions. When you switch to metered billing without updating your terms, you create a gap between how your product works and what your contract actually says. That gap is where disputes live.
This article explains what usage-based pricing clauses must cover — and why getting the language right matters more than most SaaS founders expect.
1. Define the Billing Metric With Precision
The most common cause of metered billing disputes is an ambiguously defined billing unit. If your contract says “per API call” but your system counts retries, failed requests, or batch operations differently than the customer expects, you have a problem your terms did not prevent.
Your agreement must define:
- Exactly what constitutes one billable unit
- Whether failed, retried, or cached requests count
- The measurement period (per second, per day, per billing cycle)
- Who controls the measurement — your system, a third party, or a shared dashboard
If the metric is technically complex, plain-language definitions and links to your documentation are both appropriate and enforceable — as long as the documentation is incorporated by reference in the agreement and cannot be changed unilaterally after the customer’s billing period begins.
2. Specify How and When Usage Is Measured
Your agreement should specify whether usage is measured in real time, aggregated hourly, or tallied at the end of a billing cycle. It should also address what happens when your measurement system is unavailable — does the customer receive a credit, an estimate, or a delayed invoice?
Courts have generally upheld metered billing provisions when the measurement methodology is disclosed in advance and applied consistently. Ambiguous measurement terms, by contrast, are typically construed against the drafter — that is, against you as the vendor.
Where third-party systems (cloud providers, payment processors) are involved in measurement, your contract should clarify that their data is the authoritative source, and address the procedure if that data is disputed.
3. Set Spending Caps, Alerts, and Overage Rules
Customers who receive unexpected bills — often called “bill shock” — are the most common source of SaaS chargebacks and complaints to payment processors. The FTC has issued guidance under its Negative Option Rule (updated in 2024) emphasizing clear disclosure of recurring charges and the consumer’s ability to monitor and control them.
While the FTC rules primarily address consumer-facing subscriptions, their principles have influenced how courts and arbitrators view B2B metered billing disputes. Your agreement should address:
- Whether spending caps are hard (service stops) or soft (alerts only)
- What notice the customer receives when approaching a threshold
- Whether the customer can set their own caps through your dashboard
- What happens when usage exceeds the cap — automatic overage billing, service suspension, or manual approval
Burying overage terms in a pricing schedule that is incorporated by reference — without clear disclosure in the main agreement — is a litigation risk worth eliminating now.
4. Address Disputed Usage and the Audit Process
A well-drafted usage-based SaaS agreement includes a clear dispute resolution process specifically for billing disputes — separate from your general dispute clause. This should cover:
- The window in which a customer can dispute an invoice (typically 30–60 days from invoice date)
- What documentation the customer must provide to initiate a dispute
- Your obligation to investigate and respond within a defined timeframe
- Whether undisputed portions of an invoice are due during the investigation
- The customer’s audit rights, if any, and the process for exercising them
Without a defined dispute process, a billing disagreement can quickly become a contract breach claim — with your customer arguing they were overcharged and you arguing non-payment. A technology lawyer can draft a dispute process that protects both parties and reduces escalation.
5. Clarify Liability for Unauthorized or Excessive Usage
If a customer’s account is compromised and an attacker runs up $50,000 in API calls, who pays? If a customer’s developer misconfigures an integration and generates ten times the expected usage, are they liable for the full invoice?
Your agreement needs to answer these questions before they happen. Options include:
- Full customer liability for all usage under their credentials, with a security breach exception
- Shared liability where you provide real-time alerts and the customer is liable only for usage after they acknowledged the alert
- Liability caps tied to a percentage of average monthly spend
Whatever position you take, it must be clearly drafted. Silence in the contract means the dispute gets resolved by litigation or arbitration — usually in the customer’s favor if your system failed to alert them.
6. Handle Price Changes and Tier Adjustments Properly
Usage-based pricing models often involve tiered rates — lower per-unit cost at higher volumes. When you change pricing tiers, you need contract language that governs how and when those changes take effect, and whether existing customers are grandfathered.
Your agreement should specify:
- Notice period required before price changes take effect (typically 30–90 days)
- Whether mid-cycle changes are permitted or only apply at renewal
- The customer’s right to terminate if they object to a price change
- How grandfathered pricing works if you offer it
Vague “we may change pricing at any time” language is increasingly challenged — particularly in jurisdictions with strong consumer or commercial protection statutes. Specific, advance-notice provisions are both more defensible and more customer-friendly.
7. What a Technology Lawyer Addresses That Templates Miss
A SaaS contracts lawyer drafts usage-based billing provisions with the specific mechanics of your product in mind — not a generic billing clause copied from a template library.
Standard SaaS agreement templates rarely address how your measurement system works, what happens when your infrastructure provider’s data differs from your internal logs, or how to structure a dispute process that doesn’t expose you to automatic credit obligations. A technology lawyer who understands how metered billing actually operates can draft provisions that protect your revenue while keeping customer relationships intact.
If you are migrating from flat-rate to usage-based pricing, updating your billing metric, or launching a new metered product, your SaaS agreement should be reviewed and updated before you go live — not after the first billing dispute arrives.
Frequently Asked Questions
What is a usage-based pricing clause in a SaaS agreement?
It is a contractual provision that defines how billing is calculated based on measured consumption — such as API calls, storage, or transactions — rather than a fixed subscription fee. It specifies the billing unit, measurement methodology, invoice timing, and dispute process.
Can I be held liable if a customer’s account is hacked and runs up usage charges?
It depends on what your agreement says. Without a clear provision, this is a live legal dispute. A well-drafted agreement addresses unauthorized usage, alerts, and the conditions under which liability is limited or shared.
What notice do I need to give before changing usage-based pricing?
Your agreement should specify a notice period — typically 30 to 90 days. Without a defined notice provision, mid-cycle or short-notice changes can be challenged as a breach of contract, particularly for enterprise customers with negotiated terms.
What happens if my measurement system goes down during a billing cycle?
Your agreement should address this scenario directly — whether you issue a credit, use an estimate based on prior periods, or extend the billing cycle. Silence means the customer can argue the invoice is inaccurate and withhold payment.
Do customers have audit rights over usage data?
This is negotiable. Enterprise customers often request audit rights. Your agreement should either grant limited audit rights with a defined process, or explicitly exclude them. Without a clear provision, a customer can argue they have an implied right to audit.
Is a “we may change pricing at any time” clause enforceable?
Possibly, but it is increasingly risky. Courts and arbitrators have found such clauses unconscionable or unenforceable in contracts of adhesion, particularly when customers had no practical ability to negotiate. Specific advance-notice provisions are far more defensible.
Conclusion
Usage-based pricing is a sound business model. The contracts that support it are often not. If your SaaS agreement was written for a flat-rate subscription and your product now bills by consumption, the mismatch between your contract and your billing system is a risk that will surface in disputes, chargebacks, and customer exits.
If your SaaS agreement has not been reviewed by a technology lawyer since you introduced usage-based billing, now is the time. Contact Hansen Tong at TOSLawyer.com to get an agreement that reflects how your product actually works and protects your revenue.