The narrative that ‘Cloud costs scale faster than revenue’ is hitting home again. With reports like the infamous, massive Figma AWS bill, it’s clear that while the cloud gives us unbeatable velocity (microservices, immediate scale, low friction), it demands a trade-off in optimization and financial discipline that most teams only face when it’s too late.
At what scale (team size, user base, or monthly bill) did your company finally have to shift from a ‘deploy fast, pay later’ mentality to a ‘cost-aware development’ culture? What was the single most effective, non-obvious change you made? (i.e., beyond “turned off unused VMs”, we’ve all done that). Was it a shift in org structure, a specific metric (Cost per Customer?), or a change in developer tooling
The problem isn’t the cloud, it’s the lack of ownership. We’re still incentivizing feature sprints over efficiency. Finance sees one huge AWS line item. Eng leadership is too far from the actual $ per query. Until you make $CPC (cost per customer) a core metric on every sprint board, nothing changes. Just saying “optimize” is VPE performance art
Our shift was mandatory when we hit Series C and VCs started asking why our gross margins were crap. The solution wasn’t a tool, it was an org change. We introduced a Platform Guild that owned the ‘golden path’ for infrastructure, making the cheap way the easiest way to deploy. If you went off-road for performance, you needed a cost justification sign-off. Friction, yes. But it saved millions