Typescript and productivity is an interesting discussion. I have been converted to the typescript cult, but I wasn't always. At my last job our typescript was very poorly architected, and small changes were often quite hard to type correctly. It was very hard to diagnose type errors because the intellisense output was unreadable gibberish. Code and types were so tightly coupled, nobody wanted to think about refactors. And it seemed like everybody in the engineering org was just ok with it, like it was just the price of doing business with typescript.
Typescript is useless if all you're doing is writing the same old JS spaghetti and then typing it after the fact. You need a leader within the org who actually understands the role of types in development. Without that, maybe it is better to stick with the untyped version.