Somewhere in your company, a laptop is sitting in a drawer, and nobody is entirely sure whose drawer it is. It still appears on an insurance schedule, still carries a support contract, and still has an old account signed in, but the person who used it left eleven months ago, and the offboarding checklist never made it as far as the hardware. That laptop is not an anomaly. It is the ordinary condition of most growing organizations, and the only reason it has not caused a problem yet is that nobody has gone looking.
Hardware used to be easy to watch because it stayed where you put it. Desktops lived under desks, servers lived behind a locked door, and an IT lead could walk the floor on a Friday and physically count what the company owned. That world is gone. A modern fleet is laptops that travel, phones on mixed data plans, tablets in retail sites, docking stations that drift between desks, and a long tail of monitors and headsets that add up to serious money even though no single item ever feels worth logging.
The financial pressure is sharpening, too. Component costs have climbed steeply over the past year, something Techjaja traced in detail when it explained why smartphone prices are rising in Uganda. Once a replacement device costs meaningfully more than it did twelve months ago, the machine already sitting in a cupboard turns into an asset worth recovering, and the record that tells you where it went stops looking like administrative busywork.
The Sprawl Nobody Planned For
No team decides to lose track of its equipment. It happens by accretion. A spreadsheet gets started with good intentions, then a hiring sprint adds forty people in six weeks, two offices open, a procurement request gets approved over Slack, and the spreadsheet quietly stops matching reality. Six months later the finance team is reconciling purchase orders against a document nobody trusts, and the honest answer to how many laptops do we have is a shrug with a range attached. The failure is rarely dramatic. It is a slow drift between what the company bought and what the company can actually account for, and because the gap never announces itself, it tends to be discovered during an audit, an acquisition, or a security incident, which are the three worst moments to discover anything.
What It Costs When the Record Goes Stale
Stale records cost money in ways that are easy to miss on a monthly report. Duplicate purchases are the obvious one: a manager cannot find a spare machine, so they buy a new one, and a perfectly serviceable device keeps depreciating in storage. Then there are the subscriptions and warranties that keep renewing on hardware that was retired years ago. Lease returns get messy when you cannot produce the serial number a vendor is asking for, and refresh planning turns into guesswork because nobody knows the real age distribution of the fleet. Teams that move to proper it asset tracking software usually find the first savings sitting right there, in the equipment they already own but could not previously see.
Distributed Teams Changed the Math
Remote and hybrid work did not create this problem, but it removed the informal safety net that used to mask it. When everyone worked in one building, you could find a device by asking around. Now a laptop might be in a city you have never visited, shipped by a vendor you onboarded over email, assigned to a contractor whose engagement ended in March. Shipping hardware to a home address and getting it back later is a logistics exercise with a genuine failure rate, and the cost of a single device vanishing is more than the hardware line item. It includes the data on it, the license attached to it, and the hours someone spends trying to work out what happened.
Security Teams Feel It First
Security practitioners have been making this argument for years, and they are not being dramatic about it. The CIS Critical Security Controls put inventory and control of enterprise assets at number one, ahead of everything else, on the straightforward logic that you cannot patch, configure, or defend a machine you do not know exists. NIST makes a similar case in its practice guide on IT asset management, which points out that knowing where a computer is tells you very little about what it is running or which vulnerabilities it carries. Unmanaged devices are where attackers go looking, precisely because nobody is watching them.
Where a Better Record Starts
The fix is less glamorous than it sounds, which is probably why it gets deferred. Start by agreeing on what counts as an asset worth tracking, because a list that includes every cable will be abandoned within a month. Pick the few fields that actually drive decisions: what it is, who has it, where it is, when it was bought, and what happens to it next.
Then connect the record to the moments when it changes. Assignment, transfer, repair, and offboarding are the four events that break inventories, and a system that captures them automatically will stay accurate long after a manual one has drifted. The goal is not a perfect database; it is a record people believe enough to act on.
None of this is exciting work, and it will never be the thing a leadership team puts in a board deck. But the companies that handle it well spend less on hardware, pass audits without a scramble, and give their security teams a floor to stand on. That is a decent return for a habit, and the cost of not building it only grows as the fleet does.
