Building a SaaS Product for Emerging Markets: Lessons I Wish I'd Learned Earlier
A founder in Lagos once told me his customers pay him in three currencies and none of them are stable. He was building a logistics SaaS. His churn was 4.2% monthly, which sounds fine until you do the math on annual retention.
That conversation stuck with me. Because most of the SaaS playbooks floating around Twitter — the ones about PLG funnels, self-serve onboarding, $99/month price points — they were written for San Francisco. Not Karachi. Not Nairobi. Not Jakarta. And honestly, applying them one-to-one in emerging markets is how you burn 18 months of runway.
I've spent the last few years watching founders across Pakistan, Southeast Asia, and East Africa build software companies. Some of them are quietly doing $2M+ ARR. Others crashed. The patterns are pretty clear once you look.
The pricing problem nobody warns you about
Here's the thing. Your customer in Dhaka isn't going to pay $49/user/month. Not because they can't afford it — some can — but because the reference price in their head is different. A mid-market FMCG distributor in Bangladesh compares your software to what they pay their accountant, not what a Shopify merchant in Austin pays for Klaviyo.
So you have two options. Price low and volume up. Or price in local currency and absorb the FX pain yourself.
Most successful emerging market SaaS founders I know went with option one — but with a twist. They didn't just discount. They rebuilt the product to serve a real local pain point that a US competitor never bothered solving. Take Zivni, which built its field sales management platform specifically for FMCG teams in markets where reps visit 40+ shops a day on motorbikes, often with patchy 3G. That's not a feature you retrofit into Salesforce. It's the whole product.
And the pricing works because the value is obvious. If a distributor was losing 12% of visits to ghost check-ins before, and now that number is 0.8%, the ROI conversation writes itself.
Sales is not a growth loop. Sales is sales.
I used to think product-led growth was the endgame for every SaaS company. Sign up, swipe a card, done. Then I watched three friends try to run PLG motions in emerging markets and get absolutely wrecked.
Here's what actually happens. A buyer in Casablanca signs up for your free trial. They poke around for four minutes. They don't convert. Not because your product's bad — because they were never going to buy software from a website. They buy from a person. Ideally a person who visited their office, drank tea, and answered 60 questions about data security.
The founders winning in these markets have accepted this. They run high-touch sales. They hire local reps. Their CAC looks scary on a spreadsheet until you realize their LTV is much higher too, because relational churn is way lower than transactional churn. Once you're in, you're in for years.
One founder in Karachi told me his best sales channel was WhatsApp Business. Not LinkedIn. Not Google Ads. WhatsApp. He'd send a 90-second Loom-style video to a prospect's personal number and close 31% of the calls that followed. Try running that motion in the Bay Area.
Build for the network, not the browser
Offline-first isn't a nice-to-have. It's table stakes. If your app breaks when connectivity drops for 40 seconds, you don't have a product — you have a demo.
I got this wrong at first. Early prototypes I saw (and helped with) assumed constant sync. They fell apart the moment a field user hit a dead zone. The fix isn't just caching. It's rethinking the entire data model. Queue writes locally. Reconcile conflicts on reconnect. Show the user something useful even when the server is unreachable.
Same for payments. Stripe doesn't work in half these markets. Your invoicing needs to handle bank transfers, mobile money, and — I'm not joking — occasionally cash pickups reconciled manually by an ops person. Build for that reality or find another market.
A few smaller things I've seen repeatedly
- Language matters more than you think. English-only UIs cap your TAM. Even in markets where business is done in English, the field user often prefers Urdu, Bahasa, Swahili, or Portuguese.
- Screenshots-as-support is real. Users will WhatsApp you screenshots of errors instead of filing tickets. Build your support workflow around this, don't fight it.
- Android-first, not iOS-first. Roughly 84% of the market share in most of these regions is Android. Some of it running on devices with 2GB of RAM. Your React Native bundle needs to be small.
- Feature requests will be wild. Someone will ask you to add an inventory module to your CRM. Say no often. Product-market fit dies from bloat faster than from missing features.
The part where I contradict myself
Look, I've said all this like I have it figured out. I don't. Some of the best emerging-market SaaS founders I know break every rule above. One is running pure PLG in Vietnam and it's working. Another charges $200/user/month in Nigeria and has a waitlist.
The honest answer is that "emerging markets" is a lazy category. Indonesia is not Kenya. Pakistan is not Peru. What connects them isn't demographics — it's the fact that global SaaS templates were built ignoring them, which means there's still real greenfield for founders who actually live inside these problems.
The question I'd ask any founder building here: what does your product do that a well-funded US competitor would never bother to build? If you can't answer that in one sentence, you're probably building the wrong thing.
What would you build differently if you couldn't assume WiFi?