Renewal Red Flags: Contract Terms That Will Cost You at Year Two

Most SaaS contracts read the same in the first year: a reasonable price, a discount that feels earned, terms that seem standard enough to sign without a second read. The clauses that actually matter, the ones that determine what you pay in year two, sit a few pages deeper and rarely get flagged before signature. By the time they activate, at renewal, there is no negotiating position left.

Why Year Two Looks Different From Year One

Year-one pricing is built to close a deal. Year-two pricing is built to retain revenue, and those two goals produce very different numbers. Vendors routinely offer an introductory rate, a loyalty discount, or a bundled incentive to win a new logo, then let that discount expire on the first renewal. The base contract price was never the discounted number. It was always the list price, with a temporary reduction attached for exactly one term.

This is not a fringe pattern. Zylo's 2026 SaaS Management Index found that 79 percent of IT leaders encountered a price increase at their most recent renewal, and the Vertice SaaS Inflation Index for 2026 puts average renewal inflation at 12.2 percent, roughly five times the general inflation rate. SaaStr's analysis of 2025 pricing data found SaaS list prices rose approximately 11.4 percent for the year, compared to a G7 inflation rate of about 2.7 percent. Gartner has separately reported that subscription costs from several large SaaS vendors climbed 10 to 20 percent in 2025, well ahead of the 2.8 percent average IT budget growth most finance teams were planning around.

None of this shows up as a single dramatic price hike. It shows up as a collection of individually defensible contract terms that compound quietly across a renewal cycle. That is what makes them dangerous: each clause looks reasonable in isolation, and the total impact is only visible once you add them together.

The Contract Terms to Check Before You Sign

These six terms are the most common source of year-two cost surprises in mid-market SaaS agreements. None of them are unusual enough to raise objections during a first-year negotiation, which is exactly why they get signed without pushback.

• Uncapped or compounding escalation clauses. Most SaaS contracts include an annual price escalator, and a 3 to 5 percent increase pegged to CPI or a fixed rate is standard. The red flag is the absence of a cap, or an escalator applied on top of a rate that was already discounted for year one. A 7 to 10 percent uncapped escalator compounding over a three-year term adds more than 20 percent to your effective price by the final year, with no renegotiation point in between.
• Ramp pricing that resets at renewal. If your year-one price includes language like "introductory rate" or "first-term discount," assume the vendor's renewal quote reverts to list price unless you negotiate otherwise. This is the single most common driver of year-two sticker shock: the contract was never priced at the number you paid in year one.
• Volume discount cliffs. Per-seat discounts in enterprise SaaS agreements are frequently contingent on a minimum seat count. If headcount drops and you reduce your seat count below that threshold at renewal, you do not just pay for fewer seats, you lose the discount tier on the seats you keep. A team that drops from 100 to 80 seats can end up paying nearly the same total, or more, because the remaining 80 seats reverted to a higher per-seat rate.
• True-up provisions without a matching true-down right. A true-up clause requires you to pay for any seats added mid-term, typically at list price rather than your contracted discount rate, settled at renewal. That is a reasonable mechanism on its own. The red flag is a true-up with no corresponding true-down: if usage drops mid-term, the contract gives you no mechanism to reduce your bill, only to increase it.
• Multi-year escalator stacking. Some vendors have shifted to structuring the renewal uplift as a percentage multiplied by the number of years in the new term, rather than a flat annual cap. A 3 percent stated escalation on a three-year renewal can mean a 9 percent increase applied at signing, not 3 percent per year as it first appears. Procurement advisory firms including UpperEdge have flagged this structure as an increasingly common way for vendors to lock in higher Remaining Performance Obligations without triggering the scrutiny a larger single-year increase would draw.
• Short notice windows paired with auto-renewal. A contract can contain every red flag above and still be fixable, provided you catch it before the cancellation notice window closes. A 30 or 60 day notice window buried in an auto-renewal clause is what turns a negotiable contract into a locked one. If you do not know your notice date, none of the other red flags matter, because you will not have the standing to renegotiate any of them.

A Concrete Example of How These Terms Compound

Consider a contract signed at $150,000 for year one: 100 seats at $1,500 per seat, a rate that reflects a 20 percent discount off the $1,875 list price, contingent on maintaining at least 100 seats. The agreement includes a 6 percent annual escalation clause and a true-up provision for any seats added mid-term, billed at list price, with no true-down right.

