Category: Renewals & Negotiation

Before you argue about the price of a licence, it’s worth checking how many you’re using. Most organisations are paying for a meaningful number of seats that nobody logs into, and that number is usually larger than any discount available at renewal.

It’s also the only lever that doesn’t need the vendor to agree to anything. A discount is a negotiation. Reducing quantity is arithmetic.

Where the dead seats come from

Nobody buys licences they don’t need. They accumulate, and always through the same handful of routes.

People leave, and offboarding removes their email and their VPN because those are the ones IT owns, while the six SaaS tools their manager expensed stay active. Teams reorganise, and the analytics seats bought for a project that ended are still renewing two years later. Someone runs a pilot with twenty seats, three people liked it, and the order form was for twenty. And the most expensive pattern of all: a whole department sits on a premium tier because two of them needed one premium feature, since it was easier to upgrade everybody than to manage two groups.

None of that is negligence. It’s what happens when purchasing is fast and deprovisioning is nobody’s job.

The count that changes a renewal

You need three numbers per tool, and you can get them without buying anything.

Seats purchased. From the order form, not from the admin console, because those disagree more often than you’d think and the contract is what you’re paying for.

Seats assigned. From the vendor’s admin panel. The gap between purchased and assigned is pure waste and the easiest thing to fix, since you’re paying for seats that aren’t even allocated to a human.

Seats actually used. Last login, or better, last meaningful action, over ninety days. Most admin panels expose this and the ones that don’t will usually hand it over if you ask your rep, which is a slightly awkward conversation and worth having.

Then cross-reference the assigned list against your identity provider or HR system. Every account belonging to somebody who’s left is both a cost and a security problem, and framing it as the second one tends to get it prioritised faster than framing it as the first.

The tier question, which is worth more than the seat count

Once you have usage, ask a second question about the people who are active: are they using what they’re paying for?

Tiered pricing assumes a team splits neatly into power users and everyone else. In practice most organisations put everyone on the higher tier for one of two reasons, either the feature they needed was gated there, or splitting the team into two groups sounded like ongoing admin work. That decision is often correct at the time and quietly wrong two years later, once the feature has moved down a tier or the people who needed it have moved on.

Price the mixed configuration before renewal. Twenty premium and eighty standard is frequently a larger saving than any percentage you’d have won by arguing, and it’s a change you can make unilaterally.

Doing it without buying a tool

There’s an entire software category for this, and it’s genuinely useful past a certain size. Below that size it’s a spreadsheet and an afternoon.

Start with your five most expensive subscriptions rather than all forty, because spend concentrates hard and the long tail can wait. Pull the assigned list from each admin panel, export your active employee list, and compare. Then look at last-login dates for whoever survives that pass.

Your card statements and expense reports are the other half of the picture, since they surface the subscriptions that never went through procurement at all. That overlaps with finding the tools nobody approved, and it’s the same afternoon of work, so do both at once.

Timing, which decides whether any of it counts

Here’s the part that catches people. Finding twenty unused seats in month three of a twelve-month term saves you nothing, because you already bought them. Annual contracts almost never let you reduce mid-term, and the ones that do usually cap it.

So the audit has to land before the renewal paperwork, ideally ninety days out, which is why it sits where it does in the renewal timeline. Do it early enough and the reduced count becomes your opening position. Do it late and it becomes next year’s problem.

Watch for the co-termination trap too. Vendors like aligning all your products onto one renewal date, which is convenient, and it also means a single missed window commits you to everything at once.

What to do with the number

Reducing the count is the obvious move and sometimes the wrong one. If you’re going to grow into those seats within a few months, cutting them and buying them back at a worse rate is a bad trade, so check what re-adding costs before you cut.

The alternative is to spend the number rather than bank it. A vendor facing a real reduction in seats will often protect the total contract value instead, which gives you room to ask for a rate hold, an uplift cap, better terms, or a tier upgrade for the people who need one. You’re converting waste into protection, and protection is what stops this from happening again.

Either way you now know something you didn’t before, which is what you’re actually buying with an afternoon of spreadsheet work.

CopperFeed tracks pricing and packaging changes as they’re announced, including the tier reshuffles that decide whether your current configuration still makes sense.

General guidance, not legal or procurement advice. Your own contract terms govern what you can change and when.

Most of what happens at a renewal was decided when someone signed the original order form. The price you’re quoted, whether you can refuse it, and how much notice you get before your plan disappears are all set by contract language that took about four lines to write and that nobody read closely, because at signing everyone is thinking about whether the product works.

