Account teams, partners, roadmap pressure and the annual calendar. 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 thirty nine, the last one before the capstone, and today is the relationship that runs between the negotiations. Because most licensing damage does not happen in a negotiation. It happens in ordinary conversations across an ordinary year, where nobody thought a position was being established. Today: how to read the account team's incentives accurately, what to share and what to hold, how to handle roadmap pressure, where partners fit, and the annual calendar that keeps you informed. Three knowledge checks. Let's begin.
Five objectives. First, read the incentives accurately, because your account manager has targets and a product mix, and understanding that is accuracy rather than distrust. Second, decide what you share, since plans and constraints are two different things and one of them funds their quota. Third, handle roadmap pressure, separating the technical timetable, which is real, from the commercial urgency, which has a quarter end. Fourth, place partners correctly, taking the technical advice seriously and the licensing advice as an input rather than an answer. And fifth, run your own calendar: four quarters, four activities, so that every conversation happens when you are informed.
Four things to frame it. Years rather than deals, because you will work with this vendor for a decade and every year is a chapter of one long negotiation. Different interests, which are not opposed and not aligned, and naming that honestly makes the relationship more useful rather than less. Information is currency, since what you disclose casually in March shapes what you are offered in December. And predictability pays, because being reliable and straightforward buys you more than being difficult ever will. Let me be direct about the incentives, and I do not mean this cynically.
Guest analyst clip.
Much more durable than friendliness. That is the standard I would aim for, and notice it asks something of you as well: accurate information, early warnings, and no surprises in the other direction either.
So who is actually in the room? Four roles. The account executive owns the number and the relationship, with targets on total spend and usually on specific product lines. Solution or product specialists are brought in to build the case for a particular product, and they are genuinely knowledgeable and genuinely pointed. The licensing and commercial desk is where structures and approvals actually live, and they are often the people who can say yes to a term you want. And compliance and audit is a separate function with its own mandate, as session thirty one covered, which is a different conversation under different rules. When a specialist appears in a routine meeting, a campaign has started, and that is worth noticing early rather than three months later.
First knowledge check. Your account manager asks when your S four HANA project will start. What is the best answer? A, the real target date, since honesty builds the relationship. B, an accurate statement of status without committing to a date you would not want quoted. C, refuse to discuss internal plans. D, an earlier date, to see what they offer. Pause here and pick an answer before you continue.
B. Honest and unspecific is a real option and it is the professional one: evaluating, no approved business case yet, we will tell you when there is. A hands over your deadline, which session thirty seven identified as free leverage, and it will be in their forecast within the hour. C damages a relationship you need and signals more than you think. And D is a bluff that gets tested, because inventing a date you do not have costs you credibility for years afterwards. Be truthful about status and unhurried about dates.
Which brings me to what you share. Five pairs. Share your current status, hold your internal deadlines, because a date becomes their close plan. Share what you value, hold your budget figure, since a budget is a price the moment it is known. Share genuine blockers, hold board approval timing, because approval dates set the vendor's pressure calendar. Share a clear no, hold which alternative you prefer, since preference reveals how real the alternative is. And share adoption reality, hold internal disagreement, because division invites a campaign aimed at the weaker view. Notice that the left column is substantial: being informative is not the same as being transparent about everything, and good vendors respect the distinction.
Now roadmap pressure, five points. Maintenance end dates are real, and they are also published, usually years out, and often with extended options behind them, so check the date yourself. Innovation only on the new platform is frequently true, and the question is whether you need that innovation on their timetable or yours. Products in maintenance mode are worth knowing about for planning and are not usually a reason to move this quarter. Verify against published sources, because a slide in a meeting is not a commitment while published lifecycle dates are checkable and stable. And separate the two clocks, since technical necessity has a timetable measured in years and commercial urgency has one measured in quarters. This deserves a clear head.
Guest analyst clip.
The first one has a real timetable and the second one has a quarter end. Both are legitimate, incidentally. The vendor is entitled to want the deal this quarter. You are simply entitled to notice which clock is being shown to you.
Second knowledge check. You are told mainstream maintenance for your version ends soon and you should move now. What do you do first? A, start the migration programme, since the date is fixed. B, check the published lifecycle dates and what extended options exist. C, ignore it, since these dates always move. D, ask for a discount to fund the migration. Pause here before you continue.
B. Lifecycle dates are published and checkable, and the gap between what a meeting implies and what the published date says is often years, which changes the decision entirely. A commits a large programme on the basis of a conversation. C is the opposite error and it is genuinely risky, because running unsupported is a real operational exposure even when dates shift. And D negotiates before establishing whether the premise holds, which is session thirty three's mistake in a new setting. Verify the timetable, then decide whether you are moving because you need to or because you were asked to.
Right, partners, five points. They have vendor relationships: partnership tiers, targets and certifications, which is normal and gives their advice a direction. They design your interfaces, which means they shape your document volume from session thirty three, often without pricing it. They frequently advise on licensing, so take it as an input while the named owner from session thirty five makes the decision. Resellers add a margin and add value, both of which are real, so know which one you are paying for and compare direct where you can. And ask about licensing at design time, making it a required output of the design phase so the question gets answered while changes are still cheap. Let me be fair about this, because good partners are valuable.
Guest analyst clip.
Advice from them, decision from you. That is the whole rule, and it is not a criticism of anybody. It is simply that the person who owns the consequence should own the decision.
So, a year that works, four quarters and one constant. Q one, measure: run your own measurement, update the entitlement register, know your position before anybody asks. Q two, review adoption: what is used, what is shelfware, and what the business genuinely wants next year. Q three, prepare: renewals ahead, alternatives costed, term sheet drafted, internal agreement on what a good outcome looks like. Q four, transact or do not, because it is their year end, so buy if the terms are right and be entirely comfortable waiting if they are not. And all year, one channel: a named owner, a written record, and no commitments made in corridors.
Five traps. Treating courtesy as agreement, because a pleasant meeting is not a concession and a helpful specialist is still running a campaign. Multiple channels, since different people giving different signals is how a vendor learns what you will accept. Disclosing the budget, because say a number and it becomes the price, and this happens more often through helpfulness than through pressure. Outsourcing the licence decision to a partner, a specialist or the account team, when what you want is advice from all three and the decision from you. And being adversarial, which costs you information, goodwill and escalation paths, and wins nothing at all.
Last knowledge check. What most improves your position across a ten year vendor relationship? A, negotiating hard at every renewal. B, being informed, predictable, and running your own calendar. C, keeping the account team at arm's length. D, building a strong personal relationship with your account manager. Pause here, and think about what compounds over ten years.
B. Those three compound: information means you cannot be told what you need, predictability makes you someone worth dealing with straightforwardly, and your own calendar means you are never negotiating on somebody else's timetable. A wins individual rounds and slowly makes you expensive to deal with, which costs you the early warnings and the flexibility. C removes information you need and escalation paths you will want. And D is pleasant and it is not a position, because account managers change every couple of years and the agreement does not. Let me show you what that calendar looks like.
Guest analyst clip.
Where the vendor's calendar is the only calendar in the room. So, five things for running it year after year. Keep a relationship log of meetings, claims made and commitments given on both sides, because memory is not a record and people move on. Brief anybody who meets them, with one page covering what we say, what we do not, and who to route questions to. Ask for the roadmap in writing, annually, with dates you can check, so planning rests on published facts rather than meeting notes. Review partner advice separately, with the technical recommendation and the licensing consequence assessed by different people. And hand over properly, so when the owner changes the log, the register and the term sheet go with the role.
Three sentences. Your account team are professionals with targets rather than adversaries or advisors, so read the incentives accurately, be genuinely useful and predictable, and expect the same directness in return. Roadmap pressure arrives as helpfulness and mixes a real technical timetable with a commercial one, so verify lifecycle dates against published sources and decide whether you are moving because you need to or because you were asked to. And run your own annual calendar, measuring in Q one, reviewing adoption in Q two, preparing in Q three and transacting in Q four only if the terms are right, because the organisations that struggle are the ones where the vendor's calendar is the only calendar in the room. Next time is the capstone, where we take one estate end to end and put the whole course together.
Homework before session forty, about an hour, and the last item matters more than the others. One, map the account team: who covers you, in what roles, and which product lines they carry, because ten minutes of asking gets most of it. Two, check one roadmap claim, taking something you were told and finding the published date, then note the gap if there is one. Three, write the one page brief on what anybody in your organisation should and should not say to the vendor. Four, draft your calendar, four quarters and four activities, in the diary, because that is the artefact that makes the rest habitual. And five, bring your estate to session forty, because the capstone works one estate end to end and it is far more useful with your own numbers beside you.
Five guides, all on redresscompliance dot com. Managing the SAP account relationship covers account teams, information discipline and the annual rhythm, which is the reference version of today. SAP roadmap and lifecycle dates covers what is published, what is implied, and how to tell them apart. Working with SAP partners goes into implementers, resellers and where their incentives point. SAP negotiation and the fiscal calendar is session thirty seven's reference, which is the transaction at the end of the year. And the SAP licensing operating model is where session forty lands, so the whole course applied to one estate.
That is session thirty nine. The thing to take away is that the relationship is a decade long negotiation conducted in ordinary conversations, so be informed, be predictable, and run your own calendar. Next time, the capstone. See you then.