There's an old video of Steve Jobs circa 1997 where someone in the audience puts him in the hot seat about some 'hot' technology at the time. As I recall, his

There's an old video of Steve Jobs circa 1997 where someone in the audience puts him in the hot seat about some 'hot' technology at the time. As I recall, his response was something along the lines of --- maybe we missed an opportunity to use a neat technology in the product, but the product will win in the long run because we remain focused on our customers, and work backwords into the tech. You can typically use whatever tech you want to power the thing. If you use open and well documented communications API/infrastructure then others (including your team) can extend your product with lots of different technologies. For #1 - You can find good C# coders. But you can find great developers who know C# among other things. For #2 - Generally there are two camps in acquisitions (strictly regarding tech). The Microsoft camp, and the other camp. The two camps have their own large ecosystems and there is some overlap. I think for this you just need to understand (just like you understand your customers) which potential acquirers may come along and what they care about. Many times they'll want to rewrite some things anyway and better understand your roadmap (which can always evolve!!!). Long story short, stop building prototypes. Avoid optimizing prematurely as they say. Get one prototype working well, get great developers and you'll make the right tech decisions as a team. If you don't, you get to change them. Good luck!