Licensing practice
Ten software licensing mistakes that cost real money
Every one of these is routine, none of them is exotic, and most are found during a renewal or an audit rather than at the point they were made.
· 8 min read
These are the ones that recur. Each costs either money paid for nothing, or money owed and not budgeted.
1. Licensing everybody identically
The most expensive habit in software procurement. Buying every member of staff the same plan is administratively simple and almost always wrong: a share of any workforce does not need desktop applications, and a share of any design team does not need a full subscription. Uniform licensing pays for the maximum requirement across the whole headcount.
The fix is an audit of what people actually do, by role. It is usually a day of work and it usually finds a double-digit percentage.
2. Not counting actual usage before a renewal
Most publishers provide usage reporting. Few customers read it before renewing. The result is a renewal at last year's quantity, including the seats of people who have left, the seats nobody has opened in nine months, and the collection bought for somebody who uses one product in it.
Pull twelve months of usage before every renewal. See what to check before a software renewal.
3. Buying subscriptions and forgetting they end
A perpetual licence bought and forgotten keeps working. A subscription bought and forgotten stops. The failure is a budget failure rather than a licensing one, and it lands on a Monday morning when a design team cannot open its files.
Every subscription needs a renewal date recorded somewhere a person will look, and an owner.
4. Treating a product key as proof of licence
A key activates software. It does not establish that your organisation is licensed. What does is the invoice in your name, the agreement number, and the portal access. Organisations that hold keys and no paperwork discover this at an audit.
5. Buying cheap keys
Covered in detail in how to buy genuine Microsoft licences in India. The short version: volume keys resold as singles, keys from another region, loose OEM keys and academic licences used commercially all activate, and none survives scrutiny.
6. Omitting CALs, add-ons and the separately licensed products
The lines most often missing from a quote that looked complete:
- Client Access Licences on a server purchase
- Project and Visio, which are not in Microsoft 365 plans
- Remote Desktop Services licences where people connect to a session
- Extra storage beyond a plan allowance
- Calling plans, as distinct from Teams meetings
- Copilot and other per-user add-ons
A quote without these is not cheaper. It is incomplete.
7. Sharing named-user licences
Current licensing for most design and productivity software is per named person. Two people using one subscription breaches the terms, and the publisher can see it. Where the underlying need is occasional access, there is usually a legitimate product for it — Autodesk Flex being the clearest example.
8. Assuming academic or non-profit eligibility
Academic and non-profit programmes are materially cheaper and have eligibility criteria that are checked. A commercial arm of an educational trust, a training business, or a contractor working on an institution's project is frequently not eligible, and discovering this retrospectively converts a saving into a liability.
9. Getting the invoicing entity wrong
Specific to India and entirely avoidable. An invoice raised to the wrong group entity, or with an incorrect GSTIN, loses the input credit and is tedious to correct. Where a group has several registered entities, decide which one holds the subscription before provisioning. See GST input credit on software purchases.
10. Committing for three years in an optimistic quarter
Longer terms are cheaper per year, and that is a real saving for a stable team. Against it: an annual commitment generally cannot be reduced mid-term. A company that commits at its peak headcount pays for the peak through the trough.
The usual right answer is a split — a longer term for the stable core of the team, annual or monthly for the part that fluctuates.
The pattern behind all ten
Nine of these are the same mistake in different clothes: a licensing decision made once and then not revisited, while the organisation it was made for changed. An estate licensed correctly two years ago is probably licensed wrongly now, in both directions at once.
An annual reconciliation — installations against entitlements, usage against seats, people against plans — costs a day and is the cheapest money in software procurement.
Where to go next
Software asset management is the service that does the reconciliation, and licence management is the one that keeps the renewal calendar. If you would rather start with the numbers, send us your current licence list and we will tell you what we think is wrong with it — including when the answer is nothing.






