The Licence Separation Problem
When a business unit is divested, the software that unit was using — including Autodesk products — doesn't automatically come with it. What transfers in a divestiture is the business, not necessarily the contracts that supported it. Autodesk agreements are held by the parent legal entity. Named Users are registered in the parent's Autodesk Account. The divested unit has no independent Autodesk relationship at close.
This creates an immediate post-close problem. The divested entity's workforce needs Autodesk software to operate from day one. Without a planned separation, they will either use the parent's licences under a TSA (creating compliance complexity), purchase new licences at standalone pricing (at a significant cost premium), or go without — none of which is satisfactory without active management.
The parent faces its own complications. If the EBA or volume agreement was sized to include the divested unit's user count, the parent is now paying for licences it no longer needs. This represents stranded spend until the next renewal — and represents missed leverage for a downward renegotiation. At the same time, if the parent continues to provision access for divested-entity users under its existing agreement during the TSA period, it may be inadvertently violating its own agreement terms, which require Named Users to be employees or contractors of the contracting entity.
Separation Mechanics by Licence Type
Each Autodesk licence type has different mechanics for divestiture separation. Understanding these mechanics before close is essential — the correct approach varies significantly, and some approaches that seem operationally convenient create serious compliance exposure.
Designing an Effective Autodesk TSA
The Transition Service Agreement is the bridge between close and full separation. For Autodesk software, the TSA must be more precisely scoped than most IT service agreements — generic "software access" language creates compliance exposure that will be discovered eventually, typically during an audit.
Define the exact product scope. The TSA should list each Autodesk product the divested entity will access during the transition period, not just reference "Autodesk software." As the divested entity stabilises its workforce post-close, specific products may no longer be needed. A product-level scope enables precise billing and prevents over-provisioning.
Cap the Named User count. The TSA should specify the maximum number of Named Users the divested entity may provision under the parent's agreement during the transition period. This protects the parent from compliance exposure if the divested entity grows, and gives Autodesk a clear basis for any audit review of the TSA period.
Set a hard end date with 90-day warning trigger. TSAs for Autodesk access should not roll indefinitely. An 18–24 month maximum term with a 90-day notice trigger forcing the divested entity to initiate standalone procurement is the standard framework. Without a hard end date, TSA dependency persists long past the period where it was operationally necessary, and standalone cost modelling never gets tested against reality.
Charge at cost, not zero. A common error is treating Autodesk software within the TSA as a zero-cost service — the parent "already paid for it." This creates several problems: it obscures the divested entity's true Autodesk cost baseline, creates accounting complexity, and may require true-up against the parent's actual Autodesk spend at TSA close. Charge at a per-user rate reflecting the parent's actual blended licence cost.
| TSA Design Decision | Common Error | Correct Approach | Risk if Wrong |
|---|---|---|---|
| Product Scope | "All Autodesk software" or generic IT services catch-all | Named products by SKU with explicit version scope | Divested entity accesses products not covered by parent agreement |
| Named User Count | No cap; any divested employee may access | Hard cap at agreed headcount; formal process for changes | Over-provisioning triggers parent entitlement violation |
| Duration | Open-ended or rolling monthly | Fixed term (18–24 months max) with hard end date | Indefinite dependency; standalone cost never modelled accurately |
| Pricing Basis | Zero cost or arbitrary flat fee | Per-user rate based on parent's actual blended Autodesk cost | Inaccurate standalone cost model; accounting complications |
| Notification to Autodesk | No notification; TSA not disclosed | Notify Autodesk of TSA structure; confirm it aligns with agreement terms | TSA period access treated as unlicensed use in subsequent audit |
Autodesk Licence Negotiation Handbook
How to structure Autodesk negotiations in corporate restructuring events — divestiture, merger, and standalone transitions. Includes pricing benchmarks for divested entities establishing new Autodesk relationships.
Download White PaperStandalone Cost Modelling
One of the most consistently underestimated line items in divestiture financial modelling is Autodesk standalone cost. The reason is straightforward: Autodesk pricing is highly volume-sensitive, and most enterprise organisations are buying at significantly below-list pricing through volume agreements, EBAs, or multi-year deals. The divested entity starts with none of that purchasing history.
The typical AEC or manufacturing company with 500–1,000 employees buys Autodesk software at 35–55% below list pricing, reflecting volume, tenure, and relationship. As a standalone entity of 200–400 employees, that same organisation would likely pay list pricing or close to it — representing a 50–80% increase in per-unit cost compared to their pro-rata share of parent enterprise pricing.
This delta has meaningful implications for financial modelling. If the divestiture model assumes Autodesk software costs are simply proportional to headcount transfer, the model will materially understate standalone Autodesk costs. The correct approach is to model three scenarios: TSA continuation cost, immediate standalone at current market pricing, and post-negotiation standalone after an aggressive new-relationship negotiation. See our Autodesk Licence Negotiations service for how we support divested entities in establishing competitive standalone pricing.
| Scenario | Annual Autodesk Cost | vs. Pro-Rata Parent Cost | Duration / Condition |
|---|---|---|---|
| Pro-Rata Share of Parent EBA | $680,000 | Baseline | Hypothetical — not available to divested entity |
| TSA Continuation (at parent cost) | $710,000 | +4% | Months 1–18; admin charge included |
| Standalone — No Negotiation | $1,050,000 | +54% | List pricing; typical new-account baseline |
| Standalone — Negotiated (Achievable) | $820,000 | +21% | Multi-year commitment, 3-year lock-in |
| Standalone — Negotiated (Best Case) | $735,000 | +8% | Aggressive negotiation with independent advisory support |
Audit Risk in the Post-Divestiture Period
The 24 months following a divestiture represent a markedly elevated audit risk period for both parent and divested entity. Autodesk's SAM and audit engagement team actively monitors public transaction announcements, and divestiture events are treated as audit triggers in the same way acquisitions are.
The specific risk vectors are different for each entity. The parent faces the risk of residual access — divested entity employees or contractors who retain Named User assignments in the parent's Autodesk Account after close, consuming entitlements the parent is paying for and creating a compliance representation problem. A mandatory Named User reconciliation at close and again at 30 days eliminates most of this exposure.
The divested entity's risk is more acute: it is typically operating under a TSA with imprecisely defined Autodesk access, while simultaneously onboarding new employees and contractors who may access software without formal licence allocation. The 68% compliance issue rate within 24 months of separation reflects this dynamic. Our Autodesk Audit Defence practice engages with both parent and divested entities across this transition period.
Engaging Autodesk Around a Divestiture
Autodesk should be engaged proactively when a divestiture is announced or reasonably certain to close. The commercial framing matters: Autodesk sees a divestiture as two potential sales — the parent renegotiating a smaller agreement and the divested entity establishing a new relationship. Both are leverage points that can be structured to produce better outcomes for both entities if managed proactively.
The parent's leverage is straightforward: reduced volume at next renewal should translate to reduced absolute spend while maintaining or improving per-unit pricing, in exchange for an extended term commitment. The divested entity's leverage is less obvious but real: it is a new Autodesk customer bringing known volume, and Autodesk's sales team is motivated to onboard that customer on favourable terms to establish a long-term relationship. New-customer incentive pricing, extended payment terms, and multi-year rate locks are all achievable with the right negotiating approach.
Neither negotiation should be conducted without independent advisory support. Autodesk's account management and commercial teams are experienced at structuring these conversations to maximise Autodesk's outcome. An independent adviser who has represented multiple divested entities in similar negotiations — and who understands Autodesk's pricing floor and incentive structure — is essential to achieving a genuinely competitive result.
Divestiture with Autodesk Licence Complexity?
Our team supports both parent entities and divested units through licence separation, TSA design, standalone cost modelling, and new Autodesk relationship negotiations. Independent, commercial, and structured around your outcome.