Dieter Matzion, a cloud and technology infrastructure leader at Roku with prior engineering leadership roles at Intuit, Netflix, and Google, joins Mike Weider to talk about how FinOps teams can shift cost awareness earlier in the engineering lifecycle. T he conversation covers why engineers often misjudge efficiency, how to create practical cost KPIs, and why AI is pushing the industry toward tokenomics as a separate discipline. We discuss how to make cost another engineering dimension alongside latency and performance, why leadership buy-in matters, and how teams can keep cloud spend aligned with business growth without slowing down innovation. Key topics Why shift-left FinOps delivers the most value when engineers are engaged before architecture decisions are locked inWhy the FinOps community is still early in adoption even though the practice is now part of the core curriculumThe incentive gap in cost optimization, where engineers can save millions without sharing in the upside but can still carry the downside risk of outagesWhy cost should become a standard engineering dimension alongside latency, performance, and reliabilityHow cloud cost literacy helps engineers understand the cost impact of infrastructure choices across the full application lifecyclePractical KPI ideas, including cloud cost per revenue, cost per vCPU hour, and cost per gigabyte storedWhy unit economics must be measured continuously in production, not just modeled at project kickoffHow Roku uses cost per streaming hour as a company-level benchmark and requires new features to be offset by optimizations elsewhereThe difference between FinOps and tokenomics, and why AI introduces a five-layer stack with its own KPIsHow AI coding tools may eventually benefit from a dedicated cost agent that understands cloud economics Timestamps 00:00 - Dieter Matzion’s background in cloud infrastructure and FinOps 00:26 - Where shift-left FinOps stands in the community today 03:35 - Why engineers are often poor judges of efficiency 05:38 - The “good enough” mindset and why it fails for cloud commitments 07:25 - Incentives, downside risk, and why savings are rarely rewarded 09:50 - Making cost a normal engineering optimization dimension 10:47 - Why cloud cost literacy matters across the application lifecycle 12:32 - Basic KPIs teams can start with, from cloud cost per revenue onward 13:23 - Cost per vCPU hour and cost per gigabyte stored 15:09 - Why unit economics must be measured in production, not just planned 16:02 - A real example of AI tuning reducing monthly cost dramatically 16:23 - How a gossip protocol created a major cost explosion 16:50 - Roku’s cost per streaming hour benchmark 19:52 - Using proof of concept work to estimate material cost impact 20:53 - How cost checks happen at rollout level, not just per individual code change 21:53 - Alerts, escalation, and human-in-the-loop response 22:57 - Pure cost anomalies versus KPI-driven cost regressions 23:34 - Why tokenomics exists alongside FinOps 24:04 - FinOps versus tokenomics across the AI stack 25:46 - The five layers of the AI stack and how they change optimization 26:11 - New tokenomics KPIs like cache hit ratio and routing quality failure rate 27:35 - Why AI requires a distinct discipline beyond traditional FinOps 28:40 - How AI coding tools and AI application spend change the shift-left problem 29:19 - Current enterprise limits on AI usage and who drives most spend 30:54 - How agentic workflows could eventually include a cost-aware FinOps agent 31:49 - Best advice for teams in the crawl phase 32:10 - Start small, build successes, and get leadership buy-in 33:28 - Why Roku created cost per streaming hour to keep spend from outpacing revenue
