No new theory. A realistic draft ordering document for a fictional manufacturer sits on the table, and this session takes it from the version Oracle drafted to the version the buyer signs: ten markups written as enforceable sentences, each valued in dollars, the concession ladder that predicts what Oracle grants, and the meeting choreography that lands eight of ten clauses inside Oracle's own quarter end. Module 2 closes here.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
A working session with three knowledge checks: the quarter end email offering five points for an unchanged signature, the enforceable price hold test across four candidate wordings, and the closing trade of discount points against audit terms. It ends with the markup scorecard: what each clause was worth, and the final paper signed inside Oracle's quarter on the buyer's terms.
The full narration of this session, section by section, for reading and reference.
Welcome back, session ten of forty, and the last session of module two. Today is different. No new theory, no new price list, no new clause names. Today we work. There's a draft ordering document on the table, Oracle's paper, for a fictional manufacturer called Meridian Industrial, and over the next thirty minutes we take it from the version Oracle drafted to the version Meridian signs. Every skill from the last four sessions gets used: session six's reading order, session seven's species check, session eight's markup list, session nine's benchmarks and calendar. If those sessions were the flight lessons, this is the first solo. By the end you'll know how to take any draft order from inbox to marked up in one sitting, how to write asks a lawyer could enforce, and how to trade paper against price deliberately. Three knowledge checks, and at the end, a scorecard showing what the whole negotiation was worth. Let's meet the document.
Five takeaways for the working session. One, you'll read a draft order cold, the five block structure, in the session six order, knowing exactly where the traps live. Two, you'll write the asks, turning session eight's clause list from concepts into concrete replacement wording, because the negotiation isn't we'd like better audit terms, it's here is the sentence, sign it. Three, you'll value each ask in dollars, even roughly, and this changes everything, because once the clauses have numbers, trading clauses against discount points becomes arithmetic instead of instinct, and arithmetic is much harder to bully. Four, you'll run the meeting, the actual choreography: what gets negotiated first, what gets bundled, when to stop talking. And five, you'll close module two owning the complete contract toolkit: read it, classify it, benchmark it, change it. That toolkit is the foundation the ULA module builds on next, because a ULA is just the biggest, sharpest version of the same paper. Here's the deal on the table.
The premise, four numbers. Meridian Industrial, a manufacturer, is expanding its database estate, and Oracle's draft is in. One point one eight million dollars net, that's the license price, fifty five percent off a two point six three million list basket. Session nine reflex: benchmark it before admiring it, and we will. Two hundred sixty thousand dollars, year one support, twenty two percent of that net, the annuity the entire document is quietly built to protect, growing every year afterward unless someone caps it. Ten, the clauses on session eight's markup list, and here's the finding that shapes the whole session: the draft's special terms section currently contains none of them. And May thirty first, six weeks away, Oracle's year end, which the rep mentions in every call, and which we're going to use rather than fear. One disclosure before we start: Meridian is fictional, the document is a composite. But every clause position, every concession pattern, and every dollar figure in this session reflects how these negotiations actually run. This is a flight simulator with real physics. Let's open the draft.
What's in Oracle's draft, five blocks, read in the session six order. Block one, products and metrics. Enterprise Edition, RAC, Partitioning, and the Diagnostics and Tuning packs, all on the Processor metric, twenty four licenses, which after sessions two through four you can verify against the actual hardware, and Meridian has. Block two, pricing. List, fifty five percent, net, real numbers on the next slide, and session nine already tells us which band this deal sits in. Block three, the incorporated documents. The OMA and the support policies, pulled in by reference, the frozen at signature rule and its one deliberate exception, working exactly as session six described. Block four, support. Twenty two percent of net for year one, with the policies governing every year after. Notice the word that isn't there: cap. As drafted, the increases are whatever the policies say. And block five, special terms. One migration paragraph, and otherwise, empty. Here's the sentence to remember from this slide: an empty special terms section is not neutral. Empty means every default in Oracle's standard paper applies, and session eight told you, in detail, whose defaults those are. The negotiation is mostly the act of filling that section. First, the numbers.
The deal sheet, line by line, at list and at net. Database Enterprise Edition, twenty four processors, one point one four million at list, five hundred thirteen thousand at the draft discount, and, right hand column, one hundred twelve thousand a year in support. RAC, five fifty two at list, two forty eight net, fifty four thousand of support. Partitioning, two seventy six list, one twenty four net, twenty seven thousand. The Diagnostics and Tuning packs, three hundred thousand list, one thirty five net, just under thirty thousand. And then, Advanced Security, three hundred sixty thousand at list, one hundred sixty two thousand net, thirty five thousand six hundred forty dollars of support, every year. Draft total: two point six three million list, one point one eight million net, two hundred sixty thousand of annual support. Two observations before the first check. Session nine's table says a one point one eight million dollar net deal sits in the one to five million band, where fifty five percent is commonly achieved and seventy five is strong, so the draft discount is the middle of ordinary, not a gift. And the second observation: nobody at Meridian ever asked for Advanced Security. Keep both facts loaded. The phone rings.
Knowledge check one. Friday afternoon, the rep emails: sign the draft unchanged by end of quarter, and the discount moves from fifty five to sixty percent. What's the right response? A, sign, five points on a two point six three million list basket is real money. B, decline the deadline and restart the negotiation after May. C, counter: the improved price is welcome, and the signature comes with the markup attached. Or D, escalate to Oracle management to complain about the pressure. Pause here, and ask what signing unchanged actually costs.
The answer is C. Take the price, keep the markup. The five points are real, about a hundred and thirty one thousand dollars off the net, and quarter end is exactly when offers like that appear, session nine told you why: approval authority loosens as May approaches. But look at the word doing all the work in that email: unchanged. Unchanged means the special terms section stays empty. No cap on a two hundred sixty thousand dollar support line. No price hold for the phase two everyone knows is coming. No divestiture rights for a board that reviews a carve out every other year. Standard audit terms. Session eight's arithmetic is unambiguous: over the life of this agreement, those clauses are worth more than the points, and, beautifully, Oracle's quarter end need is precisely the leverage that gets them granted. The wrong answers. A pays for one discount with every future year. B walks away from real leverage that expires May thirty first, the deadline is a tool, you don't have to hate it. D burns relationship capital complaining about a pressure tactic that is, frankly, just the job. The counter is one sentence, and it's the sentence this session exists to teach: we can sign inside the quarter, and here is the paper we sign. Now let's write that paper.
Markups one through four, the protections, written into special terms. One, the customer definition. The draft covers the signing entity alone. The markup: Meridian plus all majority owned affiliates, current and future. One sentence, and the reorganization everyone knows is coming stops being a licensing event. Two, audit terms, session eight's constitution, now in ink: forty five days notice, at most annual, defined scope, confidential handling, and Meridian's own verified data accepted. Notice these asks cost Oracle nothing today, which, as we'll see on the ladder, is exactly why they're winnable. Three, territory. The draft is silent, and Meridian runs workloads in three countries and a cloud region. The markup: worldwide use for the covered entities. Silence to sentence, finding category closed. And four, basket hygiene, the session nine move: Advanced Security, one hundred sixty two thousand net and thirty five thousand six hundred forty dollars of support every year, was never requested. It leaves the order. And when it leaves, the percentage gets recalculated on the clean basket, because the fifty five percent headline was computed on a padded denominator. Watch what that does: the clean list is two point two seven million, and suddenly the same net is a different, honest percentage. Four markups in, and we haven't touched price yet. That's deliberate. First, a drafting test.
Knowledge check two, the drafting test. Meridian wants today's pricing protected for phase two. Four candidate sentences for the special terms section. A, Oracle will offer competitive pricing on future orders. B, discount levels may continue where commercially reasonable. C, Oracle intends to maintain the pricing relationship established here. Or D, net unit prices in this order apply to additional orders of the same products through May thirty first, twenty twenty eight. Only one protects Meridian. Pause here, and ask of each sentence: could you enforce it?
The answer is D, and the test it passes is worth memorizing: an enforceable price hold is a number, a scope, and a date. D has all three. The number: net unit prices in this order, not a vibe, the actual figures on the deal sheet. The scope: additional orders of the same products, defined. The date: through May thirty first, twenty twenty eight, an ending you can point to. A lawyer can enforce that sentence, which means Oracle will think twice before drafting around it, which is the entire point. Now hold the others up to the light. A promises an offer, Oracle offers pricing to everyone, that's called a quote. B contains two escape hatches in nine words: may, and commercially reasonable, either one alone would gut it. C describes an intention, and intentions bind nobody, that sentence is a greeting card. Here's the session six lesson in miniature, and it might be the most practical minute in the course: rights live in specific words. Vague warmth in a special terms section is worth exactly nothing at phase two time, when the account team has changed and the goodwill has evaporated. So when you write your asks, write them shaped like D, so the only question left in the negotiation is whether Oracle signs. Three more markups.
Markups five through seven, the commercial block, where the recurring money lives. Five, the renewal cap: support increases capped at three percent per year for five years, replacing the uncapped policy default. The clean support base is about two hundred twenty five thousand, and after module one you know what uncapped compounding does to a number like that, the cap is the cheapest insurance on the sheet. Six, discount persistence: the final negotiated percentage applies to add on orders of the basket products. Pair it with the price hold and notice they do different jobs: the hold fixes prices for phase two, persistence fixes the rate for everything else, and together they mean Meridian never negotiates this discount again from zero. Seven, divestiture transition: divested entities keep use rights for six months post close. Meridian's board looks at a carve out every other year, and session eight's second knowledge check showed exactly what happens to companies that discover this clause missing, mid transaction, deal public, clock running. Six months of transition, negotiated now while it's hypothetical, is the difference between a checklist item and a crisis. And then the eighth move, which isn't an ask at all: the precedence check. One read of session six's precedence clause, confirming these special terms outrank the standard documents they amend. The markup only works if the hierarchy says it does. Verified. Now, what will Oracle actually say to all this?
The yes ladder, because concessions are not equally hard, and knowing which rung an ask sits on tells you what to lead with and where the leverage gets spent. Rung one, granted readily: price holds with an end date, affiliate coverage, basket cleanup. These cost Oracle little today, they mostly protect you tomorrow, and a prepared buyer gets them close to automatically. Which is the quiet scandal, by the way: most buyers don't ask. Rung two, granted with escalation: the renewal cap and discount persistence. These touch the annuity, the twenty two percent stream Oracle protects above all, so they climb the approval chain, take days, and need a reason. A quarter end signature is a reason. Rung three, granted under pressure: audit terms and divestiture rights. These move when revenue is genuinely at stake and the ask is written, specific, and attached to a signature, exactly the shape Meridian's asks now have. And rung four, rarely granted: anything unwinding matching service levels or the support model itself. That's a wall, module four will map it in detail, and the professional move is to know it's a wall before spending the meeting pushing on it. The ladder explains the strategy: bundle everything, because the easy rungs come along free while the leverage works on the hard ones. Now, the meeting itself.
Running the meeting, five rules of choreography. Rule one, paper before price. Negotiate the clauses first, then the percentage, because done in reverse, every clause ask gets answered with we already gave you our best discount, the leverage is spent, the wallet is closed. Clauses while the wallet is open. Rule two, one written markup. All the asks in a single redline, valued internally, delivered together. Serial asking, one concession per week, trains Oracle to wait you out and lets them trade the same discount against each ask repeatedly. Rule three, trade, never donate. Every concession you make buys one back, out loud, in the same sentence. Meridian's quarter flexibility is a card: we can sign by May thirty first, and, the cap comes with it. Played silently, the same flexibility is worth nothing. Rule four, let silence work. When the counter lands, stop talking. The prepared side of the table is comfortable in the pause; the side with a quota and six weeks left in the fiscal year is not. Thirty seconds of quiet has closed more clauses than most arguments. And rule five, keep the walk away real. Session nine's September option stays visibly alive until the paper is right, it's the engine under every other move, and everyone in the room can tell whether it's real. Oracle responds. Final check.
Knowledge check three. Oracle's counter arrives: the renewal cap, accepted, at four percent instead of three. The price hold, accepted. The audit terms, rejected. And instead, three extra discount points on the table. Take the trade? A, yes, three points is about sixty eight thousand dollars, take it and close. B, no, reject everything until the audit terms are granted. C, value both sides first: the points pay once, the audit terms pay at every audit, then counter with a smaller price ask and the audit language back in. Or D, accept, because audit terms never matter for compliant companies. Pause here. Session eight's rule: what pays once, and what pays every year?
The answer is C, price the trade before you take it. And start by seeing the counter for what it is: progress. The cap and the hold, the two most valuable commercial asks on the sheet, are in, at four percent instead of three, which is a normal landing. The live question is the swap Oracle proposed: three discount points, roughly sixty eight thousand dollars, once, in exchange for dropping the audit language, which shapes every audit for the life of the agreement. That's the exact exchange session eight warned about, a recurring right traded for a one time payment, so it gets priced, not reflexively accepted, and priced honestly it loses: module five will show what unshaped audits cost, and it is not sixty eight thousand dollars. The wrong answers. A takes the money without doing the arithmetic, which is how recurring rights get sold cheap. B turns the negotiation into a hostage situation over the one ask sitting on a higher rung of the ladder, ultimatums close doors, counters open them. D believes audits only visit the guilty, and sessions one through eight have been one long correction of that belief. The close that actually works: take the cap, take the hold, hand back one of the three points, keep the audit sentence. Everyone signs. Let's score it.
The scorecard, what the markup was worth. The clean basket: Advanced Security out, one hundred sixty two thousand off the net today, and thirty five thousand six hundred forty dollars of support that now never gets invoiced, this year or any year. The discount: fifty five to fifty eight on the clean basket, about sixty eight thousand more off the net, and the support base drops with it, the double effect from session nine. The renewal cap, four percent for five years: tens of thousands avoided in every high uplift year, compounding quietly in Meridian's favor for half a decade. The price hold through May twenty twenty eight: phase two, about half a million dollars of planned purchase, buys at today's net instead of restarting from list. And the block of persistence, divestiture, audit terms, and definitions, all granted: the recurring protections, the ones that don't show up in year one but decide years two through ten, the carve out clause alone could be worth two hundred thousand the day the board says yes. The final paper: nine hundred fifty three thousand net against the two point two seven million clean list, support starting near two hundred ten thousand and capped, eight of the ten markup clauses landed. Signed May twenty ninth, inside Oracle's quarter, on Meridian's paper. Both of those sentences matter, and they are not in tension. That's the working session.
Session ten in three sentences, and with it, module two. One, an Oracle draft is precise where it bills you and empty where it protects you, so the negotiation is mostly the act of filling the special terms section with session eight's list. Two, every ask gets written like an obligation, a number, a scope, and a date, and valued in dollars, so that trades between clauses and discount points become arithmetic, and arithmetic doesn't panic at quarter end. Three, module two is complete: you can read the stack, classify the license, benchmark the price, and change the paper, the full contract toolkit. And you'll need all of it, because next session opens module three: Unlimited License Agreements. The ULA, the highest stakes contract Oracle sells, unlimited deployment for a fixed fee, a certification at exit that decides whether the whole thing was a bargain or a trap, and more seven figure mistakes per page than any document in the portfolio. Session eleven covers the fundamentals and the economics: what a ULA actually is, when it genuinely makes sense, and when it's a beautifully wrapped renewal machine. Bring skepticism. See you there.
Homework, about an hour, and this week you run the simulator on your own aircraft. One, mark up your own order. Take your most recent Oracle ordering document and run today's exercise: five blocks, in order, what would you change in each? You now know how to see the empty special terms section for what it is. Two, write three asks properly, each with a number, a scope, and a date, and apply the check two test: could a lawyer enforce the sentence? If not, redraft until they could. Three, value each ask, a dollar figure per markup, even rough, because trades you cannot price are trades you lose, and someone across the table has priced them. Four, agree the walk away internally, the fallback date and position, before the next real negotiation, not during it. The September option only works if your own organization believes it. And five, pull any ULA paper your estate has ever had, the agreement and its certification if one happened. Module three starts from real documents, and the archaeology skills from module one are about to meet the biggest artifact in Oracle licensing. That's the hour, and that's module two. See you in session eleven.
Five reads, all free on redress compliance dot com. First, the Oracle contract clause negotiation playbook, today's markup list in reference form, clause by clause, keep it next to the library. Second, Oracle price holds, caps, and uplift clauses, the commercial block with wording that survives the check two test, the drafting companion to this session. Third, field tested Oracle negotiation strategies, the choreography from buyers who have run it at scale, rules one through five with war stories. Fourth, the Oracle renewal negotiation checklist, the same working session discipline aimed at a renewal instead of a purchase, because module four is coming. And fifth, dealing with Oracle sales tactics, the Friday email and every cousin it has, read once, recognized forever. That's session ten, and that's module two: the stack, the species, the clauses, the benchmarks, and one draft order that left the table better than it arrived. Module three is the ULA, five sessions on the highest stakes paper Oracle prints. Certification is coming. Be ready. See you in session eleven.