How to use this library
Start from your commercial event rather than from the vendor. A renewal, an audit letter, a true up and a migration are four different problems, and they reward different preparation.
Then read the vendor specific paper. Licensing mechanics do not generalise: Oracle counts processors, SAP counts documents and users, Microsoft counts seats, IBM counts reported capacity. The principles transfer and the arithmetic does not.
Read it early or do not bother
The single strongest predictor of whether one of these papers changes an outcome is when it gets read. Nine to twelve months before a renewal, it changes what you measure and what you ask the vendor for.
Inside the final quarter it mostly explains, clearly and too late, what you have already given away.
Read across your vendors, not just one
Most large estates carry overlapping commitments. A Microsoft agreement affects your AWS position, an SAP migration affects your Oracle exposure, and an AI commitment now touches all three.
Buyers who read across the two or three vendors they actually run consistently negotiate better than those who read a single paper very carefully.
Which paper for which situation
| Your situation | What to read first | What to do alongside it |
|---|---|---|
| A renewal in the next twelve months | The vendor's renewal or negotiation playbook | Build your own deployment position from your data |
| An audit letter has arrived | The vendor's audit defense guide | Agree scope in writing before producing anything |
| A migration is being proposed | The migration or cloud guide for that vendor | Price the licensing outcome of each option, not just the effort |
| Cost reduction with no deadline | The optimization or FinOps paper | Diary every termination and true up window first |
Where the common advice on vendor white papers is wrong
The common view is that vendor licensing papers are broadly interchangeable, so you may as well read whichever is nearest to hand, including the ones the vendor publishes. We disagree on both counts. A paper written by, or sponsored by, the party selling you the licence will be accurate and incomplete in a very specific direction: it will explain the mechanics faithfully and omit the levers that cost the vendor money. And the papers are not interchangeable, because the metric is the whole game. Reading an excellent Microsoft seat licensing paper teaches you almost nothing useful about an Oracle processor count or an IBM sub capacity report. Read the one that matches your vendor and your commercial event, and check who paid for it.
What to do next
If you are preparing for a vendor conversation, work through these.
- Identify your commercial event: renewal, audit, true up or migration. They need different preparation.
- Find the paper for your vendor and that event, and read it before you speak to the vendor.
- Build your own deployment position from your own tooling in parallel.
- Diary the dates that matter: anniversary, true up, notice period and termination windows.
- Benchmark the quote against what comparable buyers pay before responding to it.
- Open the conversation nine to twelve months out. Inside ninety days only the price is still negotiable.
