Full narration of the briefing. Click a section heading to jump the player to that moment.
Before you discuss price, discuss the count, because the count is the first argument in every one of these engagements. Across the thirty five to forty five Oracle Java engagements behind this series, the employee number Oracle quoted ran eighteen to twenty eight percent above the number the buyer could actually defend, once temporary staff and non supporting contractors were stripped out. On a large estate that gap is worth more than any discount you will be offered, and it is available before you negotiate a single percentage point. Nobody hands it to you.
You have to build it.
The whole contractor question turns on eight words. The definition captures contractor staff that support your internal business operations. Read that carefully, because it is a scope limit, not a catch all. A contractor building a product you sell to customers is not supporting your internal operations.
Neither, arguably, is an offshore team delivering a client project under your brand. That narrower reading carried in roughly four of five engagements where contractor counts were contested. So the negotiation is not really a census exercise. It is a definitional one, and the work is mapping each population to the words in your own ordering document.
So run the reconciliation properly, from your own systems, dated, before the conversation opens. Start with the payroll number Oracle used, usually pulled from a public source or an annual report, and work down. Employees who have left. Temporary staff outside the definition.
Populations in divested entities that no longer belong to you. Contractor and outsourcer staff whose work is delivering to your customers rather than supporting your internal operations. Each exclusion needs a source and a date, because you will be asked to show it. That document is worth eighteen to twenty eight percent of the largest line in the deal, and it takes days rather than months.
Now the band mechanic, and this is the part that surprises everyone the first time. The rate applies to the whole ordered quantity, not just the employees above the threshold. So a company with nine thousand nine hundred and ninety nine employees pays one million two hundred and fifty nine thousand eight hundred and seventy four dollars a year at list. A company with ten thousand pays nine hundred and ninety thousand.
One extra person removes two hundred and sixty nine thousand eight hundred and seventy four dollars from the annual bill. That is not a discount, a loophole or a negotiation. It is the published ladder doing arithmetic.
Which means there are six windows, one below every band edge, where ordering more than your actual headcount is strictly cheaper in absolute terms. The widest runs from seven thousand eight hundred and fifty eight to nine thousand nine hundred and ninety nine employees, worth up to two hundred and sixty nine thousand a year. The largest single saving, three hundred and seventy seven thousand nine hundred and nineteen dollars, sits at the thirty thousand edge. In four of our engagements the customer was sitting inside one of these windows and nobody on the Oracle side had mentioned it.
There is no reason they would, and no quote arrives with it modelled.
Here is it worked. An eight and a half thousand employee company ordering eight and a half thousand pays one million seventy one thousand dollars a year. The same company ordering ten thousand pays nine hundred and ninety thousand. It saves eighty one thousand dollars a year and carries fifteen hundred employees of growth headroom at no cost, which is roughly three and a half years of protection at five percent annual growth.
The larger order also buys true up immunity, because you cannot breach a quantity you have not reached. Compare across the whole term including the true up you no longer have to have, and the gap widens again.
So the sequence matters, and it is always the same. First defend the count, on evidence, in writing, from your own systems. Then choose the band deliberately, modelling the edges around your defended number rather than ordering the number itself. Do it in that order and the two moves compound: a smaller defensible count can drop you a band, and the band mechanic can then make a slightly larger order cheaper than the smaller one.
Do it in the other order and you have optimised a number you are about to argue about. Next part, what everyone else actually paid, because none of this tells you whether the rate you are quoted is any good.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator