From default renewal to deliberate decision: A framework for enterprise Saas and COTS optimization

Enterprise SaaS and COTS estates have become costly, fragmented and difficult to govern. Years of renewals, customization, M&A activity and decentralized purchasing have created underused licenses, duplicate platforms, unsupported systems and hidden dependencies.

Default renewal is no longer a neutral decision. When leaders renew platforms without a clear understanding of what is being used, how workflows are configured, which integrations are active and where dependencies exist across the enterprise, they risk preserving waste. Furthermore, they risk extending operational exposure and delaying AI readiness.

The right response might be usage optimization, platform consolidation, workflow simplification or phased modernization. The practical first step is a focused assessment of one high-value platform, module, workflow or business unit to determine whether the platform should be optimized, consolidated, replaced or intentionally kept.

Critical SaaS and COTS platforms should now be expected to justify their cost, risk profile and strategic role before the next renewal or modernization cycle.

Enterprises did not set out to create software sprawl. It accumulated through reasonable decisions made over time. These decisions include a new SaaS platform for a business unit, a regional system retained after an acquisition, a custom workflow added to support a critical process. They also include a premium module bundled into a renewal or an unsupported application kept alive because no one fully understands its dependencies.

Over time, these decisions create 4 common problems:

• Recurring cost growth: Enterprises pay for seats, modules and premium features that might not map to actual usage or business value.
• Application redundancy: Multiple systems often support the same function across business units, regions or acquired companies, increasing cost and complexity.
• Customization lock-in: Years of custom objects, workflows, scripts, reports and integrations make platforms harder to optimize, consolidate or replace.
• Operational and security risk: Unsupported or poorly governed COTS platforms create exposure when they lack vendor support, patches, ownership, access controls, audit logging or recovery readiness.

These risks are especially acute in regulated industries, where critical systems must be supported, secure, monitored, resilient and governable.

Many enterprises already invest in application modernization and migration programs to address these conditions. These programs often begin before the embedded business logic, cross-system dependencies and actual usage patterns are fully understood.

The result is predictable: technical migration is prioritized, while the operational and workflow complexity that must be preserved or restructured is underestimated.

SaaS and COTS optimization has become more urgent because 4 pressures are converging:

• Renewal pressure is rising. Vendors are using renewals to introduce higher pricing, new packaging, premium tiers and AI-enabled SKUs. SaaS and COTS providers are also responding with new pricing and packaging models, making it more important for enterprises to understand actual usage and value before the next renewal.
• AI has changed what is possible. Agents can increasingly simplify, automate or handle repeatable activities such as lookups, approvals, routing, reporting and status updates.
• Migration programs are accelerating. Enterprises are moving legacy estates to cloud and modern architectures on compressed timelines. Faster delivery raises the cost of incomplete understanding: migration decisions are made under more pressure and against more complex dependencies than before.
• Risk expectations are increasing. Unsupported systems, hidden integrations, unclear ownership and heavily customized platforms are harder to defend in audits, regulatory reviews, security assessments and third-party risk reviews.

Together, these forces make early assessment more valuable. Enterprises that understand where cost, risk and complexity are concentrated can act before renewal, audit or modernization deadlines limit their options.

SaaS and COTS optimization rarely starts as an abstract efficiency program. It starts when a business event exposes that the current estate is too expensive, too risky or too hard to change. These moments force leadership to make an explicit decision: optimize, consolidate, replace or intentionally keep the platform as-is.

Common triggers include:

• A major software renewal often exposes a lack of usage data and weak negotiation leverage, which can lead to rising recurring costs.
• Unsupported or end-of-life commercial off-the-shelf (COTS) solutions expose organizations to security risks, operational challenges and the loss of critical skills as expertise disappears.
• Vendor price increases can reveal cost growth that is disproportionate to the business value being delivered.
• Low license utilization exposes situations where organizations are paying for users, roles or modules that are not generating sufficient value.
• Duplicate platforms expose redundant spending, fragmented workflows and inconsistent governance across the organization.
• AI readiness gaps expose platforms or workflows that limit automation, data access or agent deployment capabilities.
• Mergers and acquisitions (M&A) integration efforts often expose overlapping systems, duplicated contracts and competing process models.
• Regulatory or audit reviews can expose gaps in ownership, patching, logging, resilience or control evidence.
• Failed modernization efforts expose hidden complexity, unclear dependencies and underestimated customization debt.
• Cloud migration or ERP modernization initiatives expose opportunities to review adjacent systems and identify legacy dependencies that might also need modernization.

