The Questions Worth Asking 90 Days Before a Renewal
A renewal quote is a decision point that usually gets treated as a formality. Here is what is worth answering before you sign.
A renewal quote is a decision point that usually gets treated as a formality.
The quote arrives, it's roughly what you expected, the alternative is a migration nobody has time for, and it gets approved. Most of the time that's the right outcome. But it should be the outcome of asking a few questions, not of skipping them.
Here's what's worth answering before you sign — starting a couple of months out, not a couple of weeks.
About what you're actually renewing
**Are we still using all of it?** Seat counts and license tiers drift. People leave, projects end, a module gets deployed and never adopted. Renewal is the natural moment to true up, and it's usually the only moment anyone looks.
**Is the tier right?** Plenty of environments are on a premium support level for equipment that doesn't need it, or on a basic tier for something that turned out to be critical. Both are worth correcting.
**What's this actually protecting?** A support contract on hardware nearing end of support has a shorter useful life than the contract term suggests. Worth knowing before you renew for three years.
About timing
**When does this really expire?** Auto-renewal clauses and notice windows matter more than the expiration date. If you have to give sixty days' notice to change anything, your actual decision deadline is sixty days before the date on the contract.
**Does this line up with anything else?** If you have three contracts expiring across the year, aligning them turns three small negotiations into one larger one. Getting there sometimes costs a short prorated term. Usually worth it.
**What's the refresh horizon?** If the hardware is likely to be replaced within the term you're about to sign, the term is too long.
About the number
**What changed, and why?** Increases have reasons: indexing, tier changes, a product being repackaged. Ask for the specific reason rather than accepting the total.
**What's included that wasn't before?** Sometimes an increase reflects genuinely added scope. Sometimes it reflects a bundle you didn't ask for.
**What's the multi-year picture?** A lower annual rate on a longer term can be a good deal or a way to lock in before a repackaging. Ask what happens at the end of the longer term, not just during it.
About alternatives
**What would replacing this actually take?** You may not intend to switch. Knowing the real answer (migration effort, retraining, integration work) tells you how much leverage you have and whether the concentration risk is acceptable.
**Is there a functional overlap?** Environments accumulate tools that do overlapping things. Renewal is a reasonable time to notice you're paying for two things that solve the same problem.
**Has the market moved?** Not to switch reflexively, but to know whether what you're renewing is still competitive on capability, not just on price.
About who's deciding
**Who owns this contract?** More renewals than you'd expect have no clear owner. They're handled by whoever was closest to the original purchase. If that person is gone, the renewal happens by default.
**Who needs to know?** Security, finance, and the team that actually uses the tool may each have information that changes the decision. They usually aren't asked.
The realistic version
You won't get through all of this on every renewal, and you don't need to. On a small contract, the first three questions are probably enough.
But on anything significant — the ones with real dollars or real dependency behind them — starting sixty to ninety days out with this list is the difference between making a decision and processing one.