For a long time I couldn’t work out why finance questioned CX spend first. I’d bring dashboards, explain the scores, and still watch the room go cold when budgets tightened. What I eventually worked out is that finance doesn’t mistrust CX because it dislikes customers. It mistrusts CX reporting that can’t help it manage risk, and the metrics that earn trust with finance are a different set from the ones I’d been bringing. The problem wasn’t a lack of data. Most of what we reported didn’t map to how financial decisions get made.
I should say up front that I didn’t learn this in one meeting. It built up over years of budget cycles, and the lesson I keep relearning is how differently the two sides hear the same slide. I’d be proud of a CSAT trend that had climbed for three quarters. Finance would be looking at the same slide and asking what happens to the line when volume doubles.
Why do CX dashboards struggle in finance conversations?
Most of mine were built to answer internal questions. Are customers happy? Did scores improve? Is the trend going the right way? Finance is asking something else entirely. It wants to understand cost behaviour, scalability and exposure: how variable demand turns into spend, what breaks when volume spikes, and where investment smooths risk and where it amplifies it. A dashboard built on CSAT, NPS or raw ticket counts describes outcomes without explaining mechanics, so it rarely lands.
At Q4 Inc, our support volume was tied to public company earnings cycles. I didn’t appreciate how useful that was until I looked at it from the finance side. Our demand wasn’t random. It followed a calendar everyone could see months ahead, which meant I could show where the pressure points would be, what staffing they needed, and what it cost to cover them or not cover them. That conversation went better than any satisfaction chart I’d brought to the same table, and it took me embarrassingly long to see why. Finance doesn’t need to be persuaded that customers matter. It needs something it can plan against.
The trust gap gets wider when CX metrics are used to imply financial causality. I’ve watched claims that an NPS improvement directly drives revenue fall apart under the first sensible question, and not because loyalty doesn’t matter. The metric can’t explain cause and effect on its own. Even the people behind it say so. In Net Promoter 3.0, Fred Reichheld and his Bain colleagues make the point that NPS was never meant to stand in for financial performance. Finance teams pick this up quickly, and the scepticism hardens, not toward CX as a discipline but toward how it measures itself. I went through the funding side of this in Support Is Not a Cost Center, because money follows predictability far more reliably than it follows passion.
Which metrics does finance already understand?
The conversation changes when reporting shifts from sentiment to structure. Cost-to-serve, throughput, backlog behaviour and failure rates invite a more productive discussion, not because they’re perfect but because they behave predictably under scale. That doesn’t mean dropping customer measures. It means translating them into operational and financial terms, so a finance lead can see what the operation does when volume doubles and what each extra contact costs.
Take the routing redesign I led at Q4. It moved first response time from 17 hours to 2, and I could have reported that as a customer win and left it there. The version that mattered to finance was different. With seven skill levels, we could see where work was concentrating and staff to real demand instead of estimated demand, which cut both the cost of waiting and the cost of idle seats. Same project, two framings. The second one answered the question finance had been asking, and the first only answered mine.
Show me a CX report that explains what happens to cost at twice the volume and I’ll show you a report finance will actually read. Most can’t do it, because they were built to prove customers are happy rather than to show how the operation behaves under pressure. I’m not arguing against satisfaction scores. I still track them. I just don’t expect them to carry a budget request on their own. If you’re building the broader argument for funding, the business case for CX is where I’d go next.
Why does overselling CX backfire?
Narrative inflation is one of the most damaging patterns I’ve seen, and I’ve been guilty of a mild version of it myself: overstating CX data to force relevance. Loose correlations, optimistic assumptions and an emotionally persuasive story can work once. Over time they cost you credibility, and even valid insights get discounted when the measurement model lacks discipline. Finance has a long memory for the number that turned out to be softer than it was presented.
The CX leaders I’ve seen earn long-term trust do something deceptively simple. They reduce ambiguity. They’re explicit about what they know and what they don’t, they separate lagging indicators from controllable inputs, and they resist the urge to inflate impact. Instead of claiming support drives revenue, they explain how it stabilises retention risk. Instead of leading with sentiment, they show how investment reshapes cost behaviour over time. That shift from storytelling to modelling is what earns influence, which is a little ironic for someone who likes telling stories.
What does a first conversation with finance look like?
Smaller than you’d think. I’d start by asking a finance partner how they decide where to put money when they have to choose, and what a good case looks like from their side. It’s a humbling exchange, because the answer is usually less about passion for the customer and more about confidence in the forecast. They want to know how sure you are, what the range looks like and what you’ll do if you’re wrong. That tells you what to prepare.
Then I’d bring one number they can check. Not a dashboard, a single figure with its source and its assumptions: the cost of a contact, the expected volume in a peak, the hours a change would save. When finance can take one of your numbers and rebuild it independently, you’ve done more for your credibility than a month of slides. It’s a small, slightly dull thing, and I’ve found it’s the point where the room starts to lean in.
What would I do differently next budget cycle?
I’d go in with fewer slides and one honest page about uncertainty. Which numbers I trust, which I don’t, what the operation does when volume spikes, and what I’d need to be wrong about for the plan to break. That page would have saved me several uncomfortable rounds of questions in the past, because finance was usually probing for exactly that gap and finding it before I volunteered it.
I’d also ask finance the question I used to skip: which number would you want to see every month if you were running this operation yourself? The answer is rarely CSAT. It’s more often something dull like cost per contact, or backlog age, or how long a spike takes to clear. Those are the numbers they’ll actually check, so those are the ones worth getting right.
There’s one more thing I’d bring that isn’t a number, which is a willingness to be told no. Some of the best finance conversations I’ve had ended without the money, and with a clearer picture of what would earn it next time. Asking what evidence would change their mind turned a refusal into a plan. It also changed how I saw the relationship: finance wasn’t an obstacle to the work, but a team I’d have to teach, and be taught by, if CX was going to be funded on its merits.
Finance doesn’t need CX to be inspirational. It needs it to be legible. Once your metrics show how the operation behaves under pressure, you start to earn trust with finance, and CX stops fighting for relevance and starts shaping decisions. The next time I’m in that room I won’t be asking for belief. I’ll be handing over something they can check.
Hutch Morzaria is a Director-level CX and Support Leadership professional with 19 years of experience building global support organizations across SaaS, Fintech, and enterprise technology. He has hired dozens of support and CX leaders across his career and holds ITIL Expert certification across V3 and V4.
