IT Asset Management for Small Business: PCs, Accounts, Cost
A practical IT asset management guide for small businesses with no dedicated IT staff: what to track, how to run a first inventory, when a spreadsheet stops working, and typical tool costs.
What IT asset management actually covers
IT asset management means keeping continuous track of the IT-related items and rights your company owns or subscribes to, along with where they are, who uses them, what state they are in, and when they expire. The scope is not limited to hardware such as PCs and smartphones. It normally also covers cloud service accounts used for work, software licences, domain and SSL certificate contracts, and network equipment. In practical terms, the goal is to reach a state where you can answer: how many do we have, who uses each one, and when does it expire?
In large companies this is handled by a dedicated department with purpose-built tooling. In smaller companies, the device count simply grows while nobody owns the problem. Rather than aiming for perfect records from the start, it is more realistic to begin by eliminating the questions you currently cannot answer.
What goes wrong when nobody is tracking
The losses that occur in companies with weak asset tracking are quiet ones. Individually each is small, but over several years they add up to meaningful money and time.
Monthly charges for unused SaaS subscriptions continue for years
Accounts belonging to former employees remain active, leaving company data reachable from outside
Nobody knows which software is installed on which PC, creating licence compliance risk
PCs running an end-of-life OS stay in daily business use
When a machine fails, nobody knows who bought it or when, so there is no warranty and no handover documentation
Leftover accounts in particular go beyond wasted money and lead directly to security incidents. Access rights for departing staff are covered in detail in our guide to offboarding cloud accounts, and preparing for OS and software end-of-life is covered in our EOL preparation guide.
Four categories to track
Trying to manage everything at once is how these projects fail. Split the scope into four categories and start with the ones carrying the most risk and cost.
| Category | Examples | Fields to record | Priority |
|---|---|---|---|
| Hardware | PCs, phones, tablets, MFPs, routers | Model / purchase date / user / warranty end / OS | Medium |
| Accounts | Cloud accounting, groupware, social media, admin consoles | Service / user / permission level / who is the admin | Highest |
| Software and licences | Office suites, business software, design tools | Seats bought / seats used / renewal date / payment method | High |
| Contracts and rights | Domains, SSL certificates, servers, network lines | Vendor / renewal date / auto-renew or not / billing contact | High |
Accounts and contracts rank highest because neglecting them causes information leakage or service outage rather than merely wasted spend. A missed domain or SSL certificate renewal surfaces as your website suddenly going dark.
Running your first inventory in five steps
For the first pass, aim to complete one full cycle rather than to be exhaustive. For a company of around 30 staff, two to three days of work is usually enough to get something usable.
1. Work backwards from payments — review twelve months of card statements and bank debits and list every IT-related charge. Unexplained subscriptions surface here
2. Work forwards from people — using the staff list, ask each person to declare the PCs and accounts they use
3. Count the physical devices — include spares in storage and machines returned by leavers, then reconcile against the ledger
4. Confirm ownership — check whose email address each service's admin account is tied to, and move personal addresses to a shared company address
5. Consolidate renewal dates — put domain, certificate, maintenance contract and licence renewal months into a single calendar
Steps 1 and 4 deliver the most value. Working backwards from payments is the only reliable way to catch services that nobody declares but that keep billing you. Checking admin account ownership prevents the situation where a service becomes unusable the moment one employee leaves. That dependency risk is covered in our article on preventing system knowledge from leaving with staff.
Spreadsheet or dedicated tool?
Dedicated IT asset management tools exist, but at smaller scales a spreadsheet ledger works perfectly well. The following gives a rough dividing line.
| Approach | Suited to | Rough cost | Limits |
|---|---|---|---|
| Spreadsheet ledger | Up to around 50 PCs, one or two sites | Effectively free (labour only) | Manual updates drift from reality |
| Cloud IT asset management tool | 50–300 PCs, multiple sites | Roughly JPY 200–500 per device per month | Initial data entry is laborious |
| MDM / device management service | Many company phones or laptops off-site | Roughly JPY 300–800 per device per month | Contract tracking still needs a separate ledger |
| Outsourced IT support | No internal owner available | Roughly JPY 30,000–150,000 per month depending on scope | Scope boundaries need defining |
These figures are general market ranges and vary with features and contract terms. The main benefit of a tool is that devices report their own details automatically, so the ledger drifts less from reality. Conversely, a company with few devices and little staff turnover can run perfectly well on a manual inventory twice a year. Outsourcing options are covered in our guide to IT support outsourcing and advisory costs.
Rules that keep it alive
A one-off inventory becomes useless within six months. Only four rules are needed to keep it current.
Add a ledger-update line to your onboarding and offboarding checklists
Require one named approver for every new IT contract, so that anyone can no longer sign up unilaterally
Set an annual date to review the consolidated renewal calendar
Store the ledger somewhere everyone can find, never on one person's PC
None of these require new tooling or budget. Asset management usually fails not for lack of a tool but because nothing in the normal workflow triggers an update. For structuring the workload of a sole or part-time IT person, see our guide for one-person IT departments.
Checklist before you start
Can you state how many PCs the company owns, right now?
Can you list every IT-related payment from the past twelve months?
Is each cloud service's admin account held in the company's name?
When did you last verify that former employees' accounts are disabled?
Do you know the renewal dates for your domains and SSL certificates?
Are any PCs running an end-of-life OS still in business use?
If two or more of these cannot be answered immediately, an inventory is worth doing. IT asset management is not a growth investment, but the first pass often pays for itself simply by stopping charges nobody needed. For the wider security picture and how to prioritise, see our complete guide to IT risk for small businesses.
Frequently asked questions
At what company size does IT asset management become necessary?
Headcount matters less than whether there are questions you currently cannot answer. A ten-person company with ten cloud subscriptions already has plenty to track, while a thirty-person company using only two or three systems can manage with a single spreadsheet. As a rough guide, a ledger starts paying off once you pass roughly twenty PCs or ten SaaS contracts.
How long does an inventory take?
For a company of around thirty staff, the first pass typically takes two to three working days in total. The slowest parts are not counting devices but tracing subscriptions from payment history and identifying who administers each service. Subsequent rounds only cover changes, so half a day every six months is usually enough to maintain.
Can a dedicated tool automate all of this?
Tools can automatically collect hardware details and installed software from PCs, but information such as who uses a device and why a contract exists still has to be entered by a person. Contract data like domains and SSL certificates is often outside a tool's scope entirely. Automation covers part of the problem only, and needs to be paired with operating rules.
We want to cancel unused SaaS but cannot tell who is using it. What now?
Most SaaS admin consoles show last login dates, which is the quickest way to identify real users. If you cannot reach the console, share the service name from the billing statement internally and ask anyone who recognises it to say so. Check whether data can be exported before cancelling, because some services delete data immediately on termination.
What format should the ledger take?
A spreadsheet with three sheets — hardware, accounts and contracts — each carrying a user column and a renewal date column is easy to work with. What matters is that it keeps getting updated, not how many fields it has, so start with a narrow set of columns and add more as the process settles. Keep the file in cloud storage so people other than the owner can reach it.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us