Renewals: The Negotiation You Can Actually Win

Renewal Power Plays

Hey everybody, and welcome back to the Operational ITAM Podcast. I'm Bill Van Nort, and today we are finally talking about the one meeting in this entire discipline where you hold the cards. 31 days ago, on the 1st of July, Microsoft raised list prices across most of the Microsoft 365 commercial suites. Office 365 E3 went from $23 per user per month to $26.

Microsoft 365 E5 went from $57 to $60. Some of the frontline plans went up by as much as 43%. That is not the interesting part. The interesting part is that Microsoft announced all of it on the 4th of December, seven months of warning, published on their own blog, with a table, with the percentages, with the effective date. Everybody got the memo.

Almost nobody had a plan. That gap between the memo and the plan is the entire subject of today's episode. Good morning, good afternoon, or good evening, wherever you're listening from. This is the show where we take the unglamorous machinery of enterprise technology and make it make sense. Grab your coffee. Today, for the first time in this series, we are playing offense.

Here's the premise. Look back at what we've covered. The audit letter that arrives on somebody else's schedule. The settlement, where you're negotiating from behind. Shadow IT, which happens whether you sanction it or not Disposal, where the best possible outcome is that nothing happens to you Every one of those is reactive, something arrives and you respond well or badly, The renewal is different, The renewal is the only recurring event in asset management where the date is known years in advance Where the other side needs something from you And where you get to decide when the work begins And we blow it consistently as a profession.

Let me give you the numbers and I'll name the source because on this show, we do that. Zylo publishes an annual benchmark called the SaaS Management Index. The 2026 edition says the average organization runs 305 applications and spends roughly $55.7 million a year on SaaS, up about 8% year over year, while the application count stayed essentially flat.

Read that again. Flat application count. 8% more money. The growth isn't sprawl anymore. It's price. Same report. 79% of IT leaders saw a price increase at renewal in the last 12 months. 78% got hit with unexpected charges tied to consumption or AI pricing. And 61%, 61, cut a project or an initiative to pay for software cost increases they did not plan for.

That last statistic is the one I'd put on a slide for your CFO. Software renewals are now canceling roadmap items. Not headcount, not capital projects. Roadmap. So here's my thesis, and it is not subtle. In a renewal, timing beats tactics. The clever negotiator who starts 60 days out loses to the mediocre one who started 18 months out. Every lever you'll hear about today takes months to build and four seconds to deploy.

The 18-Month Clock

Which brings us to today's framework. I call it the 18-month clock. Four positions on the face, and each one has exactly one job. Position one, 18 months out, count. This is your effective license position from episode three, aimed at a specific agreement with a specific end date. Entitlements on the left, deployments on the right, truth in between.

But for a renewal, you need a third column that an audit never asks for, usage. Not deployed, used. Logged in during the last 90 days and doing something once they got there. There's a version of shelfware we didn't fully cover in episode 3. The license that is deployed, assigned, compliant, defensible, and completely idle. It survives every audit.

It fails every business case. That same Zylo Index puts average license utilization at about 54%, which means roughly a third of what you bought is doing nothing at all. At 18 months, that dead third is an asset. It's the thing you're going to stop paying for. At 60 days, it's just a number you didn't have time to verify, and the vendor will happily tell you their telemetry disagrees with yours.

Position 2. 12 months out. Decide. Not decide whether to renew. Decide what you want the estate to look like on the other side. Most programs skip this, and it costs them everything. They go straight from counting to negotiating with no target state, so the vendor supplies one. The vendor's target state is always the same. More of everything.

Longer term. Newest tier bundled in. Yours is a specific sentence. 1,100 seats instead of 1,400. Two tiers instead of four. And the analytics module dropped entirely because 40 people use it. Write that sentence at 12 months and get your business owners to agree to it at 12 months when nobody is under deadline pressure. Try to take 300 seats from a department six weeks before renewal, and you'll lose that fight internally before you ever reach the vendor.

Position 3. Nine months out. Build the alternative. This is the position that actually generates leverage, and it's the one that gets skipped. Leverage in a renewal is not persuasion. It's not relationship. It's not how well you know your account rep. Leverage is a documented, costed, credible answer to the question, and what if we don't.

Credible is the operative word, not a threat, not a bluff. An actual analysis, what it would cost to move, how long it would take, who would do it, and what breaks. You may never execute it, but you have to be able to hand somebody a page.

VMware and Java Leverage

Let me make that concrete with two live examples, both of which are still unfolding right now. Example 1. Broadcom and VMware. Perpetual licensing ended, the catalog collapsed into a handful of subscription bundles, and pricing moved to a per-core model with minimum core counts per processor. Independent advisory firms tracking these renewals report opening quotes running two to five times prior cost.

Distributor communications reported by the Register in 2025 described the minimum order jumping from 16 cores to 72 per line, plus a 20% penalty for letting a subscription lapse past its anniversary. Here's the part that matters. Those same firms report that customers who arrived with a right-size core count, and a credible migration plan settled 15-30% below the opening number, and that opening quotes routinely overstated the actual footprint by 20-40%.

