PART 3 OF A SERIES ON MID-MARKET IT ASSET MANAGEMENT
Part 1: Your Fixed Asset Register Is an Archaeological Site
Part 2: You Have Asset Data. You Do Not Have Asset Management.
The drawer of saved things, the question before the purchase order, and the discipline of not buying.
The drawer of saved things
In the house I grew up in, nothing was bought twice. Before any purchase was permitted, my mother conducted what I now recognize as an audit: she opened the drawer of saved things, buttons cut from shirts too worn to mend, jars stripped of their labels, lengths of wire coiled against some future need, and she asked the question that governed our household economy. Not “can we afford it?” That question came second, if it came at all. The first question, always, was: do we not already have one?
We were not poor. We were disciplined. In that house, waste was not merely expensive; it was a kind of disgrace, and the defense against it was not a budget but a habit: the habit of looking before buying.
The inversion
I have spent the years since watching organizations with ten thousand times my mother’s budget operate with none of her discipline. The corporate purchase request begins where her process ended at the approval. An employee needs a laptop, and the workflow asks who must sign; it does not ask what the company already owns. A team requests more licenses, and the renewal moves through three signatures without anyone checking whether the licenses already paid for are being used, or whether half of them remain assigned to people who left in the spring.
The first question is never asked, because no system in the chain is positioned to answer it. And this is not a small-company affliction that maturity cures; it is sharpest at exactly the size where memory has stopped being a control: a few hundred employees, hybrid teams, two offices, and procurement split across IT, admin, and whoever holds the card.
And for the past decade, we have been busy automating this inversion. Requests move faster; approvals move faster; purchase orders are raised in minutes that once took days, and procurement teams report cycle time the way athletes report personal bests. I do not dismiss any of this; speed has real value, and manual procurement was its own kind of waste.
But the premise beneath all that acceleration goes unexamined: that the purchase should happen at all. Automation without context does not improve a decision; it accelerates a default, and in most procurement workflows, the default is to buy. We are not buying better. We are buying sooner.
In Part 2 of this series, I gave this pattern its honest name: procurement duplication: buying around your own ignorance. This essay is about the habit that prevents it; a habit that must live in the system, not in anyone’s memory.
Where money goes to die
I came to finance through audit, and audit teaches a particular kind of sight: you stop reading the numbers and start looking for the things behind them. I have walked enough year-end physical verifications to know what an asset register looks like once it has drifted into fiction, equipment on the books that nobody can locate; laptops sleeping in storeroom cupboards while new ones arrive upstairs, still shrink-wrapped; software renewed each year out of pure habit, the invoice approved by someone who has never seen a utilization report.
The gap between what a company believes it owns and what it actually owns is not a clerical curiosity. It is where money goes, quietly, to die.
The walks themselves were an education in what a list demands of the human body. Floor-to-list, then list-to-floor; the same vast pages carried in both directions; machines turned upside down, torch angled into their undersides, hunting serial numbers that ran long and unreadable, like the chassis and engine numbers of cars, and read with the same squint. An afternoon of that settles the question for life: a register that demands this much labor to confirm is not confirming anything. It is being rebuilt, by hand, every time someone needs it to be true.
You do not need my verification walks; run your own. Pull last quarter’s hardware purchase orders. Then open the storeroom, the actual cupboard, not the spreadsheet that describes it, and count what is sitting there, boxed, recoverable, or still assigned to someone who no longer works for you. If the two lists have never met, you have found the gap I am describing, and you found it in an afternoon, which should tell you how hard it was to look for you.
This is why I have come, over time, and against my own early assumptions, to regard IT asset management as a finance function wearing an operations badge. The asset register, kept honestly, is not an inventory list; it is the operational truth beneath every technology line in the budget, the one document that can tell finance what is owned, what sits idle, what is approaching the end of its useful life, and what next quarter’s spend will demand before the requests start arriving.
Before the approval, a question
Seen this way, the questions that should precede every purchase order write themselves. Six of them, and none takes longer to answer than it takes to sign the approval.
The Six Pre-Purchase Questions:
1. Do we already own this?
2. Is there an idle device that can be reassigned before a new one is bought?
3. Is there a license, paid for and unused, that can be reclaimed before the contract is expanded?
4. Is the broken unit still under warranty?
5. Is repair cheaper than replacement, and do we hold the repair history to know?
6. Did another department buy this exact thing last quarter?
Before the approval, a question; before the question, a record; before the record, a discipline.
In practice, this is less philosophy than plumbing. A laptop request should surface available stock before it routes for signature. A renewal should land on the finance desk with usage attached, licenses assigned, licenses active, and licenses idle, so the negotiation begins with evidence rather than the vendor’s quote.
Offboarding should include recovering the device and licenses using the same checklist used to recover the access card. Lifecycle data should turn next year’s replacement cycle from a guess into a forecast. And duplicate requests, two departments buying the same tool in the same quarter, each ignorant of the other, should collide in the system before they collide in the budget review.
Counting what did not happen
The difficulty, for finance, is that the return on this discipline is largely invisible. No journal entry records the laptop you did not buy; no ledger carries a line for the renewal you right-sized. Procurement avoidance is the invisible line item, real money, unrecorded, and this is precisely why asset management struggles to justify itself through conventional reporting. The remedy is to deliberately measure what the books will not show on their own. Four numbers, none of which your ledger will ever volunteer.
The Four Metrics of Procurement Avoidance:
- Reclaimed value. What was recovered, reset, and reassigned instead of repurchased.
- Fulfillment from stock. Requests closed from existing inventory rather than from new spend.
- Renewal delta. Licenses cut at renewal because usage, not the vendor’s quote, set the number.
- Audit variance. The shrinking gap between what the register claims and what the walk confirms.
Each is real money; each is invisible to conventional reporting; and together they are the beginning of a scorecard worth building properly. For now the principle is enough: finance must learn to count what did not happen.
None of this is an argument for slowness, and none of it is an argument against buying. Growing companies buy; they should, and the buying should be fast. The argument is about sequence: the question of need precedes the mechanics of purchase, and a process that skips the first to optimize the second is not efficient; it is merely quick. And your workflow engine cannot fix this on its own: an approval chain with no register behind it can only route the request; it cannot interrogate it. Good asset management does not put friction back into procurement. It puts judgment back in.
The question you must ask first
A disclosure, because you deserve one: I am the finance director of a company that builds IT asset management software, and you are entitled to discount everything above accordingly. But the conviction predates the employment. It was formed in audit rooms, on verification walks through storerooms and server closets, and earlier than either, in front of a drawer of saved things.
So here is what I would ask of you before the next purchase order crosses your desk. Do not begin with the signature chain; begin with the register. Ask what you own, what sits idle, what can be reclaimed, what the warranty already covers, ask the household question first, and build systems capable of answering it. The best ITAM programs do not just tell you what you own. They tell you what not to buy next.
Go and open the drawer.
