Category: FinOps

  • The future of FinOps – part 1

    The future of FinOps – part 1

    FinOps data has always been sensitive, and FinOps practices have always been something worth protecting. As FinOps has matured into a key enabler of business decision-making, it has also evolved into something much broader than cost management. It now sits at the intersection of observability, anomaly detection, inventory management, and investigation.

    FinOps has become an intelligence layer.

    Many FinOps practitioners have probably experienced this already. At some point, someone from security, compliance, or operations has likely asked for a list of resources that could be affected by a vulnerability or operational issue. More often than not, FinOps teams are the only ones with a complete and accessible view of everything an organization is running.

    Knowing what exists often matters more than controlling it.

    Without deliberately aiming for it, FinOps has become a critical function that helps modern cloud-based organizations operate effectively while protecting their intellectual property, infrastructure, and architecture.

    As this role continues to expand, I believe FinOps will rise to the challenge.

    In the past, I have described FinOps as consisting of three primary responsibilities:

    • Rate reduction
    • Waste reduction
    • Transparency

    Today, I believe transparency is increasingly becoming the primary objective, with rate reduction remaining a close second. Waste reduction is gradually becoming a cultural responsibility shared by everyone who builds and operates in the cloud.

    The rise of AI will only accelerate this shift. As organizations adopt AI at scale, the demand for transparency across infrastructure, applications, and consumption patterns will become even more important.

    Into Uncharted Territory

    I have spent nearly a decade helping organizations reduce waste, and I will probably never stop looking for inefficiencies. In many ways, I approach inefficiencies the same way security researchers approach vulnerabilities.

    That said, it is becoming increasingly clear that FinOps needs more researchers and fewer advocates.

    Rather than constantly pushing for change, FinOps professionals should focus on exposing information. Show people what they can influence. Show them what is going wrong. Present the evidence and allow teams to act.

    And when action is not taken, FinOps must sometimes step into the role of investigator, forensic analyst, and operator.

    During a recent conversation with a peer in the industry, I described the current transition this way:

    “With the advent of cloud, the procurement process was completely disrupted. Suddenly, anyone with a credit card and a browser could acquire infrastructure. Now AI is creating the same disruption for applications and software. Anyone with a license can build solutions that drive resource consumption.”

    This is where the next major challenge for FinOps emerges.

    Historically, FinOps practitioners have focused on understanding cloud architecture. Going forward, they will also need to understand software systems, application behavior, and how those systems consume infrastructure resources.

    The evolution of FinOps as an intelligence layer makes this possible. The more visibility we gain, the more connections we can make. The more connections we can make, the better we can understand the true drivers of cost, performance, efficiency, and risk.

    The Real Shift in FinOps

    FinOps entered the technology landscape with frameworks, methodologies, and strong guiding principles.

    Phrases such as:

    • “It’s not about saving money, it’s about making money.”
    • “Showback drives behavioral change.”

    helped establish FinOps as a governance and management discipline.

    Those principles remain valuable, but the environment has changed.

    Today, engineers, architects, and product teams are far more aware of costs during the design and development process. This mirrors what happened with security over the last decade, where security considerations gradually became part of the normal way people build systems.

    The Conclusion

    As cost awareness becomes embedded in engineering culture, the role of FinOps naturally evolves.

    We are no longer simply the people who optimize spend.

    We are the people who enable ownership.

    We provide the visibility that allows teams to demonstrate leadership. We provide the context that supports informed decisions. We transform data into understanding.

    We are the watchers.
    The analysts.
    The investigators.
    The sense-makers.
    The enablers.

    And just as we built deep expertise around cloud infrastructure, we will build the same expertise around AI. By doing so, we will help our organizations adopt these technologies successfully, make better decisions, and ultimately achieve their mission.