20-40% of the quote was error. The people who found it had counted their own cores before the quote arrived. Example 2. Oracle and Java. In January of 2023, Oracle replaced its per processor and named UserPlus metrics with the Java SE Universal subscription, priced per employee. Every employee. Not Java users. Not developers. Everyone on the payroll.

And Oracle's default reading includes contractors with system access. List has run around $15 per employee per month at the low bands. Do that math for a 10,000-person company, and it's roughly $1.8 million a year for a runtime that might live on 200 servers. The market responded. Research from the ITAM forum and Azul found around 79% of organizations have already migrated, are migrating, or plan to.

OpenJDK is free. Adoptium, Coretto, Zulu, Red Hat, and Microsoft all publish builds. So the customer who walks into an Oracle Java renewal with a completed estate sweep is having a completely different conversation than the one who walks in with a purchase order. Both examples make the same point. The alternative doesn't have to be executed.

It has to exist, on paper, with numbers. Position 4. Six months out. Ask. Now, and only now, you open the commercial conversation. You have your count, your target state, and your alternative. Six months gives both sides room to move, room to escalate internally, and room for you to walk away and come back, which is a move you cannot make at 60 days.

And that's the clock. Count. Decide. Build. Ask. 18, 12, 9, 6. There's a fifth position, and it's the one most of you are actually standing on. Call it the 60-day cliff. Inside 60 days, you are not negotiating. You are accepting, possibly with a small discount attached to make it feel like a negotiation. Everyone in the room knows it. The vendor knows it best.

Let's take a quick break. If you're getting value from this show, subscribe wherever you're listening. And if you know someone with a renewal coming up, send them this episode. It's free and it might be worth six figures to them. Every episode with full transcripts is at operationalitam.com.

Renewal Traps

Okay, now on to part two, the traps. I'm going to give you five and every one of them I have either walked into personally or watched someone walk into from about 10 feet away. Trap one, the notice window. Almost every agreement you hold contains an automatic renewal clause with the notice period. 30 days, 60 days, 90 days. Miss it and you have renewed, at whatever terms the contract specifies, which are rarely the terms you wanted.

The operational fix is embarrassingly simple. Stop tracking renewal dates. Track notice dates. The renewal date is decoration. The notice date is the real deadline, and it sits one to three months earlier. Put it in the calendar, put a second reminder 30 days ahead of that, and hang the whole clock off it. Procurement reporting suggests notice windows have been quietly shrinking, 60 days becoming 30, so the clause you read in 2022 may not be the clause you're under today.

Read the current paper, not your memory of it. Trap 2 – The Uplift Clause This is the automatic annual increase written into the contract itself, and it's the single most expensive sentence in enterprise software. Aggregated procurement analysis puts auto-uplift clauses in the high 80% range of SaaS contracts, with typical asks around 11.5%.

An 11% annual uplift, compounded over three years, is a 37% increase before anyone negotiates anything. The fix happens at signature, not at renewal. You want an explicit cap, not commercially reasonable increases, not silence, a number. If the vendor insists on an index, tie it to something published, CPI as standard, then cap the index.

And get the cap to survive the renewal, so you're not renegotiating the ceiling every time. Opinion. Flagged as opinion. I would trade a point of first year discount for a hard uplift cap every single time. The discount is one year. The cap is the whole relationship. Trap 3. The Coterm. Your vendor offers to align all your agreements to one common date.

For simplicity. For your convenience. Maybe with a little proration credit as a sweetener. Ask yourself whose convenience that actually is. Coterming builds one enormous renewal event covering products with completely different levels of criticality. And once they're on one paper, you can't walk away from part of it. The module nobody uses is now welded to the platform your order-to-cash process runs on.

That's not simplification. That's consolidation of the vendor's leverage, and you paid a proration credit for it. There are legitimate reasons to co-term. Administrative overhead is real, and if you're a two-person team with 40 agreements, I understand the appeal. But make it a decision, not a favor you accepted. Opinion flagged. My default is staggered deliberately so there's always a renewal in flight and the vendor always knows another one is coming.

Trap 4. The Discount Shell Game The vendor quotes you a discount off list price. You feel good. 22% off list sounds like a win. List price is a number the vendor invents and controls. If list went up 13% in July, a 22% discount off the new list may still be more money than you paid last year off the old one. So never negotiate against list.

Negotiate against your own unit price paid last term. Dollars per user per month, per core, per employee. Reduce it to a unit and compare unit to unit across terms. That single discipline will catch more money than every other tactic in this episode combined, because it's the one thing the quote is structured to prevent you from seeing. Trap 5.

The Multi-Year Commitment Multi-year is often the right answer. Price protection has genuine value, especially in a market where list prices move the way they move this year. But be clear about what you're selling to buy it. You're selling optionality, the right to reduce quantity, the right to leave, and often the right to renegotiate when the business changes.

