When two projects compete for the same engineering team, how does a CTO decide which one goes first? Cost of delay — a prioritization framework from Don Reinertsen's Lean product development — turns that gut-wrenching choice into a math problem. In this episode, Lucas and Luna walk through a real scenario at a fictional SaaS company called DataSync, where the CTO had to pick between a new integration worth $500,000 in annual recurring revenue and a database migration that would reduce future incident response time by 60%. Using cost of delay, they calculate the urgency of each option, factor in decay profiles, and show why the 'obvious' choice isn't always right. Listeners learn how to estimate delay cost per week, apply the CD3 metric (cost of delay divided by duration), and avoid the trap of treating all delays as equal. Anchored to July 2026, this episode gives engineering leaders a concrete tool for making trade-offs transparently — no black box, no politics.