The documents that actually bind you, and the eight clauses worth your capital. 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 SAP 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 back. Session twenty five, and this closes module five. We have covered what is in the RISE bundle, how the FUE sizing works, the public edition alternative, and the decision across all four routes. What is left is the paper, and I would argue it is the part that matters most, because the product decision is made once and the contract governs the next decade. This session is about which documents actually bind you, which clause decides conflicts between them, the eight clauses worth spending your negotiating capital on, and four phrases to watch for. Three knowledge checks. Let's begin.
Five objectives. First, name the documents: the order form, the general terms, the service description, the service level agreement, and the policies incorporated by reference. Second, know which one wins, because the order of precedence decides every conflict and it is usually the least read paragraph in the entire agreement. Third, work the eight clauses, meaning the ones that determine what this costs over ten years rather than the ones that merely look important. Fourth, read the language, so four phrases that quietly move risk to you and what to ask for instead of each. And fifth, spend your capital well, because you will not win everything, and you need to know which three you will escalate for and which you will happily trade away.
Four things to frame it. One decision: the product choice is made once, and the contract governs every year that follows, including the ones nobody is modelling. Five documents, not one, because the order form is short and the things that actually bind you are mostly somewhere else. Incorporated: policies referenced by a URL are part of your agreement, and some of them can change without you. And eight clauses out of hundreds, because knowing which eight is the difference between a thorough review and an effective one. Now, the most expensive habit in enterprise software buying is negotiating the price hard and accepting the terms as drafted. The price sets year one. The terms set years two through ten. Let me put that more strongly.
Guest analyst clip.
Discount is legible and a renewal cap is abstract. That is a very good explanation of why this keeps happening, and notice it is an organisational problem rather than an analytical one. Everyone in the approval meeting understands a percentage. Almost nobody is measured on what year six costs. So if you want the terms taken seriously, you have to make them legible too, which usually means putting a number on what the clause is worth. Let's look at the documents.
Five layers, and ask for all of them at the same time, because reviewing them one at a time is exactly how conflicts get missed. The order form: volumes, prices, term dates and any negotiated special terms, so it is short, specific, and the only part most people read. The general terms: the master agreement, covering liability, termination, warranties and governing law, rarely negotiated line by line and worth knowing anyway. The service description: what the managed service actually does, in detail, and this is where the RACI from session twenty one either lives or fails to. And the SLA and the policies: availability, credits and support response, plus the security, data and acceptable use policies incorporated by reference. Ask one question early, which is which of these documents can SAP change unilaterally during the term. Anything incorporated by a link usually can, and that answer tells you which of your protections are real and which are provisional.
Now precedence, and please read this clause before anything else in the stack. Negotiated special terms sit highest, so what you fought for survives, which means every win needs to be written there rather than in an email. The order form is next, where volumes and prices are binding, though scope language there is often thin. The general terms sit in the middle, providing the legal frame, broad and usually silent on operational detail. The service description is lower, defining the service, and in many agreements it can be revised on SAP's schedule rather than yours. And referenced policies are lowest but still binding, living at a URL, so read them and ask what happens when they change. The reason to read precedence first is simple: it tells you where a win has to be recorded to be worth anything, and a concession recorded in the wrong layer can be overridden by a document you never negotiated.
First knowledge check. The account team promises a capability by email. Where does that promise need to end up? A, nowhere, since an email from an authorised representative binds them. B, in the negotiated special terms on the order form. C, in the service description, since that defines the service. D, in the meeting minutes, signed by both parties. Pause here and pick an answer before you continue.
The answer is B. Almost every enterprise agreement contains an entire agreement clause, which says that the signed documents supersede everything said or written beforehand, and that kills A and D outright however sincerely the promise was meant. C is closer, and it fails on precedence, because the service description usually sits low in the stack and can often be revised by the vendor during the term, so a promise recorded only there can quietly evaporate. Special terms on the order form sit at the top. My working rule is blunt: if a commitment is not written there, assume for planning purposes that you do not have it. Not because anybody is lying, but because the people who made the promise will move on, and the document will not.
So, the eight clauses that decide what this costs. Renewal pricing: a stated cap or an index, because without a mechanism the second term is priced against your cost of leaving. Overage rate: volume above the commitment at your negotiated rate rather than list, which is one sentence and it is granted more often than it is asked for. Exit assistance: duration, data format and cost, because your exit terms are what make your renewal negotiable at all. Scope of the managed service: a RACI attached to the contract, since everything outside it needs a partner and a budget you have not planned. Change of the service description: can it be revised unilaterally, because if so the service you bought is not the service you are guaranteed. Audit and measurement: who measures, how often, from which system, and what a disputed classification does. Termination for convenience, which is usually theirs and rarely yours. And liability and data: where your data sits, who may access it and what happens on a breach. Let me tell you which of those I would actually fight for.
Guest analyst clip.
Mechanisms rather than amounts, and they often cost the vendor nothing this year. That last point is the practically useful one, because it tells you how to position the ask. You are not asking them to give up revenue in the quarter they are measured on. You are asking them to agree a rule about a future year, and that is a genuinely easier conversation to have than another two points of discount.
Second knowledge check. You can win two of these. Which pair protects you most over ten years? A, a larger year one discount, and extended payment terms. B, a renewal cap, and the overage rate held at your negotiated price. C, a better SLA, and additional service credits. D, more BTP credits, and extra non production environments. Pause here, and think about which of these compounds.
B, and it is the only pair that compounds. A renewal cap governs the largest single number in the whole relationship at the moment you have the least leverage, and a protected overage rate governs every unit of growth for the term. Both of them keep paying you back every single year. A is a one off that feels excellent in the approval paper and is gone by year two. C sounds prudent, but service credits are small and they compensate you in the currency of the thing that has already gone wrong, which is rarely what you actually wanted. D has real value and it is finite and consumable. The principle to carry away is that discounts are won once and mechanisms keep working.
Now the language, and four phrases to watch. Then-current list price, which means your discount does not apply to this, and what you want instead is the same effective rate as the committed volume. As may be updated from time to time, which means this can change without your agreement, so ask for notice and for no material reduction during the term. Commercially reasonable efforts, which is an obligation with no measurable threshold, so ask for a defined outcome, a date, or a named remedy. And subject to availability, which means the commitment is conditional and effectively unenforceable, so ask for a firm entitlement or for the condition to be stated precisely. Let me be fair about why this language exists.
Guest analyst clip.
Standard does not mean fixed. That is the sentence to take away from this slide, and it applies well beyond SAP. When someone tells you a term is standard, they are usually telling you the truth, and they are describing where the document started rather than where it has to end up. The cost of asking is one email, and the worst outcome is a no, which as we said in session twenty three is itself information.
On spending your capital, five points, because you genuinely will not win everything. Pick three to escalate for, and I would take the renewal cap, the overage rate and exit assistance, and I would say early and clearly that these three matter more to us than the headline discount. Trade the ones you can afford: payment timing, marketing references, a case study, a reference call, all of which are cheap for you and genuinely valuable to them. Ask before the shape is set, which is session twenty one's rule, because every term is cheaper to obtain before the commercial structure has been agreed internally on their side. Get a no in writing, because a refused clause tells you what to price as risk and it is useful at the next renewal. And bring legal in early rather than late, since legal review at the end finds problems at exactly the moment you have no leverage left to fix them.
Five traps. Reading only the order form, which is the shortest document and the least of what binds you, while the service description carries far more of the risk. Accepting the incorporated policies, which are referenced by URL, changeable by the vendor, and fully part of your agreement, so at minimum ask for notice of material change. Negotiating price and not terms, because a strong discount with default terms is a good year one and an expensive decade. Recording wins in the wrong layer, since a concession in an email or in a low precedence document can be overridden by something you never read. And reviewing at the end, where legal arrives after the commercials are agreed and the deadline is close, and everything is harder from that point onwards.
Last knowledge check. The service description can be updated by SAP during the term. What is the practical consequence? A, none, since material changes require your consent by law. B, the service you bought is not the service you are guaranteed. C, it only affects future orders, not the current term. D, you can terminate without penalty if it changes. Pause here before you continue.
B. And I want to be clear that this is not a scandal, it is simply how most cloud agreements are drafted, and services genuinely do evolve so there is a real reason for it. But the consequence is real too: the operational detail you relied on when you chose the product sits in a document the other side can revise. A assumes a consent right that generally is not there. C is wrong in most agreements, because the change applies to the running service rather than only to new orders. And D would be an excellent protection, and it is rarely present unless you specifically ask for it. The fix here is modest and usually obtainable: notice of material change, plus a commitment that the service will not be materially reduced during the term. Which brings me to a small piece of housekeeping.
Guest analyst clip.
Twenty minutes on the day you sign. Right, five things for running the negotiation. Request the full stack on day one, meaning all five documents together, because reviewing them separately is how contradictions survive all the way to signature. Keep an issues list rather than a redline: one page with the clause, what it says, what you want and why, which is far easier to escalate and much easier to trade from. Track what was refused, every no with a date, because that becomes your opening position at renewal and your input to the risk register. Diarise the review dates, so notice periods, renewal windows and price adjustment dates go in a calendar the moment you sign. And file the executed set together, including that dated copy of every referenced policy as it stood at signature.
Three sentences. You are signing five documents rather than one, and the order of precedence decides every conflict between them, so read that clause first and record every win where it will actually survive. Eight clauses determine what this costs over ten years, and the two that compound are the renewal cap and the overage rate held at your negotiated price, because discounts are won once and mechanisms keep working. And ask before the shape is set, get every refusal in writing, and file a dated copy of every incorporated policy as it stood on the day you signed. That closes module five. Next session opens module six on the wider SAP cloud and SaaS portfolio, starting with BTP: what the platform actually is, the four ways it gets bought, and who ends up owning the bill.
Homework before session twenty six, about two hours, and this one is genuinely reusable. One, find your precedence clause in any vendor agreement you hold, read it, and then check where your last negotiated win was actually recorded. That is often an uncomfortable five minutes. Two, list your incorporated policies, meaning every URL referenced in an agreement you hold, and download each one today with the date on it. Three, search for the four phrases: then-current list price, updated from time to time, commercially reasonable, and subject to availability, and simply count the hits. Four, write your three, meaning the three clauses you would escalate for at your next renewal, with one sentence each on why. And five, build the issues list template: clause, current wording, requested wording, rationale, status, on one page, because you will use it on every deal from here on.
Five guides, all on redresscompliance dot com. RISE negotiation tactics covers the eight clauses with sample wording and an honest view of what is realistically winnable on each. The RISE with SAP pillar guide gives you the full programme including the document stack from slide four. RISE hidden costs goes into what the service description does and does not cover, in considerably more detail than we had time for. SAP contract terms to watch expands slide eleven, so the language patterns and the replacement wording to ask for. And the RISE pricing benchmarks are there so you can tell whether the commercial terms you have been offered are actually competitive, which is hard to judge from inside a single deal.
That is session twenty five, and the end of module five. The thing to take away is that the deal is the paper, so read the precedence clause first and fight for mechanisms rather than amounts. Next time, module six opens on BTP. See you then.