Four clauses do nearly all of that work. They’re worth knowing by name, because they’re the ones you can still ask for, and because reading them in your current contract tells you in about ten minutes how much trouble your next renewal is going to be.

1. The uplift cap, and the word it applies to

An uplift cap limits how much the vendor can raise your rate at renewal. Three to five percent is common, and getting one at all is easier than most buyers expect, because a capped increase is still an increase and the vendor would rather have a predictable one than a fight.

The trap isn’t the number. It’s the noun the cap attaches to.

A cap on “renewal of the Plan” protects the plan you’re on. If that plan stops existing, and vendors retire plans constantly, the cap has nothing left to apply to and your quote comes back at list price for whatever replaced it. A cap on “renewal of the Services” follows you across that change, because the thing being capped is the relationship rather than one SKU.

Same clause, same percentage, completely different outcome. If you read one line in your contract today, read that one.

2. SKU continuity

This is the clause that says: if you discontinue my tier mid-term, I move to the nearest equivalent at an equivalent effective rate, not at list.

It matters because tier retirement is now the main way prices go up. Nobody sends a letter announcing a 24% increase. They announce that your plan is being consolidated into a new one, which happens to cost more and happens to be the only option, and technically your uplift cap was never breached because the plan it covered no longer exists. That’s the mechanics behind most of what shows up as a surprise renewal quote.

Ask for continuity language and expect some resistance, because this is the clause that costs the vendor real money. It’s also the one worth spending your negotiating capital on, since it’s the only one that holds when the product line is reorganised around you.

3. The notice period on tier retirement

Separate from the price, there’s the question of warning. How long before your plan goes away do you find out?

Market practice ranges from generous to insulting. Some vendors give a year. Others have given a handful of days on a full shutdown, which is not enough time to export data, let alone evaluate a replacement or get budget approved. Nothing stops that except a number in your contract, so put one there: ninety days minimum for a tier change, and more if switching would be a project rather than a swap.

The same clause does double duty if the vendor goes away entirely rather than repricing, which is a different problem with a tighter clock.

4. Auto-renewal and its notice window

Nearly every subscription renews itself. The clause usually requires written notice of non-renewal 30, 60 or 90 days before the term ends, and if you miss that window you’re renewed, whether or not you ever signed a quote or wanted the product.

Two things to negotiate here, neither of which is the existence of auto-renewal, because you won’t win that one.

First, shorten the notice window. Thirty days is reasonable and ninety is not, and vendors concede this more readily than they concede money.

Second, ask for a renewal notification obligation: the vendor must tell you in writing, at a set number of days out, that the renewal is coming and what the new price is. This costs them nothing and it removes the entire failure mode where a renewal lands because a calendar entry didn’t. It also means the price arrives while you still have time to do something about it, which is the whole argument of the renewal timeline.

Reading your own contract

You don’t need a lawyer for the first pass. Open the order form and the master agreement it references, and find four answers:

• What’s the cap, and what word does it modify? Plan, or Services. If there’s no cap, that’s an answer too, and it means your next price is whatever they decide.
• What happens if my tier is discontinued? If the contract is silent, assume list price.
• How much notice do I get? Again, silence means whatever they feel like.
• By what date must I give notice to not renew? Put that date in a shared calendar before you close the document. It’s the only one of the four you can’t fix later.

Most contracts answer two of those four. The gaps are your list for the next negotiation, and the useful thing about asking for contract language rather than a discount is that it costs the vendor nothing today, which makes it much easier to say yes to.

When to ask

The best time is at initial signing, when you have the most leverage and the least information. The second best is at a renewal where you’re expanding, because adding seats or products is the moment your signature is worth something again. Asking for protection in a flat renewal, with no new money attached, is the weakest position, though it’s still worth doing since the answer is sometimes yes.

What you’re buying with these four clauses isn’t a lower price. It’s the ability to know next year’s price this year, which turns out to be the thing that actually makes software budgets work.

CopperFeed records repricings, tier retirements and shutdowns as dated entries, so you can see which vendors are reorganising their plans before the quote reaches you.

General guidance, not legal or procurement advice. Contract language varies, and your own terms govern.

Most software renewals are decided long before anyone negotiates. The quote arrives three or four weeks out, someone forwards it to finance, finance asks whether the increase is normal, and by the time the answer comes back the auto-renewal clause has already done its work. The negotiation you think you are having is really just a request for a discount, made by the side with no time left.

The fix isn’t a better script for that call. It’s starting earlier, because almost everything that gives you leverage takes weeks to assemble and nothing that matters can be done in the last fortnight.

