Mergers and divestitures reliably trigger entitlement questions, and the agreement you signed describes a company that no longer exists. Three knowledge checks along the way, and 3 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. 3 times in the session the frame splits and a senior licensing analyst gives the view from inside real ServiceNow 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 seven, and today we take the events that break everything we built last time. Mergers, divestitures, new entities, restructuring. And the framing I want to give you at the start is this. Every clause you negotiated assumed a shape. This many employees, these legal entities, that geographic footprint. A corporate event changes the shape and leaves the clause exactly where it was. And organisational change reliably triggers entitlement questions, which means this is a known trigger rather than bad luck. So a merger or a divestiture is a licensing event whether or not anybody ever mentioned it to the licensing team, and in most organisations nobody does, because the licensing team is not on the deal distribution list. Three checks, homework, let's go.
Five objectives. First, expect the question, because organisational change reliably triggers entitlement questions from the vendor side. Second, handle an acquisition, the inherited tenant, the duplicate fulfillers, and the integration backlog decision that belongs at deal close rather than at the first joint renewal. Third, handle a divestiture, where the seats go, what transition services actually commit you to, and why a reduction needs a contractual route rather than goodwill. Fourth, read the entity definitions, because affiliate and subsidiary language written years ago decides what a newly acquired company may legitimately use. And fifth, sequence to the renewal, which is session twenty four's rule generalised, because the saving lands at the contract signature, so the corporate event and the renewal belong on one plan rather than two.
Four framings. Reliably, which is how often mergers and divestitures trigger entitlement questions, and I want that word to land because it means this is predictable rather than unlucky. Twelve to twenty percent, duplicate fulfillers across a multi tenant estate, which is precisely what an acquisition creates on the day it closes. Twenty to forty percent, the credit on a retiring tenant's book when it is negotiated into the surviving contract, and zero when it is left in an email. And month eighteen, which is when duplicate licensing and duplicate platform cost usually become visible, and notice that is the first joint renewal rather than the deal itself. The note underneath is the pattern, and it is one you now know well. Growth from an acquisition arrives automatically and gets billed. Reduction from a divestiture requires a contractual right that somebody negotiated in advance, probably years earlier.
Guest analyst clip. There is a structural reason licensing gets handled badly during corporate events, and it is not that anybody is careless. It is that the people who know about the deal and the people who know about the contract are deliberately kept apart. An acquisition is confidential until it is not. The team working on it is small, it is legal and finance and corporate development, and the licensing or vendor management person is not on that list, quite correctly, because there is no reason to widen a confidential deal to include somebody who is not needed. So the first time vendor management hears about an acquisition is very often the day it is announced, which is also the day it closes, and by then every decision that would have been cheap has already been made. What I suggest, and I have seen this work without breaching anything, is a standing item rather than a specific one. Corporate development gets a one page checklist that says, for any transaction, here are the five software questions to ask, and here is who to call once you can. Nobody has to be told what the deal is. They just have to know that a call is needed at close rather than at the next renewal, and that single page has saved clients more than most negotiations I have run.
A one page checklist with corporate development, so nobody needs to widen a confidential deal and somebody still makes the call at close. Now, what actually arrives with an acquisition.
Four things you inherit. Their instance, which by default runs untouched and outlives every integration plan ever written to retire it, and the move is to put it on the integration backlog at deal close rather than at the first joint renewal. Duplicate workers, where the same person ends up holding a full price seat in both tenants, invisible to either one, and the move is an identity match across tenants which no single instance can produce for you. Their contract, which renews on its original terms, on its own date, with its own uplift, and the move is to map both agreements onto one calendar before either of them renews unnoticed. And their consumption, their assist pool, their tables, their connectors, all now yours to account for, and the move is to add them to the baseline in the quarter the deal closes. The note is the reason acquisitions are the largest single driver of tenant sprawl, which is that identity and finance integrate first and the platform tenant gets deferred. The counter move costs you nothing at all.
Now divesting, which is the direction that goes wrong more quietly. Headcount leaves and the commitment does not, which is exactly what session twenty nine's M&A adjustment clause exists for, a pro rata reduction of committed ACV when people leave the enterprise. Without that clause you are funding the buyer, because you keep paying for seats now being used by a company you no longer own, until a renewal eventually gives you a route to reduce. Transition services are a licensing commitment, so if you agreed to run their service desk for twelve months then you agreed to license it, and that belongs in the deal model rather than in the surprise column eight months later. Per employee products move differently, because HRSD prices on the workforce, so a divestiture should reduce it immediately, and that only works if the definition from session nineteen was actually written down. And the timing is the same rule as always, a reduction recognised at a contract signature, so the divestiture close date and your renewal date belong on the same page.
Knowledge check one. You divest a division of four hundred people mid term. What happens to your ServiceNow commitment? A, it reduces automatically, the users are gone. B, nothing, unless an M&A adjustment right was negotiated in advance. C, it reduces at the next quarterly true up. D, it transfers to the buyer automatically. Pause here, and ask which direction adjustment runs by default.
The answer is B, nothing happens without the right. This is session twenty eight's asymmetry applied to a corporate event, that growth is handled automatically and reduction requires a right, so a commitment signed for a company of one size does not shrink simply because the company did. Answer C misreads what a true up is, because a true up counts consumption above entitlement and it has no mechanism for counting below it. Answer D assumes contracts follow business units, and they follow the signing entity, which is why a divested division walks away and the bill stays with you. And the clause itself is cheap at signature and close to unobtainable in the month a deal actually closes, which is the pattern for this whole session.
Entities, and who is actually covered by your agreement. Four cards. The affiliate definition, typically keyed to ownership or control thresholds, where a majority owned acquisition may be covered automatically while a joint venture usually is not. Why it matters at close, because if the target is covered then they can use the platform from day one, and if they are not then their people using it is unlicensed access rather than a head start. Regional and data residency, which is session twenty four's driver, where a separate instance for a regulated region is compliance rather than sprawl and survives consolidation for entirely good reasons. And per employee products again, because HRSD's workforce definition decides whether an acquisition adds to your licensed count on day one or at the next renewal, and you want to know which before you close rather than after. Now the note, which is the encouraging part. This is the one part of a corporate event where the answer is already written down. Somebody just has to read the definition, and reading it takes an hour.
Knowledge check two. You acquire a company and give its staff platform access on day one. What should you have checked first? A, nothing, an acquisition is part of your enterprise. B, the affiliate definition, because coverage depends on ownership thresholds written into your agreement. C, only whether you have spare seats. D, whether their systems are compatible. Pause here, and ask whether the new company is actually a party to your contract.
The answer is B, the affiliate definition. Coverage is a contractual question rather than an organisational one, so whether the new entity may use your platform depends on how affiliate is defined and whether the ownership structure meets that definition, and a majority owned subsidiary and a joint venture very frequently land on opposite sides of that line. Answer C is the right second question and the wrong first one, because having spare seats does not license an entity that sits outside your agreement, and that distinction is exactly the kind of thing that surfaces in a review two years later. The check takes an hour, and the alternative is unlicensed access that accrues quietly until somebody else finds it.
Four clauses that carry you through a corporate event. The M&A adjustment, a pro rata reduction of committed ACV when headcount leaves the enterprise, and it is the only clause that makes a divestiture commercially neutral rather than expensive. The affiliate definition, broad enough that a majority owned acquisition is covered, and explicit about what happens when an entity leaves, because most definitions handle arrival and say nothing about departure. The credit recognition language from session twenty four, where a retiring tenant's book returns twenty to forty percent inside the surviving order form and nothing at all in an email. And the reallocation right from session twenty eight, the swap right, which is what lets a changed business move committed dollars sideways rather than duplicating them. And then the fifth point, which is session thirty four's rule. Every one of these is drafting at first signature and a concession request during a live deal, when nobody has the time and you have no leverage at all.
Guest analyst clip. The divestiture case is the one that makes people angriest when they discover it, and I understand why, because it feels wrong in a way the other findings do not. You have sold a division. Four hundred people are no longer your employees, they work somewhere else now, they are on somebody else's payroll, and you are still paying for their software. And when the customer raises this, entirely reasonably, the answer they get is that the committed ACV is committed, which is contractually correct and emotionally infuriating. What I would say about it is that the anger is aimed at the wrong moment. Nothing unfair happened at the divestiture. What happened is that three years earlier somebody signed a commitment with no adjustment mechanism, at a point where adding one would have cost essentially nothing, because at signature it is a paragraph and the account team can approve it as a term. The lesson is not that vendors are unreasonable about divestitures. The lesson is that a multi year commitment is a bet that your company will still be roughly this shape, and companies of any size change shape all the time. So if you are signing anything longer than a year, ask what happens if the business gets smaller, because somebody eventually will need that answer.
A multi year commitment is a bet that your company will still be roughly this shape, and companies change shape all the time. So ask the question at signature, when it costs a paragraph. Now the sequencing.
Putting the event and the renewal on one plan, four stages. At deal close, the platform tenant goes on the integration backlog, the affiliate definition gets checked, and the licensing consequence is written into the deal model rather than discovered eighteen months later. Within the first quarter, an identity match across tenants to find the duplicates, and both contracts mapped onto one calendar so that neither of them renews unnoticed, which happens more often than you would think. Before the surviving renewal, the credit language drafted, and the consolidation sequenced so that the retirement lands on the renewal you are already negotiating anyway. And carried into the baseline, which is session thirty six's standing document updated in the quarter the deal closes, so that your estate never contains an entire company that nobody counted. Session thirty eight turns to what happens when the vendor asks the entitlement question before you do, which is the compliance review.
Knowledge check three. When should the ServiceNow consequence of an acquisition be worked out? A, at the first joint renewal, when both contracts are visible. B, at deal close, because the tenant, the duplicates, and the affiliate question all start costing money immediately. C, after the identity systems are integrated. D, once the acquired business is fully absorbed. Pause here, and ask what is running, and being billed, from day one.
The answer is B, at deal close. And I want to be blunt about answer A, because it is what actually happens in most organisations, and it is roughly eighteen months too late. The inherited tenant runs untouched, duplicate seats bill from day one, and any unlicensed access by an entity outside your affiliate definition accrues quietly the entire time. Answers C and D both describe sensible integration sequencing that has nothing whatsoever to do with when the licensing clock starts, and that is precisely the confusion that causes the delay, because software feels like a phase three problem and the billing does not agree. The counter move is free. Put the platform tenant on the integration backlog at deal close, alongside identity and finance, and the rest follows.
Four moves for a company that changed shape. One, read the definitions, affiliate, subsidiary, and workforce, written years ago, decisive on the day, and readable in an hour by somebody who knows to look. Two, match identities early, because duplicates are invisible from inside either tenant, so somebody has to deliberately look across them and nobody does that spontaneously. Three, write the credit down, in the surviving order form, because a retiring book returns twenty to forty percent when negotiated and nothing when agreed verbally. And four, land it on a signature, because the reduction is recognised when a contract is signed, so you sequence the event to the renewal you are already negotiating. And then negotiate the M&A adjustment before you need it, because in the month a deal closes nobody has the time or the leverage to obtain it, and that is exactly when everybody wishes they had it.
Guest analyst clip. If there is a single habit I would give any large organisation out of this session, it is to add software to the deal checklist, and I mean the actual checklist that corporate development runs, not a policy document somebody writes and files. Because think about what is already on that list. Property leases are on it. Employment contracts are on it. Insurance is on it. Somebody checks all of those as a matter of routine during any transaction, because at some point somebody got caught and the item got added. Enterprise software is almost never on it, despite being, for a lot of companies, a larger annual commitment than several of the things that are. And the questions are not complicated. Does the target have their own instance. Are we covered to give their people access. What is our exposure if the workforce changes size. Who is going to own retiring their tenant, and by when. Four questions, they take a morning, and they can be asked by somebody who knows nothing about licensing as long as they know to ask them. I have never yet met a corporate development team that objected to adding them, because their job is to find exactly this kind of thing before it becomes somebody's problem. They just did not know it was a category.
Get software onto the actual deal checklist, next to property leases and insurance, because it is a larger commitment than several things already on it. Session thirty eight takes the compliance review, how it gets triggered, what it checks, and how you answer from your own numbers rather than theirs.
Three sentences. Mergers and divestitures reliably trigger entitlement questions, because every clause you negotiated assumed a company of a certain shape and a corporate event changes the shape while leaving the clause exactly where it was. Acquisitions bill from day one through the inherited tenant, the duplicate workers holding a full price seat in two places at once, and the affiliate definition that decides whether the new entity may use the platform at all. And divestitures reduce nothing unless an M&A adjustment right was negotiated in advance, because growth is automatic and reduction needs a contractual route, and the reduction lands at a contract signature rather than at the deal close.
Homework, about an hour, five items. Read your affiliate definition, find out what ownership threshold it uses, and work out whether your last or your next acquisition would sit inside it, because that is an hour that occasionally saves a very great deal. Check for an M&A adjustment, which is almost certainly absent, and add it to the first signature list from session thirty four, because it genuinely cannot be obtained in the month you need it. List your corporate events, acquisitions and disposals over the last three years, and for each one ask what happened to the licensing, and expect several blanks and do not be alarmed by them. Find any inherited tenant and establish whether it is on an integration backlog or simply waiting for a renewal to notice it. And check the workforce definition, because if you hold a per employee product you want to know whether the contract says anything at all about what happens when the workforce grows or shrinks by acquisition.
Five guides. Consolidate ServiceNow instances covers the acquisition side in full, the inherited tenant, the duplicate fulfiller arithmetic, and the credit mechanic in the surviving contract. Multi-year term length as currency is where the M&A adjustment clause is actually drafted, alongside the step down right and the other exit provisions, so it is the one to hand to legal. The ServiceNow license audit guide explains why organisational change is a known review trigger, which is the bridge straight into next session. The eight clauses contract analysis has the clause set that carries a changed company through and why every one of them is a first signature item. And the HRSD licensing guide covers the per employee product where a corporate event moves your licensed count immediately, with the workforce definition that governs it. Next time, compliance reviews and audit defence. See you there.