I think the key word there was 'primary'. I think it's okay to have a main audience in mind that isn't the entire world.
From a typography standpoint, think about how you would represent Hudum versus Latin fonts on a mobile app or PWA now that Mongolia is deprecating Cyrillic script.
On the Cloud side, a lot of major K8s orchestration and edge computing innovations were sparked by Chinese telcos and tech vendors trying to work around GFW related latency issues.
No, it doesn't.
If my feature's primary market is the US, I'm not going to prioritize Japanese localization or GDPR compliance. Those two epics will remain in the backlog until a sufficiently large enough opportunity arises to justify a pivot to meet those feature requests.
I am not going to justify limited engineering resources to localization if the localization isn't aimed at my primary market.
This is why GOOG or MSFT haven't prioritized building billing infrastructure for Naira, but something a company like Zoho absolutely can.
My hunch is Zoho is using Razorpay (YC W15) for payments, and Razorpay has been pivoting to support the Africa and ASEAN markets (like most Indian companies have been for decades).
Is there publicly available information on this?
Increasingly, American companies cannot expect to succeed internationally on the strength of brand alone, if they are not willing to customize their product and service offerings to meet local requirements.