Practical guide
How to Prepare for a SaaS Price Increase at Renewal
A higher renewal quote is rarely the real problem. The problem is when it shows up. If the new price lands a few weeks before the notice deadline, the team has no time to check the contract, look at usage, talk to the vendor, or consider alternatives. The renewal goes through at the new price because the window to do anything else has closed.
October 30, 2026 · 8 minute read
Why price increases catch teams off guard
A higher renewal quote is rarely the real problem. The problem is when it shows up. If the new price lands a few weeks before the notice deadline, the team has no time to check the contract, look at usage, talk to the vendor, or consider alternatives. The renewal goes through at the new price because the window to do anything else has closed.
Most of the leverage you have comes from time. Teams that learn about an increase early can ask questions, adjust seats, and make a real decision. Teams that learn about it from the invoice cannot.
This guide covers how to prepare before a renewal quote arrives, what to do when it does, and how to keep the next one from being a surprise. It is written for IT, ops, and finance teams. It is not legal advice, so involve your legal or procurement contacts for contract questions.
Step 1: Know your dates before the vendor does
Every renewal has three dates that matter here:
- Term end date: when the current agreement ends
- Notice date: the last day you can cancel or change terms, based on the notice period
- Decide-by date: your own internal deadline, set a few weeks before the notice date so there is time to act on the decision
Plan around the notice date, not the renewal date. A renewal that ends in June with a 60-day notice period really needs a decision in early April, and the work to reach that decision should start well before that. If the notice period is hard to find, see how to find the notice period in a software contract.
Step 2: Read what the agreement says about price
Before any conversation with the vendor, pull the signed agreement and order form and look for:
- A price change clause: whether increases at renewal are limited, and how
- Notice requirements for price changes: whether the vendor must tell you about a new price by a certain point before renewal
- Term and pricing commitments: whether your current price is fixed for the full term
- Which document controls:your signed order form versus the vendor's online terms
- Auto-renewal language: what happens if nobody acts
Write what you find on the renewal record so the next person does not have to dig for it. If anything is unclear, ask your legal or procurement contact before you rely on it.
Step 3: Assign one owner
A price increase needs one person who is responsible for getting to a decision. Without a named owner, IT assumes finance is handling it, finance assumes the team lead is, and the notice date passes.
The owner does not have to do everything. They make sure the contract gets checked, usage gets reviewed, the vendor conversation happens, and a decision is recorded before the decide-by date. Name a backup too. For more on picking owners, see who should own software renewals.
Step 4: Check usage before you talk about price
The cheapest seat is the one you stop paying for. Before discussing the new price, confirm what you actually need:
- Count active users against paid seats
- Find seats assigned to people who have left or changed roles
- Check whether everyone needs the current plan or tier
- Ask team leads about planned hiring or reductions for the next term
Fixing quantity first changes the base the new price applies to. It also makes the vendor conversation more concrete. For the fields worth tracking per tool, see software license inventory: what to record for every license.
Step 5: Break the new quote into parts
A renewal quote often bundles several changes into one number. Separate them so you know what you are actually being asked to pay for:
- Price change on the same scope: the same seats and plan at a new rate
- Packaging changes: features moved into a different plan or bundle
- Added seats or usage: growth you may or may not want
- New fees: charges that were not on the last invoice
Ask the vendor in writing what changed and why. A clear answer helps you decide. A vague one tells you there may be room to talk.
Step 6: Decide, then talk to the vendor
With the contract, usage, and quote in hand, the owner can bring a recommendation to whoever approves spend. Common options:
- Renew as quoted when the tool is critical and the change is acceptable
- Renew with changes: fewer seats, a different plan, or a different term
- Counter: propose a specific price, term, and any limit on future increases you want written into the order form
- Replace or cancel when the tool no longer earns its cost, leaving time to move data out
Whatever you decide, record it on the renewal with the reason and who approved it. Put anything the vendor agrees to in the signed paperwork, not just an email. For a structured pass over each renewal, see the software renewal review checklist.
Step 7: Budget for it
Once the decision is made, update the expected cost for the next term in your budget. If the decision is still open when budgets are due, carry the quoted price as the planning figure, mark it as an assumption, and note the decide-by date. Review the line again after the decision lands. To plan every renewal across the year, see how to build a 12-month software renewal calendar for budget planning.
Step 8: Make the next increase less of a surprise
The best time to prepare for the next price increase is right after this renewal closes.
- Record the new term end date and notice date
- Note what the agreement now says about future price changes
- Confirm the owner and backup
- Set reminders counted back from the notice date, sent directly to the owner and backup, not a shared inbox (see why shared inboxes fail as renewal reminder recipients). See the 90/60/30-day renewal reminder schedule
- Bring the renewal into your regular review. See how to run a quarterly renewal review meeting
If the agreement auto-renews, also see how to avoid surprise SaaS auto-renewals.
Common mistakes
- Waiting for the renewal quote before checking the contract
- Planning around the renewal date instead of the notice date
- Negotiating price before fixing seat count
- Treating the quote as one number instead of separating its parts
- Accepting verbal or email promises that never make it into the signed paperwork
- Leaving the renewal without a named owner
- Forgetting to update the budget after the decision
FAQ
When should we start preparing for a SaaS price increase?
Well before the notice date, not the renewal date. Give yourself enough time to check the contract, review usage, talk to the vendor, and get approval before the notice date passes.
Can a vendor raise the price at renewal?
It depends on your agreement. Some agreements limit increases or require advance notice of new pricing, and some do not. Read your signed order form and agreement, and ask your legal or procurement contact if the terms are unclear.
What should we ask the vendor when a renewal price goes up?
Ask what changed, which parts of the quote are a price change on the same scope, and which reflect added seats, packaging changes, or new fees. Ask for the answer in writing.
Should we reduce seats before or after negotiating price?
Before. Confirming what you actually need first lowers the base the new price applies to and makes the conversation more concrete.
Who should handle a renewal price increase?
One named owner, usually the person closest to the tool, with a backup. Finance and procurement support the decision, but one person should be responsible for getting it made before the deadline.