What Autodesk Flex Actually Is — and What It Is Not
Autodesk Flex is a consumption-based access model that allows users to access Autodesk software by spending tokens rather than holding a named user subscription. It was introduced as Autodesk's partial answer to the competitive criticism that its shift from network (concurrent) licensing to named user subscriptions forced organisations to purchase far more licenses than they needed for infrequent or occasional users. Flex does not restore network licensing — the pool-based concurrent access model is gone permanently — but it provides a flexible, per-day access mechanism that can meaningfully reduce costs for the right user populations.
Understanding when Flex saves money and when it is more expensive than a named user subscription requires understanding the token pricing model in detail. The maths is not complicated, but Autodesk's marketing of Flex as a flexible, cost-efficient option can obscure the specific user frequency threshold at which named user subscriptions become the better commercial choice. This guide makes that threshold explicit for every major Autodesk product. For the full Autodesk licensing model context, see our Autodesk Enterprise Licensing Guide. For EBA Flex token inclusion, see our Autodesk EBA Negotiation Guide. For Flex optimization advisory, our Autodesk advisory team models named user vs Flex economics as part of every licensing engagement.
How Autodesk Flex Tokens Work
Flex tokens are purchased in prepaid packs — typically 100, 500, or 1,000 tokens — and stored in an organisational token pool accessible to all users in the Autodesk account. Any authorised user can draw tokens from the pool to access any Flex-eligible Autodesk product. Each product has a defined daily token consumption rate: accessing that product for any amount of time within a calendar day deducts the product's daily token rate from the pool, regardless of whether the user spends 10 minutes or 8 hours in the application. There is no hourly pro-rating — a single login to AutoCAD on a given day costs the same number of tokens as a full workday in the application.
Tokens are purchased at a fixed per-token price (typically $9–$15 per token for standard pack sizes, with volume discounts available and lower rates when purchased through an EBA). Purchased tokens have a defined expiry — typically two years from purchase — after which unused tokens are forfeited. There is no rollover mechanism between token pack purchases.
| Product | Tokens per Day | Cost per Day (@ $9/token) | Cost per Day (@ $12/token) | Annual Sub. Cost | Breakeven Days/Year |
|---|---|---|---|---|---|
| AutoCAD | 5 | $45 | $60 | $2,030–$2,310 | 39–51 days |
| AutoCAD LT | 3 | $27 | $36 | $570–$630 | 18–23 days |
| Revit | 23 | $207 | $276 | $3,115–$3,420 | 13–17 days |
| Civil 3D | 23 | $207 | $276 | $3,115–$3,420 | 13–17 days |
| Inventor | 15 | $135 | $180 | $2,630–$2,910 | 17–22 days |
| Navisworks Manage | 10 | $90 | $120 | $2,170–$2,420 | 22–27 days |
| 3ds Max / Maya | 10 | $90 | $120 | $2,030–$2,310 | 21–26 days |
| AEC Collection | 25 | $225 | $300 | $3,940–$4,350 | 15–19 days |
The Revit surprise: At 23 tokens per day, Revit is the most token-intensive product in Autodesk's portfolio. At standard token pricing, a user accessing Revit just 15 days per year exhausts the cost-equivalent of an annual Revit named user subscription. For BIM coordinators, lead architects, and structural engineers who use Revit daily, Flex is never cheaper — a named user subscription is the correct model. Flex for Revit is only commercially rational for very occasional users: contract reviewers, client-side project managers, and others accessing Revit fewer than 12–14 days per year.
When Flex Makes Commercial Sense
The breakeven analysis in the table above identifies the specific user populations for whom Flex is cheaper than a named user subscription. Translating that into enterprise deployment decisions requires understanding your actual user population's access patterns — and segmenting accordingly.
Seasonal and project-based workers. Construction firms with site-based users who access AutoCAD or Revit only during specific project phases — site mobilisation, as-built surveys, final documentation — typically have access patterns below the Flex breakeven threshold. A site engineer accessing AutoCAD 30 days per year during documentation phases is cheaper on Flex (30 × $45 = $1,350 at $9/token) than on an annual AutoCAD subscription ($2,030–$2,310). This use case is clear-cut: organisations with large populations of genuinely seasonal or project-phase users should be using Flex for those populations, not named user subscriptions.
Cross-disciplinary reviewers. Engineering consultancies and integrated project delivery firms often have professionals who need to review but not actively work in specific software packages — a mechanical engineer reviewing an architecture model in Revit, a project manager reviewing Civil 3D outputs, a contract administrator reviewing Navisworks clash detection reports. These users may access the relevant tool 5–15 times per year. Named user subscriptions for the review-only population are pure cost waste; Flex is the correct model.
Autodesk product trials and new capability exploration. Design teams evaluating whether to adopt a new Autodesk product — InfraWorks for infrastructure visualisation, FormIt Pro for early-stage BIM, Dynamo for parametric automation — can use Flex to access the product during evaluation without committing to named user subscriptions before the adoption decision is made. This is a low-volume use case but removes a procurement barrier to new capability exploration.
When Flex Does Not Make Commercial Sense
For users above the breakeven day threshold for their primary product, named user subscriptions are cheaper — sometimes substantially so. The important planning discipline is ensuring that users classified as "Flex users" in the deployment plan are genuinely below their product's breakeven threshold — and that the classification is revisited annually as usage patterns evolve. Common Flex deployment mistakes that increase rather than reduce cost:
Deploying Flex to moderately frequent users. A designer accessing AutoCAD 60 days per year on Flex costs 60 × $45 = $2,700 at $9/token — $390–$670 more than the annual named user subscription. Organisations that deployed Flex broadly without a breakeven analysis frequently discover their Flex spend is higher than equivalent subscriptions would have been, with the additional disadvantage that token spend is variable and harder to budget.
Ignoring the daily rate structure for multi-session users. Users who open an application briefly in the morning and again in the afternoon consume the full daily token rate twice — if those sessions fall on different calendar days. Users who habitually open applications at 11pm and again at 1am are similarly consuming two daily token charges for what feels like a single working session. The daily (not hourly) billing model is consistently underestimated in Flex cost projections.
Not monitoring token pool consumption rate. Token pools that are not actively monitored can be depleted by unexpectedly heavy usage — leaving legitimate users unable to access software mid-project because the pool is empty. EBAs with Flex token inclusion should specify a minimum included pool size and a replenishment process that avoids mid-year depletion.
Get a Named User vs Flex Optimization Analysis
Our Autodesk advisory team models named user vs Flex economics across your specific user population — using actual usage data from the Autodesk Account Console — to identify the optimal deployment mix and quantify the savings available from right-sizing. To get started, book a call with our team.
Book a Flex Optimization Review →Combining Flex and Named User Subscriptions: The Hybrid Model
Most enterprises above a certain size will have both power users (daily or near-daily users, clearly below no Flex threshold) and occasional users (seasonal, project-based, or review-only users below the Flex breakeven). The optimal deployment model is a hybrid: named user subscriptions for the power user population, Flex tokens for the occasional user population, with the token pool sized to the expected annual consumption of the occasional user group plus a 20% buffer for demand variability.
The hybrid model requires ongoing governance: annual usage audits to reclassify users whose patterns have changed (a project manager who has become a daily AutoCAD user should move to a named user subscription; a designer who has moved to a review-only role should move to Flex), and a token pool replenishment process that prevents mid-year depletion. For organisations negotiating an EBA, the hybrid model should be explicitly reflected in the EBA structure: a named user commitment for the core subscription population, plus a Flex token pool allocation included in the EBA for the occasional user population, with both sized based on the current usage audit. Our Autodesk advisory team builds this analysis into every EBA engagement.