Partner margin, price protection, support quality, and how to run a partner selection or switch without losing continuity. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
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.
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. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle 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 six of forty, and this opens module eight, which is the advanced situations and then the capstone. We start with the partner channel, and I want to open with a fact that surprises most buyers. The partner of record on your CSP subscriptions is a negotiable lever. It can be changed. And in the great majority of estates it has never once been tested, because the relationship arrived with an acquisition or a purchase somebody made years ago and has simply continued since. Now, testing it does not mean switching. Most of the time you will not switch, and that is a perfectly good outcome. But a relationship that nobody has ever compared drifts, and the drift is not usually in price, because New Commerce standardised that centrally. The drift is in service, in expertise, and in how much administrative work quietly moved back to your own team.
Five takeaways. One, where the margin is: the partner buys at one price and sells at another, and understanding that spread makes the negotiation possible rather than adversarial. Two, pricing narrowed and service did not: NCE standardised pricing and promotions centrally, which narrowed partner to partner gaps on price and widened the relative importance of everything else. Three, the band decides the route: sub five hundred seat estates were steered to CSP with EA renewals quietly declined, so for many organisations the choice was made before they arrived at it. Four, growth direction decides the cost: EA price lock saved eight to fifteen percent for estates with rising headcount, while shrinking estates on an EA overpaid by ten to twenty percent against a flexible CSP profile. Five, the partner of record is a lever, rarely tested, and switching is a defined process rather than a rebuild.
How the channel makes money, three sources, and only one of them is the licence. The margin on the licence: the spread between what the partner pays and what you pay, and under NCE pricing and promotions are set centrally, which narrows this gap between partners and makes it a smaller part of the conversation than most buyers expect. Services around it: deployment, managed services, support, migration, advisory, and this is where most partners actually make their money, which is why a licence only relationship gets priced quite differently from a services relationship. And incentives from the vendor: partners earn on the products the vendor is pushing, which is not sinister and does shape what gets recommended, and it is worth knowing when a partner is particularly enthusiastic about something. The practical consequence: a partner earning well on services can be relaxed about licence margin, and a partner earning nothing but licence margin has very little room to move.
Seat band economics, where each route fits and what actually decides it. Under five hundred seats: CSP, usually not by choice, because sub five hundred estates were steered there with EA renewals quietly declined. Large and growing: the EA, for the price lock, which saved eight to fifteen percent for estates with rising headcount over the term. Large and shrinking: CSP flexibility, because shrinking estates on an EA overpaid by ten to twenty percent. Seasonal or volatile: CSP monthly with the premium paid deliberately, since session thirty five showed annual terms locking ten to eighteen percent that could not be released. And mixed, which is most estates: a deliberate blend, which ran eight to fifteen percent cheaper net. Note what decides those rows, because it is not size alone, it is direction. Total cost depends on growth direction rather than on the contract label, so the same sized estate can belong on opposite vehicles.
First check. Two partners quote for the same CSP basket and the prices come back nearly identical. What does that tell you? A, one of them is not trying, and you should push harder on price. B, that NCE standardised pricing centrally, so the differentiation is in service, support, and advisory rather than in the licence rate. C, they have agreed pricing between them. D, you should choose whichever is marginally cheaper. Pause it, and as you think, ask yourself what New Commerce actually changed about how partner pricing gets set in the first place.
The answer is B. Under the New Commerce Experience, pricing and promotions are set centrally, which deliberately narrowed partner to partner gaps, so two similar quotes are the system working as designed rather than a signal about either party. A spends your effort on the dimension with the least room left in it, and it also damages a relationship you may shortly be depending on for support. C is an unfounded and fairly serious accusation to reach for when a much simpler and documented explanation is sitting right there. And D is the most common answer and the most expensive one, because choosing on a marginal price difference means choosing at random on everything that genuinely varies: response times, escalation quality, licensing expertise, and whether they will tell you something you do not want to hear. Compare those instead, and compare them with specifics rather than with claims.
What a good partner does, five things worth more than a point of margin. Tells you what you do not want to hear: that the seats are over tiered, that the connector will change your band, that the commitment is too large, because a partner who only ever agrees with you is a fulfilment channel rather than an adviser. Knows the terms properly: prerequisites, change windows, use rights, and the session thirty five window failure is exactly the sort of thing a good partner raises unprompted. Responds when something breaks, because support quality is the differentiator that matters on the worst day rather than the average one, and it is precisely what a price comparison never captures. Handles the administration: provisioning, reconciliation, true up mechanics, all real work that would otherwise sit with your team. And is honest about their incentives, because a partner who says openly that they earn more on a product is one whose recommendations you can actually weigh.
Guest analyst A client of ours ran a partner selection a few years ago and made what looked like a very rational decision. Three candidates, near identical licence pricing, and one of them came in about one and a half percent cheaper on the licence line. So they chose that one, and on the spreadsheet it was clearly correct. About eight months later I had a call with their licence manager and she was exhausted. And what had happened was not dramatic, there was no disaster, it was an accumulation. Provisioning requests that used to take a day were taking a week, so her team had started doing them directly. Reconciliation reports that the previous partner produced monthly now had to be assembled internally. And when they hit a genuine licensing question, about whether a particular add on could sit on a particular base, the answer came back after eleven days and it was wrong, and they only discovered it was wrong because she checked it against the Product Terms herself. Now I asked her to do one calculation for me, which was to estimate the days per month her team had absorbed. It came out at about three and a half days. Against a licence saving of one and a half percent on their volume, those three and a half days a month cost roughly four times what they had saved. She said something I have used ever since, which was that they had negotiated the only number on the table and ignored the only number that mattered.
One and a half percent saved, three and a half days a month absorbed. Cost the whole relationship, not the licence line. Second check.
Check two. Your partner never raises optimisation opportunities. What does that suggest? A, your estate is already efficient. B, their incentives run the other way, since optimisation reduces the volume they earn on, which is a reason to hold your own analysis rather than a reason to distrust them. C, they are not competent. D, nothing, optimisation is not a partner's job. Pause it, and as you think, ask yourself what happens to a partner's revenue at the moment you decide to buy fewer licences.
The answer is B. A partner earning margin on licence volume has no structural reason to help you buy fewer licences, and that is a fact about the arrangement rather than a criticism of the people in it. Given the reclaim figures from session thirty three, an estate where nobody has ever raised optimisation is very unlikely to be the genuinely efficient one, so A is improbable rather than impossible. C is unfair and usually wrong, because the same partner may be excellent at support and provisioning, which are the things you are actually paying them for. D is a defensible position and it is exactly why your own analysis from sessions thirty two and thirty three has to exist independently of anybody's advice. The mature arrangement is to hold the optimisation work yourself and use the partner for what they are structurally motivated to do well. And where a partner does raise optimisation unprompted, weight that heavily in a selection.
Running a selection, three things to compare that are not price, because price has been narrowed for you and the effort belongs where variance still exists. Support, specified: response times, escalation path, named contacts, and who answers at two in the morning, and ask for the commitments in writing rather than the descriptions, because every partner describes their support in identical language. Licensing expertise, tested: put a real question from this course to each candidate, the connector band change, the NCE window, the Copilot prerequisite, and the quality of the answers separates the field in about ten minutes. And administrative load, honestly costed: what they do and what stays with your team, because a cheaper partner who returns three days a month of administration to you is not cheaper, as the story a moment ago showed. And one question for every candidate: what would you tell us to stop buying.
Switching without losing continuity, what to plan before anybody signs anything. Timing against terms: switching mid term on committed seats is the main hazard, so establish where each subscription sits against its NCE term first. The transfer window: subscriptions can lapse during a move, so get the mechanics and the dates in writing from both partners rather than from one. Support handover: a gap where neither partner is answering is the classic failure, so name contacts on both sides and build an overlap period. Historical records: export entitlement and invoice history before the relationship ends, because afterwards it is somebody else's system. And incumbent behaviour: a rushed exit damages a working relationship, so tell them early, and most behave well while some become genuinely competitive. That last row matters, because a hostile transition is paid for in service quality at exactly the moment you have least capacity to absorb it.
Last check. You want to switch partner but your subscriptions are mid term on annual NCE. What is the position? A, switch immediately, the partner relationship is separate from the terms. B, plan the switch around the term and window structure from session thirty five, because committed terms constrain when a transfer can happen cleanly. C, cancel the subscriptions and repurchase through the new partner. D, wait three years for the next EA renewal. Pause it. The partner and the term are two different things, so the question is which of them actually binds you.
The answer is B. A is half right in a way that causes real problems, because the partner of record genuinely is a negotiable lever and the committed terms still govern the seats, so a switch has to be sequenced against where each subscription sits in its term rather than executed on whatever date suits the commercial conversation. C is the expensive mistake, since cancelling committed subscriptions mid term is precisely what NCE does not permit outside the window, and attempting it produces the session thirty five outcome of paying for seats you no longer have and no longer want. D confuses two different vehicles entirely, because a CSP partner switch has nothing to do with an EA renewal cycle, and waiting three years forfeits the whole benefit for no reason. The workable answer is a mapped plan: which subscriptions can move now, which move at their next renewal point, and an overlap period so support never has a gap.
The partner method, three steps run every couple of years, and not because you intend to switch but because a relationship nobody tests drifts. One, cost the relationship honestly: licence spend, services, and the administration that sits with your team, because that total is what you are comparing and the licence line is usually the smallest interesting part of it. Two, test on expertise rather than price: three real questions from your own estate, put to two or three candidates including the incumbent, ten minutes each, and the answers will differ far more than the quotes do. Three, map the terms before deciding: where every subscription sits against its NCE term and window, so a switch is sequenced rather than attempted, and that is the session thirty five register doing a second job. And tell the incumbent you are doing it, because it is fairer, it usually improves their offer, and it protects the handover if you do move.
Session thirty six, three sentences. One: partner margin comes from licence spread, services, and vendor incentives, and NCE standardised pricing centrally, which narrowed the licence gap between partners and moved the real differentiation to support, expertise, and administrative load. Two: growth direction decides the route rather than size alone, with EA price lock worth eight to fifteen percent to a growing estate while shrinking estates on an EA overpaid by ten to twenty percent against a flexible CSP profile. Three: the partner of record is a negotiable lever that most estates never test, and a switch is a sequenced process against NCE terms and windows rather than a date you choose, with the incumbent told early. Next session is the other structural move available to you, which is the migration from the EA to the Microsoft Customer Agreement, priced honestly.
Homework, about an hour, and this week you cost the relationship. One, total the three parts: licence spend through the partner, services bought from them, and the administration your own team still carries, and that third number is the one people never estimate. Two, write three test questions from your own estate, a prerequisite, a change window, a band trigger, and you now know the answers yourself, which is exactly what makes them useful as tests. Three, ask the stop buying question: put it to your incumbent this month, what would you tell us to stop buying, and note both the answer and how long it takes to arrive. Four, map the term positions from your session thirty five register: which subscriptions could move partner today and which are locked until a renewal point. Five, check the exit basics: could you export your entitlement and invoice history today if the relationship ended tomorrow.
Five reads before next session, all free on redress compliance dot com. First, CSP against the Enterprise Agreement, which carries seat band economics, partner margin, and migration timing. Second, navigating Microsoft's shift to CSP and NCE, on what standardised pricing changed and, just as importantly, what it did not. Third, the Australian telecommunications CSP optimisation case study, which works the blend and flexibility argument through on a real estate rather than in the abstract. Fourth, the CIO level playbook on evaluating renewal proposals across EA, MCA, and CSP, for the same basket priced across all three routes. And fifth, the Microsoft licensing guide, for where the channel sits inside the wider programme picture. Next session is migrating EA to MCA-E: the mechanics, the timing, what you lose, what you gain, and how to price the move honestly. See you there.