The enterprise agreement, the four rights, the cap against the discount, and one estate taken end to end. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real IBM negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome to session twenty, the last one. Two jobs today. The first is the negotiation itself, the enterprise agreement, the clauses that decide what it is worth, and the timing. The second is the capstone, where we take one estate through everything these twenty sessions have covered and see how the pieces connect. And I want to set an expectation about the negotiation half, because it may not be what you expect from a final session. The negotiation is the least important part of this course. It is the visible part, it is where the meetings happen, and almost everything that decides its outcome happened months earlier. Three knowledge checks. Let's begin.
Five objectives. First, read an enterprise agreement for what it is, a fixed scope, fixed price, multi year commitment that prepays growth, and very often an audit settlement wearing a bundle. Second, ask for the four rights by name, true up, swap, drop and termination for non use, because they appeared in fewer than one in four default templates and were granted in seven of nine agreements where somebody asked. Third, fix the scope before the price, because a broader scope priced fourteen to twenty four percent above a tighter scope plus discrete renewals. Fourth, never trade the cap for the discount, because a discount is a one time win recovered over the term while a cap compounds in your favour for every year of it. And fifth, run the estate rather than the meeting, because the renewal is won twelve months out and never at the renewal table.
Four numbers. Nineteen to thirty four percent, the median discount achieved from IBM's opening position at enterprise scale, with a median of twenty seven percent across the negotiations benchmarked. Twenty to thirty five percent, the share of a typical agreement carrying products with little or no recorded use, priced and renewed regardless of that. Fifteen to thirty percent off the first offer for buyers who opened with their own deployment baseline, against under ten percent for those who negotiated from IBM's paper, which is the same finding as the audit sessions in commercial clothing. And one in four, how often the four rights appeared in the default template, while being granted in seven of nine agreements where somebody asked explicitly. Then the note. The discount is the packaging. The clause set is the product, and it is negotiated at signature or never.
Guest analyst clip. There is a line I use about enterprise agreements that clients find uncomfortable and then repeat back to me two years later. An IBM enterprise agreement is the cheapest IBM contract on day one and the most expensive on day three hundred and sixty five of year three. Let me unpack why that is structurally true rather than cynical. On day one, you have negotiated a bundle against a known estate, with a discount that looks good against list, and the finance case is genuinely strong. Then three years pass. Some products in the bundle were never deployed at all. Some workloads grew past what you committed to, and the true up prices that growth at list unless somebody negotiated otherwise. Some things you no longer run are still in the base, because there is no drop right. And the renewal quote arrives, calculated from all of it, at a moment when your leverage is at its lowest because the agreement expires in ninety days. So the agreement is not a bad instrument. It is an instrument whose value is decided almost entirely by four or five clauses that nobody argues about on day one, because on day one everybody is looking at the discount.
Decided by four or five clauses nobody argues about on day one, because on day one everybody is looking at the discount. So here are the four.
Four rights. True up lets you add quantity during the term at the agreed unit price, and without it growth is repriced at list at the end, exactly when your leverage is lowest. Swap lets you move entitlement between products inside the same metric, and without it entitlement sits stranded in one product while you buy another separately. Drop lets you remove unused products at renewal without restructuring the whole agreement, and without it you carry a base that only ratchets upward, holding every decision anybody ever made. And termination for non use lets you exit a product line where consumption stays below a threshold, and without it you pay for a roadmap that never happened, for the full term. Then the note, which is the practical instruction. Ask for all four by name, in writing. They are rarely in the template and they are usually available, which is an unusual combination and worth exploiting.
Knowledge check one. On a two million dollar annual renewal, which is worth more, four points of extra discount, or a three percent uplift cap against a seven percent ask? A, the discount, because it applies immediately and is certain. B, the cap, and by more over three years, because the discount is fixed while the cap compounds on a growing base. C, they are identical in value. D, the discount, because caps are rarely honoured. Pause here. One of these is a one time adjustment. The other applies every year, to a number that grows.
The answer is B, the cap. Four points on two million is eighty thousand a year and two hundred and forty thousand across the term, fixed and limited to that base. Holding the uplift to three percent against a seven percent ask is worth around two hundred and sixty thousand across the same term, and unlike the discount it keeps compounding afterwards. So the rule that follows is worth memorising word for word. A discount is a one time win IBM recovers over the term. A cap is permanent and compounds in your favour. And you never trade one for the other in the same conversation, because bundled together the answer is always no.
So, scope before price, five points. Price against the deployed stack and never against the proposed one, because a bundle sized to the seller's catalogue rather than your estate fails regardless of what discount is attached to it. Broader scope is not cheaper scope, since in six of nine agreements rebuilt, the broader scope priced fourteen to twenty four percent above a tighter scope plus discrete renewals on the unused products. Remove shelfware before discussing price, because a flat renewal at one point zero two million against a measured need of six hundred and forty eight thousand is a three hundred and seventy two thousand a year question that no discount answers. The order of operations has a number on it, since fifteen percent off the full base lands at eight hundred and sixty seven thousand while rationalising first and then taking the same fifteen percent lands at five hundred and fifty thousand eight hundred. So scope discipline beats discount negotiation, which is session five arriving one last time in its most expensive form.
Now the cap, and what the annual increase does while nobody is watching. IBM opens at five to seven percent, and uncapped agreements took eight to fifteen percent increases at renewal, which makes this the single most skipped tactic on the buyer side. Target three to five percent, or inflation, whichever is lower, in writing, in numbers, and for the full term rather than for year one only, because a year one cap is not a cap. Negotiate it separately from the discount, because if the two are bundled into one concession the answer is no, since they are different instruments and deserve different conversations. Demand net price protection rather than list protection, putting the discount percentage in the paper as a floor so a future list movement leaves your net where you agreed it. And watch the January increase properly, because a headline six percent across the catalogue usually collapses to three or four on your actual top twenty lines once you check them against the published grid.
Guest analyst clip. The cap against the discount is the trade I most often see made backwards, and I think there is a psychological reason for it. A discount is a number you can report. You walk out of the room and say we got twenty seven percent, and everybody understands that, and it goes in a slide. A cap is a number that describes something not happening in the future, which is almost impossible to celebrate. Nobody has ever been congratulated for the increase they did not receive in year three. But look at the arithmetic honestly. The discount applies once, to the base as it stands, and IBM recovers it over the term through the escalator. The cap applies every year, to a base that is growing, and it keeps applying after the discount conversation is a memory. On the numbers I quoted, they are worth roughly the same across three years, and the cap is worth more across five and considerably more if the agreement rolls. So my practical advice is to negotiate them in different meetings if you possibly can. Because the moment they are on the same table, they become tradeable against each other, and the one that gets traded away is always the one that is harder to put in a slide.
Nobody is congratulated for the increase they did not receive in year three. Which is exactly why it gets traded away, and why you separate the conversations.
Knowledge check two. An audit is open and your renewal falls in the same quarter. IBM proposes settling both in one number. What do you do? A, accept, because one negotiation is simpler and the netting favours you. B, separate them, because audit driven agreements ran fifteen to twenty five percent above comparable deals with no claim pending. C, accept, but ask for a larger discount to compensate. D, delay the renewal until the audit is fully settled and accept the lapse. Pause here, and ask which of your two positions is weakest right now, and which asset is strongest.
The answer is B, separate them. Bundling uses your weakest moment, an open finding, to price your strongest asset, the renewal, and it hides the settlement discount inside renewal pricing so you can never prove what the compliance gap actually cost. Two papers, two negotiations, and ideally different signatories. Answer D overcorrects in an expensive direction, and I want to name that because the instinct to stall is common. Separating the workstreams does not mean stalling the renewal into a lapse, which creates its own back billing problem. It means separate documents, separate conversations, and neither one closing in the same quarter as the other.
Now timing, five points. Start twelve months out, because renewals begun two hundred and seventy days ahead closed at their original discount band while those starting inside ninety days absorbed the full increase. Use the fiscal year modestly, since IBM's year ends in December and quarter end genuinely does help, and it is worth low single digit points rather than the twenty that people imagine. The core count is worth far more, because the date is worth low single digits while the quantity is worth tens of percent, and IBM would much rather argue about the date. Ask in the right unit, stating the annual contract value you will commit to for a term rather than asking for a percentage off list, which simply invites a debate about list. And paper every concession the same day, because verbal agreements reset between meetings and roughly half of waived findings quietly reappear as uplift in a renewal baseline.
Guest analyst clip. The date is worth low single digits, the core count is worth tens of percent, and IBM would much rather argue about the date. I want to dwell on that last clause, because it describes something you will experience and might not otherwise notice. When a negotiation starts, there is a conversation available about timing. What quarter, what fiscal pressure, what happens if we sign by the thirty first. It is a genuinely enjoyable conversation. Both sides know the moves, it feels like negotiating, and the numbers move by a few points. And while that conversation is running, nobody is discussing whether the quantity in the proposal is correct, which is where the difference between a good outcome and a bad one actually lives. I am not saying ignore the calendar, because a few points is a few points and you should take it. I am saying notice which conversation you are being invited into, and make sure the other one has already happened. If you arrive at the quarter end discussion having already established, from your own data, what your estate actually needs, then the timing conversation is a bonus. If you arrive without that, the timing conversation is a very pleasant way to spend the leverage you had.
Notice which conversation you are being invited into, and make sure the other one has already happened. Which brings us to the capstone.
So, one estate, and where the money actually was. Build the baseline first, entitled against deployed, in both directions, with bundled and restricted flags recorded by hand, which is sessions two and five, and nothing else in this course works without it. Earn and hold sub capacity, meaning the four obligations, the tool inside ninety days, coverage at ninety eight percent and eight quarterly reports in a folder, which is sessions seven, eight and ten. Draw the boundary deliberately, across clusters, mobility and Power pools, because the countable boundary is an engineering choice with a price attached, which is sessions six and nine. Count the modern estate honestly, with Cloud Pak ratios, container limits, the second measurement tool, Red Hat on its own paper and cloud with its own clock, which is sessions eleven to fourteen. And shape the peak on the mainframe, where four hours a month set the bill and rate is the last lever rather than the first, which is sessions sixteen and seventeen.
And how you keep it. Run a calendar with owners, weekly coverage, a quarterly close, an annual drill and eligibility check, and a licensing question attached to the four events that break things silently. Keep the evidence findable, two years of reports, the entitlement register, topology and mobility history, and an anomaly log with dated resolutions. Treat a letter as a negotiation rather than an inspection, controlling the timeline, refusing the script in writing, building the three artifacts, dismantling the claim layer by layer and getting release language on the paper. Then negotiate from your own numbers, scope first, cap separately from discount, the four rights by name, and twelve months of preparation behind you. And notice the pattern, because every metric in this course fails in the same way. The organisation buys headroom and pays for it annually. The measurement is the asset, not the headroom.
Knowledge check three, the last one. You have one week before a renewal and no baseline. What is the honest best move? A, negotiate hard on the discount, since that is the only lever left in the time available. B, extend or bridge on your existing terms, then run the twelve month sequence properly. C, sign and fix the estate afterwards. D, refuse to sign anything until a full baseline exists. Pause here, and ask what a week actually buys you, and what a bridge preserves.
The answer is B, bridge and then do it properly. Renewals started inside ninety days settled close to IBM's opening position, and a week buys nothing except the appearance of effort. The bridge has to carry your existing discount, uplift cap and substitution rights forward word for word, because a bridge that resets the discount language is a price increase wearing a calendar costume. And answer C is the mistake this entire course exists to prevent, because fixing the estate after signature hands every gain you make to the other side, which is the same lesson as the baseline in session five and the consumption baseline in session seventeen.
Guest analyst clip. If you take one thing from twenty sessions, I would like it to be this, and it is not a fact about IBM. Every vendor conversation you will ever have is about the rate. What percentage, what discount, what uplift, what the number at the bottom of the page says. And almost every pound or dollar that is genuinely available to you sits in the quantity, which nobody at that table is going to raise, because it is not their job to raise it and frequently they do not know it either. Deployed against entitled. Cores that could run it against cores that do. Tokens against components anybody actually opened. Four hours of a month against seven hundred and twenty. In every model we have looked at, across five modules and completely different metrics, the money was in the count and the conversation was about the rate. So the capability I hope you have built is not really negotiation. It is the ability to walk into a room able to state, from your own evidence, what your organisation actually runs and actually needs. I have watched people with that capability and no negotiating training do better than skilled negotiators without it, and it is not close. Know your own number. Everything else is commentary.
So here is the whole course on one page, as a year. Weekly, coverage, with new hosts enrolled inside seven days, scan failures chased within ten business days and the resolutions documented. Quarterly, the close, generate review sign export archive across both measurement tools, plus the bundle map and the boundary review, on a dated calendar entry with a name against it. Annually, the drill and the lists, a morning rehearsing an audit against a past quarter and an hour re checking eligibility against the published lists. On event, the four triggers, hypervisor migration, credential rotation, tool upgrade, and any change to a cluster, a host count or an activated core. And twelve months out, the renewal, baseline, rationalise, model the alternative, then negotiate, in that order, because the order is worth more than the negotiation.
Three sentences. An enterprise agreement is a fixed scope, fixed price commitment that prepays growth, and the four rights that make it survivable, true up, swap, drop and termination for non use, appeared in fewer than one in four default templates while being granted in seven of nine agreements where somebody asked for them by name. Scope comes before price because a broader bundle priced fourteen to twenty four percent above a tighter one, the cap is negotiated separately from the discount because a discount is recovered over the term while a cap compounds in your favour, and an audit and a renewal never close in the same quarter or in the same number. And across twenty sessions the pattern has not changed, because the vendor conversation is about the rate and the money is in the quantity, so the renewal is won twelve months out in the consumption report and the audit posture, and the measurement is the asset rather than the headroom.
The final exercise, one page, about an hour, and it is the whole course. Write your entitled and deployed numbers, per product, with the source and the date against each, and if you cannot then that gap is your first project and you now know exactly how to close it. Write your coverage and archive counts, coverage measured against the hypervisor's host list and signed quarterly reports held out of eight, because those two numbers predict your audit outcome better than anything else you could measure. Write your worst boundary, the largest cluster or machine an IBM workload can reach, priced at the rating, because that is your exposure if measurement ever lapses. Write your renewal date minus twelve months, and put that earlier date in the calendar with a name against it, because that is the day the renewal is actually decided. And name the owner, one person with a financial mandate, because everything above that line decays within two quarters without them and holds indefinitely with them.
Five final guides. The enterprise agreement explainer covers the eight clauses, why the agreement is so often an audit settlement, and pricing against the deployed stack rather than the proposed one. The ELA pillar sets out term structures by estate size, the four rights and how often they are actually granted, and the case for scope discipline over discount negotiation. And the negotiation tactics guide gives nine specific tactics, the uplift cap most buyers skip, and what opening with your own baseline is worth in points.
The timing guide walks the twelve month sequence quarter by quarter and explains why the cap and the discount never get traded in one conversation. And the European bank case study shows a quote that opened twelve percent up and closed twenty five percent down across seven months, which is a thirty seven point swing built almost entirely before anybody sat down. That is the course. Twenty sessions, from the metric catalog to the negotiation. The progress tests and the certification exam are there when you want them, and I would take them once you have written that one page about your own estate rather than before. Thank you for your time, and good luck with the estate.