assetinventoryranked.com · Asset inventory buyer's guide · September 2026
Field notes · Guide · Survey date: September 2026
IT Asset Inventory Buyer's Guide for 2026
3 min read
Bottom line
Decide first whether you need to discover assets directly, reconcile the tools you already run, or both. Then test coverage, correlation and write-back on your own data during a 30-day evaluation. Ask every vendor for a price in writing before the pilot ends.
Which approach do you need?
Network discovery (runZero, Lansweeper, Armis)
finds what is on the network, including devices no tool knows about. Fast to start. Weaker on SaaS and identities.
Aggregation and CAASM (Axonius, JupiterOne)
reconciles the tools you already run into one record per asset. Broadest coverage. Setup scales with the number of sources.
CMDB and lifecycle (ServiceNow, Device42, Oomnitza)
system of record and workflows for IT operations and asset lifecycle. Strongest on process. Usually fed by one of the other two.
What should you ask vendors?
- 01. Which of these asset classes do you cover natively and which only through integrations: laptops, servers, cloud workloads, SaaS apps, identities, OT and IoT, network devices?
- 02. How do you decide that two records from different tools describe the same asset?
- 03. When two sources disagree, which one wins, and can we change the rule?
- 04. How often does each source refresh, and what sets the limit?
- 05. Can we ask "which assets are missing control X" across all sources in one query?
- 06. What can the product change in other systems (tickets, CMDB records, device actions), and what permissions does that need?
- 07. How long did your last three comparable deployments take to reach full coverage?
- 08. What credentials, agents or network placement do you need?
- 09. Is it SaaS, self-hosted or both, and where is our data stored?
- 10. What is the price for our asset count, in writing, and what changes it?
- 11. Which integrations are included and which cost extra?
- 12. What does the export look like if we leave?
How do you run a 30-day evaluation?
- Week 1: pick three questions your team cannot answer today, for example which servers lack an EDR agent. Write down the current answer and how long it takes.
- Week 2: connect the sources, or run discovery, on a representative slice of the estate. Record the setup time per source.
- Week 3: compare the tool's answer to the three questions with the week 1 answer. Check a sample of assets by hand.
- Week 4: test write-back: open a ticket or update a CMDB record from the tool. Get the price in writing.
What are the common mistakes?
- Comparing asset counts between vendors. A higher count can mean more duplicates, not more coverage.
- Treating the CMDB and the asset inventory as a choice. Most teams need both.
- Skipping the write-back test. An inventory that cannot hand work to the owner leaves the gap open.
- Leaving pricing to the end. Three of the seven tools in our ranking do not publish prices.
Frequently asked questions
How long does an asset inventory deployment take?
It depends on the approach. Agentless discovery tools can produce a first inventory in minutes to hours, according to vendors such as Armis and runZero. Aggregation platforms reach full coverage as each source is connected.
What is the most important criterion?
On our rubric, source coverage (22%) and correlation (18%). Without both, the inventory is either incomplete or untrusted.