The first concrete number on the table quietly sets the range for everything that follows. In an Oracle Java negotiation Oracle works hard to be the one who places it, and a prepared buyer makes sure there is a second anchor grounded in real facts.
Negotiation research is consistent on one point. Whoever puts the first credible figure on the table pulls the final outcome toward it, because every later move is measured as a distance from that starting point. Oracle understands this well. The opening Java claim, roughly your employee count times list price with a modest discount attached, is rarely a calm estimate of what you owe. It is an anchor, set high on purpose so that a large discount off it still leaves a very comfortable deal for Oracle.
The trap is that even an experienced buyer starts to argue down from that number. Every concession then feels like progress, while the anchor itself goes unexamined. The figure that should be in question becomes the fixed point the whole conversation orbits.
You do not beat an anchor by rejecting it. You beat it by placing a credible one of your own, early and grounded in facts the other side cannot easily dismiss. In an Oracle Java negotiation your counter anchor is your real deployment, not your headcount.
Oracle anchors on the employee metric, which since January 2023 counts every full time and part time employee, every contractor, and every temporary worker, whether or not they use Java. Your counter anchor is the much smaller set of workloads that actually run Oracle Java, the cost of moving everything else to a free OpenJDK distribution, and the residual subscription you would carry afterward. When you put that on the table first, the conversation starts from your number instead of theirs.
| Oracle anchors on | You anchor on |
|---|---|
| Total employee count | Workloads that truly need Oracle Java |
| List price with a discount | The residual after migration |
| A three year lookback claim | Your documented current deployment |
A counter anchor only holds if it is backed by your own documentation. A number you assert but cannot support is dismissed in a sentence. A number tied to a mapped estate, a costed migration, and a clear view of which systems need Oracle Java is one Oracle has to engage with. That groundwork is the same preparation described in building leverage before you talk to Oracle, and it is what gives your anchor weight.
Do not negotiate down from Oracle's opening figure as if it were the truth. Arrive with your own number, built from real deployment and a costed alternative, and put it on the table early. Two anchors in the room is a negotiation. One anchor is a price.
An anchor sets the range, but it does not close the deal on its own. It works because it sits on top of a credible alternative and a clear set of asks. The way these moves fit together is set out in the buyer side moves that work on Oracle Java.
A counter anchor only makes sense if you understand the metric Oracle is anchoring on. For the per employee mechanics and the numbers behind the bands, read our Oracle Java licensing guide for 2026.
Download the guide for the full buyer side playbook, then bring us your estate and we will help you shrink the number Oracle can bill.
Download the guide Book a Strategy CallFixed fee or gainshare, both backed by our guarantee. We sit between you and Oracle and we never take vendor money.
Get a QuoteWeekly intelligence on Oracle Java licensing moves and the buyer side defenses that work.