Here is what to do at each stage, working backward from the renewal date.

180 days out: find the date and read the clause

Two facts decide how much room you have, and most teams can’t answer either one on demand.

The first is the actual renewal date, which is usually not the anniversary of when you started using the product. It’s the anniversary of the order form, and if you’ve added seats or co-termed a second product onto the same paper, it may have moved since. Go and find it in the document rather than in someone’s memory.

The second is the notice window. Auto-renewal is standard, and the clause typically requires written notice of non-renewal 30, 60 or 90 days before the term ends. Miss that window and you’re contractually renewed at whatever the terms say, whether or not you ever sign a quote. That single date is the one to put in a shared calendar, because everything else is negotiable and this isn’t.

While you’re in the contract, write down the four clauses that set next year’s price: the uplift cap if there is one, whether the cap applies to the plan or to the services as a whole, and what happens if the vendor discontinues your tier. Those clauses are what a forced SKU migration runs straight through, and knowing now whether you’re covered changes what you spend the next few months doing.

90 days out: build the usage picture

Vendors come to renewals holding your usage data. If you show up without your own version of it, every claim they make about adoption goes unchallenged, and you end up arguing about price when you should be arguing about quantity.

Pull the seat list and compare it against your directory. Count the accounts that haven’t logged in this quarter, the ones belonging to people who’ve left, and the ones sitting on a premium tier for a feature they’ve never opened. In most organisations this is the largest single number available at renewal, and it’s bigger than any discount you were going to win. Counting it properly takes an afternoon.

Then get the consumption picture, which matters more every year as pricing moves off seats. If any part of your bill runs on credits, tokens, API calls or workflow runs, chart the last twelve months and look at the slope, not the average. A commitment sized to your average usage looks cheap and overruns quarterly at rates you didn’t agree to. We went through how to size that in how to budget for usage-based pricing.

This is also the point to check whether you’re paying twice for the same capability. Bundling has put transcription, search, document generation and assistant features into products that already sit in your stack, so the overlap tends to show up as two invoices doing one job.

60 days out: decide what you’d actually do

Leverage isn’t a tone of voice. It’s having a real answer to the question of what happens if you don’t sign, and that answer takes time to become real.

Price one credible alternative properly. Not a threat, and you don’t have to mention it, but you should know the migration cost, the retraining cost and the number of weeks. If the honest answer is that you’re staying no matter what, that’s fine, and it’s better to know it going in, because then you stop pretending and start trading the things you can actually trade: term length, payment timing, a services credit, a cap on next year.

Two other things belong in this window. Check whether your account is carrying an unresolved licensing question, because a true-up landing inside a renewal is the strongest card the vendor has, and it’s worth knowing what tends to trigger one. And confirm who signs on your side. A renewal that needs a signature nobody has scheduled is how teams end up accepting terms to avoid a lapse in service.

30 days out: the conversation

By now the quote exists. Ask for the line items, not the total, because the story is almost never a general increase. It’s a tier that no longer exists, a feature that moved up a level, a discount that was always time-limited, or a bundle you didn’t ask for. Each of those has a different counter, and you can’t pick one from a single number.

Ask what the price is for the same thing you had. Sometimes there’s no such option, and that’s useful information, because it means you’re being migrated rather than renewed and the conversation should be about what protection carries over.

Bring the seat count you built at 90 days. Reducing quantity is the one adjustment that doesn’t require the vendor to approve anything, and it changes the total more reliably than a percentage argument.

7 days out: protect the floor

Inside the last week you’re not negotiating price. You’re making sure nothing bad happens by default.

If the notice window has passed and you don’t want the renewal, say so in writing anyway, then read what the contract actually obliges you to pay. If you’re signing, check the term length, the uplift language and the SKU-continuity wording one more time, because those three lines set next year’s starting position and they’re the ones that get edited quietly between drafts.

And if the vendor is the one going away rather than repricing, the timeline changes shape entirely, which is its own playbook.

The habit that makes this easy

None of this is hard in isolation. It’s hard because renewals arrive scattered through the year and nobody owns the calendar, so each one feels like a surprise even when the contract has been sitting in a drive for eleven months.

One shared list of renewal dates, notice windows and last year’s price fixes most of it. Add the date you’d have to start looking at alternatives, and the surprise goes away.

CopperFeed tracks the other half: the launches, releases, repricings and shutdowns that show up in your quote months later. Pricing changes usually roll through a vendor’s customer base in a wave, so the first sign of yours is often a change that landed on somebody else.

General guidance, not legal or procurement advice. Contract language varies, and your own terms govern.