Shelfware

Shelfware is software an organisation has bought and is paying for but does not meaningfully use: licences procured in a burst of enthusiasm or bundled into a larger deal, deployed once, and then left idle until somebody notices the line item at renewal. The word predates SaaS — it described boxed enterprise software that literally sat on a shelf — but subscription billing made the problem quieter and more expensive, because nothing physical accumulates dust to remind you. A tool nobody opens still renews on schedule, still shows up as a recurring charge, and still passes unexamined through an approvals process that only checks whether the invoice matches last year's. Shelfware forms in a few reliable ways: a champion who bought the tool leaves the company and nobody inherits it; a platform deal bundles modules you never intended to use in exchange for a discount on the one you did; a pilot succeeds technically but never gets rolled out; or the tool is genuinely used by six people while the contract covers sixty. The cost is not only the wasted spend. Unused tools still hold customer data, still count as vendors your security team is responsible for, still expand the surface a breach can come through, and still require an offboarding project when you finally cancel. Finding shelfware means comparing entitlement to actual behaviour — seats provisioned against seats with a login in the last ninety days, licences purchased against active accounts in the vendor's own admin console, and spend per tool against a named business owner who can say what it is for. The remedy is unglamorous: an inventory of every subscription with a renewal date and an owner, a usage check before each renewal instead of after it, and the discipline to downgrade or cancel rather than quietly re-signing because cancelling requires a conversation.