What you will be able to do after this session

• 1Explain the model. Know what third party support providers actually deliver, and what they cannot.
• 2State the law. Answer the is it legal question accurately, with the history behind the answer.
• 3Handle security honestly. Weigh the no vendor patches question with mitigations, not slogans.
• 4Match the fit. Know which workloads belong on third party support and which never will.
• 5Use it either way. Deploy the alternative as a move, or as the priced option that disciplines every renewal.

How the session works

A taught session with three knowledge checks: the is it legal executive question answered without hedging, the no vendor patches objection weighed as a per workload tradeoff with compensating controls, and the CFO's move everything proposal corrected to the split estate. It closes with one four workload portfolio assigned honestly, banking $190K a year without losing wanted coverage anywhere.

Homework before the next session, about one hour

• 1Run the fit profile. Every workload from the baseline audit marked fits, does not fit, or cannot fit. The sustaining tier lines go first.
• 2Price your alternative. Your third party candidates at half their current fees. That number is renewal leverage whether or not anyone moves.
• 3Check the patch reality. For each candidate: when was the last Oracle patch actually applied? Systems years behind are already living the tradeoff, unpriced.
• 4Sketch one bridge. Your most migration ready estate: destination, date, and what half its support fee would fund.
• 5Draft the due diligence list. Five questions for any provider: process compliance with the case law, references at your scale, security controls, onboarding, and exit.