Knowing the "why's" and "where" will help everyone within the org (eng and finance) make better decisions on what and where to focus on (https://www.cloudforecast.io/blog/aws-tagging-best-practices...). Also, it'll make AWS Cost Explorer or any other cost managements tools WAY more effective.
Cost optimization can feel like drinking from a firehouse since there are so many different strategies, and approaches to it (autoscaling, spot, reserved instances/savings plans, eliminating idle & wasted resources, etc.). Also, you have to apply your OWN organizational context to it as well (business and tech side). There is a fine balance companies and eng dept need to take with cloud cost control since it can be a huge time commitment to pull your end dept into.
(disclaimer // founder of https://www.cloudforecast.io)