June 17, 2026
When the Numbers Don't Back You Up
This post is part of my Medium blog.
If you run FinOps at a large company, you've been in this meeting. Once or twice a year — more if it's a bad year — you get wheeled into a room with people two or three levels above you. You're not invited because they want your opinion. You're invited because someone needs you to say something specific.
Sometimes it's an emergency. Cloud spend spiked, the CFO noticed, and now you're the person in the room who has to explain why and fix it. Those meetings are stressful but at least honest — the problem is real and you're there to solve it.
The data doesn't change what's already been decided. (Image Assist by Anthropic)
Other times you're there to send a message. The CTO wants the engineering org to know it's time to take cost seriously, and having the FinOps person in the room is the signal. You're a prop, but at least the prop has a purpose.
And then there's the third kind. The kind where you're wheeled in to advance an agenda. Someone has a thesis — "if we migrated from relational databases to NoSQL, we'd save millions" — and the FinOps person is there to provide the data that supports it. The analysis is expected to confirm, not inform.
Every FinOps leader I've talked to has stories about this meeting. The one where the answer was already decided before the data arrived. The one where "let's see what the numbers say" was treated as obstruction instead of due diligence.
The executive has a thesis. The FinOps person has the data. The thesis and the data don't align. What happens next depends on the executive — and on the structural independence of the person holding the spreadsheet.
If FinOps reports to the CTO, the data tends to support the CTO's priorities. If FinOps reports to the CFO, the data tends to support cost reduction. Neither of those is objectivity. That's alignment, which is a different thing. The person holding the numbers can't be the same person who wrote the strategy. When they are, the numbers become a sales tool instead of a decision tool.
There's a reason auditors don't report to the people they audit. There's a reason financial analysts at investment banks have compliance walls between research and trading. The structure exists because the conflict is real. FinOps doesn't have that wall yet. Most FinOps teams report into the org they're supposed to be analyzing. That's not independence. That's embedded reporting with a dashboard.
Pushing for independence doesn't always have a good ending. FinOps leaders who push for objectivity sometimes get marginalized. Others get promoted because their independence turned out to be exactly what the company needed. The outcome depends on the executives, the culture, and a fair amount of luck.
But the alternative — always backing up the person who wheeled you in, regardless of what the numbers say — that's not FinOps. That's just being a prop with a laptop.
This is part of a larger argument about FinOps independence and what honesty costs. Redundant, from The Contingency Set trilogy.
In Redundant, the first book in The Condition Set trilogy, Rob Coleman runs the FinOps review that names the waste nobody wants to hear about. The numbers don't change. The question is who they get used against.