The most expensive thing in your MarTech stack is the thing nobody uses

Somewhere in your marketing technology stack, there's a tool that nobody uses. Not "underused." Not "we use it for one thing." Nobody uses it. The login credentials have been lost. The integration was never completed. The person who championed the purchase left the company eight months ago. The annual renewal went through automatically because finance didn't flag it and nobody in marketing remembered to cancel it.

That tool is the most expensive thing in your stack - not because of the licence fee, but because of what it represents. A problem that was identified, a purchase that was approved, an implementation that never happened, and a decision nobody wants to revisit because cancelling it means admitting the investment was a mistake.

Every stack has at least one

This isn't an edge case. Talk to anyone who's run a martech audit on an enterprise marketing department and they'll tell you the same thing: every stack has tools that nobody can justify. Not one or two - usually several.

The pattern is always the same. Someone identified a gap. A vendor appeared with a compelling demo. The purchase got approved based on a use case that sounded reasonable at the time. Then reality set in. The implementation was harder than expected. The integration with existing tools required development resources that weren't available. The team that was supposed to use it was already stretched thin. The vendor's customer success team checked in for the first month and then disappeared.

So the tool sat there. Not producing value. Not integrated. Not cancelled. Just existing - a line item on a budget that nobody reviews closely enough to question.

The real cost isn't the licence

The licence fee is the obvious cost, but it's rarely the biggest one.

The bigger cost is the problem that's still unsolved. The tool was purchased to fix something - a gap in reporting, a missing integration, a capability the team needed. When the tool went unused, the gap didn't close. It just stopped being talked about. The team found workarounds, or they accepted the limitation, or they forgot the gap existed because the purchase had created the illusion of progress.

Then there's the opportunity cost. Every pound spent renewing a tool nobody uses is a pound not spent on something that would actually help - better configuration of existing platforms, training for the team, consulting to fix the processes that are actually broken.

And there's the complexity cost. Even unused tools add to the stack's overhead. They show up in security audits. They hold data that may need to be accounted for under privacy regulations. They create confusion when a new team member sees them in the tool inventory and asks what they're for - and nobody can answer.

Why nobody cancels

The psychology of unused tools is straightforward: cancelling is harder than renewing.

Cancelling requires someone to acknowledge that the purchase was a mistake - or at minimum, that the implementation didn't work. That's uncomfortable. The person who approved the budget might still be in the room. The vendor relationship might feel awkward to end. The original use case might still technically be valid, even if nobody's going to act on it.

Renewing requires nothing. The payment processes automatically. Nobody has to make a decision, have a conversation, or write an email. Inaction is the path of least resistance, and in most organisations, the systems are set up to make inaction the default.

This is how tools stay in the stack for years after they stopped being relevant. Not because anyone decided to keep them, but because nobody decided to remove them.

One unused tool becomes three

The problem compounds. An unused tool doesn't just sit there costing money - it creates conditions for more unused tools to arrive.

When the original tool fails to deliver, the gap it was supposed to close remains open. The team still has the problem. So they start looking for another solution - a different tool, a different vendor, a different approach to the same issue. Sometimes that new tool works. Often it joins the first one in the stack, partially implemented, partially adopted, partially solving the problem.

Meanwhile, the platform the team already owns - the MAP, the CRM, the analytics tool - may have added the exact capability the unused tool was supposed to provide. Platform vendors ship new features constantly. The enrichment tool purchased two years ago might now be redundant because the MAP added native enrichment. The reporting dashboard bought last year might be unnecessary because the CRM's built-in analytics improved significantly. But nobody checks, because nobody's tracking the overlap between new platform features and existing point solutions.

After a few cycles of this, the stack has multiple tools doing overlapping things, none of them fully integrated, and the team is spending more time managing tool complexity than solving the problem any of them were supposed to address.

The vendor renewal conversation

Most tool renewals happen without a conversation. An invoice arrives, finance processes it, and the subscription continues. The vendor doesn't check whether you're using the tool - they're happy to keep billing. Your team doesn't flag it because nobody is tracking utilisation against cost.

Building one step into the renewal process changes this entirely. Thirty days before any tool renews, someone - the tool owner, the ops lead, whoever manages the stack - should answer four questions and document the answers.

Is the tool actively used? Not "does someone log in occasionally" - is it part of a regular workflow that would break if the tool disappeared? If the last meaningful usage was three months ago, that's not active.

Is the tool integrated with the rest of the stack? A standalone tool that doesn't connect to the CRM, the MAP, or the reporting infrastructure is a tool operating in isolation. Isolated tools produce isolated data. That's rarely worth the licence fee.

Has the original use case been addressed by another tool since purchase? Platform capabilities evolve. Check whether the MAP, the CRM, or another tool in the stack has added functionality that makes this tool redundant.

Does the cost justify the value? Not in theory - in practice. What specific business outcome did this tool contribute to in the last 12 months? If the answer requires creative interpretation, the tool probably isn't worth the renewal.

The audit nobody wants to do

The fix is simple and uncomfortable: inventory every tool in your stack, identify who uses each one, and cancel what can't be justified.

For each tool, ask three questions. Who on the team used this in the last 90 days? If nobody, that's your answer. What business outcome does this tool directly support? If the answer is vague or theoretical, the tool isn't supporting anything. If we cancelled this tomorrow, what would break? If the answer is "nothing," cancel it tomorrow.

Most teams that run this exercise for the first time are surprised by how much they're spending on tools that deliver no measurable value. The savings are usually significant - not life-changing, but meaningful enough that the budget could be redirected somewhere useful.

The harder part is building the habit. Tool audits should happen at least annually, timed to renewal cycles. Before any tool renews, someone should confirm it's still being used, still integrated, and still solving the problem it was purchased to solve. If the answer to any of those is no, the renewal should be a conscious decision - not an automatic one.

The stack should shrink before it grows

Every time someone proposes adding a new tool, the first question should be: have we fully used what we already have? The second question should be: is there anything in the current stack that could be removed to make room?

A lean stack that's properly configured, fully integrated, and actively used by the team will outperform a bloated one every time. The tools that create the most value aren't the newest or most feature-rich. They're the ones that someone actually owns, maintains, and uses every day.

The most expensive tool in your stack isn't the one with the biggest licence fee. It's the one nobody would miss if it disappeared - and the fact that it's still there tells you more about your procurement process than it does about your marketing technology strategy.