The hidden 20–30% in your SmartNet contracts

Vendor maintenance contracts are the quietest line item in IT budgeting. They renew automatically, get billed as a percentage of hardware list price, and almost never get audited against what is actually still deployed. The result is a structural leak: companies pay to maintain hardware that is dead, gone, or past end-of-life.

20–30% of a typical maintenance contract covers hardware that is dead, gone, or end-of-life.

That range is not about a few forgotten routers in a decommissioned closet. At enterprise fleet sizes, 20–30% of annual maintenance spend is often six figures to seven figures of pure waste — renewing coverage on assets that either no longer exist, were replaced but never removed from the contract, or reached end-of-life years ago while the line item kept billing.

Where the waste hides

• Dead assets — decommissioned hardware that was never removed from the maintenance contract.
• Gone assets — devices returned to the vendor, swapped in a refresh, or sent to recycling, with the coverage still renewing.
• End-of-life assets — hardware the vendor no longer supports or will sunset, where you are paying full price for coverage with a shrinking (or zero) real obligation.

The reasons these persist are structural, not malicious. Contract renewals are aggregated by a procurement team that does not have a live view of the installed base. The asset register lives in a CMDB that nobody reconciles against vendor quotes. And the vendor quote itself is a roll-forward of last year's list — so errors compound annually.

The data already exists

Finding the waste does not require a consultant or a new data source. Every company already holds the two datasets needed: the maintenance contract line items (in the vendor quote or renewal notice) and the live asset inventory (in the CMDB, or simply the last good export from the asset management tool). The work is a reconciliation: match every contract line against an asset that is actually deployed, supported, and worth covering.

That is the kind of analysis that should happen before every renewal cycle — not after the invoice posts. When the contract rolls forward each year, it should roll forward against reality: every line item justified by an asset that exists, runs, and is still supported.

A maintenance contract is a liability, not a subscription

The shift in mindset is the hard part. A maintenance contract is treated as a sunk cost — "we've always had SmartNet on everything." But it is a liability that should be minimized to what the deployed base actually needs, and re-negotiated against that reality. The companies that close the 20–30% leak do it by treating the renewal as a data problem, not a paperwork problem.

The platform we are building exists to make that reconciliation routine: upload the contract export and the asset export, and get back a line-by-line view of what is covered, what is waste, and what the contract should cost next year.