What your SaaS pricing actually commits you to

Pricing decisions get owned by product and revenue teams. Legal reviews the subscription agreement. The two rarely meet in the middle, and the gap between them is where disputes live.

Usage-based pricing makes commercial sense. Customers pay for what they use, adoption scales naturally, and revenue tracks real value delivery. What gets overlooked is that the moment you bill by consumption, you have entered a contract about measurement, not just a marketing model about value.

Every usage-based pricing structure raises questions your subscription agreement must answer:

• How usage is counted: Which actions, events, records or units trigger a billable entry?
• When usage is measured: Is it measured at the point of action, at end of day, or at invoice cycle close?
• What happens in a dispute: Who holds the authoritative log if the customer disputes the meter reading?
• When rates change: Is there a usage cap before a rate change applies, and does the customer receive notice before that happens?

If your contract is silent on these points, the customer fills the gap with their own interpretation. In a dispute, that silence works against you. Even in B2B contracts, vague measurement terms give a determined customer significant leverage to withhold payment.

Tiered pricing looks clean on a pricing page. Starter, Growth, Business. Three columns, a highlighted middle option, a clear upgrade path. What it does not show is the legal question sitting at every tier boundary: who absorbs the cost when a customer grows beyond their tier?

The answer to that question should live in your contract, not in a support team workflow. Without clear terms, the following scenarios become disputes rather than billing events:

• Seat limit exceeded: A customer on a Starter plan exceeds the seat limit mid-cycle. Are they immediately moved to the next tier, billed for overages, warned, or given time to upgrade?
• Downgrade request: A Growth customer wants to move down to Starter after a reorganisation. Can they do that, at what point in the billing cycle, with what notice period, and with what credit treatment?
• Annual true-up: An annual contract customer has grown significantly and a true-up is due. What date is the measurement taken, what rate applies, and were they told in writing this was coming?

Tiered pricing also creates a promise about what each tier includes. If your Starter plan page lists “up to 5 users and 10 GB storage” and your contract says “features subject to change,” you have a tension that a customer pushing back on a feature removal will exploit.

Tier definitions need to be consistent and referenced explicitly in the subscription agreement.

Enterprise pricing is where SaaS founders most often give ground they do not mean to. The deal is large, the customer has procurement requirements, and the pressure to close means standard terms get adjusted without a full accounting of what changed.

What actually happens in many enterprise negotiations:

• Liability caps get raised or removed: Your standard agreement might cap liability at one year of fees. An enterprise customer may push for uncapped liability on data breaches or service failures, which materially changes your risk exposure.
• Uptime SLAs become binding obligations: A good-faith service target may become a measured obligation with service credits or financial consequences attached.
• Custom pricing creates custom scope: A bespoke commercial arrangement often implies bespoke service scope. If a customer negotiated a lower rate in exchange for volume, the contract should state exactly what is included in that volume.

The risk is not that you negotiated badly. The risk is that the custom pricing was handled commercially but the legal terms were not updated to reflect the actual deal.

You end up with a pricing schedule that says one thing and a master services agreement that says another. When something goes wrong, both documents come out, and the inconsistency becomes the customer’s strongest argument.

This is the principle that ties all three pricing structures together. Pricing architecture is a commercial and legal decision at the same time. The pricing page sets expectations. The contract sets obligations.

When those two diverge, you have a risk that no insurance policy covers cleanly and no support team can resolve without escalation.

A practical alignment check covers three things:

• Definitions: Every term on your pricing page that has a quantity attached to it should appear in your subscription agreement with a matching definition. “User,” “workspace,” “monthly active record” and “processed transaction” should mean the same thing everywhere.
• Boundaries: Every pricing tier, usage limit or volume threshold should have a corresponding clause explaining what happens when a customer reaches or exceeds it. Not in a FAQ. In the contract.
• Change process: Pricing changes, especially price increases or feature tier adjustments, should follow the notice requirements in your agreement. If your terms say 30 days’ written notice and your billing system sends a push notification seven days out, you have already breached your own contract before the customer says a word.

This is not about making your contracts longer or more defensive. It is about making sure the commitments you make publicly are the commitments you can actually deliver and enforce.