Enterprise software renewal season concentrates enormous commercial risk into a small number of decisions made under time pressure. A large organisation managing Microsoft, SAP, Oracle, Salesforce, and IBM relationships will collectively renew billions of dollars of software commitment over a three-year cycle. And yet, in many organisations, the renewal process for even the largest of these relationships produces less rigorous commercial analysis than the original purchase decision received, because the renewal is perceived as a continuation of an existing relationship rather than a commercial decision with genuine optionality.
The three questions in this blog are not complex or counterintuitive. They are the questions that experienced software procurement professionals ask as a matter of course before every significant renewal, and that less experienced teams consistently skip in the rush to meet a renewal deadline. Answering all three before signing any major enterprise software renewal will not guarantee the best possible commercial outcome, but skipping any one of them consistently produces outcomes that are worse than they needed to be.
Question One: Are We Actually Using What We Are About to Renew?
This sounds obvious to the point of insult. Of course you know what you are using. Except, in practice, most organisations do not have an accurate, current picture of what they are using across a major enterprise software estate at the moment a renewal arrives. They have a picture of what was contracted and deployed at some point in the past, modified by changes that were tracked when they were large enough to trigger a formal process but not when they were small enough to slip through without one.
The honest answer to this question requires three data points that are each separately necessary. First, which licences are assigned? This comes from the vendor’s licence management portal or entitlement register and tells you what you are contractually committed to. Second, which of those licences are actually deployed? This comes from your SAM tooling or endpoint management data and tells you what has been installed or provisioned. Third, which deployed licences are actively being used? This comes from usage telemetry, login data, feature interaction data, and consumption metrics that vary by product but that most enterprise software platforms make available in some form.
The gap between licences assigned, licences deployed, and licences actively used is where shelfware lives. In most large enterprise software environments, this gap is meaningful. Research consistently shows that between twenty and forty percent of enterprise SaaS licences are underutilised or effectively unused. Renewing without quantifying this gap means renewing shelfware at full price for another term. Quantifying it provides the evidence base for a right-sizing conversation with the vendor that either reduces the renewal scope or improves the commercial terms for the scope that is genuinely needed.
The ITAM Forum publishes research on enterprise software utilisation and the commercial impact of renewal decisions made without accurate utilisation data. Their ITAM Forum enterprise software utilisation and renewal decision research provide quantified evidence on the financial value of utilisation-based renewal preparation across major enterprise software categories, including the specific data collection approaches that produce the most commercially actionable utilisation picture before a renewal conversation.
Question Two: Has Anything Changed That Should Change What We Are Buying?
Enterprise software renewals typically follow the path of least resistance, which is renewing the same configuration at updated pricing. The configuration was set at the previous renewal, and in the absence of a specific reason to change it, it renews unchanged. This default behaviour is commercially expensive because the organisation’s needs have almost certainly changed since the previous renewal, in ways that may make the current configuration either more than needed or less than optimal.
The specific changes that should prompt a configuration review before renewal fall into several categories. Organisational changes, including acquisitions that brought additional software licences into the estate, divestments that reduced the user population, restructuring that changed which business units use which products, and headcount changes that affected the total licence requirement, all potentially change what the optimal renewal configuration looks like. Technical changes, including cloud migrations that changed the deployment model for specific products, infrastructure consolidations that reduced the server count, or new integrations that created additional licence obligations, affect both the required configuration and the compliance position. Vendor changes, including new product tiers, pricing model restructuring, AI capability bundling, and end-of-life announcements for specific products or features, change the comparative value of different configuration options. And market changes, including competitive alternatives that did not exist at the previous renewal and price changes in adjacent categories, affect the reference points for what represents a commercially competitive deal.
IDC research on enterprise software procurement and commercial management documents the financial impact of structured renewal preparation across major software categories, including the specific data collection and configuration review disciplines that produce the most commercially productive renewal outcomes. Their IDC enterprise software procurement and renewal commercial research provide quantified evidence on the value of utilisation-based renewal preparation and the commercial outcomes achievable for well-prepared enterprise buyers.
Question Three: What Would We Do If We Could Not Renew on These Terms?
This is the question that most procurement teams skip because it feels uncomfortable or because the answer appears obvious. If you cannot renew on these terms, you have to accept what the vendor proposes. For many enterprise software relationships, particularly those with high switching costs, that conclusion feels unavoidable. But the discomfort of the question is precisely why it is the most important one to answer before entering a renewal negotiation.
The question is not asking whether you would actually walk away from the renewal. It is asking what your genuine alternatives are and how credible they would be to the vendor if you indicated you were considering them. An alternative that is technically feasible but would require three years and thirty million pounds to execute is not a credible negotiating alternative. An alternative that is both technically feasible and commercially comparable in total cost and execution risk is a genuine one. The distinction matters because the vendor’s account team is making exactly this assessment of your alternatives as it prepares for the renewal conversation.
Building a genuine alternative assessment before any major renewal requires doing enough work on the alternatives to be able to speak to them with technical accuracy. This does not mean completing a full migration business case for every renewal. It means knowing what the actual cost and timeline of the primary alternative to renewing would be, being able to articulate that with credibility, and using that knowledge to calibrate what terms are genuinely worth challenging versus what terms are effectively fixed given your actual position.
For some vendor relationships, an honest alternative assessment will confirm that the walkaway position is genuinely weak, that the switching costs are too high to make alternative credibility realistic, and that the commercial negotiation should focus on structural protections and pricing mechanics rather than fundamental scope changes. That conclusion is valuable because it redirects the negotiation effort toward the areas where leverage genuinely exists. For other relationships, the alternative assessment will reveal that the switching costs are lower than historical inertia has assumed, creating leverage that the organisation had not been using.
MIT Sloan Management Review’s research on enterprise procurement and negotiation strategy addresses how enterprise buyers should assess and communicate alternative options in high-stakes vendor negotiations, including the balance between genuine alternative development and strategic signalling of competitive evaluation. Their MIT Sloan enterprise procurement and negotiation strategy research provide practical frameworks for building genuine alternative credibility as a negotiating tool, covering both the analytical process of alternative assessment and the communication strategies that make alternatives commercially useful in vendor conversations.
What Happens When All Three Questions Are Answered
The commercial value of answering all three questions before a renewal is not simply that each individual question produces useful information. It is that the answers together change the fundamental dynamic of the renewal conversation. A procurement team that can demonstrate current utilisation data, articulate a well-considered commercial position based on a configuration review, and signal credible awareness of alternatives is engaging from a position of commercial competence that changes how the vendor account team responds. The concessions and flexibility that are not volunteered to passive renewers become available to commercially prepared buyers because experienced account teams can distinguish between buyers who have done the work and those who have not.
PwC’s enterprise commercial management research addresses the financial outcomes of systematic versus unstructured renewal preparation across enterprise software portfolios, providing the quantified evidence that supports investment in the preparation disciplines these three questions represent. Their PwC enterprise software renewal governance and commercial outcomes research document the financial impact of structured renewal preparation and the specific governance investments that produce the most commercially sustainable outcomes across major vendor relationships.
Building These Questions Into Every Renewal
The practical governance requirement is to build all three questions into the standard renewal preparation process, with a defined timeline that ensures all three can be answered before the renewal conversation begins rather than during it. For major enterprise software relationships, this means starting the utilisation assessment twelve months before the renewal date, completing the configuration review at least six months out, and having the alternative assessment documented at least three months before the renewal conversation is expected to begin.
These timelines sound long. They are. But the financial stakes of major enterprise software renewals, which for large organisations with multi-product Microsoft, Oracle, or SAP estates can run to tens of millions of dollars annually, justify preparation timelines that are proportionate to the commercial significance of the decision. The procurement teams that build this discipline systematically achieve materially better commercial outcomes than those that apply it selectively or only when a specific renewal feels particularly high-stakes.
Conclusion
Three questions before any enterprise software renewal: are we actually using what we are about to renew, has anything changed that should change what we are buying, and what would we do if we could not renew on these terms. Every one of them sounds simple. Not one of them is being answered systematically by most procurement teams before most renewals. The organisations that build the process discipline to answer all three, consistently and on a timeline that allows the answers to inform the negotiation, will consistently achieve better commercial outcomes across their enterprise software portfolios than those that do not.
