Run the methodology with a senior advisor.
A senior Admodum advisor will walk the methodology through with your CIO, engineering, IT services or procurement team on a private call. Engagements run as fixed fee, contingency or annual retainer.
Twenty-two pages on the named-user construct; the Premium plan uplift and the SSO contestation; the Flex token pool break-even arithmetic; the AEC Collection and Manufacturing Collection scope; the maintenance-to-subscription migration; the True-Up Agreement audit posture; and the renewal cycle inside the Autodesk subscription envelope.
Autodesk subscriptions are sold on a named-user basis. Each subscription enrols a single identified user, with device-independent activation across the user’s desktop, laptop and supported mobile clients. The named-user is the unit and the population of named users is the load-bearing input to every Autodesk procurement conversation.
The shift from concurrent-licence and serial-number activation (which sat at the heart of the legacy AutoCAD estate) to named-user subscription was completed across the principal Autodesk products by 2022. The procurement implications are direct: the named-user count is the procurement input; the deployment-activity record is the audit input; the named-user reconciliation against role-types is the renewal input.
The Admodum methodology reads the named-user population by role-type rather than by department. A CAD-using designer carries different subscription requirements than a project administrator who occasionally opens a Revit model; the role-type framing produces a defensible procurement position; the department framing produces an inflated commitment. This paper sets out the methodology Admodum applies inside the Autodesk practice across the cycle.
The Premium plan is Autodesk’s named-user uplift that delivers single sign-on, multi-factor authentication, advanced administration, usage reporting and consolidated billing on top of the standard named-user subscription. The features are real; the procurement question is whether the published per-user Premium uplift is proportionate to the value delivered.
The Premium-plan capability set, at the time of this paper, includes SAML-based single sign-on integration with the buyer’s identity provider, multi-factor authentication enforcement, advanced user-administration tooling (group management, role assignment, license assignment workflow), advanced usage and license-utilisation reporting and a single billing relationship across the Autodesk estate.
The Premium plan does not change the underlying product entitlement. A Revit named-user subscription on Premium delivers exactly the same Revit product as a Revit named-user subscription not on Premium. The Premium uplift is a licence-administration construct on top of the product subscription; it is not a product-feature upgrade.
The Premium-plan default in many Autodesk proposals is the whole named-user base. The buyer-side methodology contests the default. SSO and MFA in particular are not Autodesk-specific value; they are identity-platform value delivered by Microsoft Entra ID, Okta, Google Workspace or the buyer’s equivalent. The Premium-plan contribution is the integration glue that connects Autodesk to the identity platform, not the identity platform itself.
The methodology shortlists the Premium population against the role-types that materially benefit from the consolidated administration view (IT services, licence administrators, security operations) and sizes the Premium uplift against that shortlist, not against the whole named-user base. The result is typically a Premium population in the low single-digit percentage of the named-user base, sized against the value the Premium plan actually delivers.
The Flex token pool is Autodesk’s pay-as-you-go construct for occasional users. The buyer purchases a defined token pool against a defined contract term, and the deployed users consume tokens against a per-product daily rate when they access Autodesk software. The Flex construct is the procurement instrument for occasional-use populations.
Each Autodesk product has a published Flex token daily rate. A day of Revit access consumes a different token quantity than a day of AutoCAD access, which consumes a different quantity than a day of Civil 3D access. The published rates are the property of Autodesk and can be adjusted at renewal; the methodology reads the rate schedule at signature and sizes the token pool against the rate in effect.
The Flex versus named-user break-even is the load-bearing arithmetic. Where a user accesses a product more than a defined threshold of days per year, the named-user subscription is favourable; below the threshold, the Flex token pool is favourable. The threshold varies by product but typically sits between 20 and 30 days per year depending on the product-specific Flex token rate.
The methodology runs the break-even calculation by user and by product against the trailing-twelve-month activity record. Users below the break-even move to the Flex pool; users above the break-even keep the named-user subscription. The Flex pool is sized against the consolidated low-activity population with a contingency band wide enough to absorb seasonal peaks.
The procurement risk on Flex is the same risk that runs across every consumption-priced AI commitment in the white-paper library (the Azure MACC, AWS EDP, GCP EDP and Agentforce credit constructions): the published rate is the property of the publisher and the over-consumption price is materially above the committed-pool unit price. The methodology controls the risk through pool sizing, not through over-consumption.
The Architecture, Engineering and Construction (AEC) Collection bundles the Autodesk products commonly required across an AEC workflow into a single per-user subscription. The published AEC Collection content includes Revit, AutoCAD, Civil 3D, InfraWorks, Navisworks, 3ds Max, AutoCAD Plant 3D, AutoCAD Architecture, AutoCAD MEP and Robot Structural Analysis Professional.
The Collection break-even is straightforward: where a user actively uses more than two of the Collection products, the Collection subscription is favourable against the equivalent standalone subscriptions. Where a user actively uses one Collection product, the standalone subscription is favourable. The "actively uses" qualifier matters; access to a product (occasional file open) is not active use.
The methodology reads the trailing-twelve-month product activation record against each named user and reclassifies users where the Collection is unjustified. The reclassification typically reduces the Collection population by 15 to 25 percent against the deployed-use evidence; the reclassified users move to the relevant standalone subscription, materially reducing the per-user cost.
The Autodesk Construction Cloud (BIM Collaborate, BIM Collaborate Pro, Build, Takeoff, Cost Management) sits adjacent to the AEC Collection as a separate per-user subscription line. The procurement methodology reads the Construction Cloud population against the AEC project portfolio rather than against the AEC Collection population. The two are sized independently.
An AEC firm’s discipline mix (architecture, structural, MEP, civil, infrastructure) determines the standalone-versus-Collection economics. The methodology reads the discipline mix at the user-population level rather than at the firm level. A structural-discipline user with a different active-product profile to a civil-discipline user is sized differently against the Collection break-even.
The Product Design and Manufacturing Collection bundles the Autodesk products commonly required across a manufacturing workflow into a single per-user subscription. The published content includes Inventor, AutoCAD, Fusion 360, Nastran, Vault Basic, Factory Design Utilities and a number of additional manufacturing-specific products.
The break-even arithmetic mirrors the AEC Collection logic. Where the named user actively uses more than two of the Manufacturing Collection products, the Collection is favourable; below that, the standalone is favourable.
Fusion 360 is sold both as a standalone product (with several commercial tiers: Standard, Manufacturing, Simulation, etc.) and inside the Manufacturing Collection. The procurement question for a Fusion-heavy manufacturing estate is whether the user population is better served by the Fusion 360 standalone subscriptions at the appropriate tier, or by the Collection that bundles Fusion 360 Standard alongside the wider Inventor / AutoCAD / Nastran population.
Where the Fusion-only workflow is sufficient and the deeper Inventor and Nastran population is small, the standalone subscription mix is favourable. Where the manufacturing estate runs across Fusion and Inventor and the standalone mix would carry both, the Collection is favourable.
The methodology runs the deployed-use read against the manufacturing estate as it does against the AEC estate: by user, by product, against the trailing-twelve-month activation record. The reclassification work typically reduces the Manufacturing Collection population against the deployed-use evidence; the reclassified users move to standalone subscriptions sized against their actual product mix.
Autodesk closed perpetual-licence sales across the principal product line between 2016 and 2020 and ended Maintenance Subscription renewals shortly after. The migration window between perpetual-with-maintenance and subscription is now substantially closed, but a number of estates carry residual maintenance subscriptions and a number of buyers continue to operate perpetual licences without maintenance.
Autodesk offered a series of conversion-discount programmes through the migration window that priced a maintenance-to-subscription transition at a discount against new subscription. The discount steps narrowed across the migration and the headline conversion price moved towards near-parity with new subscription by the end of the window.
Where a residual maintenance subscription remains live, the buyer-side methodology reads the next-renewal economics carefully. The conversion incentive has narrowed; the deferred-decision risk (perpetual without maintenance) carries no support and no updates but retains the perpetual right to use; the new-subscription option carries the current Autodesk subscription pricing.
A perpetual licence without maintenance continues to operate and continues to carry the right to use the version captured at the maintenance-lapse date. The right is enforceable and the audit position on a perpetual-without-maintenance estate is materially different from the audit position on an out-of-date subscription. The methodology reads the perpetual position explicitly and protects it against the publisher-side framing that conflates it with non-genuine deployment.
Autodesk operates an audit programme under its True-Up Agreement (TLA) construct and under a wider piracy-and-non-genuine-software programme. The audit risk concentrates in three places: deployed-use overrun against the named-user count, non-genuine software deployment, and product-version overrun against the maintenance-lapse date on a perpetual estate.
The Autodesk TLA invites the buyer to true-up its named-user subscription against the deployed-use record. The construct is commercial rather than purely audit-driven; it is framed as a cooperative reconciliation but carries audit-defence implications where the deployed-use record exceeds the subscription count.
The non-genuine-software programme is materially more aggressive than the standard TLA. Where Autodesk identifies non-genuine software deployment (typically through product telemetry that flags unauthorised activation), the engagement opens with a settlement proposition rather than a cooperative reconciliation. The defence is to read the telemetry data carefully, to contest the non-genuine determination where the deployment is genuine (legacy perpetual licence, network-licence remnant) and to separate the genuine-deployment population from the non-genuine population.
The Autodesk audit defence protocol parallels the Microsoft SAM defence protocol set out in the SAM audit defence paper: first-letter response within a defined window, scope contestation, evidence-gathering protocol with parallel inventory, ELP reconciliation across genuine deployment, settlement framing, renewal-coupling decoupling and audit-clause renegotiation at the next renewal.
The protocol runs inside the Audit Defence Programme on a fixed fee, contingency or annual retainer basis.
Autodesk subscriptions run on one-year and three-year cycles. The renewal posture interacts with the named-user reconciliation, the Premium-plan contestation, the Flex token pool sizing and the Collection-versus-standalone reclassification.
The methodology runs the renewal in a defined sequence:
The closing posture runs inside the Renewal Programme with the reclassified named-user population, the Premium-plan shortlist, the Flex pool sizing, the Collection-versus-standalone mix and the multi-year commitment terms each carried through to the closing memorandum.
The Autodesk Named-User paper sits in the cluster of named-user subscription papers across the Admodum white paper library. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across the Autodesk engagements of the past twelve months. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer. The full case studies library carries Autodesk engagement summaries; the blog publishes the running practice analysis.
A senior Admodum advisor will walk the methodology through with your CIO, engineering, IT services or procurement team on a private call. Engagements run as fixed fee, contingency or annual retainer.