CLOUDY MUSINGS

Everybody loves AI until the invoice shows up! Not the cute "we spent a few hundred dollars experimenting" invoice that gets hand-waved away as innovation spend. I mean the kind of invoice that makes finance suddenly become deeply curious about architecture decisions they previously considered engineering trivia, while operations and/or product teams insist everything is still technically a pilot, and leadership starts asking whether we can "optimize this" as though that thou

After spending years working across Azure, AWS, and GCP, I can tell you the most frustrating part of FinOps is rarely the optimization itself. The hard part is getting everyone in the room to agree on what the data actually means before anyone can act. Every provider exports billing differently, every tool invents its own abstraction layer on top of that, and every dashboard ends up starting with translation instead of analysis. You spend the first hour of every cost conversa

I posted my FinOps for AI badge last week and almost immediately started getting messages. The interesting thing was most of them weren't actually about AI. A few people wanted to know whether the certification was worth pursuing, but most of the questions were really about the broader FinOps certification journey. Where does FinOps for AI fit? Should somebody take Engineer first? Is Practitioner still the right starting point? What's the deal with FOCUS? Is Professional wort

Cloud conversations still tend to start in the same place. We talk about scalability, resilience, performance, and maybe security if we are feeling disciplined. Cost usually shows up later (way later), almost like a postscript to the architecture. It is something we validate after the system is live, after usage patterns are real, and after the bill gives us a reason to care. The problem with that sequence is that by the time cost shows up, most of the meaningful decisions ha

Somewhere along the way, FinOps picked up a bad reputation. I had a customer tell me they viewed FinOps as akin to security. I felt it was a bad comparison, as most FinOps teams I work with, plus customers who have aspirations to build a FinOps team, are just trying to optimize + make cloud cost management more transparent to the organization. For a lot of teams though, it shows up as a dashboard no one asked for, a budget alert that fires too late, a preventative guardrail t

I was reminded of Conway’s Law the day I watched an episode of The Bear where Carmy tried to redesign the entire kitchen workflow in the middle of lunch service. Onions were flying. Pans were screaming. Richie yelled “cousin” every twelve seconds. Sydney was five seconds away from either fixing everything or throwing a stainless steel pan into the alley. Half the staff looked like one more missed step would send them into a new career that involved silence and scented candles

Often times I think the idea is not to confuse, but when you sort of pile on all the different services in Azure, some of the details get...

When people hear the word FinOps, their minds almost always jump to one thing: savings. “How much money can we cut from the cloud bill?”...

Like a lot of my posts, this conversation came up last week with a customer. As per usual, I figured a quick glimpse into what I've seen...

It's 2025! If you've been living under a rock the last 10-15 years, you may not know that the global cloud computing industry is...

The journey to FinOps maturity is a transformative process for many (if not all) organizations adopting cloud financial management...

In my presales role at AHEAD, I focus on the "art of the possible" in customer conversations. We often analyze customers' cloud storage...