Cloud cost used to be an IT operations problem. It is now a line the CFO reads, and most IT organisations are not ready for the conversation that follows.<\/p>\n
The shift has been building for years and is arriving all at once. Multi-year cloud commitments, usage-based billing at scale, and broad pressure on operating costs have combined to put cloud spend under board-level scrutiny it never faced during the growth phase, when the priority was speed and the bill was tolerated as the cost of moving fast. That tolerance is gone. The CFO is now in the room, asking what the spend produces and why it keeps rising, and IT is discovering that it cannot answer in the terms the question is being asked.<\/p>\n
During the adoption phase, cloud cost was governed loosely, as an operational detail managed inside IT. The numbers were smaller, the growth justified the spend, and finance largely left it alone. That arrangement worked while cloud was a growth investment and stopped working the moment it became a major, scrutinised operating cost.<\/p>\n
Now the governance is shifting from IT-led to finance-led, and the two functions speak different languages. Finance asks about cost per outcome, return on commitment, and the justification for spend that grows faster than revenue. IT has historically answered in the language of infrastructure and utilisation, which does not map onto the question. The result is a conversation where the CFO asks about value and IT answers about technology, and neither leaves satisfied.<\/p>\n
The lack of readiness is structural, not a failure of individuals. IT built its cost capability for an internal operational audience and never had to defend cloud spend to finance in finance’s terms. So the transparency that exists is technical rather than financial, the accountability sits in the wrong place or nowhere, and the link between spend and business outcome was never built because no one was asking for it. When the CFO arrives, IT has the data but not the framing, and the framing is what the conversation requires.<\/p>\n
This is the reckoning the moment represents. FinOps as an IT discipline produced dashboards and tagging. FinOps as a finance-led governance function demands something IT mostly has not built: the ability to explain cloud spend as a business investment with a return, to people who evaluate every investment that way. That is a finance competency living in an engineering organisation, and it is rarely there when the CFO first asks. It is a different skill from anything FinOps-as-IT ever required, and a dashboard does not supply it.<\/p>\n
Three capabilities separate the organisations that handle the CFO conversation from the ones it blindsides. The first is genuine financial transparency, meaning cloud spend expressed in business terms and traceable to the things it supports, not just an itemised infrastructure bill. The second is accountability structures that put cost ownership where the spending decisions are made, so that when finance asks who is responsible for a cost, there is an answer that is not simply “IT.” The third is an explicit linkage between cloud spend and business outcomes, so the spend can be defended as an investment producing value rather than a cost to be cut.<\/p>\n
None of these is built overnight, which is the entire point of building them before the conversation becomes a crisis. An enterprise that starts constructing financial transparency during the budget review that questions its cloud spend has started a year too late. The capability has a lead time, and the CFO’s patience does not.<\/p>\n
Handled well, the arrival of finance is not a threat to IT but an upgrade to how cloud is governed. A CFO engaged early, with the transparency and accountability to make cloud spend legible, becomes the sponsor that cost discipline always lacked, the equivalent of the executive owner every operating model dimension needs to advance. The same engagement, arriving as a crisis with IT unprepared, becomes an adversarial budget fight that damages trust and forces cuts in the wrong places.<\/p>\n
The difference between those two outcomes is preparation. The CFO is coming either way. Whether the conversation is a partnership or a reckoning depends entirely on whether IT built the financial transparency and accountability before it was demanded under pressure.<\/p>\n
Cloud cost has crossed from an IT concern into a finance one, and the conversation it triggers is one most IT organisations are not equipped to have. The work is not to resist the scrutiny but to be ready for it: to express cloud spend as a business investment, to put accountability where the decisions are, and to connect the spend to the outcomes it produces. The CFO’s question is already forming. The organisations that come through it well are the ones building the answer now, while it is still preparation, rather than improvising it later, when it has become a crisis.<\/p>\n","protected":false},"excerpt":{"rendered":"
Cloud cost has moved from an IT operations concern to a CFO agenda item. Most IT organisations cannot yet have the finance-led governance conversation that follows, and the time to prepare is before it becomes a crisis.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-54","post","type-post","status-publish","format-standard","hentry","category-business-value"],"_links":{"self":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts\/54","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=54"}],"version-history":[{"count":0,"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts\/54\/revisions"}],"wp:attachment":[{"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=54"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=54"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=54"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}