For most of my career, I repeated the same line you’ve probably said yourself:
Support is not a cost center.
It sounds right. It feels principled. And for a long time, I believed that saying it loudly and often was part of my job as a CX leader. We were supposed to defend the team, elevate the function, and push back against purely financial thinking.
The problem is that once you’ve sat through enough executive reviews—or owned a real budget with real trade‑offs—you realise how quickly this framing falls apart.
Support absolutely is a cost center. And insisting otherwise doesn’t make you sound visionary. It makes you sound like someone who doesn’t fully understand how the business actually runs.
Worse, it quietly undermines your credibility with the very people you need in your corner when things get tight.
Why this argument fails in the room where budgets are decided
Executives don’t misunderstand what support costs. They can already see it laid out clearly: salaries, tools, vendors, infrastructure, and a cost profile that tends to grow as the company scales. They aren’t confused or hostile to the idea of customer experience. They’re accountable for margin, risk, and predictability.
When a CX leader insists support “drives value” but can’t clearly explain how costs behave under growth, pressure, or constraint, the conversation stalls. Not because they reject CX, but because they can’t map your story onto the decisions they’re paid to make.
This is why metrics like CSAT or NPS quietly lose influence once an organisation reaches a certain size. Not because they’re useless, but because they don’t answer the executive questions that matter most. I’ve written elsewhere about why CX metrics fail in senior conversations and how to reframe them in operational terms—the exact same issue shows up here.
What executives are actually trying to understand
Every leadership team I’ve worked with—across SaaS, fintech, and scale‑up environments—has come back to the same fundamental concerns, whether they say them out loud or not.
They want to understand how fast support costs grow relative to revenue. They want to know what breaks first if hiring lags behind demand. And they want clarity on whether current investment buys stability or just postpones pain.
These aren’t cynical questions. They’re responsible ones.
If you can’t answer them, someone else will—and they’ll usually do it without your context.
The reframing that actually works
The CX leaders who earn long‑term trust don’t try to make support sound like revenue. They do something more honest, and far more effective: they explain how support behaves as a system.
They can talk clearly about cost‑to‑serve and how it changes as volume grows. They understand the difference between short‑term efficiency and long‑term resilience. And they’re comfortable saying things like, “This investment doesn’t pay off this quarter—but it prevents a much larger problem next one.”
In other words, they position support not as a feel‑good value engine, but as a cost lever. Something that can be tuned, designed, and deliberately shaped as the company scales.
This framing aligns much more naturally with how executives already think about functions like infrastructure, security, or reliability engineering. Few leaders expect those teams to “generate revenue.” They fund them because the cost of not doing so is higher and harder to control.
Support is no different.
Where CX leaders quietly lose credibility
One of the most common mistakes I see is over‑claiming. Tying support too directly to revenue without solid causality. Presenting tooling as strategy. Or framing programs like QA and Voice of the Customer as cultural necessities rather than decision tools.
I’ve seen VOC programs cut not because leaders didn’t care about customers, but because they produced dashboards instead of actionable trade‑offs. I’ve written about this before in more depth in The uncomfortable truth about Voice of the Customer programs, because it’s a pattern that repeats itself in every mature organisation.
Executives are rarely anti‑CX. What they’re allergic to is vagueness.
The single sentence that changed how I communicate support strategy
The most effective shift I made was subtle but powerful. I stopped trying to prove that support wasn’t a cost, and instead started explaining what that cost buys.
Support spend doesn’t buy customer happiness.
It buys predictability.
Predictable response times. Predictable escalation paths. Predictable risk when something goes wrong. For growing businesses, that predictability is often the difference between scaling smoothly and spending quarters stuck in reactive mode.
Once you explain support this way, budget conversations become less emotional and far more constructive. You’re no longer defending headcount—you’re designing how the organisation absorbs uncertainty.
That’s a conversation executives understand, and one they’re far more willing to fund.
What I’d urge every CX leader to stop doing
If there’s one thing I’d push CX leaders to let go of, it’s the need to win the “cost center” argument on principle.
Stop trying to pretend the cost doesn’t exist.
Stop leading with value claims you can’t model.
Stop assuming executives see the world through NPS charts.
Instead, learn the language of cost, risk, and scale. Understand how your operation behaves under pressure. Be honest about trade‑offs. And show—not tell—how your decisions bend the cost curve over time.
That’s how support stops being treated as a discretionary expense.
And that’s how CX leaders earn real influence, especially when budgets get uncomfortable.
Hutch Morzaria is a CX and Support Leadership professional with 19 years of experience building and leading support organizations across SaaS, Fintech, and enterprise technology. He has held Director-level roles at Q4 Inc, AudienceView, Johnson Controls, and others, and holds ITIL Expert certification across V3 and V4.
