SaaS Renewal Price Increase: Check the Quote Before You Agree

AI-generated editorial illustration by Viaclause. The person depicted is fictional.

Before arguing about the percentage increase, separate the price change from changes in seats, usage, discounts and contract length. Then compare the vendor's proposed numbers with the terms that govern your purchase.

Use the contract renewal checklist to connect this issue to the renewal decision, terms and notice record.

A larger invoice does not tell you which of those inputs changed. A useful challenge identifies the disputed line, its contractual basis and the result you are requesting.

Collect a packet that explains both prices

For a US business subscription, gather the current signed order, applicable master terms, amendments, last comparable invoice and new renewal quote or notice. Add the price schedule or product terms referenced by those documents. Preserve the versions and dates rather than assuming today's website is the version governing your account.

Use the same measurement period on both sides. Convert a monthly per-seat quote and an annual bundle into comparable totals, but keep payment frequency separate from the commitment period. Note currency, taxes and one-time charges separately.

Our proposed comparison record contains these fields:

• Product and edition, with included features or service limits.
• Committed seats or other billing units.
• Unit price, discount and discount expiry.
• Included usage, overage rates and minimum commitments.
• Subscription duration and billing frequency.
• Renewal date, notice date and required non-renewal action.
• Contract clause or order line supporting each input.

Explain the increase in dollars before percentages

Consider a hypothetical subscription with 100 seats at $40 per seat per month and no taxes, discounts or additional charges. Its annual price is $48,000. A proposed renewal offers 120 seats at $44, producing $63,360 a year.

The total increase is $15,360, or 32 percent. The unit price increased by 10 percent and the seat count by 20 percent. Those percentages multiply; adding them would produce the wrong total.

One transparent way to allocate the dollar change is to hold the original seat count fixed while changing the unit price:

• Unit-price effect: 100 × ($44 − $40) × 12 = $4,800.
• Additional-seat effect at the new rate: 20 × $44 × 12 = $10,560.
• Combined increase: $4,800 + $10,560 = $15,360.

This allocation is a proposed comparison method, not an accounting rule. Using the old unit rate for the seat effect would allocate the interaction differently while preserving the same total. Show which method you chose.

Now the buyer has two distinct questions: why did the unit rate change, and are the additional 20 seats required? The headline 32 percent increase cannot answer either one.

Compare the notice with the applicable terms

For a concrete vendor example, HubSpot's General Terms, sections 3.1 and 3.2, distinguish current-term fee changes from adjustments at renewal. Section 3.2 describes increases up to then-current list price and at least 30 days' advance notice, while pointing to product-specific differences. Section 3.1 lists exceptions for changes during the current term, including limits, upgrades, additional purchases and order terms.

Those public terms are an example, not a rule governing all SaaS purchases. Check your applicable order, terms and amendments before drawing a conclusion about a particular increase. A notice defect or disputed calculation needs case-specific assessment; this worksheet does not establish that an invoice is invalid or that payment may be withheld.

A worksheet for checking your renewal quote

Copy this table into your own document or spreadsheet. Complete one comparison per product or edition. Keep the order, amendment or quote supporting every entry beside it. Blank or uncertain inputs are questions for the vendor, not zeros.

For this simple model, enter D as a decimal: 10 percent becomes 0.10. Calculate N = P × (1 − D), then C = 12 × U × N + F + V. If the quote already gives a net unit rate, use that as N and do not subtract the discount again. Compare the change as C renewal − C current; divide that difference by C current and multiply by 100 for the percentage change. If C current is zero, a percentage increase is undefined: report the dollar difference.

The model assumes stable monthly unit pricing and quantities over twelve months. Use a period-by-period schedule for ramped prices, changing quantities, credits or discounts expiring partway through the year. Keep uncertain usage in separate low, expected and high scenarios, with the same usage assumption on both sides. Do not combine quantities measured in different units. An annual comparison is not the full obligation under a multi-year commitment; total each committed period separately and add applicable one-time charges and taxes.

Quick check: 100 seats × $50 gross monthly rate × (1 − 0.20 discount) × 12, plus $1,200 fixed fees and $600 estimated usage charges, gives $49,800. These invented inputs demonstrate the formula; they are not market benchmarks.

Why fewer seats might produce no savings

A smaller order may also change your unit price. Salesforce's Main Services Agreement, section 11.2, provides for repricing when renewal volume or subscription length decreases, without relying on the prior term's unit pricing. It also addresses promotional or one-time pricing renewing at the applicable list price, unless the order expressly provides otherwise. The inspected agreement is dated September 1, 2026; check which version your order incorporates.

For the buyer, that means a seat-reduction proposal needs its own quote. Do not calculate the savings by multiplying fewer seats by yesterday's rate unless the vendor has confirmed that rate for the new scope.

Here is a separate hypothetical check, not a Salesforce price example: 100 seats at $40 per month cost $48,000 annually. Reducing to 80 seats at a revised $50 rate still costs $48,000. You have cut seats by 20 percent but saved nothing. At 80 seats, the monthly unit rate must be below $50 to reduce that annual subtotal, assuming the same term and no other charges. Compare the proposed total with the current total before calling a reduction a saving.

Put the price notice and non-renewal cutoff on the same timeline. Record when the notice arrived, what price it actually specified, when the increase would begin and how the required account action or notice must be completed. If the documents leave too little time or conflict, give counsel the dates and original communications rather than a summary alone.

If the cutoff has already passed, use our steps for reviewing a missed SaaS renewal deadline alongside this price comparison. Assign responsibility using the renewal ownership guide, so a pricing discussion does not leave the required action unassigned.

Ask for a reconciliation you can verify

Use a bounded request such as this proposed example:

Please reconcile the current and proposed renewal totals by product, unit count, unit rate, discount and term. Identify the order or provision supporting each change, confirm the required notice dates, and explain whether the additional units are optional. Our current comparison shows [specific difference]. We are asking for [corrected quote, explanation or alternative scope].

Do not assume this request stops renewal or extends a deadline. Track the required action separately while the commercial discussion continues.

If the vendor supplies a revised quote, repeat the comparison. Record the agreed units, total commitment and dates in the final document, then give the executor a clear instruction supported by the completed review.

If the vendor’s explanation conflicts with your signed terms or the financial exposure is material, bring the disputed clause, both quotes and your dated timeline to counsel. Our contract review packet guide helps you organize that request.

How this article was prepared: Viaclause inspected the linked public vendor terms and checked the hypothetical calculations. The worksheet is a proposed comparison method, not a tested savings claim. No private customer contract, negotiated vendor quote or lawyer review is represented.

Sources

• HubSpot Customer Terms of Service, General Terms last modified September 16, 2026, sections 3.1 and 3.2. Inspected September 27, 2026. Supports only the named vendor example. Calculations and correspondence template are Viaclause's hypothetical working aids.
• Salesforce Main Services Agreement, Salesforce, September 1, 2026, section 11.2, page 8. Inspected September 27, 2026. Supports the promotional-pricing and reduced-volume or shorter-term repricing examples. These are public vendor terms, not a finding about any reader's contract.