This case study describes how a public sector body brought its Oracle E-Business Suite costs under control after years of paying for entitlements it no longer used, all while operating within the rigid procurement rules that govern public spending. Details have been anonymised, but the approach reflects a repeatable method. The lesson is that public sector constraints, often seen as a weakness in negotiation, can become a source of discipline and leverage when used well.
This article sits within our case studies pillar and illustrates the principles behind our contract review service.
The Starting Position
The organisation ran Oracle E-Business Suite across finance, procurement, and human resources, supporting several thousand users. Its support and licence costs had crept up year after year, and the internal team suspected it was paying for far more than it used, but it lacked a clear picture of its own entitlement position. Public sector procurement rules added complexity, requiring transparent process, documented justification, and value for money that could withstand audit and public scrutiny.
The first realisation was that the organisation did not actually know what it was entitled to, what it had deployed, or where the two diverged. Without that baseline, every renewal was negotiated in the dark, and Oracle held the information advantage. Establishing the entitlement position was the necessary first step, the same discipline we describe in our EBS user licence counting article.
Building the Entitlement Baseline
The team conducted a thorough review of every EBS module licensed, every user counted, and every component actually in use. The exercise revealed substantial shelfware: modules that had been licensed years earlier for projects that never completed, user counts that exceeded actual headcount, and components that duplicated functionality the organisation met elsewhere. The gap between what was paid for and what was used was significant.
The entitlement review found that nearly a quarter of the licensed modules and a meaningful share of the user count were no longer needed. Identifying the shelfware precisely, with evidence, turned a vague suspicion into a documented negotiating position.
The baseline was documented to a standard that would satisfy both Oracle and the organisation's own auditors, which mattered because public sector decisions must be defensible. With the shelfware identified and the genuine requirement established, the organisation could enter the renewal knowing exactly what it needed and what it could drop, drawing on the analysis we describe in our E-Business Suite product guidance.
Negotiating Within Procurement Rules
Public sector procurement rules constrain how negotiations can be run, but they also provide structure that benefits the buyer. The organisation used its formal procurement process to require Oracle to justify its pricing transparently, to document the value for money case, and to compete its proposal against the option of reducing scope. The rules that Oracle reps sometimes treat as obstacles became a framework that forced rigour and transparency into the deal.
The organisation also benefited from the credibility of its position. Because every claim was documented and every decision defensible, Oracle could not dismiss the shelfware findings or pressure the team into accepting the existing scope. The discipline of public sector governance, applied to the Oracle relationship, produced exactly the kind of evidenced, aligned negotiating stance we recommend in our procurement stakeholder map article.
The Outcome
The organisation renegotiated its EBS agreement to remove the identified shelfware, align the user count with actual headcount, and secure a support cost that reflected its genuine footprint rather than its historical one. The annual saving was substantial and recurring, and because the new agreement was based on a documented baseline, the organisation could defend the value for money case to its auditors and to the public.
Crucially, the organisation also put in place a process to maintain the entitlement baseline going forward, so the shelfware would not accumulate again. This turned a one time saving into a durable capability, ensuring future renewals would start from an accurate position. The approach mirrors the support cost discipline in our EBS support cost optimization article and the deal structure in our Apps Unlimited guidance.
What Other Buyers Can Take From This
The transferable lesson is that you cannot negotiate well what you do not measure. The organisation's savings came not from clever tactics but from knowing its own entitlement position precisely and being able to prove it. Any customer, public or private, that builds an accurate baseline of what it is entitled to versus what it uses will find shelfware to drop and a stronger position from which to negotiate.
The case also shows that procurement constraints can be an asset. The transparency and documentation that public sector rules require produced a negotiating position Oracle could not easily challenge, because everything was evidenced. Private sector buyers can adopt the same discipline voluntarily, and the rigour of building a defensible, documented case is exactly what we bring to engagements, guided by the framework in our Oracle Negotiation Playbook.
Where to Read Next
For a related migration outcome see our telecom OCI migration case study. The full set of outcomes is in our case studies pillar, and the methodology behind them is in the Oracle Negotiation Playbook.