Cross-stack FinOps: bill anatomy, order-of-magnitude war stories, chargeback culture — the capstone remix.
The cross-cutting capstone, told in primary sources: Netflix's Byte Down attribution program, Uber compressing its logging bill by two orders of magnitude, Wix halving platform spend with chargeback, Canva's $300K/month storage-class arithmetic — and the mechanism classes (representation, substrate, pricing model) that separate order-of-magnitude cuts from knob-turning.
Cost lands on the people who create it: Wix's attribution stack and deliberately simple unit price, the review loop that keeps savings from decaying, cost as a design-phase requirement, and honest build-vs-buy unit economics.
The platform team's budget line absorbs the whole data stack — every Trino query, every Spark job, every forgotten staging table lands on one cost center. So every optimization is the platform team's job, every regression is the platform team's fault, and the teams actually *writing* the expensive queries have no reason to care. That was Wix's starting position, and the ending position is the strongest cultural result in this cohort's corpus: 50% of monthly data-platform cloud spend gone, with no reported performance sacrifice — achieved not by a heroic optimization but by making cost land on the people who create it. Last week was about mechanisms that cut bills; this week is about the org design that makes cutting *self-sustaining*.
The full week 3 brief is part of LeetData Pro.