The most actionable entry points are usually platforms that combine cost, risk and urgency. These platforms include expensive systems approaching renewal, unsupported applications, heavily customized COTS, duplicate platforms after M&A or systems blocking AI and modernization. These platforms are the places where default renewal is hardest to justify.

For each major SaaS or COTS platform, leadership should make a clear, explicit decision: optimize, consolidate, replace or intentionally retain.

Many enterprises fixate on the fear of choosing the “wrong” path. But the “wrong” path is not the primary risk. The real risk is passive renewal—allowing expensive, highly dependent platforms to roll forward by default because there is insufficient visibility, evidence or ownership to challenge the decision.

How enterprises respond once these issues are exposed typically falls into a small set of repeatable decision patterns that determine whether value is recovered, complexity is reduced or risk continues to accumulate:

Seat and usage optimization is the right path when the platform still serves the business, but the enterprise is paying too much for how it is used. The focus is on identifying underused seats, mismatched role and tier assignments. It also includes premium or AI-enabled modules paid for but not adopted and repeatable workflows that can be simplified, automated or shifted outside the platform.

The most suitable platforms are the ones with high license costs, low utilization, renewal pressure or premium and AI features that are not fully consumed.

Landscape consolidation is the right path when the problem is not one platform, but too many overlapping platforms. The focus is on identifying duplicate systems, redundant instances, inconsistent workflows and fragmented ownership across business units, regions or acquired companies. Consolidation efforts often extend into enterprise application portfolio rationalization programs that define target architectures and migration pathways across overlapping systems and business units.

Most relevant are environments with multiple CRMs, ERPs, ITSM tools, workflow systems, reporting platforms or business-unit-specific applications that are serving overlapping or similar functions.

Full exit is the right path when the incumbent platform has become too expensive, too customized, too risky or too limiting to justify another default renewal. The focus is on understanding the business logic, data model, integrations and dependencies sufficiently to determine whether phased modernization or replacement is feasible. Full replacement or exit scenarios are typically delivered through large-scale modernization programs that combine phased migration, refactoring and cloud rearchitecture to preserve business-critical workflows.

Most relevant are deeply customized COTS platforms, unsupported systems, high-value workflows, environments under major renewal pressure or platforms that are actively blocking AI adoption and modernization efforts.

Most enterprises do not need to start with a full-estate transformation. A better first step is a focused assessment of one high-value SaaS or COTS platform, module, workflow or business unit.

• The assessment should answer 5 questions:
• Where is cost, risk or complexity concentrated?
• What activity is happening inside the platform?
• Which users, workflows or modules can be simplified, automated or rationalized?
• What business logic, customizations, integrations and dependencies must be understood first?
• What next step creates the clearest path to savings, risk reduction or modernization?

For SaaS optimization, the focus is activity-level usage, user segmentation, license reduction and workflow automation. For COTS modernization or platform exit, the focus is a bounded scope, such as a module or process area, to understand business logic, data models, integrations and dependencies.

This type of assessment is often conducted as part of application portfolio modernization programs that combine technical discovery, architecture analysis and business stakeholder alignment to build a migration or rationalization roadmap.

The output should be decision-ready: a prioritized opportunity view, a technical understanding of the current state, a recommended path forward and a business case grounded in the customer’s own environment.

Enterprise transformation rests on 3 layers, each with a distinct role.

• Governance as decision discipline. Enterprises decide whether each SaaS or COTS platform still earns its place in the estate. This layer is the one where renewal decisions, cost justification and portfolio prioritization are made.
• Intelligence as system understanding. Rhino exposes the business logic, workflows, dependencies and customizations embedded across SaaS, ERP and legacy systems. It is the evidence base that governance and transformation depend on.
• Transformation as execution at scale. IBM Consulting® delivers end-to-end modernization and migration programs, translating system understanding into replatforming, refactoring, consolidation or replacement at enterprise scale.

Together, these layers shift enterprises from default renewal and fragmented modernization to evidence-based transformation grounded in how systems work.

Default renewal is no longer a neutral decision. When SaaS and COTS platforms are underused, unsupported, duplicated, over-customized or difficult to govern, each renewal can extend cost, risk and operational complexity.

The right response will vary by platform. Some should be optimized. Some should be consolidated. Some should be modernized or replaced. Some should be intentionally kept. The important shift is that these decisions should be made deliberately, by using evidence from the enterprise’s own environment.

The practical next step is a time-boxed assessment of one high-value platform, module or workflow to understand the business logic it contains and the dependencies around it. It also aims to determine whether it still earns its place in the estate.

Reimagine application migration and modernization