<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Finops on F. Latini - IT Engineer</title><link>https://latini.dev/tags/finops/</link><description>Recent content in Finops on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 06 Aug 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/finops/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Cloud Bill Is Not a Finance Problem</title><link>https://latini.dev/posts/your-cloud-bill-is-not-a-finance-problem/</link><pubDate>Thu, 06 Aug 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/your-cloud-bill-is-not-a-finance-problem/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Your cloud bill is not a finance problem. It is a feedback problem, and finance cannot repair a feedback loop they are not standing in. The invoice arrives monthly, aggregated, six weeks after the decision that caused it, addressed to somebody who cannot change a single line of it. The people who &lt;em&gt;can&lt;/em&gt; change it - the ones who picked the instance size, the log retention, the always-on staging environment, the chatty cross-zone call between two services - never see a number at all. So the organisation does the only thing left available to it: an annual panic sprint that rightsizes everything, claws back twenty percent, and gives it all back within two quarters, because nothing structural changed. The alternative is to treat cost the way you treat every other platform capability. Attribution as a default of the paved road, not a tagging campaign. Unit cost, not total spend. The number shown where the work happens. Defaults that are cheap by construction. Showback before chargeback. Cost is a property the platform ships, not a spreadsheet somebody emails around in Q4.&lt;/p&gt;</description></item></channel></rss>