A Practical Guide to Software Licensing for Businesses

Why software licensing matters

Buying software isn't quite like buying a physical product. When a business acquires software, it isn't purchasing the program outright — it's acquiring the right to use it under terms set by the vendor. Misunderstanding those terms can lead to unnecessary spend, unsuitable licence choices and administrative headaches.

This guide sets out, in plain terms, what a software licence actually is, the models you're likely to encounter, and the questions worth asking before you commit to a purchase. It's a general introduction rather than legal advice — licence terms vary by vendor, product and agreement, so the specifics always need checking against the actual contract in front of you.

What is a software licence?

A software licence is permission from the copyright owner, whether that's the vendor or another rights holder, to use their software in a defined way. It does not transfer ownership of the software itself. The UK Intellectual Property Office describes an IP licence, in general terms, as an agreement between the rights owner and another party that "grants them permission to do something that would be an infringement of the rights without the licence."

Software licensing works the same way: the vendor keeps ownership of the underlying code and intellectual property, and the licence sets out what you're allowed to do with it, such as installing it, running it or accessing it as a service, along with any conditions attached to that permission.

Licence terms and fees are, as the IPO puts it, "a private matter" agreed between the parties. That's precisely why two businesses buying what looks like the same software can end up with meaningfully different rights, depending on the specific agreement each of them signed.

Common ways business software is licensed

Vendors describe and combine licensing models differently, but most business software falls into a handful of recognisable patterns:

• Per-user / named-user licensing — the licence is tied to a specific individual, usually identified by an account or sign-in, so that person can use the software once signed in rather than the licence being tied to a particular machine.
• Per-device licensing — the licence is tied to a specific piece of hardware rather than a person, regardless of who is using it at the time.
• Shared-device licensing — a variant of device-based licensing built for environments like labs or shared workstations, where multiple people use the same machine rather than each holding their own named-user licence. This model is generally intended for shared or communal setups, not machines used by one dedicated individual.
• Subscription licensing — access continues for as long as payments continue, usually billed monthly or annually.
• Perpetual licensing — a one-off purchase that, in principle, allows indefinite use of that specific version, though ongoing support and future upgrades are separate questions.
• Usage- or consumption-based licensing — cost and entitlement scale with actual usage, such as data processed or transactions completed. This is more common in cloud and infrastructure software than in desktop applications.

These categories aren't mutually exclusive, and vendors frequently combine them — a named-user subscription is a common example. The label a vendor uses ("per user," "per seat," "per device") needs to be checked against what it actually means in that vendor's specific terms, because the same word can work differently between products.

Subscription vs perpetual licensing

The most consequential licensing decision for many businesses is whether to buy a subscription or a perpetual licence, where both are genuinely on offer for a given product.

A subscription is paid on a recurring basis, and access typically continues only for as long as payment continues. Microsoft, for instance, describes a Microsoft 365 subscription as something you "pay for on a recurring basis," where you specify a number of licences based on your organisation's size and then assign one to each person. Subscriptions commonly bundle in updates and ongoing access to current versions, but exactly what's included depends on the specific product and plan.

A perpetual licence typically grants ongoing use of a particular version after a one-time purchase, subject to the applicable licence terms. This can suit stable, long-term use, but a perpetual licence doesn't automatically include future upgrades, and continued support may need to be purchased separately or may lapse after a period.

Neither model is inherently better — the right choice depends on budgeting preferences, how quickly the software category evolves, and how the specific vendor structures updates and support for each option.

One user does not necessarily mean one device

It's easy to assume that one licence, one user and one device are interchangeable. In practice they often aren't, and vendors are usually explicit about the distinction once you look for it.

Microsoft's own guidance is a clearly documented example. For qualifying Microsoft 365 subscriptions — including Microsoft 365 Apps for business and enterprise, and the Business Standard and Premium plans — a single licensed user can install the desktop apps on up to five PCs or Macs, five tablets and five phones. That's one licence and one named user, but potentially fifteen installations. Microsoft is also explicit that this doesn't extend to "multiplexing" — routing multiple people's use of the software through a single licensed account to avoid buying more licences — which it treats as still requiring a licence for each person actually using or benefiting from the software.

This is specific to Microsoft's terms for particular products, not a universal rule. Other vendors set different device allowances, and some tie a licence strictly to a single device. The only safe approach is to check the specific entitlement for the product and plan you're buying, rather than assuming it matches something you've seen elsewhere.

What should a business establish before purchasing software?

Before requesting a quotation, it's worth having answers, even approximate ones, to a core set of questions. The specifics vary by vendor and product, but the questions themselves are broadly consistent:

• Who actually needs access, and how many users or devices does that involve?
• Which specific applications or features are required — not just the product family, but the edition or tier?
• What licence term applies — subscription, perpetual, or something else — and for how long?
• How does renewal work, and is it automatic?
• Are there deployment or administration requirements, such as centralised licence management?
• What support is included, and what falls outside it?
• What happens when an employee leaves — can the licence be reassigned, and are there restrictions or waiting periods on doing so?
• Are there geographic or territorial restrictions on where the software can be used?
• What documentation or proof of purchase will you need to retain, and for how long?

The answers depend entirely on the specific product, vendor and agreement in question. This list is a starting point for a conversation with a vendor or supplier, not a substitute for reading the actual licence terms.

Managing licences after purchase

Licensing doesn't end at the point of purchase. A few habits make a meaningful difference to cost control and compliance over time:

• Maintain a simple software and licence inventory — what you own, how many seats, and which product or edition.
• Record which licences are assigned to which users, where the licensing model is user-based.
• Track renewal dates somewhere visible, rather than relying on a vendor's reminder email.
• Assign clear internal ownership for licensing decisions and renewals, even in a small organisation.
• Periodically review usage, and unassign or reallocate licences that aren't being used.
• Have a defined process for reassigning or removing licences when someone leaves, in line with the applicable terms.
• Keep purchase confirmations, invoices and licence agreements on file — you may need them for renewals or support queries.

None of this requires specialist tooling for a small business. A shared spreadsheet, reviewed periodically, is often enough to start.

Common software-licensing mistakes

Most licensing problems are avoidable, and tend to repeat across organisations:

• Buying the wrong edition or tier, then discovering a required feature sits in a higher plan.
• Confusing the technical ability to install software with having permission to use it under the licence.
• Assuming a licence automatically covers unlimited employees or devices, when it's actually scoped to a specific number.
• Overbuying seats "to be safe," which quietly inflates renewal costs every year.
• Losing track of renewal dates, and either lapsing unexpectedly or auto-renewing something no longer needed.
• Acquiring software through an unverified or unclear source, without checking where the licence actually originates.
• Not retaining purchase documentation, which becomes a problem the moment a vendor asks for proof of entitlement.

Where S3NTRA fits in

Sourcing the right licence for your organisation is often more about asking the right questions than knowing every vendor's rulebook by heart. S3NTRA helps organisations identify suitable software licensing options and source legitimate licences and subscriptions through a quotation-based procurement process. If you'd rather talk through your specific requirements than work through vendor documentation alone, get in touch.