Comparison
Cost anomaly detectionvsUnit economics
Cost anomaly detection
a job that was accidentally left running was flagged on day two rather than found in the invoice five weeks later.
Automated monitoring for unexpected changes in spend, alerting on a deviation rather than on a threshold. The billing feedback loop is otherwise measured in weeks, which is long enough for a mistake to become a significant number. Routing the alert to the team that owns the resource rather than to finance is what turns it from a report into a fix.
Full entry →Unit economics
the bill went up thirty percent and the cost per order fell, which is the only version of that sentence worth reporting.
Expressing infrastructure cost per unit of business value — per order, per tenant, per thousand requests — rather than in absolute currency. It is the only framing in which a growing bill can be evaluated, because absolute cost conflates growth with waste. It also gives engineering a target that survives a good quarter, which a spend cap does not.
Full entry →