Most of the tooling I've seen does cost visibility and optimization reasonably well. Rightsizing, reserved instances, cleaner dashboards, and better tagging. That's useful stuff.

What I haven't seen solved cleanly is the next layer. Not what did we spend, but what did we get for it. Cost per customer, cost per feature, and margin by product line.

At scaling SaaS companies this is the question the CFO is actually asking. Engineering can pull the AWS bill. Nobody can tell you whether cloud costs are growing in line with revenue or ahead of it, or which features are quietly margin-negative.

I'm curious how teams here are approaching this. Internal tooling? Something off the shelf? Just living with the gap?