Every organization that commissions a technology spend review for the first time has some expectation of what it will surface. Most of those expectations are wrong — not because the problem is worse than anticipated, but because it’s different. The waste tends to show up in places that aren’t obvious from the outside, and the patterns are more consistent across organizations than most people expect.
The patterns that show up in almost every review
Enough organizations have done this work — and enough reviews have produced similar findings — that it’s possible to predict, before looking at any data, what categories of waste are most likely to exist.
Active services for people who no longer work there
This is the single most consistent finding across every engagement type. Software licenses, mobile lines, device subscriptions, and carrier services remain active for months or years after employees leave because offboarding processes don’t include vendor-side deactivations.
The gap exists because offboarding is typically managed as an IT and HR process, and vendors are outside that process. When an employee leaves, the IT checklist handles device return and directory deactivation. Finance handles final pay. But the vendor — the carrier, the SaaS platform, the MDM provider — receives no notification and continues billing until someone tells them to stop.
At a 50-person company with 20% annual turnover, 10 employees leave per year. If even half of their services take six months to be identified and canceled, that’s five employees’ worth of services billed for six months at no benefit. Multiplied across a portfolio, the annual cost is material.
Contracts that auto-renewed without anyone noticing
Most technology contracts include auto-renewal clauses. The mechanism works the same way regardless of vendor: if neither party provides written notice within the notification window — typically 30, 60, or 90 days before the renewal date — the contract extends for another full term at current pricing.
Organizations that don’t maintain a renewal calendar don’t have visibility into when these windows open and close. Contracts cycle through renewal after renewal at original pricing, often at a time when the vendor relationship, the usage level, and the market pricing have all changed significantly from when the contract was first signed.
The finding in reviews is not that organizations are choosing to auto-renew without negotiation. It’s that they don’t know the window has opened until after it has closed.
Duplicate tools doing the same job
Department-level purchasing is the structural cause of tool duplication. When teams make their own software decisions — which is how most organizations operate, particularly at the SMB and mid-market level — there is no mechanism to check whether another team is already paying for a tool that would meet the same need.
Over time, the organization ends up with multiple project management tools, multiple document storage systems, multiple analytics platforms. Each renews independently. Each has an internal champion who selected it and is resistant to migration. And no one has a view of the full portfolio that would make the duplication visible.
Billing errors on carrier invoices
Telecom and carrier invoicing is unusually error-prone relative to other vendor categories. The billing systems are complex, pricing structures are opaque, and errors introduced at provisioning or at contract execution can persist for years without detection.
Common errors include services billed at list rate when the contract specifies a discounted rate, circuits billed at a higher bandwidth tier than was provisioned, features included in a contract being charged as add-ons, and services continuing to bill after formal disconnection orders were submitted.
The error rate on telecom invoices is high enough that professional invoice auditing has been a service category of its own for decades. Most organizations doing an initial review find some level of billing error.
No single view of the environment
This isn’t a cost finding in itself, but it’s the underlying condition that allows the above findings to persist. Finance sees the expense line. IT sees the technical details. Operations sees the service delivery. No one has a view that connects spend, usage, contracts, renewals, and users into a single picture.
The lack of a unified view isn’t negligence — it’s a structural consequence of how technology procurement evolves over time in most organizations. But it’s the condition that allows waste to accumulate without detection.
The patterns that don’t show up as often as people expect
Catastrophic overspending on the wrong vendors
Organizations sometimes come into a review expecting to find that they’ve made fundamentally bad vendor choices — that they’re paying 3x market rate for everything, or that a major vendor relationship is deeply dysfunctional. This is rare.
The waste that reviews surface is usually incremental — services that should have been canceled, contracts that should have been renegotiated, duplicate tools that could be consolidated. It’s meaningful in aggregate, but it’s rarely the result of a single catastrophically bad decision.
Waste that’s immediately fixable without any vendor coordination
Most of the actions that reviews produce require vendor involvement — cancellation orders, renegotiation conversations, billing dispute submissions. The expectation that a review will produce a list of internal adjustments the organization can make on its own is usually wrong. Most of the value requires vendor-side action.
This is one of the reasons implementation support matters. The findings are only valuable if the actions get executed, and most of the actions require someone to manage the vendor relationship through to completion.
What determines whether findings translate into action
Reviews that produce findings but no action are common. The gap between a clear prioritized action plan and actual cost reduction is where most engagements stall.
The factors that determine whether findings translate into action:
Internal ownership. Every action in a Clarity Report needs an internal owner — someone responsible for seeing it through to completion. Reviews that produce a document but no ownership assignments produce change at a much lower rate than reviews that assign every action to a named internal contact with a timeline.
Vendor coordination support. The more an organization has help managing vendor conversations — cancellation submissions, billing dispute escalations, renegotiation preparation — the higher the completion rate. Vendor processes are not always efficient, and persistence is required.
Executive sponsorship. Cost reduction work that has visible support from finance or executive leadership moves faster than work that exists only at the operational level. Vendors respond differently when they know the conversation has executive attention.
A defined review cadence. Organizations that build on the initial review with a quarterly or annual refresh maintain the savings over time. Without a cadence, the environment drifts back toward the conditions that created the original waste.
