FinOps in Action | Engineering Enterprise FinOps ft. Piotr Kuczmera

Engineering Enterprise FinOps ft. Piotr Kuczmera | Ep # 72

June 4, 2026 / 34:44/E72

What if the biggest mistake your FinOps program makes is skipping the requirements phase entirely?

In this episode of FinOps in Action, host Taylor Houck sits down with Piotr Kuczmera, Head of FinOps at ZF Group, to unpack how he built a FinOps practice from scratch at a 150,000 person global enterprise, and why the first question every organization should ask is not "how do we cut costs" but "what exactly do we need?"

Piotr shares how a single report request from his manager five years ago turned into a full scale internal FinOps platform, a hub and spoke operating model across 15 to 20 business units, and a team built on the combination of FinOps practitioners and data engineers working side by side.

Here is what they covered:

Why FinOps is more than cost savings. Piotr explains that equating FinOps with cost optimization alone leads to failed implementations, and that starting with a clear requirements conversation, like a tailor fitting a suit to the right occasion, is what sets a practice up for long term success.
How chargeback became the turning point. When ZF connected individual names to specific budgets and sent real invoices, something clicked. Engineers and budget holders stopped asking about aggregate project spend and started asking "why am I paying this much and how do I reduce it?"
The case for building your own platform. ZF evaluated the major third party FinOps tools and walked away. Licensing costs, limited multi-cloud support, and a lack of flexibility in adapting to existing finance and procurement processes all pointed toward a homegrown solution built on native cloud tooling and a BI layer they already owned.
The hub and spoke model for FinOps at scale. At the center sits a core team of FinOps consultants and data engineers. In each business unit, a nominated budget owner and a FinOps champion bridge the gap between central strategy and local execution.
AI for FinOps, not just FinOps for AI. Piotr is most energized by how AI can automate repetitive FinOps workflows and take recommendations beyond basic CPU and memory parameters to consider commitment connections, usage patterns, and resource families all at once. He also sees FinOps as a function that should open doors for AI adoption, not slow it down.
FinOps as connective tissue. Across financial colleagues, engineering teams, and business managers, Piotr sees FinOps as the function responsible for translating the right information to the right persona, not flooding finance with VM data, and not giving engineers a budget variance they cannot act on.

Chapters:

01:27 Meet Piotr Kuczmera

02:14 FinOps Is Not Just Cost Savings

03:30 Building Trust Across Departments

05:00 The FinOps Team Structure at ZF Group

08:00 Hub and Spoke: Champions and Budget Owners

10:00 Scale and Cadence Across 15 to 20 Categories

12:00 Back to the Beginning: One Report at a Time

14:00 Build vs Buy: The Platform Decision

18:00 Why Ownership of Data Changes Everything

21:00 Chargeback as the Accountability Switch

23:00 Translating FinOps Across Personas