For a company under 200 employees, software license management reduces to four practical jobs: know every tool you pay for, know how many seats you pay for versus actually use, know when each contract renews and what its notice deadline is, and have a named owner for each one. Everything else in the enterprise ITAM canon — license harvesting engines, software metering agents, CMDB integration, audit-defense tooling — solves problems that mostly do not exist at SMB scale, where nearly all software is SaaS billed per seat rather than perpetual licenses subject to vendor audits.
If you have been reading enterprise SLM vendor content and feeling like you must be missing something: you are not. This page separates the part of the discipline that applies to you from the part that applies to a 20,000-seat Oracle estate.
Why the Enterprise Playbook Doesn't Map
Classic software license management grew up around perpetual licenses: you bought Oracle, SAP, or Microsoft licenses outright, deployment could silently exceed entitlement, and vendors ran formal audits with real financial teeth. The tooling — discovery agents, entitlement reconciliation, effective-license-position reports — exists to win those audits.
An SMB SaaS stack inverts almost every assumption. You cannot meaningfully "over-deploy" a SaaS product — the vendor's own billing enforces the seat count. Your risk runs the other direction: paying for seats nobody uses, and auto-renewing contracts nobody reviewed. The discipline you need is closer to vendor and renewal management than to compliance defense — which is why our vendor management framework for controllers overlaps heavily with this page.
The Four Jobs, Concretely
- Complete inventory. Every paid tool, found from the money, not from memory — mine your accounting exports (Xero walkthrough here) and expense claims. Memory typically misses 20–40% of vendors.
- Seats paid vs. seats used. For each tool over ~$2,000/year, compare licensed seats to active users (most admin panels show last-login). Re-check at every renewal, not continuously.
- Renewal dates and notice deadlines. The contractual decision point per tool, with an alert that fires 60–90 days before it.
- A named owner per tool. One person accountable for the usage answer and the renew/cancel recommendation.
That's the whole program. It fits in a tracker and a quarterly habit.
What You Can Skip Below 200 Employees
| Enterprise SLM concept | What it is | Below 200 employees |
|---|---|---|
| Software metering agents | Endpoint agents measuring per-app usage | Skip. SaaS admin panels give you last-login for free |
| Effective License Position (ELP) reports | Formal entitlement-vs-deployment reconciliation | Skip. SaaS billing is the reconciliation |
| Audit defense tooling | Evidence preparation for vendor license audits | Skip unless you hold legacy Microsoft/Oracle perpetual licenses |
| CMDB / ITAM suite integration | Licenses linked to a configuration management database | Skip. You don't have a CMDB, and don't need one for this |
| License harvesting automation | Auto-reclaiming unused licenses into a pool | Skip the automation; keep the habit — manually right-size at renewal |
| Software request/approval workflow engine | Ticketed intake for all software requests | Simplify to a spend-threshold approval matrix in your expense policy |
| Renewal calendar with notice-deadline alerts | Know when decisions are due | Keep — this is the core |
| Seat utilization review | Paid vs. active seats | Keep, as a renewal-time check |
| Contract repository | Order forms attached to vendor records | Keep — terms live in PDFs, not in your ledger |
| Named tool owners | Accountability per contract | Keep |
The pattern: skip anything that exists to measure continuously or defend audits; keep anything that exists to decide renewals well.
Worked Example: A 120-Person Company's First License Review
A 120-person professional-services firm runs the four jobs for the first time. The inventory pass (15 months of accounting data plus expense claims) finds 74 paid tools against the 51 the ops lead could name — $46,000/year of the gap sitting in expense claims and processor-masked charges.
The seat review covers the 11 tools over $2,000/year:
| Tool (category) | Seats paid | Active (60-day) | Annual cost | Action at renewal |
|---|---|---|---|---|
| CRM | 45 | 38 | $32,400 | Right-size to 40 → saves $3,600 |
| Design platform | 25 | 12 | $10,800 | Right-size to 15 → saves $4,320 |
| E-signature | 10 | 9 | $4,800 | Renew as-is |
| Analytics suite | 20 | 4 | $9,600 | Owner review — likely downgrade tier → saves ~$6,000 |
| Other 7 tools | — | — | $41,300 | Renew; two get annual-prepay conversion → saves $1,950 |
Total identified at first pass: ~$15,870/year (about 11% of the firm's $144,000 SaaS spend) — squarely in line with industry estimates that hover around a quarter of SaaS spend being wasted or underused, given this firm only reviewed its top 11 tools. None of it required an agent, a CMDB, or an ELP report; it required an export, eleven admin-panel checks, and renewal-time follow-through. The follow-through is the catch: every saving in that table is only collectible at each contract's notice deadline, which is why the renewal calendar is the keep-pile's centerpiece.
The Minimal Toolset
- System of record: a renewal tracker holding vendor, cost, seats, owner, renewal date, notice period, and the contract PDF. Satellite does exactly this scope — CSV import, renewal alerts, expense-based discovery to keep the inventory honest — at a flat $299/month, and deliberately does not do metering agents or ITAM workflows.
- Process: a quarterly inventory refresh from accounting exports, plus the 90-day renewal process for material contracts.
- Policy: a one-page approval matrix by annual contract value, in the expense policy.
A spreadsheet can hold the data but cannot fire the alerts — and at SMB scale, the alert is the license management.
FAQ
Do SMBs ever face software license audits?
Rarely, and almost only for legacy perpetual licenses (Microsoft volume licensing, Oracle, Adobe pre-Creative-Cloud). If you hold those, keep purchase records and deployment counts for them specifically. Pure-SaaS stacks have effectively no audit exposure of this kind.
Is software license management the same as SaaS management?
They overlap. "License management" historically means entitlement compliance for installed software; "SaaS management" means visibility, spend, and renewals for subscriptions. For an SMB whose stack is ~95% SaaS, the useful subset of both is the four jobs above.
How often should we review seat utilization?
At renewal, per tool — that's when the finding is actionable. A continuous utilization dashboard is enterprise tooling for enterprise scale; at 200 employees it mostly tells you in March what you can only act on in November.
What about open-source and free-tier tools?
Track free tiers that hold company data or could silently convert to paid — a one-line entry with an owner is enough. Open-source license compliance (GPL obligations etc.) is a real but separate engineering topic, not part of this finance-side program.
Skip the ITAM suite; keep the calendar. Load your vendor list into the free renewal tracker and the four jobs are covered by Friday — or sign up for Satellite at a flat $299/month.