Full narration of the briefing. Click a section heading to jump the player to that moment.
Maximisation is a word that makes some people uncomfortable, so let me define it plainly at the start. You paid for the right to deploy unlimited quantities of specific products for a fixed period. Maximisation means actually using that right before it expires, and being able to evidence what you used. That is not a loophole.
It is the deal you signed. I am Daniel, Claire is with me, and this session is how that programme runs, what it is worth, and where the honest line sits.
Start with the value, because it justifies the effort. Structured preparation before certification lifts certified quantities by twenty to forty five percent compared with passive reporting, which means simply submitting whatever the discovery tools happen to show on the day. On a substantial estate that difference is routinely seven figures of perpetual entitlement, received at no additional licence cost, because you already paid for the right during the term. And it is permanent.
That entitlement sits on your books and governs your position for the next decade, so the gap between prepared and unprepared compounds far beyond the certification itself.
The first lever is sequencing, and it is entirely legitimate. Look at the Oracle deployments already planned for the next eighteen months: the new environments, the platform refresh, the capacity expansion, the project going live next spring. If any of that lands after your count freezes, you will pay for those licences separately even though your unlimited right was running when the decision was made. So bring genuine, funded, planned work forward to complete at least a quarter before the freeze.
You are not inventing deployment. You are scheduling work you were doing anyway on the correct side of a contractual date.
The second lever is completeness, and this is where most of the twenty to forty five percent actually comes from. Passive reporting misses things constantly. Disaster recovery sites that nobody thought to include. Development, test and integration environments.
Instances on hardware that discovery tools never reached. Partner hosted systems. Cloud deployments where the counting rule was never confirmed. None of that is new deployment.
It is deployment you already have, running today, that simply was not in the submission. Finding it is an inventory exercise, and it is the single highest return activity in the whole programme.
Third lever, and the one that decides whether the first two survive: evidence. Records win certifications. A number you cannot substantiate is a number Oracle will challenge, and challenges resolve in favour of whoever has documentation. So capture deployment evidence continuously through the final year rather than reconstructing it in the last month: configuration exports, inventory snapshots with dates, change records, architecture documents.
The count you can defend is the count you keep, and defending a count six months after the fact with no contemporaneous records is a losing position however true your claim is.
Now the line, and it is clearer than people expect. On the right side: deploying real workloads you genuinely intend to run, completing planned projects early, and counting every legitimate instance you already operate, with records. On the wrong side: standing up instances with no purpose purely to inflate a number, claiming deployment that is not running, or counting things outside your contracted scope. The second list is not clever.
It fails at audit, it damages the relationship, and it can unwind a certification. Everything valuable in maximisation is on the first list, which is why the honest version is also the effective one.
The move from this briefing: take your Oracle deployment roadmap for the next eighteen months and lay it against your count freeze date. Anything genuine landing just after the freeze is a candidate to bring forward, and anything already running that is not in your inventory is money sitting on the table. That single comparison is the maximisation programme in one page. Next session: counting itself, and the specific places where certifications turn into disputes.
See you there.
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