The SaaS renewal playbook for 2027: negotiate with usage data, not gut feel

The SaaS renewal playbook for 2027: negotiate with usage data, not gut feel

For years, a SaaS renewal negotiation went roughly the same way. The vendor sent a quote a few weeks out. Someone checked it against last year’s invoice, asked for a few points off, and signed. The seat count rolled forward because nobody had time to argue with it.

That model is breaking, and Microsoft is the clearest example of why. Its July 2026 price increase is the one on every renewal calendar this winter. But the change that did the most to your bargaining position happened eight months before that, and it came with a lot less noise.

Here’s the uncomfortable part. The vendor walks into the call knowing how many seats you bought and how many people actually log in. Most buyers walk in with last year’s invoice and a spreadsheet called something like licenses_FINAL_v3.

This piece is about closing that gap. It covers what to pull 90 days before a renewal, how to model the tier mix and the metered charges, what to ask for and when, and what to write into the contract. Microsoft is the worked example because it’s the renewal everyone is watching. The method is meant for every renewal on your list.

Microsoft’s 2026 price increase started in November

On November 1, 2025, Microsoft removed its Level B through D volume discounts on Enterprise Agreement and MPSA online-services renewals (Microsoft Licensing). Those tiers used to reward larger customers with a lower per-seat price. The change doesn’t bite on the day it was announced. It takes effect at your next agreement renewal or new purchase, with on-premises and Government/Education excluded.

SoftwareOne estimated the impact on affected EA and MPSA customers at 6 to 12% (SoftwareOne). That’s a third-party estimate, not a Microsoft figure, but it gives you the order of magnitude. And it lands before the July list prices even enter the math.

Then came the headline change. On July 1, 2026, Microsoft’s US commercial list prices moved like this (Microsoft 365 Blog; US Cloud):

• Office 365 E3: $23 to $26 per user per month (13%)
• Microsoft 365 E3: $36 to $39 (8%)
• Microsoft 365 E5: $57 to $60 (5%)
• F3: $8 to $10

Put the two together and the picture changes. If you’re on an EA or MPSA and your renewal falls in the Q4 or January cluster, your quote can carry both increases at once: the lost volume discount and the new list price. A team that budgeted 5% for its E5 renewal because that’s the number in the press coverage is probably budgeting low.

Two caveats before going further. These are US list prices, and very few large customers pay list. And the November change applies only to EA and MPSA (Microsoft Licensing). If you buy through a Cloud Solution Provider or on an MCA-E, your price and discount are set by the partner and aren’t published anywhere, so treat the numbers here as a way to size the change, not a quote.

None of this is secret. Some licensing advisers have written about the November-to-July connection. What your reseller’s renewal email usually won’t do is hand you the numbers you’d need to push back on it.

Pull four numbers 90 days before the renewal

Ninety days gives you time to find the problems, fix some of them, and still have a position before the vendor’s quote arrives. Four numbers do most of the work.

Active users vs. licensed seats. How many seats you pay for, and how many people used the product in the last 30 or 90 days. One way I’ve heard the gap put is “owned vs. used vs. assigned,” and it’s a useful split: seats you bought, seats assigned to a person, and seats that person actually uses. Each gap has a different fix.

Last-login distribution. A single average hides the story. You want the spread: how many users logged in this week, this month, this quarter, and not at all. The long tail of people who haven’t logged in for 90 days is where the easy savings sit.

Feature usage by tier. A premium seat is only worth it if the person uses the premium features. For Microsoft, that means knowing who actually touches the capabilities that separate E5 from E3.

Contract value vs. invoiced spend. What the contract says you committed to, against what you were actually billed. Mid-term additions, true-ups and add-ons drift, and the renewal quote usually starts from the higher number.

What does this kind of pull turn up? Our benchmark report puts license non-utilization across a dozen widely deployed enterprise apps between 24% for Slack and 55% for Salesforce (Torii). Read that as seats not earning their keep rather than a precise, defined rate; the report doesn’t publish its method. It also doesn’t include Microsoft, so don’t carry those percentages over to your 365 estate. The same report found about 2.5% of seats in paid apps still assigned to people who had left the company (Torii). That’s roughly 1 in 40, sitting on an invoice, belonging to nobody.

Your numbers won’t match these. But almost nobody’s come back clean.

Match each seat to the tier it needs

Once you know who uses what, you can model the tier mix. This is where Microsoft’s price gaps matter more than the increase itself.

At the new US list prices (Microsoft 365 Blog), Microsoft 365 E5 costs $21 per user per month more than E3, or $252 a year. E3 costs $29 a month more than F3.

