FinOps - From Zero to Maturity

Cloud FinOps is about getting the most value out of your cloud investments. It helps you understand your cloud spending, optimize usage, and leverage pricing models and discounts. It's not just for tech and finance teams, but a cultural shift that impacts everyone in the organization. It requires continuous monitoring and adjustment. In a containerized environment, FinOps principles can be applied by accurately dividing costs among applications and collaborating closely with engineers. Building a FinOps culture involves fostering collaboration, shared goals, trust, and leadership support. The ultimate goal is to make smart decisions, align teams, and drive business value. All right, so we've got this stack of excerpts here from Cloud FinOps, second edition. Yeah. Cloud FinOps, sounds kind of intimidating, right? Like something only hardcore tech folks need to worry about. Yeah, it can seem that way, for sure. But really, FinOps is all about getting the most value out of your cloud investments. Okay. And that's something that I think everybody should care about, right? Absolutely, especially since cloud costs can feel like a bit of a black box sometimes. One minute, everything's running smoothly, and the next, you're staring at a bill that makes your jaw drop. Yeah, you wouldn't believe how many companies are overspending simply because they haven't tagged their resources correctly. Oh, really? Oh yeah, it's like trying to track your expenses without itemizing your receipts. Total chaos. So tagging is important. Yeah. Okay, so FinOps helps you avoid those nasty surprises by giving you more visibility and control over your cloud spending. Exactly, it's like having a financial GPS for your cloud journey. It helps you understand where your money's going, identify areas where you can optimize, and make sure your cloud investments are actually driving business value. I'm already starting to see why this is becoming such a big deal. It's not just about saving money. Right. It's about making smarter decisions about how you use the cloud. Precisely. Okay. And here's something that might surprise you. FinOps isn't just the responsibility of some specialized team. It's a cultural shift that impacts everyone in the organization. Wait, so it's not just for the tech wizards and finance gurus? Definitely not. Okay. I mean, think about it. Engineers need to consider cost as a factor when they're designing and building applications. Right. Finance teams need to understand the nuances of cloud pricing models. And executives need to set clear expectations and align incentives to support FinOps initiatives. So it's like a team sport where everyone has a role to play. Exactly. Yeah. And it all benefits from a well-executed FinOps strategy. I like that. Okay. You know, speaking of things that can be a bit of a mystery. Right. Let's talk about those infamous cloud bills. I've heard they can be pretty daunting. They definitely can be, especially if you're used to traditional IT budgeting where you have, you know, fixed costs and predictable expenses. Right. The cloud is a different beast altogether. Yeah. With its pay-as-you-go models and constantly changing pricing. No kidding. Yeah. So where do you even begin to unravel the mysteries of a cloud bill? Well, the good news is cloud billing data has come a long way. Okay. The book actually walks us through this evolution. And it's pretty fascinating. Okay. Remember those old school invoices from like 2008? Oh yeah. Barely any detail, just a lump sum for cloud services. Yeah, that doesn't sound very helpful. Thankfully, we've moved beyond those dark ages. Okay, good. Today, you have access to detailed usage reports, cost allocation tags, and even tools that can analyze your spending patterns and flag potential anomalies. Oh wow. So it's less about deciphering hieroglyphics and more about having the right tools and strategies to make sense of the data. Exactly, and that's where Phenops comes in. Okay. It provides the framework and the guidance to transform those raw numbers into actionable insights. Okay, so we've established that Phenops is about understanding and optimizing your cloud spending. But how do you actually go about doing that? What are the key levers you can pull? So the book breaks it down into two main approaches. Okay. Usage optimization and rate optimization. Okay. Think of them as the two sides of the Phenops coin. Gotcha. So usage optimization sounds like making sure you're not wasting resources. Right. It's all about right sizing your cloud instances, eliminating idle services, and generally making sure you're not paying for more than you actually need. So kind of like making sure you're not leaving the lights on when you leave a room. Exactly. But instead of light switches, you're dealing with virtual machines, storage buckets, and a whole ecosystem of cloud services. Exactly. And rate optimization, is that about getting the best deals from your cloud providers? That's part of it, yeah. Okay. Rate optimization is about leveraging the various pricing models and discounts that cloud providers offer to your advantage. Okay. Have you heard of reserved instances, for example? I've heard the term, but to be honest, I'm a little fuzzy on the details. Okay, so it's a bit like prepaying for a gym membership, right? Sure. You commit to using a certain amount of compute capacity for a set period of time, and in return, you get a significant discount on the hourly rate. So you're like hedging your bets, betting that you'll need that capacity anyway. Exactly. But the key is to do your homework. Right. Understand your usage patterns, and make sure you're committing to the right resources at the right level. Otherwise, you could end up overspending, even with a discount. That makes sense. Yeah. So there's a bit of an art to this whole rate optimization thing. There definitely is. It's about understanding the nuances of different pricing models, knowing when to commit, and being able to negotiate effectively with your cloud providers. Okay, so we've got usage optimization, which is about using what you need efficiently. Right. And then rate optimization. Yeah. Which is about playing the cloud pricing game, like a pro. That's a good way to put it. Okay, got it. Yeah. But remember, both of these approaches require continuous monitoring and adjustment. Okay. You know, your cloud needs are constantly evolving, so your Finop strategy needs to evolve with them. It's not a one and done kind of thing. Right. You need to stay on top of it, constantly tweaking and refining your approach. Exactly, and that's what makes Finop so interesting. It's a dynamic and evolving field. Speaking of dynamic and evolving, let's talk about containers. Okay. They seem to be all the rage these days, but I have to admit, I find them a bit intimidating. Well, containers can be a bit of a mind bender, especially when it comes to cost management. They allow you to package and run applications in a very efficient way, sharing resources on a single server. But that shared resource model also makes it tricky to track costs and allocate them to specific teams or projects. So how do you even begin to apply Finop's principles in a containerized world? Yeah, well, the book dives into this specifically focusing on Kubernetes, which is kind of the gold standard for container orchestration these days. One key concept is custom container proportioning. Okay, break that down for me. Sure. What in the world is custom container proportioning? So imagine you have multiple applications running in containers on a single server. Okay. Custom container proportioning allows you to accurately divide the cost of that server among those applications based on their resource usage. Ah, so everyone gets their fair share of the bill, even though they're sharing resources. Precisely. And then there are things like Kubernetes cluster autoscalers, which automatically adjust the number of servers based on demand. So you're only paying for what you actually need at any given moment. Nice. Yeah. But managing costs in a containerized environment requires even closer collaboration between the Finop folks and the engineers who are building and managing those Kubernetes clusters. Okay, I'm starting to see that Finop isn't just about numbers and spreadsheets. Right. People, processes, and communication. You're absolutely right. And the book dedicates a whole chapter to building a Finop culture. Okay. And it's all about fostering collaboration, breaking down silos, and getting everyone to think about cloud costs in a proactive way. You know, one thing that I've always struggled with is effectively partnering with engineers on cost optimization. Yeah. They're the ones closest to the cloud infrastructure. Right. But sometimes it feels like they're speaking a different language. That's a common challenge, for sure. And the book has some great insights on this. Okay. First, it emphasizes the importance of shared goals. You need to make sure engineers understand how their cost-saving efforts contribute to the bigger picture. Whether it's speeding up product development, freeing up budget for new initiatives, or simply avoiding that dreaded bill shock, it's all connected. Right, because if they see it as just another task being imposed on them by the finance police, they're less likely to be engaged. Exactly. The book also talks about fostering a culture of trust. Okay. Avoiding blame and encouraging open communication. You want engineers to feel comfortable raising concerns, asking questions, and experimenting with different optimization approaches without fear of getting their heads bitten off. It's about empowering them to be part of the solution, not making them feel like they're being micromanaged. Precisely. And that's where leadership plays a crucial role. I was just gonna say, what about the role of leaders in driving FinOps adoption? What can they do to set the right tone and create the right environment? They need to champion the cause. That means setting clear expectations, aligning incentives, and making sure cost efficiency is baked into the company culture, not just an afterthought. So it's about leading by example, walking the walk, not just talking the talk. Exactly. And it's about empowering their teams to embrace FinOps principles. Right. And making sure they have the resources and support they need to succeed. Okay, so we've established that FinOps isn't just about slashing costs. It's about making smart decisions, aligning teams, and driving business value. Right. But where does it all lead? What's the ultimate goal? Well, the book paints a picture of FinOps nirvana. FinOps nirvana. Yeah. And it's all about data-driven decision-making. You know, I've always struggled to connect our cloud spending to actual business results. This concept of unit economics, which you mentioned earlier, seems like it could be a game-changer. It absolutely can be. Okay. Unit economics is all about understanding the cost of a single unit of something meaningful to your business. Okay. It could be the cost to acquire a new customer, the cost to process a transaction, or the cost per active user. So instead of just saying, we spent $1 million on cloud this month. Right. You're saying, it cost us $5 to acquire each new user through our cloud-based platform. You're getting it. And that kind of insight is incredibly powerful. Right. It allows you to make data-driven decisions about product development, pricing, marketing campaigns, and overall business strategy. So FinOps nirvana is all about using data to connect the dots between cloud costs and business value. Exactly. It's not just about doing more with less. It's about doing the right things with the resources you have. You know, you're making FinOps sound downright inspiring. It is. When you think about it, FinOps is really about enabling innovation. Okay. By optimizing your cloud spending, you're freeing up resources to invest in new products, improve customer experiences, and ultimately drive your business forward. Right. I'm definitely feeling more enlightened about FinOps now. Good. It's a lot more than just number crunching and cost cutting. Yeah. It's a strategic approach to cloud management that can have a real impact on your business. That's the beauty of FinOps. Yeah. It's not just about saving money. It's about creating value. Well said. Yeah. And there's so much more to explore. Absolutely. You've only just scratched the surface of what FinOps has to offer. Right. We'll be diving into more specific strategies, real-world examples, and actionable insights in the next part of our deep dive. Okay. Sounds good. Stay tuned. Okay. So we left off talking about FinOps nirvana and data-driven decision-making. Right. And how unit economics can help us connect those dots between cloud spending and those tangible business outcomes. You know, that really resonated with me. I've always felt like there's this disconnect between what we spend on the cloud and then what we actually get back in terms of business value. It's a common challenge. Yeah. Many companies get caught up in just looking at that total cloud spend, but that only tells part of the story. Right. It's like judging the success of the marketing campaign solely on how much money you spend, right? Exactly. You need to know what you got in return for those dollars. Right. Like new customers, increased engagement, brand awareness, whatever your goals are. So how does unit economics help us bridge that gap? I'm still kind of wrapping my head around this whole concept. Sure, think of it this way. Okay. Unit economics breaks down your cloud costs to the level of individual units that are meaningful to your business. Okay, give me an example. I'm a visual learner. Let's say you're running an e-commerce platform in the cloud. Okay. A key unit metric for you might be the cost to acquire a new customer. So instead of just looking at your overall cloud bill, Right. you're figuring out how much of that spending is directly tied to bringing in each new customer. Exactly, and that's a powerful insight. Right. It allows you to compare the cost of acquiring customers through different channels, optimize your marketing spend, and ultimately make better decisions about how to grow your business. Yeah, the book has some really fascinating real world examples of how companies are using unit economics to drive those strategic decisions. One that really stood out to me was this online grocery company that started tracking the cost to fulfill each customer order. Hmm, what's interesting about that example is that they weren't just looking to cut costs. Right. They were looking to identify areas where they could improve operational efficiency. And by understanding how much each step in the fulfillment process was costing them, from picking and packing to delivery, they were able to pinpoint bottlenecks and streamline their operations. Which ultimately led to a better customer experience. And I'm guessing a more cost effective operation. Precisely, it's a win-win. Another great example is the software company that started measuring the infrastructure cost per active user. That's a clever one. Yeah. I could see how that would directly impact their pricing and resource allocation decisions. Absolutely. By knowing how much it costs to support each user, they can set their pricing in a way that ensures profitability. They can also make informed decisions about how to allocate resources to different features or customer segments. So it's all about connecting those technical cloud costs to the business realities of revenue and customer acquisition. It's like building a bridge between the world of bits and bytes and the world of dollars and cents. Okay, I'm sold. Unit economics sounds like the holy grail of FinOps maturity. But let's be realistic, it can't be easy to implement. Right. You're right. It does require careful thought and planning. You need to choose metrics that are truly meaningful to your business. Crack them accurately and make sure everyone understands how those metrics connect to those overall goals. It's not just about collecting data for the sake of collecting data. It's about using that data to inform and drive strategic action. Precisely. And remember, FinOps is a journey, not a destination. You don't need to have all the answers right away. It's about continuous improvement, iterating and adapting as your cloud needs evolve. Makes sense. It's about progress, not perfection. Exactly. Okay. And one more thing I want to emphasize, FinOps isn't just about being efficient. It's about being effective. Okay. It's not just about doing more with less. It's about doing the right things with the resources you have. That's a really important point. Yeah. It's easy to get caught up in those technical weeds and lose sight of that bigger picture. But ultimately, FinOps is about enabling innovation, improving customer experiences and driving your business forward. Right. It's about making sure those cloud investments are delivering real value. Speaking of the bigger picture, we've talked a lot about the what and the how of FinOps. Right. But I'm curious to hear more about the who. Okay. We know FinOps is a team sport, but who are those key players and what are their roles? Excellent question. Yeah. Remember those different personas we discussed earlier? The engineers, the finance folks, the executives, they each bring a unique perspective to the table. Okay. And their roles are crucial to FinOps success. Okay. So let's start with the engineers. Okay. They're often the ones closer to the cloud infrastructure, right? Building, deploying, and managing those applications and services. Right. What's fascinating about their role is that they are often the first line of defense against cloud waste. Okay. They have the power to make real-time decisions about resource allocation, optimization, and even the choice of cloud services. So the book emphasizes the importance of empowering engineers to make those cost-conscious decisions. It's not just about following a set of rules handed down from on high. It's about giving them the knowledge, tools, and autonomy to optimize their work from a cost perspective. Right. It's about integrating FinOps principles into their daily workflows and decision-making processes. And what about the finance folks? Okay. They bring a different kind of expertise to the table. Yeah. Focusing on budgeting, forecasting, and cost analysis. Their role is critical in ensuring that cloud investments are aligned with the overall budget and strategic goals. Okay. They are the guardians of the company's financial health. So the book really stresses the importance of collaboration and communication between finance and engineering. Absolutely. It's not about finance dictating terms to engineering. It's about both teams working together to find solutions that are both financially sound and technically feasible. Right. They need to speak each other's language, understand each other's priorities, and find that sweet spot where cost efficiency and innovation intersect. And then we have the executives. Right. They set the tone, they drive the culture, and they ultimately hold everyone accountable. The book argues that leadership support is absolutely essential for FinOps to truly take root and flourish. It's not just about giving lip service to cost efficiency. Right. It's about backing it up with actions, incentives, and resources. It's about making sure FinOps is a core part of the company's DNA, not just a passing fad. You know, you mentioned automation earlier. How does that play into the FinOps equation? Automation is a game changer. Think of it as your secret weapon in the fight against cloud waste. It allows you to continuously monitor your cloud environment, identify optimization opportunities, and even take action to remediate those issues automatically. So instead of relying on manual processes, which can be time-consuming and prone to error, you're letting the machines do the heavy lifting. Exactly. And that frees up your FinOps team to focus on more strategic initiatives. Okay. Like building relationships with engineers, analyzing data, and driving those unit economics insights we talked about. So the book gives examples of different types of automation tools, right? Yeah, there are tools for everything from tag governance to scheduled resource start-stop. Okay, so tag governance helps ensure your cloud resources are properly tagged for accurate cost allocation. Right, exactly. And scheduled resource start-stop. That's where you automatically shut down resources when they're not needed, like outside of business hours. Exactly, and then there are tools for usage reduction, which can automatically identify and remediate over-provisioned or underutilized resources. It feels like the more you can automate, the more efficient and effective your FinOps practice becomes. It's all about working smarter, not harder. And automation is the key to achieving that. You know, we keep coming back to the importance of data. You've mentioned a few times now how critical it is to have good data for FinOps to be effective. Data quality is paramount. It's the foundation upon which your entire FinOps practice is built. So what do we mean by good data in the context of FinOps? Good data is clean data. Okay. It's accurate, consistent, and complete. It's been properly tagged, allocated, and normalized. It also needs to be readily accessible and easy to analyze. Exactly, and that's where those automation tools we talked about can be incredibly helpful. They can help you automate data collection, cleaning, and validation, ensuring you're working with the highest quality data possible. Garbage in, garbage out, as they say. Couldn't have said it better myself. Yeah. If you want to make informed decisions and drive real value from your FinOps practice, you need to start with a solid foundation of clean, reliable data. Okay, we've covered a lot of ground, from the nitty-gritty of data quality to the high-level vision of FinOps nirvana, but I want to circle back to something we touched on earlier, the importance of building a strong FinOps culture. Mm-hmm. What are some key ingredients for creating that kind of environment? Culture is often the missing ingredient in successful FinOps implementations. Yeah. It's not just about having the right tools and processes in place. It's about creating an environment where everyone understands and embraces FinOps principles. So it's about changing mindsets and behaviors, not just implementing new software. Exactly. The book talks about the importance of shared goals, transparency, and collaboration. Okay, so shared goals. So everyone's rowing in the same direction. Yeah. Working towards the same objective. Exactly. Everyone needs to be on the same page about what you're trying to achieve with FinOps and how their individual efforts contribute to the bigger picture. Right. It's not about finance versus engineering. It's about everyone working together to optimize cloud spending and drive business value. And transparency. Yeah. That's about open communication and making sure everyone has access to the information they need. Precisely. You need to make sure everyone has access to the data, understands how costs are being tracked and allocated, and can see the impact of their decisions. And that transparency helps build trust and encourages more proactive engagement, right? Absolutely. And then there's collaboration. FinOps can't happen in a vacuum. Right. You need to break down those silos between teams, foster open communication, and encourage knowledge sharing. So it's about creating a sense of shared ownership and accountability for cloud costs. And it's about celebrating successes together. Yeah. When you achieve a significant cost optimization. Right. Make sure everyone involved gets recognized and rewarded. It's a team effort. Okay, because ultimately, a strong FinOps culture is about more than just saving money. Right. It's about creating a more efficient, effective, and collaborative organization. It's about empowering everyone to be part of the solution and creating a culture of continuous improvement. Right. And those benefits extend far beyond just the cloud bill. Okay, so we've explored the depths of data-driven decision-making, unit economics, the evolving roles of different teams, the power of automation, the importance of clean data, and the magic of a strong FinOps culture. We've covered a lot of ground, but remember, this is just the tip of the iceberg. Right, there's always more to learn and explore in the ever-evolving world of cloud FinOps. Absolutely, and that's what makes this field so exciting, is constantly evolving. Right. Presenting new challenges and opportunities. It's not just about keeping up, it's about staying ahead of the curve. And to do that, you need to be constantly learning, experimenting, and sharing your knowledge with others. Yeah. Engage with the community, attend conferences, read blogs, stay curious. Well said. We'll be back with part three of this deep dive, where we'll continue to unpack those fascinating insights from the book, so stay tuned. Welcome back to our deep dive into cloud FinOps. We've covered a lot of ground, haven't we? From the fundamental concept of cloud billing to the strategic power of unit economics. Yeah, and we've explored the crucial role of people and culture in creating that successful FinOps practice. But as they say, the real magic is in the details, right? Yeah, so let's roll up our sleeves and dive into some specific strategies and techniques that can help you actually optimize that cloud spending. Sounds good to me. The book provides a wealth of practical advice and those real world examples. One thing that keeps popping up is the importance of really understanding your cloud usage patterns. Yeah, it's the foundation of any effective optimization strategy. You can't optimize what you don't understand. Right, it's like trying to lose weight without knowing what you're eating. Exactly, you need to know what resources you're using, when you're using them, and then how much they're costing you. So how do you go about getting that level of visibility? It feels like cloud usage data can be pretty overwhelming sometimes. Yeah, it can be, but thankfully, there are tools and techniques to help you make sense of it all. The book talks about things like detailed billing reports, cost allocation tags, and even machine learning algorithms that can analyze your spending patterns. Machine learning for cloud costs? Yeah. That sounds pretty high tech. It is. These algorithms can learn your normal usage patterns and then alert you to any anomalies or unexpected spikes in spending. It's like having a financial watchdog for your cloud environment. I like that, a financial watchdog. Okay. Okay, so once you have a clear understanding of your cloud usage, then what's the next step? Then you can start to identify those opportunities for optimization that might involve right-sizing resources, eliminating idle services, or even renegotiating pricing with your cloud providers. I imagine right-sizing can be a pretty big lever for cost savings. Yeah. But how do you know if your resources are right-sized in the first place? That's where monitoring comes in. You need to keep a close eye on your resource utilization and look for patterns. Are your virtual machines consistently running at a low CPU utilization? Okay. Are your storage buckets half empty? Right. These could be signs that you're over-provisioned. So it's about finding that sweet spot, right, between having enough capacity to handle peak demand, but not so much that you're wasting money on those unused resources. Precisely. And there are tools that can help you automate this process. Okay. They can analyze your usage patterns and recommend right-sizing adjustments. Okay, so we've talked about usage optimization. What about rate optimization? Right, remember those commitment-based discounts we discussed earlier? Yeah. They can be a great way to save money, but only if you manage them effectively. Right, because if you over-commit, you're stuck paying for resources you don't need. Exactly. And if you under-commit, you might miss out on potential savings. It's a bit of a balancing act. So how do you strike that balance? Well, the book suggests creating a repeatable process for evaluating your commitment needs. That involves analyzing your usage patterns, forecasting future demand, and understanding the nuances of those different commitment types. So it's not just a one-time decision. Right. You can continuously monitor your commitments and make adjustments as needed. Absolutely. You know, your cloud needs are constantly evolving, so your commitment strategy should evolve with them. You know, one area that I'm particularly curious about is optimizing costs in a containerized environment. It feels like that adds a whole new layer of complexity. It definitely does. Containers allow for that efficient resource sharing, which is great, but it also makes it more challenging to track costs and allocate them accurately. Right. So how do you even begin to apply CoinOps principles in that kind of environment? Yeah, the book dives into this specifically with Kubernetes. Okay. One key concept is custom container proportioning, which we touched on earlier. Right. That's where you divide the cost of a shared server among the different applications running in containers based on their resource usage. Exactly. It's a way to ensure that everyone is paying their fair share. Right. The book also talks about namespace-based cost allocation. Okay. Which allows you to track costs at the level of Kubernetes namespaces. Namespaces, those are like logical groupings of resources within a Kubernetes cluster, right? That's right. By tracking costs at the namespace level, you can get a more granular view of your spending and identify areas for optimization. It feels like FinOps in the container world requires even closer collaboration between those FinOps practitioners and the engineers managing those Kubernetes clusters. Absolutely. They need to be speaking the same language and working together to find solutions that are both cost-effective and technically sound. You know, we've talked a lot about optimizing existing cloud costs. Right. But what about preventing unnecessary spending in the first place? Oh, that's a fantastic point. The book dedicates a whole chapter to cost avoidance strategies. Oh, I love that they call it cost avoidance. Yeah. It's so much better than just reacting to a big bill after the fact. Exactly. It's all about being proactive and implementing measures to prevent unnecessary spending from happening in the first place. So what are some of those proactive measures? Well, one key strategy is implementing cost-aware architecture design principles. Okay. It's about making sure engineers are considering cost as a key factor when they're designing and building those cloud applications. So it's not just about building something that works. It's about building something that works efficiently and cost-effectively. Precisely. Another important strategy is establishing clear guidelines and policies for cloud resource provisioning. That sounds like putting some guardrails in place to prevent runaway spending. Exactly. Think of things like requiring justification for new resources, setting limits on resource usage and implementing automated approval workflows. Yeah, those all sound like great ideas. And of course, there's always education and training. Absolutely. Making sure everyone in the organization understands those basics of cloud cost management and how their actions can impact the bottom line. It's about creating a culture of cost consciousness. Precisely. And by taking a proactive approach to cost avoidance, you can prevent a lot of headaches and unnecessary spending down the road. You know, one topic that's becoming increasingly important these days is sustainability. Yes, cloud sustainability is a hot topic. Yeah. As companies become more aware of their environmental impact, they're looking for ways to make their cloud operations more sustainable. And how does Phenops tie into that? Well, Phenops principles can be applied to reduce the environmental footprint of your cloud infrastructure. Okay. It's about using resources efficiently, minimizing waste, and even choosing cloud providers that prioritize sustainability. So it's not just about saving money, it's about saving the planet. Exactly. And the good news is that these two goals often go hand in hand. Right. By optimizing your cloud infrastructure for cost efficiency, you're often also reducing your energy consumption and carbon footprint. It's a win-win for both your business and the environment. Absolutely. And there's a growing movement called Green Ops, which is all about integrating sustainability considerations into those cloud operations. So it's not just about the bottom line anymore, it's about that triple bottom line, people, planet, and profit. Well said. And I think that's a perfect note to end on. Yeah. So let's explore the what, the how, and the why of Cloud FinOps. It's been an incredible journey. We've covered a lot of ground, but the key takeaway is that Cloud FinOps is more than just a set of tools or techniques. Right. It's a mindset, a culture, a journey of continuous improvement. It's about taking control of your cloud finances, aligning them with your business goals, and empowering everyone in the organization to be part of the solution. And remember, the cloud landscape is constantly evolving, so your FinOps practices need to evolve with it. Stay informed, stay connected with the FinOps community, and never stop learning. Well said. And on that note, thanks for joining us on this deep dive into Cloud FinOps. Yeah, thanks for listening, everybody. We hope you've learned a lot, and we encourage you to continue exploring this exciting and ever-evolving field. Remember, it's not about perfection, it's about progress. Take it one step at a time, experiment, learn, and celebrate your successes along the way. And as always, thanks for listening to the deep dive.