I’ve been putting a lot of effort in keeping my modeling portal bilingual until now but stats don’t lie and tell me that multi-language support is not part of my “minimum viable product“. For instance, more than 90% of the RSS subscribers in the portal follow the English version of the feed (instead, around 20% of the visitors come from Spanish-speaking countries).
Therefore, if I want to maximize the impact (and of course the visibility) of the portal and the services I offered there, I should focus on providing more content and less on providing Spanish versions of that content. Playing the “language” card in a portal like mine does not seem to pay off. Of course, this changes if you sell products to other “customer” profiles but software developers are too used to read and use English tools to factor this in when deciding which product to buy.
Not providing multi-language support does not mean that you should not design your product with that in mind so that adding language support in the future does not imply any major challenge (just the definition of new language resource files with the appropriate translations)!