Most software renewals are approved on autopilot. The contract comes up, the vendor sends a quote, and the renewal is routed through procurement without a real evaluation. The assumption is that if the software is in use, it should be renewed. That assumption is worth testing.
Question one: what is the actual utilization?
Not the licensed utilization — the actual utilization. The number of users who have logged in in the last 90 days, not the number of licenses purchased. For most enterprise software portfolios, there is a meaningful gap between those two numbers. The gap is negotiating leverage, and it disappears if you don't know it exists.
Actual utilization data is harder to get than it should be. The vendor's usage reporting is often designed to obscure low utilization rather than surface it. Getting clean utilization data requires pulling from identity providers, SSO logs, or direct API integrations — not from the vendor's dashboard.
Question two: is this tool doing something another tool already does?
Duplicate functionality is endemic in enterprise software portfolios. Organizations acquire tools through separate procurement decisions made by separate teams, and nobody maintains a functional inventory that would surface the overlap. The renewal conversation is the moment to ask whether this tool's core capability is already covered by something the organization is paying for.
The answer requires a functional taxonomy — a map of what each tool does, not just what category it belongs to. Most organizations don't have this. Building it pays for itself quickly.
Question three: what is the cost of switching?
Switching cost is the number vendors use to justify price increases at renewal. It is often real — there is genuine friction in migrating data, retraining users, and rebuilding integrations — but it is also often overstated. The vendor's estimate of your switching cost is not a neutral number.
Having a genuine switching cost estimate — built from your own data about the integrations, the user base, and the migration complexity — changes the negotiation. It converts a number the vendor owns into a number you own, and that changes the leverage in the conversation.
These three questions don't guarantee a better outcome at every renewal. But they change the default from autopilot to analysis, and over a full software portfolio, that change compounds.