
Software licenses can accumulate without a company noticing. A new employee receives the tools needed for the job, a department starts a trial, a service is purchased for a project, and a subscription keeps renewing after the work has ended. The problem is not only the expense: if nobody knows which applications are in use, managing access, updates and responsibilities also becomes harder.
Taking inventory means connecting contracts, accounts, devices and operational needs. There is no need to begin with expensive software: a small business can build a reliable register with clear roles and regular checks. This guide proposes a method for understanding what the company owns, what has been assigned, what is actually used and which decisions can reduce waste without interrupting work.
Why licenses slip out of control
Many purchases arise from legitimate and urgent needs. The sales team tries a CRM, the design department requests a creative tool, and support opens a new ticketing system. If each team buys independently, information remains scattered among company cards, invoices, administrators' emails and suppliers' control panels. The recurring cost is visible in accounting, but it is not always linked to whoever uses the product.
Staff changes also matter. Someone who changes role may keep tools they no longer need; when a person leaves the company, a license may remain assigned to an account that is no longer operational. A periodic inventory makes these situations verifiable. The aim is not to remove tools indiscriminately, but to understand where a resource is needed and where it can be reassigned or reduced.
Distinguish installed software, accounts and usage rights
Seeing an application on a computer does not prove that an appropriate license was purchased. Equally, a purchased license does not prove that a program is installed or used. Cloud services can have accounts without local installations, while some products are activated on shared devices. An inventory must keep these elements separate.
For each product, ask which version or service is available, who owns the contract, how many usage rights are included, which users or devices have been assigned them and what use is actually necessary. Conditions may differ between editions of the same product. The inventory should therefore be more than a list of icons: it should provide a verifiable connection between needs, assignments and purchase documents.
Define the scope of the inventory
The first step is deciding what the review covers. Besides programs on PCs, consider SaaS applications, productivity suites, browser-based tools, add-ons, company-managed mobile apps and services purchased for individual projects. Free products may also deserve attention: check their terms of use, who provides support and what data they process.
The NIST Cybersecurity Framework 2.0 includes software, services and systems managed by an organization in its inventories. For a small business, that does not mean recording every detail on day one. It is more useful to start with services that carry recurring costs, have access to company data or play an essential role in work, and then extend the register to other applications.
Gather information from different sources
A single source rarely tells the whole story. Invoices show purchases and renewals; administration panels show licenses and users; device management tools show installations; department managers explain whether an application is still needed. Comparing these perspectives reveals differences that a single export would not expose.
Asking each manager which tools the team uses also helps identify subscriptions purchased outside the IT process. Approach the comparison collaboratively: if a service solves a real problem, understand and govern it. Cancelling it without knowing how it is used can create interruptions or push employees toward alternatives that are harder to control.
What information to record for each product
A useful register should support decisions, not merely fill rows. For each product, record:
- Name, supplier, edition and business purpose.
- Internal owner and the department using it.
- Number of licenses purchased, available and assigned, where applicable.
- Assignment model: user, device, shared access or consumption.
- Cost, billing period, renewal date and conditions for making changes.
- Administrative account and location of the contract and invoices.
- Important dependencies, such as hosted data, integrations and essential functions.
Passwords need not go into the inventory spreadsheet. The register can say who safeguards access and where the contract is stored, while secrets remain in a protected space. NIST control CM-8 also cites owners, versions and license information among the useful attributes of a component inventory.
Understand the licensing model before counting seats
A license may be tied to a person, a device, simultaneous users, features, usage volume or an environment. A monthly subscription and a perpetual license have different economic models; updates, support and use across several locations may also depend on the contract. Counting “one license per computer” without reading the model can lead to the wrong conclusion.
Record the unit the supplier actually bills for. If the plan is per user, the number of installations may not match the seats purchased; if it is per device, counting the people who use it does not tell the whole story. The product's official terms and the signed agreement take precedence over any general rule in a guide.
Connect licenses to the right people
For services with named-user licenses, the supplier's panel generally shows who has been assigned each product. Compare that list with current staff, roles and departmental needs. You may find a duplicate account, an outside collaborator who no longer works with the company or someone assigned a higher tier than necessary.
In Microsoft 365, for example, the administration center allows administrators to assign and unassign user licenses. This feature does not decide which licenses are unnecessary on its own: you must consult the people who understand the work being done. Before changing an assignment, check possible effects on email, files, integrations and business continuity.
Check installations and devices
For installed software, an inventory of managed PCs and devices can show where applications are present. However, read the data cautiously: an old installation may not be used, while a portable version or web app may not appear on the expected list. Comparison with managers and the supplier's panel remains necessary.
Identify devices that are no longer assigned, replaced PCs and test machines. Before removing a product or freeing a license, check whether it is needed to open archives, run automations or maintain compatibility with other tools. Cleaning up the inventory helps when it reduces uncertainty; automatic deletion based on one scan can disrupt work that is still needed.
Separate purchases, assignments and use
Three figures are often confused: how many rights were purchased, how many are assigned and how many appear to have been used during the observed period. A purchased but unassigned seat differs from a seat assigned to someone who rarely opens the application. The former may indicate excess capacity; the latter calls for a review of the person's role and future needs.
Some platforms offer usage reports, but coverage and update times depend on the service. No activity in the chosen period does not prove that a product is useless: it may only be needed for accounting closings, seasonal campaigns or emergencies. The data is a starting point for a conversation, not an automatic decision.
Assess the plans and features actually needed
Two people can use the same product for different purposes. Someone editing standard documents may not need the advanced functions required by a colleague who administers the system or works with specialist files. When the supplier offers several tiers, comparing the features used with those included in each plan may reveal oversized assignments.
Nevertheless, test any plan change: an apparently secondary feature may support an important process, an integration or a collaboration requirement. Documenting why someone needs a higher tier helps maintain consistent assignments when staff change. Do not confuse a lower unit price with a better overall result: a cheaper plan may create manual steps that consume time.
Find duplicate subscriptions and overlapping tools
Different departments may buy applications with similar functions: storage, video meetings, signatures, task management or data analysis. Overlap does not automatically mean that one product should be removed. Establish which features are needed, what data is hosted and how difficult it would be to move work from one platform to another.
A table organized by function rather than supplier name helps show the full picture. If two tools genuinely serve the same process, consider a common choice and a controlled migration. If they meet different needs, document the distinction so that every review does not start from scratch. Before closing a contract, plan for data export and management of any remaining access.
Bring services purchased outside IT into view
A service may have been paid for directly by a department and be absent from technical registers. This often begins as an attempt to solve a problem quickly, not necessarily as improper behavior. Comparing recurring expenses, company cards and tools reported by teams brings these purchases into the inventory.
The review should ask who owns the account, what data is uploaded, how permissions are managed and who receives renewal notices. Moving ownership from a personal address to an account governed by the company can reduce dependence on one person, if the supplier allows it. Once again, the priority is to understand and organize the service before interrupting one that is useful.
Prepare for renewals and deadlines in good time
The best moment to review a subscription is before the window in which it can be changed. Record the renewal date, commitment period, cancellation process and commercial contact so decisions can be planned. Conditions vary between suppliers, purchasing channels and contract types; some changes may only take effect at renewal.
For example, Microsoft explains that the ability to reduce the number of licenses also depends on the billing arrangement and the available window. Do not turn one supplier's rule into a promise that applies to everyone. Setting internal reminders ahead of deadlines gives departments time to provide information and supports decisions without haste.
Distinguish license cost from the cost of change
The price per seat is only one part of the comparison. A platform may require configuration, training, integrations, support, extra storage or migration work. A reduction that removes an essential function could create more manual tasks or increase the risk of mistakes. Before changing a plan or product, assess the effect on the entire process.
It is also useful to estimate the cost of doing nothing: paid but forgotten accounts, unreviewed renewals and duplicate tools. There is no need to invent percentages. For each case, simply record the verified fee, seats involved, remaining period and effort needed to change the situation. A documented decision makes clear the reason for a saving or for keeping a license.
Manage staff onboarding, role changes and departures
Licenses should follow the user lifecycle. When someone joins, they receive the tools approved for the role; when their duties change, plans are reviewed; when they leave, the company checks how to revoke access and recover assignments. A shared process involving the manager, IT and administration prevents each group from working from a different list.
Removing a license may affect associated data. Before acting, check the supplier's instructions on retention, transfer and access to information. Adobe's documentation on reassigning licenses distinguishes removal of access from management of a user's assets. The same general principle applies elsewhere: first preserve what is needed, then deactivate in an orderly way.
Avoid shared accounts as a shortcut
Sharing a single account among colleagues may look like a way to reduce purchased seats, but it often conflicts with a product's licensing model and makes actions hard to attribute. It also weakens password management and identity verification. Look for the right solution among the supplier's supported options: roles, device licenses, temporary access or plans suited to actual use.
Applications do not all treat accounts in the same way. Before setting an internal rule, read the contract and product instructions. An accurate inventory lets the company explain why a particular number of accesses is needed instead of relying on shared credentials that hide the problem without solving it.
Assess use respectfully and cautiously
Activity data can help identify apparently unused seats, but it must be interpreted in context. The observed period, the product's purpose and the person's role all affect the meaning of a last-access date. An account used for a quarterly task can look inactive for weeks without being unnecessary.
Limit access to reports to people who need them for decisions, and use only the information necessary. Some platforms hide identifying details by default in their reporting tools. Before increasing the granularity of monitoring, check internal rules and the applicable context. The goal is to optimize business tools, not turn an inventory into an automatic assessment of employees.
Assign clear responsibilities
A register with no owner quickly becomes outdated. Each product needs at least one contact who confirms its operational value and someone authorized to manage the contract, renewal and administration panel. IT can collect technical data, administration can review costs, and the department manager can decide whether the service is still needed.
Agreeing who approves new purchases and who updates the inventory after a change avoids duplication. For a critical service, document a substitute for the main contact as well. There is no need for a heavy bureaucratic structure: understandable responsibilities and a review point tied to deadlines or staffing changes are enough.
Start with a four-step review
An initial review can follow a simple sequence:
- Collect contracts, invoices, panel exports and installed software data.
- Combine the information by product, contract, owner and licensing model.
- Compare seats purchased, seats assigned and needs confirmed by departments.
- Decide case by case whether to retain, reassign, reduce or investigate further.
Every decision should have an owner and a review date. Uncertain cases remain open until actual use or the impact of a change is understood. Starting with products that have recurring costs or many users produces a useful picture without waiting for a perfect inventory of every application in the company.
Choose between a spreadsheet and dedicated tools
For a limited portfolio, a shared spreadsheet with controlled access may be enough. It needs consistent fields, a responsible person and links to original documents. When products, sites and assignments become numerous, asset management tools can help collect installations, accounts and deadlines in a more structured way.
Automation does not eliminate human review. A scan can show that a program is present, but not whether a contract allows that use or whether the department needs it. Choose a tool only after defining the questions it must answer. A clear process in a simple spreadsheet is more useful than a complex platform fed with incomplete data.
Measure results without inventing savings
A few indicators make progress visible: the share of products with an identified owner, renewals reviewed in advance, the difference between seats purchased and assigned, assignments recovered after role changes and cases still lacking a verified contract. These figures describe work completed; they should not automatically be converted into money saved.
To estimate an actual saving, the contract or invoice change must have taken effect, not merely a license being removed from a user. A freed license may remain paid for until the next contractual window. Keeping opportunities identified, changes requested and confirmed financial effects separate avoids premature promises and makes the review more credible.
Frequently asked questions
Is an unassigned license always waste?
No. It may be needed for planned new hires or a temporary requirement. Still, compare it with the cost, renewal date and reduction options allowed by the contract. If it remains available for a long time without a clear reason, review it before renewal.
Can I move a license from one employee to another?
It depends on the product and the agreed terms. Many managed services allow an assignment to be removed and given to someone else, but procedures and limits can vary. Before making the change, also ensure that the previous user's data, files or activities are handled correctly.
Does a report showing no activity prove I can remove the seat?
No. The reporting window may exclude seasonal use, and some reports do not show every feature. Confirm with the process owner, check dependencies and consult the contract. Only then decide whether to reassign or reduce the license.
Does every company need software to manage licenses?
Not necessarily. For a few applications, a carefully maintained register may be enough. A dedicated tool becomes useful when the volume and frequency of changes make it difficult to reconcile data from several panels, sites and departments. The quality of the process remains decisive in both cases.
Conclusion: from a list to a decision
A license inventory is not a list to compile once and forget. It connects products, people, contracts and real activities. When that information is current, avoiding passive renewals, recovering unnecessary access and choosing plans that match the work become easier.
The most dependable savings come from documented reviews and changes made within the applicable timeframes, without removing essential tools or losing data. Starting with the most important services, assigning responsibilities and repeating the review regularly enables even a small business to govern its software more clearly.
Would you like to explore this topic for your business? Azienda Digitale can help you assess the right solutions and put them into practice. Azienda Digitale