Ask HN: How do you measure ROI for introducing Rust into a company?

I would first ask why you are doing this in the first place, "introducing Rust into a company"?

What is motivating you to do that? Or is this being pushed on you to solve a problem which rust isn't a cure all?

I would recommend starting by examining your software architecture, engineering personell capabilities, and then proceed to see how rust fits in the picture, if at all.

This will depend on the current use case for your company. Can it save the company money in the long-run? I don't think this can be answered on the language alone.