Autodesk licensing
Autodesk Flex versus named-user subscriptions: counting the days
Flex is pre-paid tokens drawn down per day of use. Whether it beats a subscription is pure arithmetic, and most firms have never done it.
· 6 min read
Flex exists for one situation: people who need Autodesk software occasionally. For them it is substantially cheaper than a subscription. For everybody else it is substantially more expensive. The dividing line is a number of days per year, and it is calculable.
How Flex works
You buy tokens in advance. When a person opens a covered product, tokens are consumed for that day's access to it. Open it twice in a day and it costs the same as once. Do not open it and it costs nothing.
Different products consume different token quantities per day — a full-featured product costs more per day than a lighter one — so the arithmetic is per product, not global.
Tokens have a validity period. Buying a large quantity against uncertain use risks them expiring unused, which is the main way Flex is bought badly.
The arithmetic
For one person and one product:
- Find the token cost per day for that product
- Multiply by the days per year that person will open it
- Compare against the annual subscription price for that product
Below the crossover, Flex wins. Above it, the subscription wins, and it wins by more the further above you go.
The crossover lands at a modest number of days for most products — low enough that anybody using the software weekly is clearly a subscription, and anybody using it monthly is clearly Flex. The genuinely ambiguous band is narrow, and in it the subscription is usually the better choice because it is predictable.
Where it reliably wins
- The project manager or director who opens drawings to check something, not to draw
- The structural or civil engineer who needs a specialist product for a few weeks a year
- A second product for somebody who has a subscription to their main one — the engineer on Revit who needs Civil 3D twice a quarter
- Seasonal or project-driven peaks, where three extra people need access for one month
- Reviewers and approvers generally
A firm with a dozen people in those categories is frequently paying a dozen full subscriptions, and that is the single largest saving available in most Autodesk estates.
Where it loses
Daily and weekly users, unambiguously. Flex is not a cheaper subscription; it is a different product for a different pattern, and used for regular work it costs considerably more.
The number you need
Days of actual use, per person, per product, over twelve months. Autodesk's admin reporting provides this. Pull it before a renewal.
Do not estimate it. Estimates are wrong in both directions in a way that is consistent enough to be funny: the person everybody describes as a heavy user turns out to open it twice a month, and the director who "never touches it" is in it weekly.
Practical cautions
Tokens expire. Buy against measured use plus a margin, not against a hopeful projection.
Administration is real. Flex needs somebody watching the balance. Running out mid-project is a bad afternoon.
Not every product is covered. Check the current eligible product list.
Mixed estates need a reconciliation habit. The right split this year is the wrong split next year, because people's roles change. Revisit annually.
The configuration that usually wins
- Subscriptions for regular users, on their main product
- Collections for the people genuinely working across several products — see the AEC Collection explained
- Flex for occasional users, and for second products held by subscription users
Common questions
Can Flex and subscriptions coexist? Yes, and the mix above is the normal configuration in a well-managed estate.
Can two people share a Flex pool? Yes — that is the point. Tokens are organisational, drawn down by whoever uses the software. This is the legitimate answer to the need people otherwise try to meet by sharing a named-user licence, which is not permitted.
What happens if tokens run out mid-day? Access stops. Monitor the balance.
Is Flex cheaper than the old network licences? Different model, and not directly comparable. Network licences were concurrent-use; Flex is metered daily use.
Where to go next
Product pricing is on AutoCAD, Revit and AEC Collection, and the licensing change that produced Flex in what changed with named-user licensing. To have the arithmetic done, send us a usage export — it is the one input that makes this a calculation rather than an opinion.