During year one, the team grows and adds 20 users without formally amending the contract, now running 120 active seats against a 100-seat agreement. At renewal, two things happen at once. First, the true-up clause bills the 20 additional seats retroactively at the $1,875 list rate: 20 times $1,875 equals $37,500. Second, the base contract renews at the new 120-seat count, with the 6 percent escalator applied to the discounted per-seat rate: 120 times $1,500 times 1.06 equals $190,800.

Total year-two cost: $228,300, against a year-one cost of $150,000. That is a 52 percent increase, driven entirely by terms that were present and negotiable in the original agreement. None of the individual clauses would have looked alarming read on their own at signing. Combined, and triggered by ordinary headcount growth, they produced a cost increase well outside any reasonable annual budget assumption.

Why These Terms Slip Through

Red flag clauses survive into signed contracts for a structural reason, not a diligence failure alone: the team negotiating the deal in year one is rarely the team managing the renewal in year two. Legal or procurement may review the initial agreement, but by the time the notice window opens, contract ownership has often shifted to finance, IT, or whoever happens to receive the vendor's renewal email.

That handoff gap matters because notice windows are typically short. Sixty-nine percent of software contracts include an auto-renewal clause with a cancellation window of 30 to 90 days, and 60 days is the most common threshold. Forty percent of organizations still track those dates manually, using calendars or spreadsheets rather than a contract repository, which is exactly the kind of system that fails when a deal owner changes roles or a renewal date shifts mid-year. The result, per Zylo's most recent survey, is that 61 percent of organizations have had to cut a budgeted project or initiative in the past year because of an unplanned SaaS cost increase they did not see coming in time to plan around it.

What to Ask For Before You Sign

The fix for all six red flags happens at the negotiating table in year one, not at the renewal conversation in year two, because leverage to remove a clause is highest before you have signed it.

Ask for an escalation cap of 3 to 5 percent, applied annually rather than stacked across a multi-year term, and get it in writing rather than accepting a verbal assurance that increases will be "reasonable." If the vendor offers an introductory discount, ask directly what the year-two price will be and get that number, not just the year-one number, into the contract. Request that any minimum seat count tied to your discount tier include a grace band, typically 10 to 15 percent, so a modest headcount reduction does not trigger a full tier reset. If the contract includes a true-up provision, negotiate a matching true-down right so usage reductions can lower your bill the same way usage increases raise it. And treat the notice window as a non-negotiable term worth fighting for on its own: extending a 30-day window to 90 days costs the vendor nothing and gives your team the runway needed to catch every other red flag before it activates.

Frequently asked questions

What is a normal price escalation clause in a SaaS contract?

A 3 to 5 percent annual increase, tied to CPI or set as a fixed rate, is standard in most mid-market SaaS agreements. The red flag is not the existence of an escalator but the absence of a cap, or an escalator layered on top of an already-discounted year-one price. Anything above 7 percent annually, or an escalator that compounds across a multi-year term without a ceiling, is worth pushing back on before signing.

What is the difference between a true-up and a true-down clause?

A true-up requires you to pay for seats or usage added during the contract term, typically at list price, settled at renewal. A true-down would let you reduce your bill if usage drops during the same period, but most vendor contracts only include the upward mechanism. Negotiating a matching true-down right is one of the highest-value, most frequently overlooked asks in a SaaS renewal.

How much can a SaaS contract increase between year one and year two?

It varies widely, but combined red flags routinely push increases well past a single-digit escalator. Zylo's 2026 index found 79 percent of IT leaders saw a price increase at their last renewal, and the Vertice SaaS Inflation Index puts average renewal inflation at 12.2 percent. When ramp pricing, true-up charges, and escalation clauses stack together, as in a contract that grows seats mid-term, increases of 30 to 50 percent in a single renewal are realistic.

Can I renegotiate these red flag terms after I have already signed?

Yes, but with less leverage than you would have had before signing. Mid-term amendments are possible for specific issues, such as adding a seat reduction right, but a full escalator cap or true-down clause is far easier to win during the original negotiation or at a scheduled renewal, before the auto-renewal clause has triggered and locked you into another full term.

What is the single most important term to check before signing a multi-year SaaS contract?

The notice window. Every other red flag in this list is negotiable as long as you have standing to renegotiate, and that standing disappears the moment an auto-renewal clause fires. Confirm the exact notice date, not just the renewal date, and build your internal review process around that earlier deadline rather than the contract's end date.