How we picked
Asset management inside a helpdesk lives or dies on one thing: whether the asset data is fresh enough that agents trust it. Every tool in this category can store a spreadsheet's worth of hardware records. The difference is what keeps those records current — an agent installed on the endpoint, a network probe scanning subnets on a schedule, an RMM feed, or a human who is supposed to update the register and doesn't. We ranked automated discovery heavily, because a stale CMDB is worse than no CMDB: it produces confident wrong answers during incidents.
The second thing we weighted is the join between the asset and the ticket. Plenty of platforms sell "ITSM with assets" where the two modules barely speak — you can look up a laptop, and separately you can look up a ticket, but the agent working the ticket doesn't see the laptop's patch level or the change that touched it last Tuesday. That join is the entire value proposition. Freshservice and ServiceNow do it natively and well. Vivantio does it cleanly along ITIL lines. Syncro does it from the MSP direction, where the RMM already owns the device.
Third, we split the list by estate shape rather than company size, because those correlate poorly. A 60-person company with a regulated hardware inventory and a 900-person company with everything in SaaS have opposite requirements. Halo earns its place because asset management there isn't IT-only — it extends to facilities, vehicles, and HR-issued equipment, which is the actual situation in manufacturing, healthcare, and field-service organizations that keep getting sold IT-shaped tools.
What to prioritize
- Discovery method, in writing. Ask whether it's an installed agent, an agentless network scan, or an integration with something you'd have to buy separately. Agent-based discovery covers remote and hybrid workers who never touch the office LAN; network probes do not. If half your fleet is at home, an agentless-only tool will silently under-report your estate.
- Reconciliation between installed software and purchased entitlements. This is where asset management returns money. A tool that lists installed apps is inventory; a tool that tells you you're 40 seats over on one product and 200 seats under on another is a business case. Freshservice and ServiceNow do this; most of the cheaper options don't.
- Relationship mapping, if you have shared infrastructure. Being able to answer "what breaks if this host goes down" during an outage requires modeled dependencies, not tags. If you run on-prem servers or internal applications with real dependency chains, this pushes you toward ServiceNow or Vivantio. If you're all-SaaS with laptops, it's overhead you don't need.
- Lifecycle and contract dates that trigger work. Warranty expiry, lease end, and refresh dates should automatically create tickets or approval requests, not sit in a field waiting for someone to run a report. Confirm the tool can fire workflow off a date field — several in this category can only report on it.
- Barcode or QR handling and a mobile app. If someone will do a physical audit or provision hardware at a desk, they need to scan and update from a phone. Test this on real hardware during the trial; mobile asset flows are consistently the weakest part of otherwise strong platforms.
- An export you'd actually accept. Your asset data will outlive your helpdesk vendor. Confirm full CSV or API export of assets, relationships, and custom fields before you commit — some CMDBs export the items but not the relationships, which is the expensive half to rebuild.