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).
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).