Pfizer. Two point one million cut from Oracle application spend.

Pfizer cut two point one million dollars from Oracle application spend over three years through a license utilization assessment, support optimization, and renewal discipline.

Where was Pfizer's Oracle application spend going?

A material share of the application spend covered users and modules that activity data could not justify. The E Business Suite estate had been licensed for organizational peaks and project ambitions, and the annual support stream renewed all of it at roughly 22 percent of net license fees.

Application spend decays differently from infrastructure spend. Nobody decommissions a module; people simply stop using it, and the support stream keeps billing as if they had not.

• Driver one: user populations licensed at historical peaks.
• Driver two: modules purchased at implementation and never deployed.
• Driver three: support renewing by inertia across all of it.

What did the license utilization assessment find?

The assessment matched every licensed module and user count against measured activity and found consistent excess. Active users sat well below licensed counts, and several licensed modules showed no production activity at all.

How do you measure real application usage defensibly?

From system activity, not from access lists. Login and transaction data over a trailing period establishes the active population in a form Oracle's own teams recognize, which is what makes the resized renewal defensible.

Which levers cut the application spend?

Three levers carried the program: resize user counts to measured activity, remove never deployed modules from the support base, and consolidate the remaining position into a single renewal negotiation with caps in writing.

1. Establish measured active users per module over a trailing period.
2. Match every licensed module to production evidence or flag it.
3. Terminate support on modules with no deployment, respecting license set rules.
4. Resize user based licenses at the renewal boundary.
5. Cap support increases on the surviving base in the renewal paper.

Why did the savings take three years to fully land?

Because support terminations and resizes execute at renewal boundaries, not mid term. The program sequenced each move to its earliest contractual window, which is why the full two point one million accumulated across three years rather than one.

What was the outcome for Pfizer?

The program banked two point one million dollars over three years while every active module and user kept full support. The saving recurred, because it came from removing scope rather than discounting it.

• Recurring relief: removed modules and resized counts stop billing every year.
• Zero disruption: no production function was touched at any point.
• Cleaner baseline: each subsequent renewal started from measured reality.

What should other application estates copy?

The measurement habit. An annual usage review against the licensed position costs days and protects millions, and it converts every renewal from a vendor anchored quote into a buyer anchored order.

Where the common advice on Oracle application renewals is wrong

The standard advice on Oracle application estates is to leave them alone, because EBS is stable, support is mandatory, and the renewal is a formality. We disagree. In roughly 25 to 35 Oracle engagements Fredrik Filipsson benchmarked in 2024 to 2025, licensed application users ran 20 to 40 percent above measured actives and unused modules carried support in half of the estates, which makes the formality renewal the most expensive meeting of the year. The buyer side move is to measure usage every year and treat the application renewal with the same rigor as a database negotiation.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Pull trailing activity data for every licensed Oracle application module.
2. Compare licensed user counts against measured actives per module.
3. Flag modules with no production activity for support review.
4. Map license sets before terminating any support line.
5. Schedule resizes and terminations to their renewal boundaries.
6. Stand up an annual usage review as a permanent control.

White Paper · Oracle

Cut Oracle Spend 30 to 50%: The 5 Year Playbook

The five year buyer side playbook that cuts Oracle spend across Database, Java, Apps, OCI, and support, and the math behind a 30 to 50 percent cut. Read it free.

Read the white paper

Frequently asked questions

How did Pfizer cut two point one million dollars from Oracle application spend?

By resizing user counts to measured activity, removing never deployed modules from the support base, and sequencing each move to its renewal boundary across three years.

Why do Oracle application estates accumulate excess spend?

Because modules are abandoned rather than decommissioned and user counts are licensed at peaks. Support renews the whole position annually unless measurement corrects it.

Can you reduce Oracle EBS user counts at renewal?

Yes. User based licenses resize at renewal boundaries when supported by measured activity data, which is why trailing usage measurement precedes every successful resize.

Does cutting application support risk production stability?

No, when scope is the lever. The program touched only modules with no deployment and users with no activity; everything running kept full support throughout.

How long does an application spend optimization take?

Plan for value landing across two to three renewal cycles. Terminations and resizes execute at contractual boundaries, so sequencing determines how fast the savings accumulate.