DORA × Engineering Cost: The ROI Story Tools Miss
A VP of Engineering walks into the quarterly review with a clean DORA dashboard: lead time down from 9 days to 4, deployment frequency up from 1.2 per week to 2.8, change failure rate trimmed from 18% to 11%. The CFO listens patiently, then asks the only question that matters: "What did that save us in dollars?" The room goes quiet. The DORA tool does not know. The finance tool does not know either, because it does not see deployment data. The CTO ends up arguing on principle. Two quarters later, the platform team's budget is cut to fund a sales hire.
Most engineering organizations track DORA and cost in two separate systems. Sleuth, Swarmia, LinearB show you DORA. Jellyfish (its standalone finance module) and Faros show you cost. The DORA State of DevOps reports explicitly link the four DORA metrics to organizational performance, but only at the outcomes layer, not the dollar layer. To translate "we cut lead time from 9d to 4d" into a real number the CFO defends, you need both data sources in the same query. This article walks through the four integration points, then a worked Q1 → Q2 example with a 2.73x quarterly ROI.