Overcoming the Cost-Center Stigma of Customer Support

A few years back, I worked at a remote startup that did weekly "coffee chats" — random 30-minute pairings with someone outside your team. 

I was skeptical. But those calls kept turning into something useful: I'd mention a customer problem, and I'd happen to be talking to exactly the person who could fix it. Things that had been stuck for weeks got resolved in days.

The problem was that it only worked because I got lucky.

In a company of 30, luck is plausible. At 200 or 500 people, you can't wait for the algorithm to pair you with the right person. And that exposed the real issue: I had genuine, valuable intelligence about customer problems, and no reliable system for making anyone act on it, because support was primarily viewed as a cost center.

That gap — between the insight support teams hold and the influence they actually have — is exactly why the cost center label sticks.

Why the cost center label sticks

Support is usually the last function built at a startup, and somehow also the first questioned when budgets tighten. 

We don't ship features. We don't close deals. We create value by focusing on retention, trust, and product intelligence. That’s a lot harder to spot on a spreadsheet when compared to sales numbers or new product revenue.

At its core, customer service is an operations function. It keeps the engine running. It finds what's broken, absorbs the friction so the rest of the business doesn't feel it, and feeds insights back into the product. Put support under ops and you usually measure the right things — efficiency, quality, reliability, and impact. 

But support is almost never put under ops. 

Walk into many SaaS companies and you'll find support reporting to a CRO or a VP of Sales. Revenue-oriented people, measuring revenue targets. That means it often leads to asking support to answer questions it was never designed to answer.

Support people are usually good at what we do because we're wired for empathy. But have you ever walked into a leadership meeting with nothing but feelings? You'll lose the room fast. When you say, "Customers are really frustrated with the login flow," the response is, "How many? How frustrated? What does that mean for revenue?"

While customer sentiment is very real and important, data is more credible in the minds of the leadership team. If you don't have numbers, you're facing a fight you’ll never win.

A helpful fix is to move support under operations, but neither you nor I have the power to restructure our organizations. So if support is reporting under revenue, the job becomes learning to speak a different language — one that revenue-focused people should understand.

But that leads to another challenge: recognizing that great support is by nature easy to overlook.

Great support often seems invisible. A customer who receives help and moves on doesn't register as a win. The deal that didn't churn because someone on your team spent an hour de-escalating an angry power user is money not lost. 

But what doesn't happen isn't remarkable. 

Nobody stands up in a meeting and says, "We kept $40K this quarter because support caught this before it became a problem."

Because of all that, leadership defaults to what they can see: headcount, tooling costs, ticket volume. All of which look like expenses because without the right framing, they are.

Which leads to an important point: every customer support team should stake a claim to revenue, regardless of where they report up to.

It’s a critical shift, because it makes the value of support impossible to ignore.

Making the case that support isn't a cost sink

Your billing flow changed in January. Since then, your team has been drowning in customer conversations. You bring it up in a leadership meeting at the end of the quarter:

"Customers hate the new invoicing process."

With this one sentence you've offended Product, who now walks you through the months of research and design that went into the change. You've alienated Ops, who love how much more streamlined the internal process is. And Revenue is dismissive because regardless of what you invoicing looks like, it’s not going to help them hit next quarter’s goals.

At best, the room moves on. At worst, you're now in a boxing ring against numerous other people and there's nobody to tag in to help you out.

You're the only person in the room on the customer's side and you're probably going to lose this battle. But you have everything you need to win it. You just need to repackage the information you have.

Leverage your support data, not just feelings or anecdotes

Start by tracking the basics like ticket volume trends, repeat contact rates, and CSAT scores tied to specific pain points or product areas. These are your building blocks, and most help desk tools track them already.

Having that information defuses the situation and ties it to data:

"We're seeing a 30% spike in billing tickets this quarter. They're concentrated around the invoice flow that changed in January."

You're saying the same thing as before; you're just speaking a language that others better understand. You’re letting your data do the heavy lifting.

Each layer you add sharpens the picture:

• Volume tells you something is happening. 

• Trend data tells you when it started. 

• Categorization tells you what's driving it. 

• Revenue figures tell you how to prioritize it.

Your job is to connect the dots for others. Pair every piece of customer feedback with relevant business context. 

Show them the money

Data gets you into the room. But to stay there, you need to show them the monetary impact.

You've already shown that ticket volume spiked 30% after the invoice flow changed in January. Now take it further. There are two ways you can do this:

• Show the additional work and costs of product issues

• Show the revenue impact and potential of support’s actions and opportunities

The first shows what product problems cost you in terms of customer support; the second shows what’s possible if you can shift from viewing support as a cost center to a revenue driver.

Show the cost of the additional work generated by product issues

What does it cost to handle a ticket at your company? Every time you’re sharing ticket volume data, multiply it by the incremental volume and project it forward.

Let me break it down:

Take your total support costs — salaries, tools, overhead, benefits — and divide them by your ticket volume. That's how much each ticket costs you.

To keep it straightforward, let's say you have five agents, each paid $80K with $20K in other benefits. That’s $100K per year per person in compensation. Then let’s say your support tooling and additional overhead is another $20K per year. 

That’s $520K in support costs annually.

Now let's say you have 500 tickets per week. Multiplied by 52 weeks, you're looking at 26,000 tickets per year. That means your average cost per ticket comes in at $20.

That billing issue we’ve been talking about? 

If it drove a 30% spike in conversation volume, that’s about 1950 in additional tickets over the quarter. At $20/ticket, that means it’s costing about $39K per quarter. That’s $156K per year if things don’t improve.

Tie customer support work to revenue retention and opportunities

The cost of extra work is easy to calculate. But what about the revenue impact of customer support?

Everyone knows acquiring new customers is expensive, which is why retention is so important.

