Your SaaS Renewal Has an AI Tax Built In

A founder I work with runs a 28-person product team at $7M ARR. Last week the renewal quote on her project tracking tool came in 31% higher. Same vendor, same headcount, same workflow.

One line on the quote read "Premium AI tier, pricing reflects standard upgrade." Her old tier wasn't on the menu anymore.

When her ops lead pushed back, the vendor offered a 4% discount and a longer term. The legacy SKU stayed retired.

What's actually happening

Vendors are using renewals to move customers off legacy pricing tiers and onto AI-inclusive ones, whether the customer uses the AI features or not. McKinsey's 2026 software pricing data says 62% of SaaS platforms have introduced an AI-premium tier in the last twelve months. Tropic calls the resulting increase the AI Tax. It's running 20-37% at renewal.

Mechanically, here's how it works. The tier you bought two years ago gets retired. The new equivalent tier includes AI features bundled in. You can't opt out of the AI features. Pricing them as a separate line isn't an option. The migration shows up as "standard pricing update" in the broker's email, not a 30% surcharge.

Atlassian moved a 2,000-seat Jira Cloud Premium contract from $189,000 to $203,175 last year using this kind of migration. HubSpot added a 5% migration fee on existing customers. Slack, Google Workspace, and Salesforce all ran versions of this in 2025.

The vendor isn't raising your price. They're retiring the SKU you bought and selling you a different one.

Why most companies don't push back hard

Two reasons keep showing up.

By the time the quote arrives, there's usually 30 to 60 days to renewal. Switching costs are real. A procurement team that would push back on a 30% increase in a normal cycle quietly accepts the bundled tier because finding, evaluating, and migrating to a competitor takes nine months.

The AI features themselves are real. Whether your team uses them is a separate question, but the vendor can point to actual capability shipping. "You're paying for what we built" is a defensible argument even when nobody on your team has opened the feature.

Switching cost plus feature optics is what makes the migration work.

What to do this quarter

Pull the renewal calendar for your top fifteen software contracts. For each one, check two things. When the contract auto-renews. Whether the vendor has communicated a SKU change in the last six months. SKU retirement notices usually arrive six to twelve months ahead of renewal, buried in product update emails.

If a notice is on file, start the conversation now. Three things to ask for in writing.

First, a SKU-level price lock at the legacy rate, even if the SKU is being retired. Vendors will sometimes grandfather strategic accounts that ask in writing.

Second, a carve-out preventing AI features from triggering an automatic billing uplift. If they won't unbundle the AI, ask for a usage cap before incremental charges apply.

Third, a multi-year cap at CPI plus 3% on any tier you do migrate to. Annual increases of 8-12% compound fast across a five-year stack.

Companies pushing back on these terms are getting half the increase or better. The ones treating renewal as a paperwork exercise are paying the full AI Tax.

The shape of 2026 renewals

Software vendors found a way to monetize AI without proving usage. Customers who take the quote at face value are funding it. Buyers treating each renewal as a real procurement event are negotiating it down or walking.

Your renewal quote isn't a price update. It's a contract you haven't negotiated yet.