(As a consultant) I've been asked to write a business case on switching the underlying technology of a product from a somewhat mature open source codebase to a custom implementation.Engineering is convinced the current underlying technology will eventually kill the product it backs (re: customization of their product has been more difficult than it should be due to the underlying tech and finding people proficient at this underlying tech or training them in it has been difficult). However, the "business side" of the company needs convincing because they are focused on short-term goals.With that in mind, I'm trying to better understand my audience's language and thought processes and was wondering if y'all knew of resources that talked about similar problems formally.(If it helps I've mostly been on the science/engineering side of businesses for nearly a decade so this is really my first exposure to needing to convince the "business side" in a formal manner with their own language)(Also, if it helps, this open source technology seems to have a massive hype machine behind it; it's not hard to find engineers/scientists having very serious problems with it but it is masked by how a certain search engine is pushing tons of flattering articles to the front of the search)