If it costs $4,000 to acquire a customer with an ARR of $2,000 and they only stick around for one year, you’re in the red. If that same customer stays for five years, you’re way in the green

Customers stick around for two reasons:

1. The product or service provides value

2. The support they receive is sufficient

As a support leader, you don’t directly control the first, but you can influence it. And you definitely play a big part in the latter. 

Start by identifying the conversations where retention is genuinely at risk — customers expressing frustration with a core workflow, threatening to cancel, or asking how to export their data. Tag them. Follow up. And when they stick around because someone on your team took the time to solve their problem, record it. That’s churn prevention and revenue saved.

The same logic applies to expansion opportunities. 

Your support inbox is full of signals that have nothing to do with immediate issues:

• Customers asking how to manually do something your higher tier plan handles automatically gives opportunity for an easy upsell. 

• Customers trying to use your product in ways it wasn’t designed for opens an opportunity to ask questions and uncover ideas for new products and features.

These are revenue signals. Exactly what you do with them — have support upsell, escalate to a CSM or sales rep, or something else — will depend on your company’s structure, but at a minimum you can build a simple process to surface these opportunities. 

Coach your team to ask discovery questions to understand what customers really need. Run a report each month to see how many of these lead to upsells or cross-sells, and use the results to re-frame how your company leadership views support.

Pair the data with a story

Tying your support team’s work to revenue impact is essential, but telling stories is often what makes it real.

Once you have the data, find the human example that makes it real. 

Walk through one ticket: the customer, the issue, the time it took to resolve, what happened next. 

Then extrapolate. 

If it took three total hours of agent time to handle this issue for one customer, and ten of these come in every week, that's effectively half an agent dedicated to this problem every single week — around $40K a year, until it's fixed. 

Depending on your product or service and the type of issue, there might be an even bigger impact on your customers. Do these tickets indicate customers who have to put important work on hold? Is your software critical to their operation? Is their ability to realize revenue stalled because your workflow is broken? 

Revenue figures and numbers get people’s attention, but it’s sometimes easy to write off issues as customers being unreasonable or having unrealistic expectations. When you tie those numbers to a real story, it becomes far more difficult to ignore.

Build alliances across your company

I’m reminded of the best piece of relationship advice I’ve ever received:

“When you’re with the right person, everything is great 98% of the time. And the 2% that isn’t great is two people working together to solve a problem. Not two people fighting each other to be the winner.”

While intended as marriage advice, this applies to working relationships as well. 

Every company is split into separate departments, and it’s easy to forget that everyone’s on one team. We all want the same thing: a product that works and happy customers who stick around. That shared goal should be the foundation of every conversation you have across teams.

If your spouse makes something and it’s truly awful, you can probably laugh together and say, “That’s terrible.” But that’s because you trust each other.

Building that foundation takes time. Until you’ve established trust with your counterparts, how you deliver criticism matters as much as the criticism itself. Nobody responds well to being told their work is causing problems. Lead with what’s working. Be specific about what isn’t. Come with data, and if you can, come with a suggested fix. The goal is solving a problem, not winning an argument.

And celebrate wins together!

When a product change reduces ticket volume because suddenly everything is more intuitive, credit the team that made it happen. When a feature your team spent months advocating for is finally shipped, celebrate the win and thank the team that built it (and show the revenue or cost savings impact!).

Teams that celebrate together are not only better at communicating, they’re genuinely more useful to one another. Product starts looping in support earlier, asking if anything feels unclear from a customer perspective. Engineering becomes more responsive to bug reports, because they trust you know what you’re talking about and have done the math.

I got lucky with coffee chats at that startup I worked at. Most people have to build those cross-functional relationships more deliberately. Make a point of getting to know the people in engineering, marketing, and product long before you need something from them.

You’re all pulling toward the same goal, and building those relationships moves you from just being ‘customer support’ to being a trusted partner.

Recommended Reading

The Supportive

How To Be Heard By Your Product Team

Make yourself impossible to ignore

You can have the data, the story, the delivery, and even the alliances. But if your leadership team doesn’t know to invite you to the table, none of it matters.

To get invited, build a regular reporting cadence and stick to it. A monthly summary shared with leadership keeps your customer service team visible without requiring anyone to ask for it. When people see your numbers consistently, they start to expect them. And when they start to expect them, they start to factor them into decisions.

Make a habit of including the wins as well as the data:

• The customer who was two days from canceling stayed because an agent caught it in time. 

• The bug your team flagged that almost affected the entire enterprise tier. 

• The product feedback loop that led to a feature request being prioritized. 

These things happen every week. Most of them go unrecorded because support is too busy solving the next problem to document the last one.

So start documenting them: a line in your monthly report, a shout-out in a weekly stand-up, a slide in a quarterly review. It doesn't need to be elaborate. It just needs to exist somewhere that leadership can see it.

Present when you get the chance. There is nothing like standing up in front of your colleagues and making the case for what support does. It plants a seed. People leave that room knowing your team exists, your customers are real people with real problems, and you're the one helping solve them.

A seat at the table isn't given. It's earned.

No one is going to pull up a chair and wave you over to the decision-making table. And with decades of executives viewing support primarily as a cost center, you’re not going to shake that stigma overnight. 

It’s going to take some hard work.

But here's what's also true: no one else in your company has what you have. 

No other team talks to customers all day, every day, across every kind of problem — from confusion to frustration to genuine loyalty. The product team has research and hypotheses. Sales has pipeline data. You have the unfiltered reality of what it's actually like to use your product, at scale, in real-time.

That's not a cost. That's the most valuable intelligence in the building.

The trick is learning to put it to use in a way that leadership can understand and act on, and clearly connecting the dots between your support team’s work and what it means for retention and revenue. 

It’s not easy, but it’s totally doable.

Go get after it.