IT Asset Management used to serve a single function: tracking what a business owns. That’s changing. CIOs are increasingly relying on ITAM solutions to decide what they should and shouldn’t keep paying for. Meanwhile, the teams that get burned aren’t the ones without an ITAM tool; they’re the ones whose ITAM tool only tells them what exists, not what’s being used. This shift is being driven by three pressures on IT organizations:
- SaaS sprawl, as departments and employees adopt tools outside IT’s visibility
- Shadow IT, where unauthorized software and devices go untracked and unsecured
- Increased CFO scrutiny of software and IT spend, requiring CIOs to defend budgets with data, not estimates
What “spend intelligence” actually requires
Using ITAM as a spend intelligence tool isn’t as simple as bolting a new dashboard onto an old system. Executing this transition successfully depends on connected data. To answer the question “what are we paying for, and is it being used,” a platform needs to link the following in one model:
- Hardware and software assets
- License and subscription usage
- The users and devices tied to each asset
- Related tickets and lifecycle activity
That means CIOs need a platform with the capacity to support this model, not retrofitted for it. AssetSonar’s IT Graph, for example, connects assets, software, users, contracts, and tickets in one place. This makes it possible to view spend, ownership, and usage together instead of across disconnected tools and spreadsheets.
Supporting this model also requires a specific set of core capabilities, including:
- Hardware asset lifecycle tracking
- Software management, including Shadow IT detection and software normalization
- IT service management for tickets and workflows
- Patch management and vulnerability management
- Workflow Automation for offboarding, renewals, and license reclamation
Proof points: what spend intelligence looks like in practice
Organizations that connect asset, license, and usage data tend to report similar outcomes: fewer unused licenses, faster offboarding, and clearer audit trails. Documented examples illustrate the range of impact this kind of visibility can produce. A K-12 school district using AssetSonar reduced Chromebook loss by 4x and saved $28,000 in its first year after adopting a connected asset model.
Results like this come from customers using AssetSonar, one of several IT management platforms built around this kind of connected data model. AssetSonar’s standing as a G2 High Performer in the mid-market indicates that this approach is gaining traction across the category, not just at a single vendor.
What CIOs should ask ITAM vendors
When evaluating an ITAM platform, CIOs should look past the feature list and ask whether the tool actually supports connected, financially useful data. A good starting point is whether the platform can automatically link license data to actual usage, without relying on manual exports or spreadsheet reconciliation. It’s also worth asking whether the system can surface unused, underused, or duplicate licenses before renewal, rather than after the fact, when the opportunity to cut costs has already passed.
Visibility matters just as much as automation. CIOs should confirm that a platform can detect Shadow IT across on-premises, browser- or cloud-based tools. After all, intelligence is only as complete as the data feeding it. Integrations are another key consideration: the platform should connect with existing identity, MDM, and SaaS systems. These include Okta, Azure AD, Intune, Jamf, or Microsoft 365. This is preferable to requiring a wholesale replacement of tools already in place.
Finally, CIOs should ask who actually gets to see the resulting data. If Finance and IT are working from separate systems or separate versions of the truth, the promise of spend intelligence breaks down before it starts. The right platform gives both teams a shared, consistent view of spend.
What this looks like in a real budget cycle
Most CIOs don’t feel the absence of spend intelligence until renewal season. That’s when Finance asks a simple question IT can’t answer quickly: which of these subscriptions are we actually using? Without connected data, answering that question means pulling license counts from one system, usage logs from another, and device assignments from a spreadsheet someone updated three months ago. Then someone has to reconcile all of it by hand before the renewal deadline hits.
With a connected model, the same question has a different shape. Licenses are already linked to the users and devices assigned to them, so unused or underused seats surface on their own instead of requiring a manual audit. A platform that also connects tickets and lifecycle activity adds another layer: if an employee offboarded two months ago but their software licenses were never reclaimed, that gap shows up automatically instead of persisting in the background, unnoticed until the next renewal invoice arrives.
The difference isn’t just speed. ITAM as an intelligence layer changes who owns the decision. In the manual version, IT is reacting to a Finance question under pressure, often defaulting to “renew as-is” because there isn’t time to investigate further. In the connected version, IT can bring Finance a recommendation before the renewal notice even arrives, backed by actual usage data rather than a best guess.
This is also where the CFO scrutiny mentioned earlier stops being an annual fire drill. Instead of reconstructing spend visibility from scratch every renewal cycle, IT and Finance are working from the same continuously updated picture. That’s the practical difference between ITAM as a compliance record and ITAM as a spend intelligence layer: one gets consulted once a year under pressure; the other gets checked continuously, and shapes decisions before pressure builds.
Spend intelligence is the new baseline
Spend intelligence is no longer a premium feature bolted onto ITAM. Today, it’s a baseline expectation. As IT budgets face more scrutiny and technology stacks grow more fragmented, CIOs can no longer treat IT asset tracking and cost control as separate problems solved by separate tools. The organizations getting this right are the ones treating connected data as the foundation of ITAM, not an afterthought layered on top of it.
For CIOs evaluating their next ITAM platform, the real question isn’t which vendor has the longest feature list. Now CIOs have to consider whether the platform is built around a connected data model that can turn asset, license, and usage information into a defensible spend decision, because that is increasingly what modern ITAM is meant to be.


