Term, ramp, co-termination, auto renewal and the uplift clause. 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 one, and this opens module five on the agreement itself. We have spent twenty sessions on metrics, definitions and measurement, and all of that work is settled by a short document that most organisations read for the total and then sign. Everything we have established, peak or average, what counts, when it is measured, is either written on the order form or it is not agreed. So today: the seven lines that carry nearly all the risk and none of which is the price, the uplift clause and why it usually beats a discount, term, ramp and co-termination, and the renewal mechanics that decide whether you get a negotiation at all. Three knowledge checks. Let's begin.
Five objectives. First, read an order form properly, because seven lines carry nearly all the risk and none of them is the price. Second, value an uplift cap correctly, since it usually beats a larger discount and is easier to win. Third, use term and ramp deliberately, because length is a currency and a ramp matches spend to adoption rather than to ambition. Fourth, control the renewal mechanics, where auto renewal and the notice window decide whether you have a negotiation at all. And fifth, understand the quantity floor: what you committed to, and why counts go up and rarely come back down.
So, the document that decides. It is short, often two pages, which is why it gets read for the number and little else. It is binding, and it incorporates terms by reference, and those terms can move when the order form does not. It sets precedent, because whatever it says becomes the baseline for every renewal that follows. And it is fixable once: before signature it is a conversation, and afterwards it is a concession request. Let me explain why two pages outrank everything else we have discussed.
Guest analyst clip.
If it is not there, it is not agreed. Which means every definitional question from this course belongs on this document: peak or average, what counts as a contact, when a conversation starts, which version of the Product Terms applies. All of it, on the order form.
Right, seven lines to read before anybody looks at the total. Term: how long, and when exactly it starts, and you want a start date tied to availability rather than to signature. Uplift: what happens to price at renewal, and you want a stated cap covering every line rather than just the largest. Quantity: what you have committed to per line, a number you can evidence, with a stated reduction right. Ramp: whether the commitment steps up over the term, matched to the adoption plan rather than to the ambition. Co-termination: do added lines end with the master term, and yes is the answer you want. Renewal: automatic or not, and the notice period, with a window you can actually meet. And terms referenced: which documents bind you, pinned to a dated version rather than a live page. None of those is the price, and all of them are worth more than a point of discount over three years.
First knowledge check. Over a three year term, which is usually worth more? A, two additional points of discount. B, a capped uplift at renewal. C, extended payment terms. D, a larger implementation credit. Pause here and pick an answer before you continue.
B. A discount applies once to a known number, while an uplift cap applies to every year that follows and compounds, so across three years and the renewal beyond it the cap is usually the larger figure, and it protects you at the moment your leverage is weakest. A is what gets celebrated internally because it is visible on the day. C is a treasury benefit rather than a licensing one. And D is a one off contribution to a project, and it is very often the thing offered instead of the cap, which tells you which of the two the other side values more.
So, the uplift clause, and I would call it the single most valuable sentence in the document. Silence means no protection, because with no clause the renewal price is whatever is proposed at the time. A cap is a number rather than a principle, meaning a stated percentage ceiling, and anything softer is an intention. It must cover every line, because a cap on the subscription but not the add ons leaves the growing part uncapped. Ask what it applies to, unit price or total, because a capped rate applied to a grown quantity is not a capped bill. And it is easier to win than discount, because it costs the account team nothing in the current year. Let me expand on that last point, because it is the practical one.
Guest analyst clip.
Which brings us to term, ramp and co-termination. Longer term, better rate, is the standard trade, and it is real, and it costs you flexibility you may well need. A ramp matches spend to adoption, lower in year one and higher later, at the same total contract value.
Co-termination protects leverage, so additions end with the master term rather than starting their own clock, and without it the estate fragments into six renewal dates a year, none of them large enough to be worth preparing for properly. And check start dates, because a term beginning at signature can burn months before anybody can log in.
Second knowledge check. You add a product mid term. What should the order form say about its end date? A, a fresh three year term for the new product. B, co-terminated with the existing master term. C, a rolling annual term for flexibility. D, whichever gives the best unit price. Pause here before you continue.
B. Leverage is concentration, so everything landing on one date gives you one negotiation that matters, while separate dates create a series of small conversations you cannot prepare properly for. A is what happens by default, and it quietly extends your commitment beyond the master term. C sounds flexible, gives away the term discount, and still fragments the calendar. And D is a reasonable instinct that trades a structural advantage for a rate, and a slightly better price on a badly timed line is a poor exchange.
Now auto renewal and notice, which is the clause that decides whether you negotiate at all. It is automatic unless you act, so most agreements renew themselves, on their terms, with no conversation required. The notice window is short, often measured in months before term end, and it is very easy to miss quietly. Missing it removes your options, because you are renewed and any change afterwards becomes a favour rather than a negotiation. So the date belongs in a system, not in somebody's head and not in an email folder. And work backwards from it, because the notice date is the deadline and preparation starts many months earlier. Let me be specific about how this actually gets missed.
Guest analyst clip.
Somewhere with an alarm on it, owned by a role rather than a person. That is the whole control, and it is administratively trivial, which is exactly why it keeps not happening.
A word on the quantity commitment, and why counts go up and rarely come back down. The commitment is a floor: you may add above it freely, and going below it is a contractual question rather than an operational one. Additions raise the floor, because a mid term true up frequently becomes the new minimum at renewal. Reduction rights are rare by default, so if the document is silent then the answer at renewal is usually no. Which is why you ask for a reduction band, a stated percentage you may reduce at renewal without renegotiating the entire agreement. And evidence it all term, because a reduction request either arrives credible or it does not arrive at all.
Five failures. Read for the total, where the number is checked, the seven lines are not, and the signature looks the same either way. Terms incorporated by live link, so referenced documents that can change without your agreement or your knowledge. No uplift clause at all, because nobody asked, because nobody expected renewal pricing to be a subject. The notice date nowhere, known to one person who has since changed role. And definitions left out, so every measurement question from this course agreed verbally and recorded nowhere at all.
Last knowledge check. The order form references Product Terms by a web link. What should you ask for? A, nothing, referenced terms are standard practice. B, the dated version attached, so it cannot change under you. C, removal of the reference entirely. D, a summary of the terms in an email. Pause here and pick an answer before you continue.
B. A live link means the document you agreed to can be revised by one party without notice, and product definitions live in exactly those pages, so pinning the version is how every definition in this course stays agreed. A is true as a description of practice and it is not a reason to accept the risk when the fix is purely administrative. C will not be accepted and it is not necessary. And D has no contractual force at all, and a summary in an email is precisely the kind of comfort that evaporates at the moment you need it. Let me set out the review itself.
Guest analyst clip.
One hour, before signature, every time. Read the seven lines aloud, in a room, with the person who will own the renewal present, because reading aloud catches what skimming does not. Check the definitions are present: peak or average, what counts, when measured, and missing means unagreed. Record the notice date immediately, in the system, with the owner named, on the day the document is signed rather than at some point afterwards. Log the referenced versions: which documents, which version, dated, stored alongside the order form. And write the renewal position now, one paragraph on what you will want at the end of the term, because it ages remarkably well and it is much harder to write later.
Three sentences. The order form is a short document that outranks every analysis in this course, because every definitional question we have raised, peak or average, what counts, when it is measured, is either written there or is not agreed at all. Seven lines carry nearly all the risk and none of them is the price, and a capped uplift is usually worth more over a term than two additional points of discount. And auto renewal and the notice window decide whether you get a negotiation at all, so the notice date belongs in a system with an owner on the day you sign, and the quantity you commit to is a floor that rises with every addition unless you negotiate a reduction band.
Homework before session twenty two, about two hours. One, read your current order form, all of it, checking the seven lines specifically rather than the total. Two, find the uplift clause, and if there is none, write that down, because it is the most valuable ask you have available. Three, find the notice date, then check whether it exists anywhere other than in the document itself. Four, list the referenced documents and whether each is pinned to a version or points at a live page. And five, check co-termination by mapping every line's end date, then count how many separate renewal dates you are currently holding.
Five guides, all on redresscompliance dot com. Salesforce contract terms, ten clauses, works through the clauses that decide outcomes line by line. Salesforce auto renewal covers the renewal mechanics, the notice window and how to keep control of it. The Salesforce renewal timeline works backwards from the notice date month by month. Salesforce minimums and true ups covers the quantity floor and why counts rarely come down. And the Salesforce negotiation CIO playbook places these clauses inside the wider negotiation.
That is session twenty one. The thing to take away is that all the analysis in the world is worth nothing if it does not end up on the order form, and the seven lines you should be reading are not the ones anybody points at. Next time, the SELA: what a Salesforce Enterprise License Agreement actually is, when it genuinely fits, and the traps sitting inside it. See you then.