So price them. Three things to insist on. One, a true down right at each anniversary, even capped at 10 or 15%, a floor you can descend to. Two, the uplift cap, applied to every year of the term. Three, an assignment clause that survives a merger or a carve-out, because if your company gets acquired and the license doesn't transfer, you just bought a very expensive coaster.

Six Weeks Left

That's the five. Let's do a listener question. This one comes from Indianapolis, and it is painfully well-timed. He writes, Our renewal is in six weeks and the quote doubled. What do I do? I'm going to answer this honestly, because you deserve that more than you deserve encouragement. At six weeks, you cannot win this negotiation. The leverage isn't there.

Anyone who tells you otherwise is selling a webinar. But you can do three things, and all three are worth real money. First, stop negotiating price and start negotiating time. Ask for a short-term extension, three months, six months, at current pricing or close to it. Vendors grant these more often than you'd think, because it keeps the revenue and keeps you at the table.

That extension isn't a concession you won, it's runway you bought, and you spend every day of it doing positions one and three of the clock. Second, attack quantity, not rate. You will not move their rate in six weeks. You may absolutely be able to move your count, because that's your data, not theirs. Pull 90 days of usage. Find the inactive seats.

Every seat you remove comes off at full price, which is a better outcome than any discount you were going to get. Third, and this is the one people skip, read the actual clause that doubled it. An uplift clause? A tier change? A metric change, like the Oracle employee metric? A module that used to be optional? The quote doubling has a cause, and the cause is written down somewhere.

You can't argue with a number. You can absolutely argue with a clause applied incorrectly, and I've seen that go the customer's way more than once. Then, the day it's signed, calendar next year's notice date, and start the clock. This year, you're paying tuition.

The Serials Department

Now let's go back to the library. We have been in this library since episode one. In episode three, I told you the hardest truth in software asset management. None of these books are yours. Every volume on loan, every loan with terms. In episode five, the late fee notice arrived, and I told you the librarian doesn't actually want your late fees.

The librarian wants you borrowing more books. Today we go to a different room. Down the hall, past circulation, there's an office with a wall of binders and a very tired person inside. That's the serials department. Journal subscriptions. The renewals. And the serials budget works exactly like your software budget. The publisher sells a bundle, take the whole package, get a better per title rate, sign for multiple years.

It renews quietly, it rises annually, and nobody reads most of it. This isn't a metaphor I'm inventing. In 2019, the University of California system walked away from its agreement with Elsevier, one of the largest academic publishers in the world. They canceled. The sky did not fall. Two years later, they signed a new agreement on terms they actually wanted.

They could do that for one reason. They knew exactly which journals the researchers were reading, and how often, and could prove it. That's the whole lesson. The librarian who knows precisely which titles get opened has a completely different conversation with the publisher than the librarian who doesn't. Same publisher. Same bundle. Same price list.

Different conversation. Because one of them has the usage data and the other one has a feeling. You are the librarian. Go get the usage data. Which brings us to today's principle. And let's take the whole run from the top. Hardware is a custody discipline. Software is an evidence discipline. Audit defense is a process discipline. Settlement is a commercial discipline.

Shadow IT is a service discipline. Refresh is an economics discipline. Disposal is a liability discipline. And renewal is a leverage discipline. Leverage is not aggression, and it is not a personality trait. Leverage is preparation that arrived early enough to matter. It is a count you can defend, a target state your business already agreed to, and an alternative that exists on paper.

Build those three things, and you barely have to negotiate at all. Show up without them, and no amount of skill in the room will save you because the deal was decided months before anyone sat down. Class dismissed. Here's your homework, and this one takes about 90 minutes. List every software agreement above whatever threshold matters in your organization.

For each one, capture three dates, the renewal date, the notice date, and the date the last agreement was signed. Most of you will find the notice date is missing entirely, and that alone is worth the exercise. Then count how many renew in the next 18 months. That's your real workload. Find the largest number on that list and ask one question.

Who owns this renewal? If the honest answer is nobody, you just found the most valuable 90 minutes available to you this quarter. Next episode, we answer the question I've been dodging since episode one. Do you actually need a tool? Back in that first episode, Mike from Columbus told me he couldn't afford an ITAM platform and asked what to do.

I gave him a short answer. He deserved a full one, and next week he gets it. We'll walk the readiness test. Five questions, and if you fail any of them, buying a tool makes your problems more expensive instead of more visible. I've bought these platforms, implemented them, and inherited failed implementations from people who bought them for the wrong reasons.

All of that is going in. Before I let you go, the case files. I've asked a few episodes running, and I'm asking again. If you've lived through something in this discipline other people can learn from, send it to me. Anonymized, sanitized, no company names. Just the situation, what you did, and what happened. Details at operationalitam.com The best teaching material in this field isn't in a framework document.

It's in what happened to you last quarter. I'm Bill Van Nort, this is the Operational ITAM podcast. Start the clock, build the alternative, and never negotiate in the last 60 days. I'll talk to you next week. Take care.