Operations | Monitoring | ITSM | DevOps | Cloud

Security used to be something teams added at the end of a release cycle. Engineering pushed code fast. Security teams reviewed it later. But this flow only worked when the software moved slowly. Modern cloud environments broke the old security model. Containers, microservices, APIs, and infrastructure as code now change too fast for security to sit outside delivery workflows.

Every time I step on set with a guest for FinOps In Full Bloom, I’m anticipating the lightbulb moments I know will pop up during the podcast. These are the conversations that reveal how curiosity and collaboration can spark real transformation in the cloud.

In the cloud computing industry, we hear the word “scaling” a lot. We talk about scaling up resources to meet demand, scaling our teams, and scaling our platforms. What tends to get lost is whether your costs are scaling in proportion to the value you’re delivering. If those two metrics don’t move in tandem, it’s likely you’re leaving money on the table. It’s not enough to simply use the cloud.

If you’ve already worked through cloud cost optimization strategies, the fundamentals aren’t new. CloudZero’s State of Cloud Cost report shows that cloud cost optimization is now a priority for most organizations. We’ve also covered these foundations in depth, including how cloud cost optimization works in practice and how FinOps teams approach cost accountability. What’s less discussed is what happens next. Cloud environments don’t stand still. Architectures change.

FinOps teams have been expected to understand millions of dollars in cloud and AI spend using tools that a handful of (usually technical) specialists can operate. Dashboards, filters, exports, and SQL have been the norm. That era is over. CloudZero is now bringing AI directly into the FinOps workflow so anyone in the business can ask natural-language questions about cloud and AI spend, and get accurate answers back from the platform.

Imagine this. A product team rolls out a change to improve reliability. The deployment succeeds. Traffic grows. Weeks later, cloud costs increase, and the finance team asks what changed. No one can point to a single decision or owner. This situation is common in cloud environments. Infrastructure scales automatically, and costs are shaped by technical choices made across engineering, data, and product teams. Most organizations review cloud spending after it has already occurred. Ownership is unclear.

As an engineer, engineering leader, or CTO, your architectural choices shape how fast your team builds products and how efficiently you manage technology costs. Your architecture determines how much control you have over data, infrastructure, and customization. The Software-as-a-Service (SaaS) model is one of the most common ways to deliver software reliably to users anywhere.

On a recent episode of FinOps In Full Bloom, host Thalia Elie sat down with Anderson Oliveira, a Senior FinOps Account Manager at CloudZero. With more than two decades in IT and deep FinOps expertise, Anderson brought clarity, humor, and a refreshingly human perspective to the conversation. Their chat covered everything from visibility and budgets to cultural friction and how to shift teams from resistance to results. Here are 13 insights and takeaways every FinOps-minded leader should hear.