Here’s an illustrative example, using list prices. Take a company with 1,000 users, all on E5. The July increase from $57 to $60 adds $36,000 a year to that bill. Now say the usage pull shows 200 of those users never touch an E5-only feature. Moving them to E3 saves 200 × $252, or $50,400 a year.

Right-sizing a fifth of the seats saves more than the entire price increase. That’s the argument for doing the tier work before arguing about the sticker price.

The same logic runs down to F3, Microsoft’s frontline tier. It’s far cheaper and far more limited, so check what each group of users actually does before moving anyone. A blended model, meaning the count of seats on each tier multiplied by its price, is what you take into the call.

One trap sits inside E5. Security Copilot is included with Microsoft 365 E5 and E7 as a monthly capacity allowance: 400 Security Compute Units per 1,000 licensed users, with no rollover (Microsoft Learn). Unused units disappear at the end of the month. That’s worth knowing in both directions. If you cut E5 seats, you also cut the allowance. If your security team leans on Security Copilot heavily, the allowance may run out, which matters for the next section.

Model the metered charges as a range

Seat prices are the easy part to forecast. The harder part is anything billed by consumption.

Microsoft has announced a pay-as-you-go rate of $6 per SCU for Security Copilot usage beyond the included allowance. As of this writing, it isn’t live. Microsoft says it will start “at a future date,” with 30 days’ notice (Microsoft Learn). You’ll see some renewal coverage describe it as an active charge. Microsoft’s own page says otherwise, and it’s worth checking before you budget against it.

So how do you plan for a charge that doesn’t exist yet? As a range, not a number. Your low case assumes you stay inside the allowance. Your high case assumes your heaviest month of use continues after the overage switches on. If the 1,000-seat example above ran 100 SCUs over its 400 in a month, that’s $600 a month at the announced rate. Small on its own; not small once agents and other metered tools stack on top.

That stacking is the bigger pattern. More software is shifting to a seat price plus a usage charge, and the usage part is what surprises finance mid-year. I covered who ends up owning that bill in “FY2027 is the year finance takes over the AI budget,” the previous part of this series. For renewals, the practical step is simpler: give every metered line a floor and a ceiling, and show finance both.

Run the negotiation in a set order

With the numbers in hand, the sequence matters as much as the asks.

Start with utilization. Open with what you use, not with what you’d like to pay. “We have 1,000 E5 seats and 200 of them don’t use E5 features” is a different conversation from “can you do better on price?” It turns the call from a discount request into a correction of the bill.

Then ask for flexibility, not just a lower rate. Two terms carry most of the value:

• Swap rights, so you can move seats between tiers during the term as usage changes
• True-down rights, so you can reduce seat counts at set points instead of only adding them

A discount helps once. These terms keep helping every time your headcount or usage shifts.

Then time the ask. Vendor sales teams work to quarterly and annual targets, and a deal that closes inside the period counts toward them. For Microsoft, aim to have your position ready well before its fiscal year closes, and before the end of whichever quarter your renewal falls near. Getting your numbers together in the final week of the quarter is too late to be useful.

Write the terms into the contract

A good call is worth nothing if the terms don’t make it onto paper. Four clauses do most of the protecting:

• Price caps on renewal increases, stated as a percentage
• True-down at defined dates, with the minimum seat count spelled out
• Benchmark clauses that let you revisit pricing if the market moves
• Notice periods long enough to run this whole 90-day process before auto-renewal kicks in

Microsoft’s own language shows why term length is a pricing decision. Its FAQ on the 2026 changes says: “Customers on existing multi-year agreements will continue at their current pricing until renewal” (Microsoft Licensing).

Read that from the other side. A multi-year agreement protects you from repricing during the term, and the full weight of every change lands on the day it renews. So the price you lock in this winter is the base for the next cycle too. If the tier mix is wrong at signing, you’re locking in the wrong mix at the new price.

Repeat it for the rest of your top ten

Microsoft is the example, not the whole job. The same four numbers work for any renewal: seats against active users, the login spread, tier fit, and contract value against invoiced spend.

The benchmark range above suggests where to look next. If a widely deployed app can sit anywhere from roughly a quarter to over half non-utilized (Torii), your other large renewals probably deserve the same pull. Rank them by renewal date and contract value, and start the clock 90 days out for each.

The hard part is getting the data together, especially across ten vendors with ten admin consoles. Torii is one way to do that. For Microsoft 365 Copilot specifically, it syncs purchased, assigned, and unassigned seats, plus prompts and active days over 7, 28, 90, and 180-day windows (Torii Product Updates).

So start with one. Find your largest renewal in the next six months, count back 90 days, and put the seat pull on the calendar for that date. If the 90-day mark has already passed, pull the numbers anyway. A late count still tells you which tier mix to ask for, and it’s cheaper to find the wrong mix now than to lock it in for another term.