White Paper

The Support Cost Reduction Guide.

Oracle support runs at roughly 22 percent of net license cost with annual escalation, and the Support Cost Reduction Guide shows how to bring that bill down by shedding shelfware, planning around matching service levels, and using Support Rewards.

FreeBehind a work email
~22%Typical support rate
Support RewardsOffset through OCI
01 What is inside

Where the support bill hides, and how to cut it.

Support is the quiet majority of Oracle spend over a license lifetime. The guide shows the levers that actually move it, and the policy traps that stop the obvious ones from working.

  • The 22 percent rule. How support is priced on net license fees and escalates each year.
  • Matching service levels. Why Oracle policy constrains partial termination, and how to structure around it.
  • Finding shelfware. A method for spotting licenses you pay support on but no longer deploy.
  • Terminating cleanly. The order of operations to drop support without breaking entitlements you still need.
  • Support Rewards. How the program offsets support spend through OCI consumption, and when that math works.
  • A reduction workbook. A checklist to model the saving before you commit to anything.
Free download

Get the guide.

Enter a work email and we send the guide, plus The License Position weekly note. Buyer side only, unsubscribe anytime.

No public email is required from us and no price is shown. We capture everything through this form.

02 Why it matters

Declining support spend is itself an audit trigger.

Cutting support is sensible, but doing it carelessly invites a notice. A drop in support or new license spend is a known audit trigger, so the saving has to be planned with the audit risk in view.

03 FAQ

About the guide.

Oracle support runs at roughly 22 percent of net license cost with annual escalation. The guide shows how to bring that bill down without losing the cover you need.
Matching service levels are an Oracle policy that constrains partial termination, so you usually cannot drop support on part of a license set while keeping it on the rest. The guide explains how to plan around it. This area is contract dependent and we flag it as such.
It can. A drop in support or new license spend is a known audit trigger, so the saving should be planned with the audit risk in view. The guide covers how to sequence the change safely.
The License Position

Already downloading? Keep the briefings coming.

A short weekly note, buyer side. One development, why it matters, and one move you can make this week.

Buyer side only. Unsubscribe anytime. Last reviewed June 2026