Picking technology stacks in a company is a very difficult thing, it’s not just “is something viable”. While I believe Rust is just getting started on its path of redefining all low level programming, succeeding where C++ didn’t, I don’t think it’s this simple a question.
You need to frame the use case as to what Rust will do to help the company succeed, example: I recently did a PoC at work with a Rust library that would form the core of a suite of distributed SDK libraries for my company. We are in the process of validating the toolchains around Obj-C and all iOS and tvOS platforms, PHP, C# and possibly a few other languages. The point of this is to reduce the duplication of code across all of these shipping pieces of software, where it makes sense (BTW, everything works great so far).
If you really want to put Rust in play inside an organization, you should choose to do something with it that has clear benefits for the business that make it a good decision. Otherwise it comes down to just another language, and adding additional languages to a development organization should not be taken lightly. Rust is awesome, I firmly believe that it will gain significantly on the backend, and when WebAssembly matures, I think it will also do awesomely there. But the tooling is still young, and depending on how an Organization is going to use it, it could actually delay delivery because underlying libraries might need to be built to make the project successful.