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.
Leave a Reply