software asset management - abstract dark theme illustration

Software Asset Management for SMBs: A Practical Guide

Software asset management, SAM, is the discipline of knowing what software your business owns, where it runs, what it costs, and whether you are compliant with its licenses. For most small and mid-sized businesses it sounds like an enterprise luxury. In practice it is the difference between a predictable IT budget and an audit letter. South African companies running Microsoft, Adobe, or any per-user licensing are contractually exposed the moment their records drift from reality, and with cloud subscriptions, drift happens monthly.

The problem has a shape. Businesses buy software in three ways now, direct purchase, volume agreements, and click-through cloud subscriptions that anyone in the company can start with a credit card. Nobody tracks the third category, which means renewal costs hide, unused seats accumulate, and shadow subscriptions carry data nobody controls. This guide covers the SAM practices that fit a smaller business, what to track, how often, and which tools make it manageable.

What Software Asset Management Actually Involves

SAM has four moving parts. Discovery, finding every piece of software running in your environment, including the ones nobody declared. Inventory, the ongoing record of what is installed where and who uses it. Compliance, matching that inventory against what your licenses actually permit. And lifecycle management, renewing, reallocating, or retiring software deliberately instead of by accident.

The compliance piece deserves respect, and it has a formal side: the ISO/IEC 19770 series defines the international standard for software asset management processes, and larger clients increasingly expect their suppliers to show ISO-aligned SAM discipline as part of procurement due diligence. A true-up bill from a vendor audit, the settlement for licenses you used but did not buy, is not a negotiation from strength. And under POPIA, an unmanaged application holding customer data that nobody in the business owns is a compliance problem beyond money. Our article on finding and managing shadow IT covers the discovery side of this in depth.

The Real Costs of Not Managing Software

Waste is the quiet cost. Industry studies consistently find that large fractions of purchased software seats go unused, and that businesses overspend on shelfware while simultaneously buying duplicates of tools they already own. For a 50-person company, a 20 percent waste rate on a software budget of a few million rand a year is a real number that lands on the bottom line.

Risk is the loud cost. Under-licencing discovered in a vendor audit, and Microsoft does audit mid-market South African companies regularly, its licensing terms give it the contractual right to, produces a true-up demand with legal weight behind it. Renewal surprises are the third cost: auto-renewing subscriptions that nobody remembers buying, priced per user, quietly growing as headcount grows.

What a Practical SAM Process Looks Like for an SMB

You do not need an enterprise SAM department. You need a repeatable quarterly routine:

  • Run a discovery scan quarterly. Automated asset discovery beats a spreadsheet of what people remember installing. It also catches the local admin who installed a database server on their laptop.
  • Keep one authoritative inventory. Software name, vendor, license type, seats owned, seats in use, renewal date, owner, and cost. If it lives in three spreadsheets, it lives nowhere.
  • Match installs to entitlements every quarter. Flag over-deployment immediately, it only gets more expensive. Flag unused seats too, because those are reclaimable licenses you have already paid for.
  • Put renewal dates in a calendar 90 days out. The decision to renew, renegotiate, or cancel should be made deliberately, not by silence.
  • Assign every application a business owner. If a tool has no owner, it has no security review and no renewal decision. It just has a debit order.

If you maintain a hardware and software asset register, this process plugs straight into it, and our guide to why asset registers drift and how to fix them covers the register itself.

Tools: From Spreadsheets to Automated SAM

For a 20-person business, a well-maintained spreadsheet with quarterly discovery runs is honest work. Somewhere past 50 devices, manual tracking starts losing to reality, and automation pays for itself. Managed platforms, including Claritam’s approach of continuous AI-driven discovery rather than annual snapshots, keep the inventory accurate without anyone spending Fridays updating it.

What matters when evaluating a SAM tool is less the feature list and more whether it fits your stack: does it discover your cloud subscriptions as well as your installed software, does it track SaaS seats that renew monthly, and does it produce an audit-ready entitlement comparison on demand. The IT asset management capabilities you need are the same whether the tool is on-premises or delivered as a service.

How Often Should You Review?

Quarterly is the honest answer for most SMBs, with two exceptions. Any business expecting rapid headcount change should review licensing monthly, because per-user costs move fastest in growth periods. And any business that has never done a SAM review should do one now, not quarterly, because the first review always finds surprises. Our article on how often to audit IT assets sets out sensible review intervals by category.

Frequently Asked Questions

What is software asset management?

Software asset management is the ongoing practice of discovering, inventorying, and tracking software across a business so that licensing, spending, and risk stay under control. It covers what is installed, what is owned, what is used, and what renews when. Done well, it turns software from a runaway cost into a managed asset.

Why does SAM matter for small businesses?

Because small businesses accumulate per-user cloud subscriptions quickly, waste spend on unused seats, and face vendor audits with the same contractual exposure as larger firms, without the budgets to absorb true-up bills. A quarterly SAM routine prevents the surprise and typically pays for itself in reclaimed licenses.

How often should software inventory be updated?

Quarterly for most SMBs, monthly during growth phases or where per-user costs move quickly. Automated discovery narrows the gap to near-continuous. The key rule is that the interval must be shorter than your fastest change cycle, headcount growth or subscription creep.

What is license compliance risk?

It is the gap between what your business actually deploys and what its licenses permit. Vendors including Microsoft run routine audits of mid-market companies, and discovered over-deployment triggers a true-up settlement at list prices. Under POPIA, unmanaged applications holding personal data add regulatory exposure on top.

Can SAM reduce software costs?

Yes, usually immediately. The first inventory typically finds unused seats, duplicate tools, and forgotten auto-renewals. Reclaiming and consolidating those routinely cuts software spend by double-digit percentages without cancelling anything the business actually uses.

Where This Goes Wrong, and the Fix

Software asset management fails in predictable ways: the spreadsheet nobody updates, the discovery tool nobody runs, the renewal that slipped, the intern who started a trial that became a debit order. Each failure is small. Together they are how a 40-person company ends up paying for software it cannot name, while the licences it actually needs sit expired. The fix is not more discipline, it is a system that watches continuously and tells you what changed. Claritam exists because annual audits and manual registers lose to monthly reality, and its continuous asset discovery keeps software, licenses, and risk visible without a quarterly scramble. If your last software inventory is older than your newest hire, that is the place to start.

Know what is on your network

Request an assessment

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *