How Redress Compliance helped Pfizer rationalise its Oracle application support portfolio — eliminating shelfware, restructuring licence entitlements, and negotiating reduced support fees without compromising compliance or operational continuity.
📖 This case study is part of our comprehensive Oracle Third-Party Support Guide — covering support cost reduction strategies, third-party alternatives, legal considerations, and negotiation tactics for enterprise IT leaders.
Pfizer, one of the world's largest pharmaceutical companies, faced a challenge common among large, complex enterprises: years of Oracle application licence accumulation had created a substantial layer of annual support costs attached to products that were no longer actively used. Oracle's support model — charging approximately 22% of net licence fees annually with compounding annual uplifts — meant that legacy applications, retired modules, and over-provisioned entitlements were quietly draining millions from the IT budget each year.
Pfizer engaged Redress Compliance to conduct a comprehensive Oracle application support review. Over a four-month engagement, our team mapped every Oracle application licence across Pfizer's global estate, identified 47 licences attached to products that were no longer required or had been superseded by alternative platforms, and developed a structured reduction and negotiation plan. The result was a $2.1 million reduction in Oracle application support spend over three years — achieved entirely through rationalisation and negotiation, without any disruption to production systems or compliance exposure.
Comprehensive mapping of 200+ Oracle application licences across Pfizer's global operations, including EBS, Middleware, and database options.
47 unused or redundant Oracle licences identified and terminated, removing $700K+ in annual support obligations.
Remaining support contracts renegotiated with Oracle to remove annual uplift indexation and secure volume-based discounts.
Every termination backed by documented usage analysis ensuring no active deployment relied on discontinued entitlements.
Pfizer's relationship with Oracle spans more than two decades. As one of the world's leading pharmaceutical and biotechnology companies — with operations in over 60 countries, more than 80,000 employees, and annual revenues exceeding $50 billion — Pfizer's IT infrastructure is correspondingly vast and complex. Oracle technology underpins several mission-critical business systems across the enterprise.
Oracle E-Business Suite (EBS) has historically served as the backbone for Pfizer's financial management, procurement, and supply chain operations. Multiple EBS instances run across regions, supporting general ledger, accounts payable, purchasing, and inventory management for a global manufacturing and distribution network. Oracle Database Enterprise Edition powers the underlying data layer for these applications and numerous other business intelligence, clinical trial, and regulatory reporting systems. Oracle Middleware — including WebLogic Server, SOA Suite, and Oracle Integration Cloud adapters — connects internal applications and supports integration with external partners, contract research organisations, and regulatory bodies.
Over the years, as Pfizer grew through acquisitions (including Wyeth, Hospira, and Array BioPharma), the Oracle estate expanded through inherited licences, duplicate entitlements, and products acquired alongside business units that were subsequently restructured or divested. The result was an Oracle application portfolio that had grown organically — and expensively — without periodic rationalisation.
60+ countries, 80,000+ employees, $50B+ revenue. Oracle EBS, Database EE, and Middleware deployed globally across manufacturing, R&D, and corporate functions.
Multiple M&A transactions brought inherited Oracle licences. Over 200 distinct Oracle application and technology entitlements on the books.
Oracle annual support fees exceeding $6M/yr across applications alone, with ~4% annual uplifts compounding the cost base year after year.
Pharmaceutical companies operate under uniquely demanding regulatory and compliance frameworks. Every IT system that touches clinical data, manufacturing records, or financial reporting is subject to validation requirements from bodies including the FDA, EMA, and GxP standards. This creates a natural conservatism around IT change — systems are often retained in production long after they have been technically superseded, because the cost and risk of decommissioning a validated environment can be substantial.
Oracle is well aware of this dynamic. In regulated industries, the practical barriers to dropping Oracle support are higher than in other sectors, because Oracle can argue that without ongoing support (and access to security patches), the validated status of production systems may be compromised. This gives Oracle implicit leverage at support renewal time — and it is precisely the kind of dynamic that requires independent, expert analysis to challenge effectively.
Pfizer's IT leadership recognised that while the company's core Oracle systems remained essential, the support bill had grown disproportionately to actual usage. A significant portion of the annual support spend was attached to Oracle application modules, database options, and middleware products that had either been replaced by alternative platforms, were no longer deployed in production, or had been inherited through acquisitions and never operationally adopted. Unlike a full third-party support transition — which would have been strategically complex for Pfizer's regulated environment — a targeted support rationalisation offered a lower-risk, high-impact path to cost reduction.
📌 Related Guide: For a full comparison of staying on Oracle support versus moving to third-party alternatives, read our Third-Party Support vs. Oracle Premier Support Guide.
While the concept of "stop paying for software you don't use" sounds straightforward, the reality at enterprise scale is significantly more complex. Pfizer faced five interconnected challenges that made Oracle support rationalisation a non-trivial exercise.
Like many large enterprises that have grown through acquisition, Pfizer did not have a single, authoritative inventory of all Oracle application licences and their associated support contracts. Licences had been procured over different contract vehicles — some through direct Oracle agreements, others through Oracle partners, and still others inherited via M&A transactions. Support line items were spread across multiple Oracle Customer Support Identifiers (CSIs), making it difficult to see the full picture. Without a consolidated view, it was impossible to determine which support payments were essential and which were funding unused entitlements.
Oracle's application ecosystem is deeply interconnected. An Oracle EBS module may depend on specific database options, middleware components, or integration products that are separately licensed and separately supported. Simply dropping support on what appears to be an unused product can inadvertently create a compliance gap — if that product is still invoked as a dependency by an active system. Pfizer's IT environment, with its multiple EBS instances, custom integrations, and legacy batch processes, required careful dependency analysis before any support termination could proceed.
Oracle's support policies include a punitive reinstatement clause: if you terminate support on a licence and later need to restore it, Oracle requires payment of all back support fees plus a reinstatement penalty (typically 150% of the annual support fee). This creates a powerful psychological deterrent against termination — procurement teams are understandably reluctant to drop support on anything they are not 100% certain is permanently unused. The reinstatement policy turns every support termination decision into a high-stakes judgement call, which is exactly how Oracle designed it.
In Pfizer's regulated environment, certain Oracle systems are validated under GxP standards. Dropping Oracle Premier Support on a validated system could be interpreted by auditors as a risk to the system's validated state — particularly if the system no longer receives security patches. Pfizer's quality and compliance teams needed assurance that any support termination would not affect validated environments or create regulatory audit findings. This required a granular, system-by-system assessment that went beyond simple licence usage data.
Oracle's sales and support teams are financially incentivised to maintain and grow support revenue. Support fees represent Oracle's most profitable revenue stream — approximately 22% of licence value annually, with near-zero marginal delivery cost and compounding annual uplifts. Any attempt to reduce this revenue is met with systematic resistance — ranging from subtle discouragement ("you'll lose access to critical security patches"), to fear-based messaging ("your environment could become non-compliant"), to bureaucratic obstacles (requiring sign-offs through multiple Oracle internal teams, imposing narrow cancellation windows, and routing reduction requests through account managers who are measured on revenue retention).
Pfizer had previously attempted ad-hoc support reductions without expert guidance. These efforts were stalled by Oracle's internal processes: requests were redirected, timelines slipped past cancellation deadlines, and the procurement team was left uncertain about which reductions were safe to pursue. The net result was inaction — and continued payment of support fees on unused software. A structured, independently-led approach was essential to break through these barriers and present Oracle with a reduction package that could not be easily deflected or delayed.
📌 Related Guide: For detailed strategies on reducing Oracle support costs across your entire portfolio, see our Oracle Cost Optimisation Playbook.
When Redress Compliance was engaged, we began by establishing the strategic framework for the optimisation effort. Rather than pursuing a blunt cost-cutting exercise, we designed a three-track approach that balanced savings with risk management and regulatory compliance.
Identify Oracle application licences with zero production deployment, no active users, and no dependency linkages to active systems. These represent pure cost with zero business value — the safest and highest-ROI reductions.
Where Pfizer holds more licences than current deployment requires — due to legacy sizing, M&A accumulation, or infrastructure consolidation — reduce the licence count to match actual usage and terminate support on the surplus.
For licences that remain essential, negotiate with Oracle to remove annual support uplift indexation, secure a reduced support rate, and consolidate multiple CSIs into a single, manageable agreement structure.
This three-track model ensured that every category of savings opportunity was addressed — from the straightforward (unused licences) to the more nuanced (over-provisioning and contractual terms). Critically, all three tracks were executed in parallel, allowing us to present Oracle with a comprehensive reduction package rather than piecemeal requests that Oracle could more easily deflect.
📌 Related Guide: For a detailed walkthrough of Oracle support cost reduction strategies, see our Oracle Support Renewal — Optimisation and Lower Costs guide.
Redress Compliance conducted a comprehensive discovery across Pfizer's global Oracle environment. We consolidated data from multiple Oracle CSIs, cross-referenced licence entitlements against Oracle's official records (obtained via Oracle's Licence Management Services portal), and reconciled these against Pfizer's internal deployment records, CMDB data, and application team feedback. The result was a unified inventory of over 200 Oracle application and technology licences, each tagged with its associated annual support cost, contract renewal date, and deployment status. For the first time, Pfizer's IT procurement team had a single, accurate view of their entire Oracle support obligation.
For each licence in the inventory, we performed a detailed usage and dependency assessment. This involved working directly with Pfizer's application teams, DBA teams, and middleware support engineers to confirm whether each product was actively deployed in production, actively used by business processes, or required as a dependency by other active systems. We used Oracle's own measurement scripts alongside Pfizer's monitoring tools to validate findings. This phase was critical — it converted qualitative assumptions ("we think we stopped using that") into documented, evidence-based conclusions that could withstand both internal governance review and any subsequent Oracle compliance inquiry.
Given Pfizer's regulated environment, every proposed support termination was reviewed against the company's GxP validation register. Any Oracle product supporting a validated system — regardless of how lightly used — was flagged for additional review by Pfizer's quality assurance team. In several cases, products that appeared unused from a technical standpoint were in fact retained to maintain the validated status of an upstream system. These were excluded from the termination list. This rigorous approach ensured that no support reduction could later be challenged on regulatory grounds — a concern that had previously paralysed Pfizer's internal attempts to rationalise Oracle costs.
Redress assembled a comprehensive support reduction package covering all three tracks. Track 1 identified 47 Oracle licences for outright support termination — including legacy EBS modules that had been replaced by SAP, Oracle Database options that had never been enabled, and middleware products inherited from the Wyeth acquisition that were never deployed in Pfizer's production environment. Track 2 identified 12 additional licences where the entitlement quantity exceeded current deployment by 40% or more, allowing partial support reduction. Track 3 compiled the negotiation brief for the remaining active support portfolio, including benchmarking data on support rates from comparable pharmaceutical and life sciences enterprises.
Redress led the negotiation process with Oracle's support renewal team. The comprehensive, evidence-based reduction package made it significantly more difficult for Oracle to employ delaying tactics. Every termination was backed by documented non-usage, every right-sizing was supported by measurement data, and every negotiation position was reinforced by industry benchmarking from comparable pharmaceutical and life sciences enterprises.
Oracle initially resisted the scope of reductions, arguing that certain products might be needed for future projects and that dropping support on database options could create "security vulnerabilities." Redress countered each objection with evidence: future project roadmaps confirmed no planned Oracle expansion in the affected areas, and the security argument was defused by demonstrating that the specific database options in question had never been enabled — meaning there was no attack surface to protect. Pfizer's position — prepared by Redress — was clear: support costs must reflect current deployment reality, not speculative future demand. Oracle's internal approvals took several weeks, but the reduction package was ultimately accepted in full, with all 47 terminations processed and the renegotiated support terms confirmed in writing.
The following table illustrates the financial impact across each track of the optimisation effort.
| Optimisation Track | Licences Affected | Annual Support Removed | 3-Year Saving |
|---|---|---|---|
| Track 1: Shelfware Elimination | 47 licences terminated | $480,000/yr | $1,440,000 |
| Track 2: Entitlement Right-Sizing | 12 licences reduced | $95,000/yr | $285,000 |
| Track 3: Support Renegotiation | Remaining portfolio | $125,000/yr | $375,000 |
| Total | 59 licence actions | $700,000/yr | $2,100,000 |
The largest savings category — shelfware elimination — accounted for nearly 70% of the total reduction. This is typical of large enterprises that have grown through acquisition: inherited licences are often "invisible" to current management because they were never actively procured by the current team. They simply appear as line items on Oracle's annual support invoice, auto-renewed year after year. The second most impactful category was support renegotiation — by removing the annual support uplift indexation on the remaining portfolio, Pfizer locked in a flat support rate for three years, avoiding an estimated $375,000 in compounding cost increases.
Critically, these savings are recurring. Unlike a one-off licence negotiation discount, support reductions compound over time — every dollar removed from the annual support base is a dollar saved every year in perpetuity (or until usage changes). The $700,000 annual reduction will continue to deliver savings well beyond the initial three-year measurement window.
The final, audited savings total across all three tracks was $2.1 million over three years. This represented a 34% reduction in Pfizer's total Oracle application support spend — achieved without any operational disruption, compliance incident, or loss of business functionality. The savings were independently verified against Oracle's invoicing to ensure accuracy and were reported to Pfizer's CFO as a completed cost optimisation initiative.
The shelfware elimination exercise removed 47 Oracle licences from Pfizer's support obligations. These included legacy EBS modules from the Wyeth integration, Oracle Database options (such as Advanced Compression and Spatial) that had been licensed but never enabled, and middleware products that had been replaced by alternative integration platforms. Each termination was fully documented, with evidence of non-usage and non-dependency, providing Pfizer with a permanent audit defence record.
For the first time, Pfizer's IT procurement and SAM teams had a single, authoritative view of every Oracle licence, its support status, deployment footprint, and business owner. This inventory became the foundation for ongoing Oracle licence governance — enabling Pfizer to proactively manage future support renewals rather than passively accepting Oracle's default invoicing. The inventory is now maintained annually as part of Pfizer's software asset management programme.
Every support termination was validated against Pfizer's GxP register. No validated system was affected, and no regulatory audit finding resulted from the optimisation exercise. Pfizer's quality assurance team signed off on the final reduction package before execution, and the documentation trail was archived for future regulatory inspection. This outcome was critical — in the pharmaceutical industry, any cost savings that introduces regulatory risk is a false economy.
The engagement fundamentally changed how Pfizer engages with Oracle commercially. By demonstrating — with data — that Oracle's support revenue from Pfizer was partially based on unused entitlements, the procurement team established a new baseline for future interactions. Oracle's account team now knows that Pfizer has independent advisory support, a detailed understanding of its licence position, and the willingness to act on optimisation opportunities. This shifts the negotiation dynamic for every future Oracle interaction.
This engagement reinforced several principles that apply to any large enterprise seeking to optimise Oracle application support costs.
Across our engagement history, we have never encountered a large enterprise that did not have significant Oracle shelfware. The average discovery rate is between 15% and 30% of the total Oracle licence portfolio. The shelfware problem is particularly acute in companies that have grown through M&A, where inherited licences are rarely rationalised post-integration. A comprehensive, independent review will almost always uncover savings that pay for the engagement many times over.
The fear of Oracle's reinstatement penalty prevents many organisations from acting on support reductions. In practice, if the usage analysis is thorough and the termination decisions are evidence-based, the probability of needing to reinstate is extremely low. In this engagement, zero reinstatements were required — because every termination was validated against actual deployment and future project roadmaps. The key is certainty: if you are certain a product is permanently unused, the reinstatement risk is effectively zero.
Regulatory compliance is often cited as a reason not to touch Oracle support contracts. While the concern is legitimate, it is also frequently overstated. With proper validation mapping and quality team involvement, regulated enterprises can safely terminate support on non-production, non-validated Oracle products. The key is involving the quality and compliance function early — not as a blocker, but as a validation partner. In Pfizer's case, the quality team's sign-off gave the entire initiative credibility and removed the regulatory veto that had stalled previous attempts.
Oracle's internal teams are skilled at deflecting support reduction requests when they arrive one at a time. A single product termination request can be stalled through bureaucratic process for months. By assembling a comprehensive reduction package — covering shelfware, right-sizing, and negotiation terms in a single, structured proposal — Redress ensured that Oracle could not easily divide and delay. The package approach also strengthens the client's commercial position: it demonstrates systematic, expert-led analysis rather than opportunistic cost-cutting.
Unlike a one-off licence discount, support cost reductions deliver value every year. A $700,000 annual reduction in Year 1 saves $700,000 again in Year 2, Year 3, and every subsequent year. If Oracle's standard ~4% annual uplift had remained in place, the compounding effect means the savings grow over time. This makes Oracle support optimisation one of the highest-ROI activities available to enterprise IT procurement teams — particularly when the effort is relatively contained (4 months in this case) compared to the multi-year financial return.
Oracle support spend is the single largest hidden cost centre in most enterprise IT budgets. Every $1 removed from the annual support base saves $1 every year thereafter — compounding as Oracle's standard uplifts are avoided. For a company like Pfizer, the three-year $2.1 million saving is really just the beginning.
Pfizer's engagement is part of a broader pattern of Oracle support optimisation outcomes we have delivered across industries. Here are three comparable results.
Situation: Costco's Oracle estate included dozens of licences accumulated over 15+ years of incremental procurement, many attached to systems that had been decommissioned or migrated to alternative platforms.
Actions: Redress conducted a full usage analysis, mapped all dependencies, and assembled a termination package covering 63 unused licence entitlements across EBS, Database options, and Middleware.
Result: $4.2M in savings through support termination on confirmed shelfware.
Takeaway: Retail enterprises with long Oracle histories almost always have significant shelfware. The savings potential scales directly with the size and age of the Oracle estate. Read the full Costco case study.
Situation: LVMH's decentralised brand structure meant Oracle licences had been procured independently by individual maisons, creating substantial overlap and unused entitlements across the group.
Actions: Redress worked across multiple LVMH brands to consolidate the Oracle licence view, identify cross-brand redundancies, and execute a group-wide support reduction programme.
Result: €10.5M in savings over three years through coordinated shelfware elimination and support renegotiation.
Takeaway: Decentralised organisations with autonomous business units face the highest risk of Oracle licence duplication. Group-level consolidation unlocks the largest savings. Read the full LVMH case study.
Situation: Roche's Oracle Siebel CRM system was stable on a locked version with no planned upgrades. Continuing Oracle Premier Support delivered diminishing value while costs increased annually.
Actions: Redress evaluated third-party support options, assessed the compliance implications for Roche's regulated environment, and managed the transition to a specialist third-party Siebel support provider.
Result: $1.5M in savings through a 50% reduction in Siebel support costs with improved response times.
Takeaway: Stable, version-locked Oracle applications are ideal candidates for third-party support — particularly when upgrade plans have been permanently shelved. Read the full Roche case study.
We had suspected for years that we were paying Oracle for software we weren't using, but the complexity of our environment and the fear of getting it wrong kept us from acting. Redress Compliance gave us the data, the methodology, and the confidence to execute. The $2.1 million saving was significant, but what really changed was how we manage Oracle commercially. We now have visibility and control that we never had before. This should have been done years ago.
No. Oracle cannot force you to maintain support on any licence. You have the contractual right to terminate support at each renewal anniversary. However, Oracle may make the process bureaucratically difficult, require specific notice periods, or attempt to bundle support terminations with other commercial discussions. An independent advisor can navigate these obstacles efficiently.
Oracle's reinstatement policy requires payment of all back support fees from the date of termination plus a reinstatement penalty (typically 150% of the annual fee). This is why thorough usage and dependency analysis is essential before termination. When done properly — as in Pfizer's case — the risk of needing reinstatement is effectively zero.
For a large enterprise like Pfizer with 200+ Oracle licences, a typical engagement runs 3–5 months from kickoff to Oracle execution. Smaller estates can be completed in 6–8 weeks. The timeline depends primarily on internal stakeholder availability and the complexity of the dependency mapping exercise.
Absolutely. In fact, support rationalisation should be the first step before evaluating third-party support. Eliminating shelfware and right-sizing entitlements reduces the scope (and cost) of any subsequent third-party support transition. It also provides the detailed licence and usage data that third-party support providers need for accurate quoting.
No. Oracle perpetual licences remain valid regardless of whether support is active. You can continue to use the software indefinitely — you simply lose access to new patches, updates, and Oracle's support desk. For stable, version-locked systems, this may be a perfectly acceptable trade-off, particularly if third-party support is engaged as an alternative.
Most enterprises are paying Oracle for software they no longer use. A targeted support review by Redress Compliance can identify and execute savings within weeks — with zero risk to production systems or compliance.