Application rationalization opportunities exist across every layer and dimension of an enterprise portfolio. This article provides a systematic breakdown of rationalization strategies for different portfolio segments, with specific examples, decision criteria, and expected outcomes.
As discussed in Part 1 of this series, success of Application Rationalization depends on the availability of comprehensive data of application inventory. Analyzing and classifying the applications based on this data into various dimensions enables focused actions based on the dimensions. This also helps to prioritize the approach and take appropriate decisions to derive maximum benefit to the organization.
For example, please see in below table; how we can create a multi dimensional portfolio view
| By Type | By Technology Layer | By Business Function | By Technical Health | By Business Value | By Lifecycle Stage |
|---|---|---|---|---|---|
| Custom-built vs. COTS SaaS vs. On-premises Transactional vs. Analytical | Front-end / User Interface Middle-tier / Business Logic Back-end / Data Integration / Middleware | Revenue-generating Cost-center support Compliance/Regulatory | Modern vs. Legacy Supported vs. Unsupported Scalable vs. Constrained | Strategic Utility Tactical Obsolete | Growth Mature Declining End-of-life |
In Part 1 we learned that the Rationalization Recommendation falls into one of the following categories
| Action | Description | When to Apply | Typical Savings |
|---|---|---|---|
| Retain | Keep as-is | Strategic, healthy apps | 0% (baseline) |
| Retire | Decommission completely | Obsolete, unused apps | 100% of run cost |
| Replace | Swap with modern alternative | Legacy, high-maintenance apps | 30-70% cost reduction |
| Consolidate | Merge multiple apps | Redundant functionality | 50-80% cost reduction |
| Rationalize Data | Simplify data architecture | Data sprawl, redundancy | 40-60% storage reduction |
Further the Replace Action can fall into one of the following modernization paths
| Action | Description | When to Apply | Typical Savings |
|---|---|---|---|
| Rehost/Relocate | Lift and shift — move app to cloud as-is with no changes. Fastest, least benefit or Move infrastructure to cloud without purchasing new hardware — VMware on AWS for example | Speed is priority, large portfolio, budget constrained | 20–30% |
| Replatform | Lift, tinker and shift — minor optimizations like moving to managed database without changing core code | Want some cloud benefit without full rewrite. | 30–40% |
| Refactor/Remediate | Redesign the application making suitable changes to accommodate hosting in the cloud like logging, configuration etc. Or Fix security, compliance or technical debt issues before or during migration | App is strategic, needs scale, agility, or cloud native features | 40–70% |
| Rearchitect | Entirely build the functionality from scratch | The Application is strategic and long term use. Run it a on a modern stack instead of legacy | 20–40% |
| Repurchase | Drop and shop — replace with a SaaS product e.g. move CRM to Salesforce | Commercial SaaS does it better and cheaper | 20–40% |
Now let us see how we can approach rationalization from perspective of different dimensions
RATIONALIZATION BY APPLICATION TYPE
Custom-Built Applications – In a typical large enterprise there are usually 200-500 custom applications with an average age of 8-15 years which are about 60-70% of total portfolio costing about 50-70% of IT maintenance budget. Common approaches for the rationalization are to evaluate if the application is required (business process might have changed or no longer exists), newer COTS/SaaS application are available providing better functionality and cost effective, there may multiple applications doing the same functionality or the application performance might have degraded over the years. Please refer to the table below for further information
The four strategies
Strategy 01
Retire
Business process no longer exists. Decommission the application and archive or purge its data.
20–30% of portfolio
Strategy 02
Replace
A COTS or SaaS alternative exists that covers 80%+ of requirements at lower TCO.
30–40% of portfolio
Strategy 03
Consolidate
Multiple applications perform the same function across teams or departments.
15–25% of portfolio
Strategy 04
Refactor
High business value application with an unsustainable technical foundation.
5–10% of portfolio
Strategy detail
Strategy 01
Retire — business process no longer exists
The fastest and most cost-effective path. Zero migration complexity, minimal risk, immediate savings on maintenance and hosting.
Identification criteria
Zero or minimal usage — <5% of intended users
Business process discontinued or automated elsewhere
No unique data, or data already archived
Sunset date already passed (zombie apps)
Common candidates
Manual workflow apps replaced by automation
Shadow IT projects formalized elsewhere
Proof-of-concept apps never decommissioned
Department tools after org restructure
Case example
Manual Expense Approval Workflow System
Built 2010, last used 2019. Fully replaced by Concur SaaS. No active users. Technology stack unsupported.
$120K
Annual savings
2 weeks
Effort
Low
Risk
Strategy 02
Replace — COTS / SaaS alternative available
Swap custom-built applications for proven commercial products. The decision hinges on requirements coverage, 3-year TCO comparison, and vendor stability.
Replace if
COTS covers ≥80% of requirements out-of-box
3-year SaaS TCO < custom maintenance cost
Vendor is stable and established
Users accept customization trade-offs
Keep custom if
Highly differentiated competitive process
Security / compliance requires on-premises
COTS covers <60% of requirements
Migration cost > 3 years of maintenance
Common replacement categories
CRM, Help desk, HR systems
Document & project management
Inventory & asset management
Analytics / BI, Collaboration, Survey / Forms
Case example
Custom Project Management Tool — built 2012
$300K/yr (3 FTEs), 250 users
Replace with Smartsheet — $60K/yr
$240K annual savings · 7.5-month payback
Strategy 03
Consolidate — multiple apps doing the same thing
Applications built independently by different teams or departments with overlapping functionality, redundant data, and similar user bases.
Identification criteria
Multiple apps with overlapping functionality
Built independently by different teams
Similar user bases or use cases
Redundant data storage
High combined maintenance burden (>30% of app budget)
Consolidation strategy
Replace all with a single SaaS or enterprise platform
Phased migration over 12 months
Single integration layer post-consolidation
Vendor assumes maintenance responsibility
Case example — 5 inventory systems → NetSuite / SAP
Plant Inv.
100 users
Warehouse
80 users
Retail Store
150 users
Spare Parts
40 users
IT Assets
25 users
$850K
Annual savings
63%
Cost reduction
16 months
Payback period
Strategy 04
Refactor — strategic app, poor technical foundation
The most selective strategy. Justified only when business value is significant, no COTS alternative exists, and the current architecture is actively blocking revenue or innovation.
Refactor if
Generates significant revenue (>$10M)
Competitive advantage depends on it
No suitable COTS alternative (<60% fit)
Architecture prevents business innovation
Customer experience is measurably suffering
Security or compliance risk is unacceptable
Do not refactor if
Replace or retire delivers better ROI
Business process itself is being phased out
COTS can satisfy 80%+ of requirements
ROI payback period exceeds 3 years
Case example
E-commerce Platform — $50M annual revenue
Built 2008, PHP 5.x, MySQL monolith. Cannot scale for peak traffic, 3-day deployment cycles, active security vulnerabilities. No viable COTS replacement at this revenue scale.
$50M
Revenue at stake
12–24 mo
Timeline
High
Risk
Expected portfolio outcomes
| Strategy | % of custom apps | Savings / TCO impact | Typical timeline |
|---|---|---|---|
| Retire | 20–30% | $50K–$200K per app / year | 1–3 months per app |
| Replace | 30–40% | 50–80% TCO reduction | 3–12 months per app |
| Consolidate | 15–25% | 50–80% cost reduction | 6–18 months per program |
| Refactor | 5–10% | Cost increase short-term; revenue protection long-term | 12–24 months per app |
Portfolio distribution — illustrative 50-app estate
Commercial Off-The-Shelf (COTS) Applications – In a Typical Enterprise there are 100-300 COTS applications constituting about 30-40% of total portfolio with an average tenure of 5-10 years and costing about 30-40% of IT license budget. In many organizations departments work in isolation and may have multiple numbers of the same application in use with less utilization,. The product would have been bought in anticipation of a project which did not materialize, the application would have become obsolete and no longer supported, there may be different applications delivering the same functionality etc. All these scenarios represent potential cost savings and reduction of application portfolio
The four strategies
Strategy 01
Eliminate
Unused or under-utilized licenses consuming budget with no active business value.
60–80% of COTS apps
Strategy 02
Consolidate
Vendor sprawl reduction — multiple tools doing the same job across the organization.
40–60% of COTS apps
Strategy 03
Renegotiate
Contract optimization — better terms, model changes, bundles, and competitive pressure.
80–100% of contracts
Strategy 04
Retire
Product end-of-life — vendor support withdrawn, security unpatched, compliance at risk.
10–20% of COTS apps
Strategy detail
Strategy 01
Eliminate — unused or under-utilized licenses
Identify and remove licenses with no active usage. The fastest path to immediate savings with zero impact on productive users.
Identification methods
License usage reports from vendor
Login analytics — last login >90 days
User surveys (“Do you use this?”)
Chargeback analysis — who’s paying but not using
Optimization levers
Reduce to active user count only
Implement license pooling for occasional users
Switch named licenses to floating/concurrent model
Set quarterly usage review cadence
Case example
Adobe Creative Cloud Enterprise — 500 seats @ $600/year = $300K/year
Usage audit reveals only 180 of 500 licensed users (36%) are active. 320 seats consuming $192K/year with no business return.
Daily users
100 users
Keep — named license
Monthly users
80 users
Keep — floating license
Never logged in
120 users
Eliminate immediately
Last login >6 months
200 users
Eliminate immediately
Optimized license model
100 named licenses @ $600 = $60K/year
100 floating licenses @ $400 = $40K/year
Total optimized cost: $100K/year
$180K
Annual savings
60%
Cost reduction
2–4 wks
Per app audit
Strategy 02
Consolidate — vendor sprawl reduction
Multiple vendors serving the same function across teams create management overhead, missed volume discounts, and hidden integration costs.
Identification criteria
Multiple vendors for similar functionality
Overlapping capabilities across products
High management overhead — different portals and processes
Missed volume discounts due to split spend
Numerous licensed instances of same software type
Common consolidation targets
BI / Analytics platforms
Collaboration and communication tools
CRM systems across business units
Security and monitoring tooling
DevOps and development toolchains
Case example — collaboration tool sprawl
15 collaboration tools across 6 categories
Organic tool adoption across teams has created a fragmented ecosystem with no unified platform, duplicated spend, and poor cross-team collaboration.
Video conferencing
Zoom, WebEx, GoToMeeting
Chat
Slack, Teams, Google Chat
File sharing
Dropbox, Box, OneDrive, Google Drive
Project mgmt
Asana, Trello, Jira, Monday.com
Email
Office 365, Gmail
Calendaring
Outlook, Google Calendar
Consolidation target — Microsoft 365 E5
Teams replaces video conferencing + chat
SharePoint + OneDrive replaces all file sharing
Planner replaces project management tools
Outlook replaces email + calendaring
$750K
Annual savings
61%
Cost reduction
5 months
Payback period
Strategy 03
Renegotiate — contract optimization
Almost every COTS contract has negotiation headroom. Changing license models, applying competitive pressure, or consolidating spend unlocks 15–40% savings with no migration required.
Negotiation levers
Version downgrade — use a cheaper tier if features unused
License model change — named users to concurrent / connected
Bundle discounts — consolidate volume across the organization
Competitive pressure — run RFP from alternative vendors
Multi-year commitment in exchange for lower unit price
Highest-impact categories
Development and DevOps tools
Design and creative software
Training and e-learning platforms
Security and monitoring tools
Database licenses — SQL Server, Oracle
Competitive RFP approach
Identify 2–3 credible alternatives before renewal
Share RFP results with incumbent vendor
Use renewal timing as leverage — start 6 months early
Negotiate total contract value, not just per-seat price
15–40%
Typical savings
3–6 mo
Per vendor
80–100%
Contracts addressable
Strategy 04
Retire — product end-of-life
End-of-life software carries security, compliance, and operational risk that increases over time. Every EOL product must have an active remediation plan.
Identification criteria
Vendor announced end-of-support
Technology stack obsolete or unsupported
Security vulnerabilities no longer patched
Compliance violations due to unsupported platform
Case example — Oracle Forms 6i
End of Premier Support: 2009
Currently on Extended Support @ $150K/year
50 users — HR data entry screens only
Action: migrate to modern web forms or SaaS HR
Common EOL products in enterprise estates
Windows Server 2012
EOS Oct 2023
SQL Server 2012
EOS Jul 2022
Oracle Forms 6i
EOS 2009
Adobe Flash
EOL Dec 2020
Internet Explorer 11
EOS Jun 2022
SAP ECC 6.0
EOM 2027
100%
Must be addressed
6–24 mo
Timeline
High
Risk if ignored
Expected portfolio outcomes
| Strategy | Portfolio scope | Savings / impact | Typical timeline |
|---|---|---|---|
| Eliminate | 60–80% of COTS apps | 30–60% license cost reduction | 2–4 weeks per app |
| Consolidate | 40–60% of COTS apps | 40–70% cost reduction | 6–12 months |
| Renegotiate | 80–100% of contracts | 15–40% cost reduction | 3–6 months per vendor |
| Retire | 10–20% of COTS apps | 100% must be addressed — security & compliance risk | 6–24 months |
Portfolio impact — illustrative COTS estate
SaaS Applications – A large Enterprise can have 200-800 SaaS subscriptions growing 25-40% annually with about $5M-$50M annual spend and which are 40-60% shadow IT owned (unapproved) with a typical average subscription age: 2-4 years. As these are unapproved there may multiple licenses of the same application, not properly evaluated and security compromised application, purchased but seldom used, over subscribed, licensed at a higher tier than required paying more money, bought with add-ons which are never used and too many applications of the same kind. Please refer to table below for some rationalization approaches for these
The four strategies
Strategy 01
Shadow IT discovery & elimination
Unmanaged SaaS subscriptions outside IT visibility — redundant, unauthorized, or abandoned.
2–5x more apps than tracked
Strategy 02
Subscription rightsizing
Wrong tier, over-licensed seats, or unused add-ons across approved SaaS applications.
70–90% of subscriptions
Strategy 03
Consolidate
SaaS sprawl reduction — feature overlap and functional duplication across the portfolio.
30–50% of SaaS apps
Strategy 04
Negotiate
Enterprise agreement optimization — volume, competitive leverage, and bundle expansion.
80–100% of contracts
Strategy detail
Strategy 01
Shadow IT discovery & elimination
Most organizations have 2–5x more SaaS apps in use than officially tracked. Discovery is the first step — followed by structured rationalization of what’s found.
Discovery methods
Expense report analysis — credit card charges
SSO / identity provider logs
Network traffic analysis via CASB tools
Browser plugin usage scanning
Email receipt scanning for SaaS invoices
Common candidates
Collaboration and file sharing tools
Email marketing tools
Social media management tools
Analytics and BI tools
CRM tools adopted by individual teams
Case example — 3-month portfolio scan
530 SaaS apps discovered — 380 were unknown to IT
Known/approved SaaS: 150 apps at $4.2M/year. Shadow SaaS: 380 apps at $1.8M/year. Total: 530 apps, $6M/year.
Legitimate business need
80 apps
$600K/year
Approve & centralize
Redundant to approved tools
180 apps
$800K/year
Eliminate — migrate to approved
Personal / unauthorized
100 apps
$300K/year
Terminate & block
Abandoned / unused
20 apps
$100K/year
Decommission immediately
Action 1
Approve & centralize — 80 apps
Negotiate enterprise pricing. Current spend: $600K (individual subscriptions) → Negotiated: $350K (enterprise agreements)
Savings: $250K
Action 2
Eliminate redundant — 180 apps
Migrate to approved alternatives. Current spend: $800K → Replacement cost: $0 (capacity exists in approved tools)
Savings: $800K
Action 3
Terminate unauthorized — 100 apps
Block access and notify users. No migration required.
Savings: $300K
Action 4
Decommission abandoned — 20 apps
Cancel subscriptions. No user impact.
Savings: $100K
$1.45M
Total savings
81%
Of shadow spend
3–9 mo
Discovery + remediation
Strategy 02
Subscription rightsizing
Over-licensed seats, wrong-tier plans, and unused add-ons are the most common waste patterns in approved SaaS. Rightsizing requires a structured usage audit followed by tier mapping.
Common waste patterns
Over-licensed — more seats than active users
Wrong tier — enterprise plan for basic-feature users
Unused add-ons — paying for features nobody uses
Rightsizing process
Pull usage reports for last 90 days
Categorize users by activity level
Map each user type to appropriate license tier
Notify users, execute changes, monitor complaints
User tier mapping
Power user
Daily, advanced features
Keep premium tier
Regular user
Weekly, basic features
Downgrade to mid-tier
Occasional user
Monthly, minimal use
Downgrade to basic / free
Inactive user
Never or rarely logs in
Remove license
Case example — Slack Enterprise Grid
2,000 seats @ $12.50/month = $300K/year
Only 1,200 users active in the last 30 days. 800 seats represent $120K/year in waste.
Case example — Microsoft 365 E5
500 E5 @ $57/user/month = $342K/year
E5 bundles features most users never access. Rightsizing to matched tiers recovers significant spend.
20–40%
Typical savings
1–2 wks
Per app audit
70–90%
Subscriptions addressable
Strategy 03
Consolidate — SaaS sprawl reduction
Organic SaaS adoption creates feature overlap and functional duplication. Consolidation reduces vendor count, simplifies management, and unlocks volume discounts.
Consolidation patterns
Feature overlap — different tools, same capability
Functional consolidation — multiple point solutions into one platform
Vendor consolidation — reduce number of contracts managed
Common consolidation targets
Collaboration and communication tools
Project management platforms
Design and creative suites
Marketing and analytics tooling
Development and DevOps toolchains
SaaS categories most prone to sprawl
Collaboration
File sharing
Project mgmt
Communication
Design / Creative
Analytics
Marketing tools
Dev tools
25–50%
Cost reduction
6–12 mo
Timeline
30–50%
Apps consolidatable
Strategy 04
Negotiate — enterprise agreements
Every major SaaS contract has negotiation headroom. Enterprise agreements, multi-year commitments, and competitive pressure routinely yield 15–35% savings with no change to the tool itself.
A. Volume commitment
Commit to multi-year term for discount
Consolidate departmental spend to single contract
Pre-purchase growth capacity at lower rate
B. Competitive leverage
Run RFP with 2–3 credible alternatives
Share shortlist with incumbent before renewal
Start negotiations 6 months before contract end
C. Bundle expansion
Add adjacent products in same vendor family
Replace point solutions with platform bundles
Use existing spend as leverage for better unit price
Salesforce example — license mix optimization
Current: 200 Sales Cloud Enterprise @ $150/user/month = $360K/year
Feature utilization: <60% of Enterprise capabilities being used
Action: Downgrade majority to Professional tier + negotiate bundle pricing
Combined with competitive RFP to validate pricing against HubSpot/Dynamics
15–35%
Typical savings
2–4 mo
Per vendor
80–100%
Contracts addressable
Expected portfolio outcomes
| Strategy | Portfolio scope | Savings / impact | Typical timeline |
|---|---|---|---|
| Shadow IT | 60–80% of shadow eliminated | $500K–$5M depending on portfolio size | 1–3 mo discovery + 3–6 mo remediation |
| Rightsizing | 70–90% of subscriptions | 20–40% cost reduction per app | 1–2 weeks per app |
| Consolidate | 30–50% of SaaS apps | 25–50% cost reduction | 6–12 months |
| Negotiate | 80–100% of major contracts | 15–35% cost reduction | 2–4 months per vendor |
Portfolio impact — illustrative SaaS estate
RATIONALIZATION BY TECHNOLOGY LAYER
Presentation Layer / User Interface – The most common issues with User Interfaces are that there are multiple front-end frameworks (React, Angular, Vue, legacy) often with inconsistent user experience using redundant UI components and involving huge accessibility gaps. Please refer to table below for some rationalization approaches for these
The three strategies
Strategy 01
UI framework standardization
Consolidate 5 competing front-end frameworks into a single standard to reduce hiring, training, and maintenance overhead.
30% front-end cost reduction
Strategy 02
Component library consolidation
Build a single enterprise design system to eliminate duplicate UI development and enforce brand and accessibility standards.
60% duplicate UI reduction
Strategy 03
Portal consolidation
Replace 15 separate employee-facing portals with a single unified experience platform with SSO and role-based dashboards.
$480K/year savings
Strategy detail
Strategy 01
UI framework standardization
130 applications currently span 5 different front-end frameworks — creating fragmented hiring pools, duplicate component work, and inconsistent user experiences. Standardizing on React eliminates this fragmentation over a 2-year migration program.
Current state — 130 applications across 5 frameworks
React
40
Standardize on this
Angular
25
Keep (strategic apps)
Vue
15
Keep (strategic apps)
jQuery
30
Migrate to React
Legacy
20
Retire / replace
Year 1 — establish standard
Adopt React as official front-end standard
Build enterprise component library on React
All new development in React only
Begin retiring 10 legacy apps
Migrate 10 jQuery apps to React
Year 2 — complete migration
Retire remaining 10 legacy apps
Migrate remaining 20 jQuery apps to React
Maintain Angular / Vue for strategic apps only
Full design system adoption across all new apps
Measure and report front-end cost reduction
Hiring & skills
Single framework means a larger candidate pool, faster onboarding, and no framework-specific silos within teams.
Component reuse
Shared design system components built once, used everywhere — eliminating parallel UI development across teams.
Faster development
Engineers familiar with one stack move faster. Less context-switching, fewer dependency conflicts, simpler CI/CD pipelines.
Consistent UX
Unified framework enforces shared patterns and behaviors — users experience the same interaction model across all applications.
30%
Front-end cost reduction
2 years
Migration timeline
50 apps
Migrated or retired
Strategy 02
Component library consolidation — enterprise design system
Without a shared component library, every team builds the same UI elements independently — buttons, forms, tables, modals, navigation. A single enterprise design system eliminates this duplication and enforces consistency at the source.
Design system pillars
Single component library
Material-UI, Ant Design, or custom — one source of truth for all UI components
Shared UI patterns
Standardized layouts, navigation structures, and interaction patterns across all apps
Accessibility built-in
WCAG compliance enforced at component level — not retrofitted per application
Brand consistency
Tokens for color, typography, spacing — brand changes propagate instantly across all apps
Before — without design system
Every team builds their own button components
Accessibility fixes applied app by app
Brand updates require changes across all codebases
Inconsistent UX patterns confuse users
Duplicate testing effort for identical components
After — with enterprise design system
Components built once, tested once, used everywhere
Accessibility compliance inherited automatically
Brand token update propagates to all apps instantly
Unified UX patterns across every application
Teams focus on business logic, not UI primitives
60%
Duplicate UI eliminated
Faster
Feature delivery via reuse
Simpler
Long-term maintenance
Strategy 03
Portal consolidation — unified employee experience
15 separate portals mean 15 separate logins, 15 maintenance budgets, 15 hosting bills, and a fragmented employee experience. Consolidating to a single portal with SSO and role-based dashboards eliminates all of this.
Current state — 15 separate portals
Employee portal
HR information
Benefits portal
Insurance, 401k
IT portal
Help desk & support
Learning portal
Training & courses
Travel portal
Booking & expenses
+ 10 additional portals
15 separate portals
→
Single employee experience portal
SSO · Unified navigation · Role-based dashboards
Consolidation approach
Single employee experience portal as the entry point
Federated authentication — one SSO login for everything
Unified navigation across all formerly separate portals
Role-based dashboards — each employee sees what’s relevant
Existing back-end systems integrated via APIs — not rebuilt
Employee experience improvements
One login instead of 15 — 20% productivity improvement
Consistent navigation reduces learning curve
Search across all content from a single interface
Notifications and alerts unified in one place
Mobile-first — single app instead of 15 bookmarks
Annual savings breakdown
Development
$400K/year
Hosting
$80K/year
Productivity gain
20% improvement
$480K
Annual savings
1 vs 15
Portals to maintain
20%
User productivity gain
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| Framework std. | 50 apps migrated or retired | 30% front-end development cost reduction | 2 years |
| Design system | All new and migrated apps | 60% reduction in duplicate UI development | 6–12 months to establish |
| Portal consol. | 15 portals → 1 | $480K/year — development + hosting savings | 12–18 months |
Middle Tier / Application Logic – The common issues are APIs proliferation (thousands of endpoints) duplicating business logic with inconsistent data validation, without any API governance. Following strategies can be adopted
The three strategies
Strategy 01
API consolidation
Catalog, deduplicate, and consolidate 2,500 REST APIs with 80% functional overlap into a clean, documented API layer.
2,500 → 800 APIs (68% reduction)
Strategy 02
Business logic centralization
Replace duplicated business logic across 12 apps with a single authoritative microservice as the source of truth.
$300K/year development savings
Strategy 03
Microservices rationalization
Consolidate 250 microservices — 40% near-idle, 60 orphaned — into a right-sized, owned, and governed service estate.
250 → 120 services (52% reduction)
Strategy detail
Strategy 01
API consolidation
2,500 REST APIs with 80% functional overlap have accumulated through years of independent team development, acquisitions, and legacy system wrappers. Cataloguing, deduplicating, and consolidating yields a clean, versioned, documented API surface.
Current state problems
2,500 APIs — 80% functional overlap
Inconsistent naming and versioning conventions
No API catalog or documentation
Larger attack surface — more endpoints to secure
Consumers don’t know which API to call
Rationalization approach
Catalog all APIs using Swagger / OpenAPI
Identify functional duplicates across the catalog
Consolidate to canonical versioned APIs
Provide adapter layer during consumer migration
Deprecate and retire redundant endpoints
Case example — customer lookup API
16 variations of the same API across systems
Every team that needed customer data built their own endpoint — resulting in 16 overlapping APIs with inconsistent responses, different auth models, and no shared documentation.
Before — 16 redundant endpoints
Customer lookup
├─/api/v1/customers/search
├─/api/customer/find
├─/legacy/getCustomer
├─/crm/searchCustomers
└─+ 12 other variations
After — single canonical API
✓ /api/v2/customers — single source of truth
↳ Adapter layer serves legacy consumers during transition
2,500
APIs today
→
800
Canonical APIs
68%
API reduction
Fewer
Attack surfaces
Full
OpenAPI documentation
Strategy 02
Business logic centralization — pricing microservice
Pricing logic duplicated across 12 applications in 7 different languages means 12 independent implementations that drift apart over time. A pricing bug requires 12 fixes. A promotion rule change takes months. Centralizing into a single microservice eliminates this entirely.
Current state — pricing logic in 12 systems
E-commerce website
JavaScript
Own pricing impl.
Mobile app
Swift / Kotlin
Own pricing impl.
Point of sale
Java
Own pricing impl.
Call center
C#
Own pricing impl.
Partner portal
PHP
Own pricing impl.
+ 7 other systems
Problems with duplication
Inconsistent pricing results across channels
Bug fixes require changes in all 12 systems
Business rule changes take months to propagate
Each implementation drifts independently over time
Testing effort multiplied across every system
After centralization
Change pricing rules in one service — all channels update instantly
Consistent pricing everywhere — one calculation engine
Promotions go live in hours, not months
Single test suite covers all use cases
New channel integrations take days, not weeks
Pricing microservice
Single REST API — all 12 apps call this
Single source of truth
$300K
Development savings/year
1 fix
Instead of 12 per bug
Hours
To launch promotions
Strategy 03
Microservices rationalization
Microservices proliferation creates operational complexity that outweighs the architectural benefits. 250 services — many low-traffic, many orphaned — drive disproportionate infrastructure cost, debugging complexity, and distributed transaction failures.
Low traffic
40%
of services have fewer than 10 requests per day — not justified as independent deployables
Orphaned
60
services owned by departed employees — no one responsible for maintenance, upgrades, or incidents
Overlap
30%
of services have overlapping functionality — same domain logic implemented independently by different teams
Consolidation approach — merge by domain
Customer service
+
Account service
+
Profile service
→
Customer domain service
Order service
+
Cart service
+
Checkout service
→
Order domain service
60 orphaned services
→
Retired / decommissioned
Rationalization actions
Consolidate low-traffic services by domain — 250 → 120
Merge related services into cohesive domain services
Retire all 60 orphaned services with no active owner
Establish mandatory service ownership model going forward
Operational benefits
Fewer deployment pipelines to manage and monitor
Reduced distributed tracing complexity
Fewer distributed transaction failure points
Lower infrastructure cost — $200K/year
250
Microservices today
→
120
Rationalized services
52%
Service count reduction
$200K
Infrastructure savings/yr
100%
Services with an owner
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| API consolidation | 2,500 → 800 APIs | 68% reduction — improved security, documentation, maintainability | 6–12 months |
| Logic centralization | 12 apps → 1 service | $300K/year development savings — 1 fix instead of 12 | 3–6 months |
| Microsvcs. rational. | 250 → 120 services | $200K/year infrastructure savings — 52% service reduction | 6–12 months |
Portfolio impact summary
Data Layer / Databases – The Common Issues are database sprawl (hundreds of instances), redundant data storage, inconsistent master data and high licensing costs. The strategies that can be adopted is given below
The three strategies
Strategy 01
Database consolidation
Consolidate 350+ database instances across 6 technologies into a right-sized, governed estate with a three-phase program.
$1.8M/year savings (72% reduction)
Strategy 02
Data redundancy elimination
Customer data duplicated across 18 systems with no single view. MDM platform creates a golden record and eliminates fragile sync jobs.
$230K/year + 2.5yr ROI
Strategy 03
Technology rationalization
Standardize from 8 database technologies to 3 — one per workload type — to simplify skills, licensing, and operations.
$1.6M/year savings
Strategy detail
Strategy 01
Database consolidation
350+ database instances across 6 technologies are costing $2.5M/year in licensing alone, require 8 DBAs to manage, and run at an average of 20% capacity utilization. A three-phase consolidation program recovers $1.8M/year.
Current state — 350+ instances, 20% average utilization
SQL Server
150
instances
Oracle
80
databases
PostgreSQL
50
databases
MySQL
40
databases
MongoDB
30
instances
Others
Various
Cassandra, Redis, etc.
Current cost burden
Licensing: $2.5M/year total
DBA management: 8 FTEs
Backup and DR: $800K/year
Average capacity utilization: 20%
Consolidation approach
Multi-tenant architecture on consolidated instances
Decommission small, dev, and test databases
Always On Availability Groups for SQL Server
Migrate non-critical workloads to open source
Three-phase consolidation program
Phase 1
Oracle consolidation
80 databases → 12 consolidated instances
Multi-tenant architecture
Decommission small and test databases
$800K/year savings
Phase 2
SQL Server consolidation
150 instances → 25 instances
Always On Availability Groups
Shared infrastructure model
$600K/year savings
Phase 3
Open source migration
Non-critical workloads → PostgreSQL
Eliminate Oracle dev/test licenses
Long-term license elimination
$400K/year savings
$1.8M
Annual savings
72%
Cost reduction
8 → 4
DBAs freed for optimization
Strategy 02
Data redundancy elimination — master data management
Customer data spread across 18 systems with no golden record creates inconsistent records, compliance risk, and fragile synchronization jobs. An MDM platform centralizes this into a single authoritative customer view.
Customer data in 18 systems — no single source of truth
CRM (Salesforce)
120K customers
ERP (SAP)
115K customers
E-commerce (custom)
200K customers
Support (Zendesk)
80K customers
Marketing (HubSpot)
150K customers
+ 13 other systems
Current problems
Inconsistent customer records across systems
No single 360-degree customer view
50+ fragile data synchronization jobs
GDPR and data residency compliance risk
Duplicate storage costs across every system
MDM solution
Implement MDM platform — Informatica, Profisee, or Reltio
Create golden customer record as single source
Spoke-and-hub integration architecture
Real-time data synchronization replacing batch jobs
Data governance and quality rules enforced centrally
MDM golden record — spoke and hub
All 18 systems read from and write to a single authoritative customer record
Single source of truth
360-degree customer view
Real-time sync
GDPR compliant
Cost and ROI breakdown
$200K
MDM platform / year
$500K
Implementation (one-time)
$150K
Sync job maintenance saved / yr
$80K
Storage reduction / yr
$230K
Net savings/year
50+
Sync jobs eliminated
2.5 yr
ROI payback
Strategy 03
Database technology rationalization
8 database technologies require 8 skill sets, 8 backup strategies, 8 vendor relationships, and 8 sets of licensing negotiations. Standardizing to 3 — one per workload type — resolves all of this without sacrificing fit-for-purpose selection.
Standardize from 8 technologies to 3
Transactional
PostgreSQL
Replaces:
MySQL
MariaDB
SQL Server (non-critical)
Keep Oracle for mission-critical only
Analytical
Snowflake
Replaces:
Teradata
Netezza
On-prem warehouses
Redshift
Cloud-native elastic scaling
NoSQL
MongoDB
Replaces:
Cassandra
DynamoDB
CouchDB
Specific document use cases only
Operational benefits
Fewer skill sets — deeper expertise per technology
Stronger vendor negotiation via volume concentration
Simplified backup and DR — 3 strategies not 8
Single toolchain for monitoring and observability
Decision criteria
Transactional OLTP workloads → PostgreSQL
Analytical / reporting workloads → Snowflake
Document / unstructured data → MongoDB
Mission-critical existing Oracle → keep and optimize
Annual savings breakdown
$1.6M
Total annual savings
8 → 3
Database technologies
3
Skill sets to master
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| DB consolidation | 350+ instances → right-sized estate | $1.8M/year — 72% cost reduction, 8 → 4 DBAs | 3 phases over 18 months |
| MDM / redundancy | 18 systems → golden record | $230K/year net savings — 50+ sync jobs eliminated | 12–18 months |
| Tech rationalization | 8 technologies → 3 | $1.6M/year — $1.2M licenses + $400K management | 12–24 months |
Combined portfolio impact
Integration Layer / Middleware – For Integration layer the common issues are point-to-point integration spaghetti, multiple integration technologies, no integration governance and brittle, hard-to-maintain integrations. The strategies that can be adopted are
The two strategies
Strategy 01
Integration platform consolidation
750 integrations across 6 platforms and hundreds of point-to-point scripts — standardize on MuleSoft with a four-action rationalization program.
750 → 420 integrations · $700K/year savings
Strategy 02
API gateway consolidation
5 API gateways with inconsistent security, no unified monitoring, and duplicate throttling logic — consolidate to Apigee as a single control plane.
5 gateways → 1 · $150K/year savings
Strategy detail
Strategy 01
Integration platform consolidation
750 integrations spanning 6 platforms, 300+ point-to-point connections, and 200+ scripts cost $1.5M/year and require specialized knowledge across every platform. Standardizing on MuleSoft Anypoint reduces this to a single governed integration estate.
Current state — 750 integrations across 6 platforms · $1.5M/year
MuleSoft
30
Standard — expand to this
Dell Boomi
45
Migrate → MuleSoft
Informatica
25
Migrate → MuleSoft
Custom ESB
150
Top 100 → rebuild, rest retire
Point-to-point
300+
Retire low-value, keep strategic
Scripts / cron
200+
Audit — retire or formalize
Four-action rationalization program
1
Migrate Boomi + Informatica → MuleSoft
70 integrations migrated to MuleSoft. Retire Boomi and Informatica licenses on completion.
License savings: $400K/year
2
Rebuild top 100 custom ESB integrations
High-value custom integrations rebuilt as MuleSoft flows with proper error handling, monitoring, and documentation.
Development savings: $300K/year (one platform)
3
Retire 200 low-value integrations
Audit all point-to-point and script-based integrations. Decommission those with no active consumers or business justification.
Reduces total count by 27%
4
Keep 250 custom integrations (long-tail)
Low-complexity integrations not worth migrating cost-wise. Document, own, and monitor — do not actively develop.
Managed as technical debt — reviewed annually
750
integrations today
→
420
post-rationalization
Annual savings breakdown
$700K
Total annual savings
44%
Integration reduction
1
Platform to master
Strategy 02
API gateway consolidation — single control plane
5 API gateways evolved organically — Kong for public, Apigee for partners, AWS for cloud, Nginx as a legacy proxy, and a homegrown custom gateway. Each has its own security policies, monitoring, and rate limiting — creating inconsistency, management overhead, and gaps.
Current state — 5 gateways, inconsistent policies
Kong
Public APIs
Retire — migrate to Apigee
Apigee
Partner APIs
Standard — expand to all traffic
AWS API Gateway
Cloud microservices
Migrate internal → Apigee
Nginx
Legacy reverse proxy
Retire — replace with Apigee
Custom gateway
Homegrown
Decommission entirely
3 gateways retired
1 migrated
1 expanded
1 migrated
1 expanded
Current problems
Inconsistent security policies across 5 gateways
No unified monitoring or analytics view
Duplicate rate limiting and throttling logic
High management overhead — 5 separate toolchains
Developer experience varies by API type
After consolidation to Apigee
Single security policy applied to all API traffic
Unified analytics and monitoring dashboard
Consistent rate limiting and quota management
Single developer portal for all API consumers
Simplified on-call and incident response
Apigee as unified API control plane
All public, partner, internal, and cloud API traffic through a single governed gateway
Unified security
Single analytics
Consistent rate limiting
One developer portal
$150K
Annual savings
5 → 1
Gateways
Unified
Security + monitoring
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| Integration platform | 750 → 420 integrations | $700K/year — $400K licenses + $300K dev savings | 12–18 months |
| API gateway | 5 gateways → 1 (Apigee) | $150K/year — Kong + custom gateway eliminated | 6–12 months |
Combined portfolio impact
RATIONALIZATION BY BUSINESS FUNCTION
Finance & Accounting typical Financial portfolio consist of ERP / General Ledger (SAP, Oracle, NetSuite),Accounts Payable automation,. Accounts Receivable / Billing,. Expense management (Concur, Expensify),Procurement (Coupa, Ariba),Tax compliance,. Financial Planning & Analysis (Anaplan, Adaptive),Treasury management, Audit & compliance tools and Financial reporting / BI. The recommended strategy is given below
The two strategies
Strategy 01
ERP consolidation
Five ERP systems across corporate and divisions — SAP, Oracle, Dynamics, QuickBooks, and a custom GL — driving a 15-day month-end close and 20+ reconciliation interfaces.
$2.05M/year savings · 18-month payback
Strategy 02
Finance tool stack optimization
Expense management split across Concur, Expensify, Chrome River, and manual spreadsheets — inconsistent policy, fragmented reporting, and duplicate licensing.
$40K/year savings · unified policy
Strategy detail
Strategy 01
ERP consolidation — SAP S/4HANA single instance
A multi-ERP environment requires 20+ reconciliation interfaces, produces manual journal entries at period-end, takes 15 days to close the books, and creates significant audit complexity. Consolidating to SAP S/4HANA eliminates all of this.
Current state — 5 ERP systems · $3.55M/year total
SAP
Corporate
$2.0M/year
Migrate to S/4HANA
Oracle ERP
Division A
$800K/year
Decommission
MS Dynamics
Division B
$400K/year
Decommission
QuickBooks
Subsidiaries
$50K/year
Decommission
Custom GL
Legacy
$300K/year
Retire
SAP S/4HANA
Single instance, multi-company
$2.8M/year
Target state
Integration and process pain — before consolidation
20+
Reconciliation interfaces between systems
15 days
Month-end close cycle
Manual
Journal entries at period-end
High
Audit complexity across 5 systems
After consolidation — SAP S/4HANA
0
Reconciliation interfaces — real-time consolidation
3–5 days
Month-end close — 70% faster
Automated
Journal entries and intercompany
Single
Audit trail — one system of record
Cost and savings breakdown
$2.8M/year
SAP S/4HANA license (new)
$3M
Migration cost (18 months, one-time)
$1.55M/year
Oracle + Dynamics + QB + Custom GL retired
$500K/year
Operational efficiency — faster close, fewer reconciliations
$2.05M
Annual savings
18 months
Payback period
5 → 1
ERP systems
Strategy 02
Finance tool stack optimization — expense management
Three separate expense platforms plus manual spreadsheets create policy inconsistency, fragmented fraud detection, and duplicate vendor relationships — for a combined cost that exceeds what a single enterprise contract would cost for the full user base.
Current state — 4 expense platforms · $190K/year · 3,000 users
Concur
Corporate
$120K/year
2,000 users
Standard — expand to all users
Expensify
Sales team
$30K/year
500 users
Migrate → Concur, retire
Chrome River
EMEA
$40K/year
300 users
Migrate → Concur, retire
Spreadsheets
Various teams
$0 (hidden cost)
200 users
Onboard to Concur
$190K/year
4 platforms · 3,000 users
→
$150K/year
Concur enterprise · all 3,000 users
Benefits beyond cost savings
Policy consistency
Single expense policy applied uniformly — no regional or team exceptions
Better fraud detection
Unified AI-powered audit across all submissions — not fragmented across tools
Unified reporting
Global T&E spend visibility in one dashboard — not assembled from three exports
$40K
Annual savings
3 → 1
Expense platforms
3,000
Users on one platform
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| ERP consolidation | 5 ERPs → SAP S/4HANA | $2.05M/year — decommission savings + operational efficiency | 18 months · $3M migration |
| Expense management | 4 platforms → Concur | $40K/year — unified policy, fraud detection, reporting | 3–6 months |
Finance rationalization — portfolio targets
Common HR Tech Stack: An HR portfolio consists of applications like HRIS / Core HR (Workday, SuccessFactors, ADP), Payroll (ADP, Paychex),Recruiting (Greenhouse, Lever, Jobvite), Applicant tracking, Onboarding, Learning management (Cornerstone, Docebo), Performance management (Lattice, 15Five), Engagement surveys (Culture Amp, Glint), Benefits administration (Benefitfocus, Ease), Time & attendance and HR analytics. The strategy for rationalization could look like as follows
The two strategies
Strategy 01
HR suite consolidation
Seven best-of-breed HR tools with 15 point-to-point connections and no single employee record — consolidate to Workday HCM while keeping best-in-class tools where justified.
7 → 3 apps · $100K/year savings
Strategy 02
Recruiting stack rationalization
Eight sourcing channels costing $180K/year — LinkedIn drives 45% of hires while niche job boards deliver marginal ROI. Reallocate spend to high-performing channels.
$50K/year savings · better hire quality
Strategy detail
Strategy 01
HR suite consolidation — Workday HCM
Seven best-of-breed HR tools each solve one problem well but create 15 point-to-point integrations, no single employee record, and a fragmented employee experience. Consolidating to Workday HCM replaces five tools with one platform while retaining two where best-in-class value is clear.
Current state — 7 tools · $575K/year · 15 integrations · no single record
ADP Workforce Now
Core HR + Payroll
$200K/year
Migrate to Workday
Greenhouse
Recruiting
$80K/year
Retire — Workday Recruit
BambooHR
Onboarding
$25K/year
Retire — Workday Onboard
Cornerstone
LMS
$100K/year
Retire — Workday Learning
Lattice
Performance
$50K/year
Retire — Workday Perform
Culture Amp
Engagement
$40K/year
Keep — best-in-class
Various others
Multiple
$80K/year
Audit and retire
LinkedIn Recruiter
Sourcing
$60K/year
Keep — top hire source
Before — fragmented estate
7 separate HR applications
15 point-to-point integrations
No single employee record
Employee data in 7 systems
Inconsistent HR workflows
After — Workday + 2 best-in-class
3 tools total (7 → 3)
2 integrations (Workday ↔ Culture Amp + LinkedIn)
Single employee record in Workday
Unified talent suite — one platform
Consistent HR experience company-wide
Final state — 3 tools · $550K/year
Workday HCM
$450K/year
Core HR, payroll, recruit, onboard, learn, perform
Culture Amp
$40K/year
Best-in-class engagement — retained
LinkedIn Recruiter
$60K/year
Top sourcing channel — retained
$100K
Annual savings
7 → 3
HR applications
15 → 2
Integration points
Strategy 02
Recruiting stack rationalization
Eight sourcing channels cost $180K/year but deliver very unequal results. LinkedIn alone drives 45% of hires. Niche job boards collectively drive less than 20% at combined spend that could instead fund a referral program — historically the highest-quality hire source.
Source analysis — hiring ROI by channel
LinkedIn
45%
Keep
Indeed
20%
Keep
Employee referrals
15%
Invest more
All niche boards
20%
Eliminate
Current sourcing channels — $180K/year
LinkedIn Recruiter
$60K/year
Keep — 45% of hires
Indeed Sponsored
$40K/year
Keep — volume source
ZipRecruiter
$15K/year
Eliminate — low ROI
Glassdoor
$10K/year
Eliminate — low ROI
AngelList
$5K/year
Eliminate
Handshake
$8K/year
Eliminate
Dice
$12K/year
Eliminate
Referral program
$30K/year
Invest — best quality hire
$180K/year
8 channels · mixed ROI
→
$130K/year
3 channels · high ROI
Optimized channel mix
LinkedIn Recruiter — $60K (45% of hires)
Indeed — $40K (20% of hires)
Referral bonuses — $30K (highest quality)
Quality of hire improvement
Referrals outperform job board hires on retention
Faster time-to-hire via warm introductions
Lower cost-per-hire than sponsored jobs
Employee engagement boost from referral program
$50K
Annual savings
28%
Cost reduction
Better
Quality of hire
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| HR suite | 7 tools → 3 (Workday + 2) | $100K/year — license + $75K integration savings | 12–18 months |
| Recruiting stack | 8 channels → 3 | $50K/year — 28% reduction + better hire quality | 1–3 months |
HR rationalization — portfolio targets
Sales and Marketing : A typical portfolio consist of Email marketing (Mailchimp, SendGrid), Email marketing (Mailchimp, SendGrid),social media management (Hootsuite, Sprout), Content management (WordPress, Adobe Experience), SEO tools (Moz, SEMrush, Ahrefs), Analytics (Google Analytics, Adobe Analytics), A/B testing (Optimizely, VWO), Customer data platform (Segment, mParticle), Ad platforms (Google Ads, Facebook, LinkedIn), Video (Wistia, Vidyard) and Various point solutions (30-100 tools)
The three strategies
Strategy 01
CRM consolidation
Four CRM systems plus spreadsheets — no unified customer view, duplicate data entry, inconsistent sales process — consolidate to Salesforce as the single source of truth.
$530K/year savings · 9-month payback
Strategy 02
MarTech stack rationalization
87 marketing applications across 7 categories costing $630K/year — consolidate to HubSpot Marketing Hub Enterprise and four specialist tools.
87 → 10 tools · $475K/year savings
Strategy 03
Sales enablement cleanup
Ten sales tools plus ten point solutions at $1.03M/year — keep the high-value core stack, consolidate overlapping tools into Salesforce native features.
$173K/year savings · 17% reduction
Strategy detail
Strategy 01
CRM consolidation — Salesforce as single source of truth
Four CRM systems operating in parallel create fragmented customer data, inconsistent sales processes, and a reporting environment that requires manual reconciliation. Consolidating to Salesforce Sales Cloud Enterprise eliminates all of this at a net saving of $530K/year.
Current state — 4 CRM systems + spreadsheets · $1.03M/year
Salesforce
Enterprise Sales
$500K/year
Upgrade to Sales Cloud Enterprise
HubSpot CRM
SMB Sales + Marketing
$150K/year
Migrate data, retire
Microsoft Dynamics
Field Sales
$200K/year
Migrate data, retire
Custom CRM
Partner Channel
$180K/year
Rebuild in Salesforce, retire
Spreadsheets
Various teams
$0 (hidden cost)
Onboard all users to Salesforce
Salesforce Sales Cloud Enterprise
All teams — target state
$600K/year
Single source of truth
Current problems
No unified customer view across segments
Duplicate data entry across 4 systems
Inconsistent sales process by division
Reporting requires manual reconciliation
Forecasting accuracy compromised
After consolidation
Single customer record — all segments unified
One data entry point — no reconciliation
Standardized sales process company-wide
Real-time reporting and dashboards
Einstein AI for forecasting and lead scoring
Single source of truth
Every team sees the same customer data — no conflicting records
Process standardization
One sales methodology applied consistently across all divisions
Better forecasting
Pipeline data from all teams in one place — accurate board-level reporting
Einstein AI
AI-powered lead scoring, opportunity insights, and forecast accuracy
$530K
Annual savings
9 months
Payback period
$400K
One-time migration cost
Strategy 02
MarTech stack rationalization — HubSpot Marketing Hub Enterprise
87 marketing tools across 7 categories at $630K/year have accumulated through team-by-team adoption with no central governance. Consolidating to HubSpot Marketing Hub Enterprise — which covers email, social, content, SEO, analytics, and ads natively — reduces this to 10 tools at $155K/year.
Current state — 87 tools across 7 categories · $630K/year
Email
12 tools
$80K/year
Consolidate → HubSpot
Social
8 tools
$45K/year
Consolidate → HubSpot
Content
15 tools
$120K/year
Consolidate → HubSpot
SEO
10 tools
$60K/year
Keep SEMrush, retire rest
Analytics
18 tools
$200K/year
Keep GA4, retire rest
Paid ads
7 tools
$40K/year
LinkedIn Ads direct, retire
Misc
17 tools
$85K/year
Audit — keep Wistia, retire rest
Target state
HubSpot Mktg Hub Ent.
$120K/year
Covers 6 of 7 categories
Final state — 10 tools · $155K/year
HubSpot Mktg Hub
$120K/year
Core platform
Google Analytics
Free
Best-in-class
SEMrush
$20K/year
Advanced SEO
Wistia
$15K/year
Video hosting
87 tools · $630K
Current state
→
10 tools · $155K
Target state
$475K
Annual savings
75%
Cost reduction
87 → 10
Tools
Strategy 03
Sales enablement tool cleanup
Ten named sales tools plus ten additional point solutions at $1.03M/year. The core stack (Salesforce, Outreach, Gong, ZoomInfo) delivers clear value. Peripheral tools — scheduling, e-signature, proposals — overlap with Salesforce native capabilities and can be consolidated.
Current state — 20 tools · $1.033M/year
Salesforce
CRM
$500K/year
Keep — core
Outreach.io
Sales engagement
$120K/year
Keep — core
Gong
Conversation intelligence
$80K/year
Keep — core
ZoomInfo
Data enrichment
$100K/year
Keep — core
LinkedIn Sales Nav.
Social selling
$60K/year
Keep — sourcing
DocuSign
E-signature
$40K/year
Replace with Salesforce
PandaDoc
Proposals
$30K/year
Replace with Salesforce
Calendly
Scheduling
$8K/year
Replace with Salesforce
Zoom
Video
$15K/year
Consolidate to Teams/Meet
10 point solutions
Various
$80K/year
Audit — retire low-value
Keep — high-value core stack
Salesforce — CRM and workflow hub
Outreach.io — sales sequence automation
Gong — call recording and coaching
ZoomInfo — contact data enrichment
LinkedIn Sales Navigator — social selling
Consolidate into Salesforce native
DocuSign → Salesforce e-signature ($40K saved)
PandaDoc → Salesforce CPQ proposals ($30K saved)
Calendly → Salesforce scheduler ($8K saved)
Zoom → existing video platform ($15K saved)
Point solutions → audit and retire ($80K target)
$1.033M/year
20 tools current
→
$860K/year
Core stack optimized
$173K
Annual savings
17%
Cost reduction
Less switching
Rep productivity gain
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| CRM consolidation | 4 CRMs → Salesforce | $530K/year — decommission savings + single customer view | 12–18 months · $400K migration |
| MarTech rationalization | 87 → 10 tools | $475K/year — 75% cost reduction | 6–12 months |
| Sales enablement | 20 tools → core stack | $173K/year — 17% reduction + rep productivity | 3–6 months |
Sales and marketing rationalization — portfolio targets
IT Operations: A common portfolio usually consist of Service management (ServiceNow, Jira Service Desk), Monitoring (Datadog, New Relic, Nagios, Zabbix, SolarWinds), Log management (Splunk, ELK, Sumo Logic), APM (AppDynamics, Dynatrace),Infrastructure monitoring (Prometheus, Grafana), Security (50+ tools: SIEM, EDR, vulnerability scanning, etc.), Backup / DR (Veeam, Commvault, Rubrik),Asset management (ServiceNow, Lansweeper),Remote access (VPN, jump boxes, PAM) and Various scripts and homegrown tools
The two strategies
Strategy 01
Observability consolidation
Infrastructure, APM, and logging spread across 10 tools at $1.67M/year — plus 6 FTEs maintaining open-source stacks. Consolidate to Datadog for unified observability.
$1.07M/year savings · 64% reduction
Strategy 02
Security tool rationalization
40 security tools at $2.5M/year — SIEM duplication, overlapping endpoint and cloud protection. Consolidate to an integrated security platform plus two specialist tools.
40 → 8 tools · $1.15M/year savings
Strategy detail
Strategy 01
Observability consolidation — Datadog unified platform
Infrastructure, application performance, and log management are served by three separate tool stacks. Open-source tools appear free but require 6 FTEs to operate — adding $720K/year in hidden labour cost. Total true cost is $1.67M/year. Datadog replaces all of this at $600K/year.
Current state — 3 stacks · $1.67M/year (including FTE cost)
Infrastructure monitoring
SolarWinds$80K/year
Nagios (open source)2 FTEs = $240K
Zabbix (open source)1 FTE = $120K
Prometheus + Grafana1 FTE = $120K
Subtotal: $560K/year
Application performance
New Relic$200K/year
AppDynamics$180K/year
Custom scripts$60K maint.
Subtotal: $440K/year
Log management
Splunk$400K/year
ELK Stack (open source)2 FTEs = $240K
CloudWatch$30K/year
Subtotal: $670K/year
Hidden FTE cost — open source is not free
2 FTEs
Maintaining Nagios · $240K/yr
2 FTEs
Maintaining ELK Stack · $240K/yr
2 FTEs
Zabbix + Prometheus · $240K/yr
Datadog — unified observability platform
Infrastructure monitoring, APM, log management, and security in a single platform. No FTEs required to maintain the tooling itself.
Infrastructure
APM
Log management
Security monitoring
Unified dashboards
Unified dashboards
Infrastructure, app, and log data in one view — no context switching
Better correlation
Cross-stack correlation — trace from infra alert to app error to log entry
Fewer tools to learn
One platform for the entire on-call team — less cognitive load during incidents
Reduced on-call burden
Fewer alert sources, better noise suppression, faster root cause identification
$1.67M/year
10 tools + 6 FTEs
→
$600K/year
Datadog — all stacks unified
$1.07M
Annual savings
64%
Cost reduction
6 FTEs
Freed from tool maintenance
Strategy 02
Security tool rationalization — integrated platform
40 security tools at $2.5M/year with overlapping coverage in every category. Consolidating to an integrated security platform — Microsoft Defender, Palo Alto Cortex, or CrowdStrike — plus two specialist tools reduces this to 8 tools at $1.35M/year while improving overall security posture.
Current state — 40 tools across 9 categories · $2.5M/year
SIEM
2 tools
Splunk + QRadar
Consolidate → keep Splunk only
Endpoint protection
3 tools
Overlapping coverage
Consolidate → Defender
Vulnerability scanning
5 tools
Fragmented coverage
Consolidate → Tenable
Web app firewall
2 tools
Duplicate WAF
Consolidate → single WAF
Cloud security
4 tools
Multi-cloud overlap
Consolidate → Defender for Cloud
Identity & access
3 tools
IAM sprawl
Consolidate → Defender for Identity
DLP
2 tools
Duplicate DLP
Consolidate → platform native
Email security
2 tools
Overlapping filters
Consolidate → Defender for Office
Point solutions
17 tools
Miscellaneous
Audit — retire most
Target state — 8 tools · $1.35M/year
Microsoft Defender Suite
$800K/year
Endpoint + Cloud + Identity + Email
Splunk SIEM
$400K/year
Keep — best-in-class SIEM
Tenable
$150K/year
Vulnerability management specialist
Problems with 40-tool sprawl
Overlapping coverage creates false sense of security
Alert fatigue — too many consoles, too many signals
10-person security team managing 40 tools
No unified threat correlation across tools
Inconsistent policy enforcement across categories
After platform consolidation
Integrated threat detection across all vectors
Single console — unified alert triage
Security team focuses on threats not tool management
Native integration with Windows and Azure estate
Consistent policy applied across endpoint, cloud, identity
40 tools · $2.5M
Current state
→
8 tools · $1.35M
Integrated platform
$1.15M
Annual savings
46%
Cost reduction
40 → 8
Security tools
Expected portfolio outcomes
| Strategy | Scope | Savings / impact | Timeline |
|---|---|---|---|
| Observability | 10 tools → Datadog | $1.07M/year — licenses + 6 FTEs freed from tool maintenance | 6–12 months |
| Security tools | 40 → 8 tools | $1.15M/year — 46% reduction + improved security posture | 12–18 months |
IT operations rationalization — portfolio targets
RATIONALIZATION BY TECHNICAL CHARACTERISTICS
Applications can be classified for Rationalization based on the common characters that has come to define them as “problematic” in terms of how they perform,. What it takes to run and value it delivers
Legacy Technology : The strategy for legacy technologies are summarized below
Identification criteria
Technology stack end-of-support
Vendor has withdrawn security patches, bug fixes, and official support. Continued operation creates unmitigated compliance and security risk.
Unable to hire developers
Skills are scarce, expensive, or only available from an aging workforce. Bus-factor risk is extreme — one departure leaves the system unmaintainable.
Security vulnerabilities unfixable
Known CVEs cannot be patched because the underlying technology is unsupported. Every day the system runs is an unacceptable risk.
Cannot integrate with modern systems
No REST API, no webhook support, proprietary protocols only. Forces expensive custom adapters and brittle point-to-point connections.
Legacy technology reference — rationalization paths
| Technology | Typical issues | Rationalization path | Effort |
|---|---|---|---|
COBOL mainframe |
Extremely expensive — scarce COBOL skills command premium rates. High operational cost. No cloud-native path. |
Modernize or replace | |
PowerBuilder |
No active vendor support. Appeon acquired it but ecosystem is marginal. Thick-client model incompatible with modern delivery. |
Rebuild in web tech | |
Visual Basic 6 |
End-of-life since 2008. No 64-bit support. Cannot run on modern Windows without compatibility shims. No path to cloud. |
Migrate to .NET or web | |
Oracle Forms 6i |
End of Premier Support 2009. Extended support only. Ancient, poor UX. Requires Oracle Application Server — itself end-of-life. |
Oracle APEX or low-code | |
Adobe Flash |
Fully deprecated December 2020. Blocked by all major browsers. Active security vulnerabilities. No longer executable without hacks. |
HTML5 / React | |
Perl / CGI scripts |
Unmaintainable — no type safety, no modern tooling, no containerization. Typically undocumented and owned by a single developer. |
Python / Node.js |
Rationalization approach — three phases
Phase 1
Assessment
2–4 weeks
Inventory all legacy appsWeek 1
Assess business criticalityWeek 2
Evaluate replacement optionsWeek 3
Prioritize by risk + valueWeek 4
Phase 2
Quick wins
3–6 months
Retire zero-usage legacy apps20%
Replace with SaaS where possible30%
Document remaining portfolioAll
Phase 3
Strategic migrations
1–3 years
Modernize mission-critical apps20%
Replace high-maintenance apps20%
Maintain only critical legacy10%
Expected outcomes
Legacy footprint reduction targets
20%
Retired immediately — zero-usage apps
30%
Replaced with SaaS — quick wins
40%
Modernized or rebuilt — strategic
10%
Maintained — mission-critical only
Result: 90% reduction in legacy footprint across a 3-year program
Unsupported / Out-of-Maintenance: Many organizations have applications that are no longer supported for various reasons. These are very suitable candidates for rationalization
Identification criteria
Vendor no longer provides patches
Security updates, bug fixes, and hotfixes have ceased. Every known vulnerability is permanently unpatched — a static, growing attack surface.
Extended support expired or prohibitively expensive
Paid extended support (ESU) is available but costs multiples of standard licensing and provides only critical patches — not feature or compatibility updates.
Community no longer active (open source)
For open-source dependencies: no recent commits, no CVE responses, no maintainers. Equivalent risk to commercial end-of-support.
Case example — Windows Server 2008 portfolio
Portfolio discovery findings
45
Applications on Windows Server 2008
Jan 2020
End of support date — already passed
200+
Unpatched CVEs on each server
12 months
Target remediation timeline
Rationalization — 45 applications across 5 decisions
45
total apps
Retire
15
33%
Replace with SaaS
10
22%
Migrate to Server 2022
12
27%
Refactor
5
11%
Risk accept
3
7%
Retire
15 apps
No longer used — decommission immediately
Applications with no active users or business process. Fastest path to risk elimination — data export, dependency check, then decommission.
Replace SaaS
10 apps
Available SaaS alternatives — migrate and retire
Commercial SaaS alternatives exist and cover the required functionality. Migrate users, migrate data, decommission the on-prem app and its Server 2008 host.
Migrate OS
12 apps
Compatible — lift to Windows Server 2022
Applications that run without modification on a modern OS. Migrate the application and its data to a new Server 2022 host — in-place upgrade or new server build.
Refactor
5 apps
Strategic apps — require code changes before migration
Mission-critical applications with hard OS dependencies (Win32 APIs, 32-bit only, deprecated frameworks). Code must be updated before the OS can be upgraded.
Risk accept
3 apps
Air-gapped systems — accept residual risk
Fully isolated from the network with no external connectivity. Risk accepted with documented controls, compensating measures, and a defined sunset date.
Delivery timeline — 12 months
Remediation program — Windows Server 2008 · 45 apps · $800K
Retire (15)
Replace SaaS (10)
Migrate OS (12)
Refactor (5)
Risk accept (3)
Expected outcomes
200+
Unpatched CVEs eliminated per server
$800K
Total remediation investment over 12 months
93%
Of portfolio fully remediated (42 of 45 apps)
Performance / Scalability Issues : Applications with performance and scalability issues not delivering required functionality can be a huge bottle neck issues. For the business
Identification — scalability failure symptoms
Cannot handle current load
Application degrades or fails at normal production traffic levels — not just peak
Frequent outages during peak times
Predictable failure at known demand events — sales, end-of-month, product launches
User complaints about slowness
Response time degradation under load is measurable and actively harming user experience
Manual scaling required
Operations team manually provisions capacity before known events — not automated, not elastic
Rationalization options
Option 1
Retire
If the business case is weak — declining usage, superseded by another system, or the business process itself is being phased out
Option 2
Optimize
If the architecture is fundamentally sound but under-resourced — caching, indexing, CDN, or additional compute can close the gap
Option 3
Replatform
If cloud hosting solves the scale problem without code changes — lift-and-shift to managed cloud services with auto-scaling
Option 4
Refactor
If the application is strategic and the architecture itself is the bottleneck — decompose to microservices, event-driven, or serverless
Case example — customer portal (monolith)
1,000
Current max concurrent users
→
10×
Scale gap
→
10,000
Business requirement
Option A
Optimize current (add servers + caching)
Investment$200K
Timeline2–3 months
Max scale3,000 users
Option B
Replatform to cloud (lift-and-shift)
Investment$400K
Timeline6 months
Max scale5,000 users
Option C
Refactor to microservices
Investment$2M
Timeline18 months
Max scale100,000+ users
Added benefitsAPI economy, CI/CD
Option D
Replace with SaaS customer portal
Running cost$150K/year
Migration cost$300K one-time
Max scaleUnlimited
UXModern, maintained
Decision — Option D
Replace with SaaS — lower risk, faster time-to-market
Why not Option C (refactor)?
$2M investment vs $300K migration
18 months vs 3–4 months to go-live
High execution risk — complex refactor
Dev team capacity better used on differentiating features
Why Option D wins
Unlimited scale — vendor responsibility
Modern UX maintained by vendor
Refocus dev team on competitive advantage
Lower total cost over 3 years
High Total Cost of Ownership : Some applications has very high TCO and are unfavorable compared to the business value that it brings
Identification — high TCO signals
Top 20% of apps consume 80% of budget
Pareto distribution of IT spend — a small number of applications drive a disproportionate share of total cost. These are the primary rationalization targets.
Maintenance cost exceeds business value
The annual cost of keeping the application running exceeds the measurable business value it delivers. The ROI calculation is permanently inverted.
“Expensive to keep the lights on”
Engineering teams spend the majority of their time on maintenance, incidents, and patching — with little capacity left for new features or innovation.
TCO analysis framework
Direct costs
Software licenses and subscriptions
Infrastructure — servers, storage, network
Development and maintenance — FTEs and contractors
Support — vendor and internal helpdesk
Hosting and cloud costs
Indirect costs
Integration maintenance overhead
Security and compliance burden
Training — onboarding and upskilling
Opportunity cost — dev time not building features
Technical debt tax — slowdown from accumulated debt
Case example — custom claims processing system
Custom Claims Processing System — Full TCO Analysis
Insurance carrier · built 2009 · 8-person development team · mission-critical but high-cost
Direct costs
Development team — 8 FTEs @ $150K
$1.2M/yr
Infrastructure
$400K/yr
Licenses — databases and tools
$200K/yr
Support
$100K/yr
Direct subtotal
$1.9M/yr
Indirect costs
Integration maintenance
$200K/yr
Security patches and audits
$150K/yr
Training
$80K/yr
Opportunity cost
$300K/yr
Indirect subtotal
$730K/yr
Total TCO — Custom Claims Processing System
Direct $1.9M + Indirect $730K
$2.63M/year
Rationalization — replace with Guidewire ClaimCenter
Current state
Custom Claims Processing System
Development team (8 FTEs)
$1.2M/yr
Infrastructure
$400K/yr
Licenses + support
$300K/yr
Indirect costs
$730K/yr
Total annual TCO
$2.63M/yr
→
Target state
Guidewire ClaimCenter SaaS
SaaS subscription
$600K/yr
Ongoing customization
$200K/yr
Migration (one-time)
$1.2M
Infrastructure
$0 (vendor)
Total annual TCO
$800K/yr
TCO comparison — current vs target
$1.83M
Annual savings — 70% TCO reduction
8 months
Payback on $1.2M migration investment
8 FTEs
Freed to build differentiating features
RATIONALIZATION BY LIFECYCLE STAGE
In a large enterprise applications are introduced and they go through a series of upgrade providing the much critical functionality required for the enterprise in a stable manner and then they fail to adapt to the changing technology and business requirements and finally are replaced with the new applications.
Introduction / Growth Stage
Characteristics — new application signals
Recently deployed — under 2 years
Too new to have accumulated significant technical debt but old enough that adoption patterns are measurable and projections can be validated against actuals.
Usage growing
Active user base is expanding — but growth rate vs projection is the key metric. Strong absolute numbers can mask underperformance against business case.
Active development
Engineering team is actively adding features. Investment is ongoing — making this the right moment to validate whether continued investment is justified.
Rationalization strategy — validate before committing
Generally keep — but answer these three questions first
Is adoption meeting projections?
Compare actual downloads, MAU, and engagement against the original business case. Significant shortfall requires a root cause investigation before further investment.
Is it cannibalizing existing apps?
New apps can inadvertently pull usage from established, higher-value applications. If the net portfolio impact is negative, the new app may be doing more harm than good.
Should it consolidate with similar new apps?
Multiple new apps launched in the same period may overlap in functionality. Early consolidation is dramatically cheaper than waiting until both are entrenched.
Case example — 3 mobile apps launched in the past year
App A
Customer mobile app
Downloads
target: 50K
48K
MAU
target: 10K
9.5K
Downloads vs target
MAU vs target
96% of download target · 95% of MAU target — performing in line with business case
Keep
Customer-facing, strategic — on track
App B
Field service mobile app
Downloads
target: 500
120
MAU
target: 400
45
Downloads vs target
MAU vs target
24% of download target · 11% of MAU target — severe adoption failure requiring investigation
Retire
Failed adoption — investigate root cause
App C
Sales mobile app
Downloads
target: 200
185
MAU
target: 150
140
Downloads vs target
MAU vs target
93% of targets — good adoption, but 60% feature overlap with Salesforce mobile already licensed
Consolidate
Retire — migrate users to Salesforce
Actions
App A
Keep
Customer mobile app — continue investment
Adoption is tracking within 5% of projections across both downloads and MAU. Customer-facing and strategically important. No overlap with existing apps. Continue active development.
App B
Retire
Field service app — failed adoption, investigate then retire
Only 24% of download target and 11% of MAU target after one year. Before retiring, investigate root cause — was the problem the app itself, the rollout, or the original business case? Document findings to avoid repeating the pattern.
App C
Retire
Sales app — good adoption but consolidate to Salesforce mobile
Adoption is strong at 93% of target — but 60% of features overlap with Salesforce mobile, which the organization already licenses. Migrating users to Salesforce eliminates duplicate development and license cost while users retain equivalent functionality.
Outcome — apps B + C retired
$400K
Annual savings — App B + App C maintenance eliminated
3 → 1
Mobile apps in active development
Dev capacity
Freed to focus on App A — the strategic customer-facing app
Maturity Stage
Characteristics — stable application signals
Stable user base
User count has plateaued — neither growing nor shrinking significantly. The application serves a consistent, known audience with predictable demand patterns.
Minimal new features
Development activity is limited to bug fixes, security patches, and minor enhancements. No significant backlog of new capability is planned or expected.
“If it ain’t broke, don’t fix it”
Users are satisfied, the system does its job, and there is no urgent pressure to change. The risk is complacency — hidden costs accumulate while alternatives improve.
Rationalization strategy — optimize for efficiency
Reduce maintenance costs
Audit the FTE and contractor time spent on the application. Stable apps often carry over-staffed maintenance teams from their active development era.
Consider managed services
Hand off infrastructure and operational management to a managed service provider — reducing FTE overhead without requiring application changes.
Migrate to lower-cost infrastructure
Rightsize the hosting environment. Stable, low-traffic apps often run on over-provisioned servers sized for peak loads that never materialize.
Evaluate SaaS alternatives
Commercial SaaS products now cover most generic business functions. For stable, non-differentiating apps, SaaS is almost always cheaper and lower-risk long term.
Case example — internal timesheet system
Internal Timesheet System
Option A
Keep as-is
Annual cost$300K/year
Migration cost$0
Staffing2 FTEs
Key riskDeveloper retirement
Risk: Lead dev retires in ~2 years — knowledge cliff
Option B
Migrate to managed service
Annual cost$180K/year
Migration cost~$80K
Staffing2 FTEs → 0.5 FTE
Savings vs A$120K/year
Reduces FTE risk — vendor takes operational burden
Option C
Replace with SaaS (Replicon, TSheets)
Annual cost$100K/year
Migration cost$150K one-time
Staffing2 FTEs → 0
Payback period9 months
Lowest long-term cost · zero FTE dependency risk
Decision — Option C
Replace with SaaS — lower long-term cost, zero FTE risk
Lower long-term cost
$100K vs $300K/year — 67% reduction
$150K migration pays back in 9 months
3-year total cost: $450K vs $900K
Modern mobile UX
Mobile-first timesheet entry for field workers
No training — modern consumer-grade UX
Vendor maintains and improves continuously
Integrates with payroll
Native connectors to ADP, Workday, SAP
Eliminates manual payroll reconciliation
Removes 2 FTEs from maintenance entirely
Outcome — option C selected
$200K
Annual savings — $300K → $100K/year
9 months
Payback on $150K migration investment
2 FTEs
Freed — zero ongoing maintenance dependency
Decline Stage
Characteristics — declining application signals
Usage decreasing
Active user count is in sustained decline — not seasonal dip. Month-on-month trends confirm users are leaving and not returning. The application is entering an irreversible contraction phase.
Being replaced by newer app
A successor application is live and receiving new users. The declining app is in a transitional overlap period — the organization is paying to run two systems that serve the same purpose.
In “sustain mode” only
No new features are planned. The team is only patching and keeping the lights on. Maintenance cost is now pure overhead with no return on further investment.
Rationalization strategy — accelerate retirement
01
Set sunset date
Commit to a firm shutdown date — announced publicly to users. A hard deadline creates urgency and prevents indefinite “just a bit longer” deferrals.
02
Migrate remaining users
Identify what the holdout users actually need. Most resistance comes from a small number of specific workflows or documents — address those directly.
03
Archive data
Export all content to a compliant long-term archive before shutdown. Distinguish between content that must be retained for compliance vs content that can be purged.
04
Decommission
Shut down servers, revoke licenses, remove DNS entries, cancel hosting contracts. Document the decommission for audit and compliance records.
Case example — legacy intranet portal
Legacy Intranet Portal
Replaced by SharePoint and Microsoft Teams · still costing $120K/year · 1,200 holdout users
User decline — 2015 to 2025
8,000
Peak — 2015
15% of peak
1,200
Current — 2025
$120K
Annual maintenance cost — still being paid
Stale
Most content not updated since 2020 or earlier
Resistant
1,200 users resistant to change — holding back shutdown
Accelerated retirement plan — 6 months
Months 1–2
Analysis
Identify what 1,200 users still access
Most common: old documents, legacy forms
Survey remaining users — what do you actually need?
Map content to SharePoint or archive destination
Months 3–4
Migration
Move active documents to SharePoint
Recreate 5 critical forms in Power Apps
Archive all remaining content
Validate nothing critical is left behind
Month 5
Communication
Announce shutdown date — 60-day notice
Provide SharePoint training to all users
Offer 1-on-1 support for holdouts
Escalate non-compliant departments
Month 6
Decommission
Set portal to read-only
Final data export and audit
Shutdown servers
Cancel licenses and hosting contracts
6-month delivery timeline
Analysis
Mo 1
Mo 2
Migration
Mo 3
Mo 4
Communication
Mo 5
Decommission
Mo 6
Outcome
$120K
Annual savings — full maintenance eliminated
4 months
Payback on $40K migration investment
6 months
Full decommission from start to shutdown
End-of-Life Stage
Characteristics — zombie application signals
Official end-of-support announced
Vendor has publicly communicated a support end date. The application is running on borrowed time — every month of inaction increases security and compliance exposure.
Zero or minimal users
Login analytics show no meaningful activity. The application is consuming licenses, infrastructure, and maintenance budget for a user base that has effectively abandoned it.
“Zombie apps” — should be retired but aren’t
The application has no active business purpose but continues to exist through inertia, fear, or organizational paralysis. Retirement is clearly correct but no one has pulled the trigger.
Rationalization strategy — immediate retirement, no debate
Zombie apps do not warrant a full options analysis. The question is not whether to retire them — it is how quickly and cleanly to do it.
Why apps become zombies — 5 common reasons
01
No one knows if it’s still used
No usage monitoring in place — fear of turning something off that might be in use somewhere
02
Fear of breaking something
Unknown dependencies — the app might be feeding a report, a batch job, or a downstream system
03
“Might need it someday”
Vague future need cited as justification — no specific scenario, no timeline, no business owner
04
No budget or time allocated
Decommissioning has a cost and effort — without a funded project it simply never gets prioritized
05
Politics — someone’s pet project
The app was championed by a senior stakeholder. Retiring it is perceived as a political statement, not a technical decision
Cleanup process — 5 steps · 6 months · 80 apps
150
Apps flagged by automated scan
→
80
Confirmed zombies after human review
→
80
Apps retired in 6 months
Step 1
Identify
Automated discovery — flag candidates
No logins in 90+ days
No code changes in 2+ years
No support tickets in 1+ year
No active scheduled jobs
150 apps flagged as candidates
Step 2
Validate
Human review — confirm true zombies
Check with business owners
Review all scheduled jobs
Identify data retention requirements
Check downstream dependencies
80 apps confirmed — 70 reprieved with legitimate use cases
Step 3
Data
Data handling — archive, migrate, or delete
Archive data required for compliance
Migrate critical data to active systems
Delete genuinely redundant data
Document retention decisions
Data classified — archive, migrate, or purge per compliance policy
Step 4
Decommission
Controlled shutdown — turn off, wait, delete
Turn off app — monitor for complaints
Wait 30 days — zero issues = proceed
Delete from production environment
Cancel licenses and hosting contracts
Reclaim infrastructure — 200 VMs freed
30-day monitoring window eliminates risk of premature deletion
Step 5
Document
Close the loop — update records and learn
Update CMDB — remove retired apps
Document what was retired and why
Archive code repository — do not delete
Record lessons learned for future programs
CMDB accurate — full audit trail maintained
6-month delivery timeline — 80 apps
Step 1 — Identify
Mo 1
Step 2 — Validate
Mo 1
Mo 2
Step 3 — Data
Mo 2
Mo 3
Step 4 — Decommission
Mo 3
Mo 4
Mo 5
Step 5 — Document
Mo 5
Mo 6
Results — 80 apps retired in 6 months
$1.2M
Annual savings — licenses, hosting, maintenance
200 VMs
Infrastructure reclaimed and redeployed
80 apps
Retired in 6 months — zero production incidents
RATIONALIZATION BY BUSINESS VALUE
The recommended strategy for rationalization for applications based on business value is given below
Invest / Retain — high value, healthy
Refactor / Replace — high value, unhealthy
Optimize / Tolerate — low value, healthy
Retire — low value, unhealthy
Business Value ↑
Low
High
⚡
Refactor / Replace
Fix or swap it
High business value, poor technical health. Too important to abandon — must be modernised.
Re-platform
Re-architect
SaaS swap
⭐
Invest / Retain
Protect and grow
High business value, strong technical health. Strategic assets — keep investing and extend.
Enhance
Scale
Extend features
🗑
Retire
Decommission it
Low business value, poor technical health. No justification to maintain. Sunset and free the budget.
Decommission
Migrate data
Archive
⚙
Optimize / Tolerate
Reduce cost, keep running
Low business value but technically sound. Reduce spend, limit investment, watch for consolidation.
Consolidate
Outsource
Cost-cut
Technical Health →
Refactor / Replace
High value · Low technical health
Business-critical but technically failing — this quadrant demands urgent action.
Signs you’re here
High user adoption but frequent outages
Drives revenue or core operations
Built on EOL platforms or legacy stack
Hard to find engineers who maintain it
Security debt accumulating
Strategies to consider
Re-platform to cloud-native services
Replace with modern SaaS equivalent
Refactor critical modules, sunset rest
Strangler fig migration pattern
API-wrap legacy, migrate consumers
Decision criteria
Cost to re-platform vs replace (TCO)
SaaS parity with current functionality
Data migration feasibility
Integration dependencies count
Business disruption tolerance
Real-world example
E-commerce platform on legacy .NET 3.5
Core revenue engine driving $5M/yr — but built on .NET 3.5, SQL Server 2008, and on-premise servers. Outages every quarter. Decision: re-platform to Azure App Service + SQL Managed Instance. 14-month project.
Outcome: +$10M/yr capacity unlocked, 99.9% uptime, 40% infra cost reduction
Invest / Retain
High value · High technical health
Your strategic crown jewels — protect them, fund them, and grow them deliberately.
Signs you’re here
Drives revenue, compliance or strategy
Modern stack, active development
High user adoption and satisfaction
Strong team ownership and roadmap
Low technical debt, good test coverage
Strategies to consider
Accelerate feature development
Expand user base and integrations
Invest in scalability and resilience
Use as internal platform for others
Protect against technical drift
Decision criteria
Strategic alignment score
Business capability coverage
Competitive differentiation value
User growth trajectory
Technical health trend (improving?)
Real-world example
Customer identity platform on Azure AD B2C
Cloud-native, SOC 2 compliant, 2M active users. Fully managed, 99.99% SLA. Supports all product lines. Decision: retain and extend with new MFA flows and partner federation. Replace legacy AD FS instances pointing to it.
Outcome: $80K/yr saved retiring AD FS servers, onboarded 3 new enterprise clients
Retire
Low value · Low technical health
The clearest rationalization decision — decommission, migrate data, reclaim resources.
Signs you’re here
Fewer than 5% of users active monthly
Business process it supports is obsolete
Functionality covered by another app
High support cost, low business impact
No owner willing to fund it
Strategies to consider
Set a decommission date and communicate
Migrate data to a system of record
Archive for compliance if required
Redirect users to replacement
Reclaim servers, licences, budget
Decision criteria
Monthly active user count (threshold: <5%)
Data retention regulatory requirements
Integration dependency count
Cost to decommission vs maintain
Stakeholder resistance level
Real-world example
Legacy intranet portal on SharePoint 2010
Once had 8,000 users. Down to 1,200 (15% of peak). Superseded by Teams and a modern intranet on SharePoint Online. On-premise servers still running at $120K/yr. Decision: 6-month decommission plan, migrate 4 remaining active sites.
Outcome: $120K/yr saved, 4 servers freed, 6-month timeline completed on schedule
Optimize / Tolerate
Low value · High technical health
Keep it running, reduce what you spend on it, and watch for consolidation opportunities.
Signs you’re here
Stable, works fine, rarely touched
Small but loyal user group
Supports a niche business process
Low innovation demand from business
Duplicate of functionality in another app
Strategies to consider
Freeze new feature development
Move to managed service or outsource
Consolidate with overlapping app
Right-size licences and infrastructure
Set review checkpoint in 12–18 months
Decision criteria
Overlap with apps in Invest quadrant
Cost per active user per month
Consolidation feasibility score
Support burden (tickets per month)
Licence right-sizing opportunity
Real-world example
Room booking add-in for Outlook
Works perfectly. 200 users. Azure-hosted, zero incidents. But Microsoft 365 now includes room booking natively via Places. Decision: freeze investment, migrate users to native M365 feature over 6 months, decommission add-in.
Outcome: $40K/yr licence cost eliminated, zero feature development required
DECISION FRAMEWORK & PRIORITIZATION
Rationalization Decision Matrix
| Criteria | Retire | Replace | Consolidate | Refactor | Retain |
| Business Value | None/Low | Low-Medium | Medium | High | High |
| Technical Health | Any | Poor | Any | Poor | Good |
| Usage | <10% | >50% | Varies | >80% | >80% |
| Alternatives Available | N/A | Yes (SaaS) | Yes (overlap) | No | No |
| Strategic Importance | No | No | No | Yes | Yes |
| Cost to Maintain | High | High | High | High | Low |
| Migration Effort | Low | Medium | Medium | Very High | N/A |
Prioritization Framework – An example of how to prioritize the applications is given below
Business impact
Measures the value delivered by rationalizing this application. Score higher when the action frees significant budget, improves productivity for many users, protects revenue, or advances a strategic goal. Score lower for niche tools with limited reach.
Effort level
Reflects the cost and time required to execute the rationalization. Low effort actions — quick retirements or simple license cuts — earn a 2× multiplier. High effort transformations like full re-platforms carry a 0.5× penalty, ensuring only high-impact changes justify the investment.
Risk reduction
Captures the urgency added by leaving an application in its current state. Score higher when the application carries active security vulnerabilities, compliance gaps, unpatched end-of-life dependencies, or significant operational fragility that increases with every month of inaction.
Priority scoring formula
16
Priority score
=
7
Business impact
×
2.0×
Effort multiplier
+
2
Risk reduction
Score your own application
Interactive scorer
Business impact 7 / 10
Cost savings · user productivity · revenue impact · strategic value
Effort level 2.0×
How much time and cost to implement this rationalization
2.0×
Low — <3 mo, <$100K
1.0×
Medium — 3–9 mo, <$500K
0.5×
High — >9 mo, >$500K
Risk reduction 2 / 5
Security · compliance · operational · technical debt
Example applications
The Summary
01
Business Case
02
Blueprint Framework
03
Roadmap
04
Financial Model
05
Risk Mitigation
06
Org & KPIs
07
Success Factors
The strategic imperative
Why Rationalize Now?
Three compounding forces are creating an unsustainable gap between what IT costs and what the business needs it to deliver.
3–5%
IT budget growth per year
15–20%
Business demand growth
30–40%
Apps on unsupported platforms
$4M
Average security breach cost
Financial pressure
IT budget growing 3–5% annually while business demand grows 15–20% — an unsustainable gap that compounds every year.
- 500 apps at $25M today
- 580 apps at $28M in Year 3 if unchanged
- $16M/yr freed with full rationalization
Technical debt crisis
Aging, unsupported apps create risk across security, compliance, scalability and talent retention — growing every quarter.
- Security breach risk: $4M avg cost
- Compliance fines: $10M–$50M exposure
- 60% of apps use obsolete technology
- 12–18 months to launch new capabilities
Strategic enablement
Rationalization is the prerequisite for every digital transformation initiative your business is trying to execute.
- Cloud migration requires a clean portfolio
- AI/ML needs modern architecture
- M&A integration demands consolidation
- Customer experience held back by legacy
Without rationalization
Year 1: 500 apps · $25M · status quo
Year 3: 580 apps · $28M · budget crisis
Security incidents: 40/yr → rising
Time-to-market: 12 months · stagnant
VS
With rationalization
Year 1: Begin programme · $2–8M savings
Year 3: 200 apps · $10M · $15M saved/yr
Security incidents: 5/yr · -88%
Time-to-market: 4 months · -67%
The methodology
Blueprint Framework
Eight assessment dimensions converge to classify every application and assign the right rationalization action from a portfolio of seven strategies.
Eight assessment dimensions
01
Application type
Custom-built · COTS · SaaS
02
Technology layer
UI · Logic · Data · Integration
03
Business function
Finance · HR · Sales · IT Ops
04
Technical characteristics
EOL · Unsupported · High TCO
05
Lifecycle stage
Growth · Maturity · Decline · EOL
06
Business value
Strategic · Utility · Tactical · Obsolete
07
Technical health
Modern · Adequate · Poor · Critical
08
Deployment model
On-prem · Private · Public · SaaS
Rationalization actions portfolio
Retire
20–30%
100% saved
1–3 mo
Replace
25–35%
50–80% TCO
3–12 mo
Consolidate
15–25%
50–80%
6–18 mo
Rehost
10–15%
20–40%
2–6 mo
Replatform
5–10%
30–50%
4–9 mo
Refactor
5–10%
40–80%
12–24 mo
Retain
5–15%
10–20%
Ongoing
Three-phase transformation
Implementation Roadmap
36 months, three distinct phases — each one self-funding the next from the savings it generates.
Baseline
500
$25M / yr
—
Year 1
375
$22M / yr
$3M saved
Year 2
275
$15M / yr
$10M saved
Year 3
200
$10M / yr
$15M saved
Mo 1–6Discovery & Quick Wins
Complete portfolio inventory
Retire zombie apps — zero usage
Shadow IT discovery & elimination
Top 5 vendor contract renegotiations
Governance model established
$1M
Investment
$2–8M
Annual savings
50+
Apps retired
30%
Portfolio cut
Mo 7–18Strategic Consolidation
Multi-CRM consolidation → 1 platform
ERP consolidation across all BUs
400 DB instances → 80
200 SaaS vendors → 50
Legacy datacenter exit
$5M
Investment
$15M
Cumul. savings
150+
Apps retired
70%
DC footprint cut
Mo 19–36Modernization
Legacy app refactoring — strategic
API-first architecture
Microservices adoption
Low-code platform rollout
AI/ML platform enablement
$8M
Investment
$25M
Cumul. savings
200
Target apps
60%
Total portfolio cut
The numbers
Financial Model
Total investment of $14M over 3 years generates $15M in annual savings — programme pays for itself within 14 months.
Phase 1 investment ($500K–$1M)
Assessment tools & consultants$200K
Programme team (2 FTEs)$150K
Quick wins execution$150K
Governance & change mgmt$100K
Phase 1 savings ($2M–$8M/yr)
Decommissioned app licenses & hosting$1.5M
Shadow IT elimination$800K
Vendor renegotiation$500K
Operational efficiency$200K
Phase 2 investment ($3M–$8M)
SaaS migrations & data conversion$2M
Cloud migration costs$1.5M
Integration development$1M
Programme team (5 FTEs)$500K
Cost avoidance (not in ROI)
Security breach avoided$4M–$10M
Compliance fine avoidance$5M–$50M
Customer churn prevention$2M–$10M
M&A integration savings$3M–$8M
Risk management
Risk Mitigation
Eight programme risks assessed and actively managed — with six de-risking strategies that protect the programme from the most common failure modes.
Business disruptionHigh · Med prob
Mitigation
Phased approach with extensive testing, rollback plans maintained until stability proven
User resistanceMed · High prob
Mitigation
Change management programme, training, executive sponsorship visible from Day 1
Data lossCritical · Low prob
Mitigation
Rigorous data migration processes, validation, verified backups before every decommission
Cost overrunsHigh · Med prob
Mitigation
Stage-gate funding model, agile methodology, contingency budget and monthly burn review
Savings not realisedHigh · Med prob
Mitigation
Independent validation of every savings claim, strict business case discipline at all times
Timeline delaysMed · High prob
Mitigation
Experienced programme team, realistic planning with built-in buffer, agile iteration
Vendor lock-inMed · Med prob
Mitigation
Multi-vendor strategy, API-first architecture, contractual exit clauses in all agreements
Technical failuresHigh · Low prob
Mitigation
Mandatory proof-of-concepts and pilot programmes before any full rollout
De-risking strategies
Prove value first
Phase 1 delivers $3M+ to self-fund later phases — programme pays for itself from savings
Business-led decisions
Business units own all rationalization decisions — IT enables, business decides every action
Incremental delivery
No big-bang transformation — continuous delivery, fail fast and learn from every sprint
Reversible actions
Maintain rollback options for 30 days after every decommission until full stability confirmed
Independent validation
Third-party audits of all savings claims — no self-reported numbers accepted at steering level
Executive governance
Steering committee monthly, fast approvals (days not months), clear decision rights at every level
Readiness & measurement
Organizational Readiness & KPIs
Three governance layers drive execution. Six capability gaps must close. Progress tracked across portfolio health, financial, and business impact metrics.
Executive Steering — Monthly
CIO · CFO · BU Leaders · CISO
- Approve rationalization decisions
- Remove organisational roadblocks
- Validate savings independently
- Align programme with business strategy
Programme Office — Daily
Director · Architects · Analysts · Leads
- Execute rationalization roadmap
- Manage vendors and SIs
- Track benefits realisation
- Report to steering committee
Domain Working Groups — Weekly
Finance · HR · Sales · IT · Security
- Assess domain applications
- Recommend rationalization actions
- Execute migrations within domain
- Validate outcomes and savings
Portfolio health
500
200
Total applications
Monthly
30%
0%
Apps on EOL technology
Quarterly
15%
60%
SaaS adoption rate
Quarterly
Financial metrics
$25M
$10M
Annual IT spend
Monthly
75%
35%
Maintenance % of budget
Quarterly
$3M
$200K
License waste (shelfware)
Quarterly
Business impact
12 mo
4 mo
Time-to-market
Per project
40/yr
5/yr
Security incidents
Monthly
180
50
Vendor count
Quarterly
What makes it work
Critical Success Factors
Ten factors separate programmes that deliver lasting transformation from those that stall in Year 2. The top four are non-negotiable.
01
Executive sponsorship
CIO and CFO alignment is non-negotiable. Board-level commitment sustained for the full 3-year journey — programmes die when executive attention shifts after Year 1.
02
Business-led decisions
IT proposes, business decides. Business units own every outcome. No ivory-tower architecture — no decision survives without the owning business unit’s buy-in.
03
Financial discipline
Every action requires a rigorous business case with independent savings validation. Reinvest Phase 1 savings to fund Phase 2 — self-financing by Month 7.
04
Quick wins in first 90 days
Deliver visible value within 90 days. Early savings build credibility, maintain executive attention, and fund later phases. The programme lives or dies on its first quarter.
05
Change management
User training, communication strategy, and proactive resistance handling from Day 1. Most rationalization failures are people failures, not technical ones.
06
Vendor partnerships
Leverage cloud provider migration incentives, engage SIs for capability gaps, negotiate win-win agreements. Vendors are transformation partners.
07
Data-driven portfolio view
Automated discovery tools, usage analytics, and a real-time dashboard. Gut-feel rationalization produces gut-feel results — every decision needs a data foundation.
08
Agile execution
Iterative delivery, fast learning cycles, adaptation based on real results. No multi-year waterfall plans — deliver value every sprint and reprioritize based on what you learn.
09
Governance without bureaucracy
Clear decision rights, approvals in days not months, empowered teams. Heavy governance is the leading cause of rationalization programmes stalling in Year 2.
10
Celebrate successes publicly
Recognise teams, share wins broadly, maintain energy across 3 years. Rationalization is a marathon — momentum must be actively managed, not assumed.
The time to act is now.
$1M for Phase 1 · self-funds remaining phases · $15M/yr in Year 3