Why SaaS Renewals Matter: A Strategic Procurement Guide
- Sergii Dovgalenko
- Jun 2
- 4 min read
Updated: Jul 26
Let's start with some facts created outside this resource:
SaaS inflation reached 13.2% in March, while the US CPI was 3.3%.
SaaS prices rise by an average of 9% upon auto-renewal if left unnegotiated.
The average enterprise faces nearly 211 SaaS renewals every year.
The burden of SaaS renewals
Most organizations still approach SaaS renewals as an operational routine. The agreement expires, procurement negotiates a discount, legal reviews the wording, finance approves the budget, and the platform quietly continues for another year. Operationally, this often looks efficient. Commercially, it can become one of the most expensive governance failures.
Modern SaaS environments have evolved significantly and are no longer merely simple software subscription landscapes that can be easily navigated.
Today, most companies operate in fragmented ecosystems that extend far beyond traditional software solutions. These ecosystems are typically spread across various departments, each with its own needs and preferences, leading to a complex web of applications and tools that is often challenging to manage effectively.
Within these organizations, business units operate independently, frequently selecting their own software solutions to address specific operational challenges. This independence can lead to a proliferation of tools that, while beneficial for individual teams, may not integrate seamlessly with one another, resulting in inefficiencies and data silos.
Operational teams tasked with ensuring smooth workflows often struggle to coordinate efforts across these disparate systems, hindering productivity and collaboration.
Moreover, the rise of corporate cards has facilitated the purchase of software solutions without centralized oversight, contributing to shadow IT. Employees may opt to acquire tools they believe will enhance their work processes, but these unapproved purchases can pose security risks and compliance issues, as IT departments may not be aware of all the software being used within the organization.
In addition to these challenges, the integration of AI add-ons into existing SaaS products is becoming increasingly common. While these advanced features can provide significant enhancements, they also add another layer of complexity to the SaaS landscape. Companies must integrate these AI tools with their current systems, ensuring they work harmoniously and deliver the intended benefits without disruption.
Furthermore, relationships with various vendors can become strained and disconnected as companies engage with multiple software providers. Each vendor may have its own support systems, contract terms, and update schedules, leading to a lack of cohesion in how software is managed and utilized across the organization.
This fragmentation can result in increased operational costs and a diminished return on investment for the software solutions being employed. In summary, the modern SaaS landscape presents a multifaceted environment that requires careful management and strategic oversight.
Companies must be vigilant about understanding the complexities of their software ecosystems, ensuring they can effectively leverage technology to drive productivity and innovation while minimizing risks associated with fragmentation, shadow IT, and vendor disconnect.
IT no longer dominates the SaaS budget; it belongs to the Business, which manages over 50% of the budget and over 70% of apps.
Vendors divide and conquer
Vendors understand this environment extremely well. In fact, many SaaS commercial models benefit directly from operational fragmentation and delayed governance maturity. The ideal SaaS customer is not an organization with strong ITAM controls, centralized visibility, aggressive renewal preparation, and procurement participation in technology governance. The ideal SaaS customer is fragmented, operationally dependent, politically decentralized, and late.
Late renewals are extremely attractive for vendors commercially because the negotiation position changes fundamentally once operational dependency becomes embedded into the organization. By the time renewal discussions begin, the platform is already integrated into workflows, users are trained, business processes depend on it, AI functionality becomes operationally linked to delivery activities, and migration suddenly looks risky, expensive, or politically impossible.
At this stage, many companies are no longer negotiating from a position of leverage. They are negotiating out of fear of disruption.
SaaS renewals as a commercial leverage
This is why SaaS renewals should not be treated as an administrative activity. They are leverage events. In many companies, the renewal cycle becomes the only realistic opportunity to
reassess platform strategy,
challenge pricing structures,
eliminate inactive subscriptions (shelfware),
review duplicated functionality,
negotiate scale-down rights,
benchmark commercial conditions,
reconsider sourcing strategy,
or reassess vendor dependency.
The 90-day rule
Unfortunately, many companies still manage renewal preparation through arbitrary governance rules inherited from older procurement models. One of the strangest examples is the famous “90 days before expiry” approach that still appears in many procurement procedures and contract management policies. Nobody can usually explain why exactly 90 days became the magical number. The answer is often simple: somebody copied it years ago, and nobody challenged it afterward.
Strategic SaaS renewals should start based on actual sourcing complexity rather than arbitrary calendar assumptions. The required preparation window may depend on:
need-by date (!!!)
governance approvals,
legal review,
IT security assessment,
architecture discussions,
cost benchmarking/assessment effort,
migration feasibility,
implementation planning,
transition risk,
stakeholder alignment,
and the sourcing strategy itself.
Some renewals may require several months of preparation, while others require very little effort. Assuming all SaaS renewals behave identically is commercially risky
.
The rise of AI Monetization
The rise of AI monetization creates an additional layer of governance complexity. Vendors increasingly introduce token-based pricing, AI consumption charging, workflow or output monetization, AI bundles, compute-linked licensing, and “AI-enhanced” premium structures, which can significantly change the long-term commercial profile of SaaS agreements.
Many companies still struggle to establish reliable visibility over basic license utilization and subscription ownership. Introducing variable AI consumption models on top of already fragmented SaaS governance can rapidly create uncontrolled commercial exposure.
SaaS renewal governance or the lack thereof
Many of my colleagues will recognize the situation: by the time procurement receives a contract, many strategic decisions are already taken elsewhere and are operationally irreversible.
Strong SaaS governance, therefore, requires much more than negotiation capability alone. It requires:
operational visibility,
ITAM maturity,
budgetary, spend planning, and renewal governance,
sourcing discipline,
AI spend controls,
license utilization transparency,
vendor dependency analysis,
benefit realization tracking,
and governance integration between procurement, IT, and operational business owners.
SaaS Cost Optimization Checklist
To structure these areas more practically, I prepared a SaaS Cost Optimization Checklist covering SaaS visibility, ITAM controls, renewal governance, AI spend management, sourcing strategy, vendor dependency, true-down protections, TCO controls, procurement participation in IT governance, and SaaS negotiation practices.
The checklist is available for free on The Good Spending:
Comments