What is Localise apps?

Global products often fail to address local nuances. Take a successful app from one market and adapt it to the specific needs of another. Consider cultural differences, infrastructure limitations, and local regulations. Gojek did this by adapting ride-sharing for Indonesia's unique market.

Which companies use Localise apps?

Companies that exemplify the Localise apps framework include Gojek - Localized ride-hailing and delivery services for the Indonesian market, Paytm - Adapted mobile payments for India's specific needs and regulations, Jumia - Tailored e-commerce for African markets with unique logistics challenges.

How do you use Localise apps?

To apply Localise apps, start by understanding the key components of the framework and mapping them to your specific business context. The framework works best when used systematically as part of a broader strategic analysis.

When should you use Localise apps?

Localise apps is most useful when evaluating strategic options, analysing competitive dynamics, or making resource allocation decisions. It provides structure to what might otherwise be an intuitive or ad-hoc process.

Localise apps: Framework Explained

Localise apps: Framework Explained | Faster Than Normal

App localisation is a market-entry strategy that takes a proven digital product from one geography and rebuilds it — not just translates it — for a target market where local culture, infrastructure, regulation, and user behaviour demand a fundamentally different product experience.

Section 1

How It Works

The core insight is deceptively simple: global products are almost never truly global. They are products built for their home market that happen to be available elsewhere. The gap between "available" and "adapted" is where enormous value hides. When Uber launched in Jakarta, it offered sedan rides booked via credit card in a city where 85% of commuters rode motorbikes and fewer than 5% of the population had credit cards. The product was technically available. It was functionally useless.

App localisation exploits this gap by treating a successful foreign product as a demand signal rather than a product spec. The original app proves that people want ride-hailing, mobile payments, or grocery delivery. Your job is to figure out what ride-hailing actually looks like when the roads are unpaved, the addresses don't exist, and the payment infrastructure runs on cash and mobile money. The demand is universal. The implementation is radically local.

This works because of an asymmetry in organisational capability. Large technology companies optimise for scale, which means standardisation. Every local adaptation is a cost centre — a deviation from the global codebase, a compliance burden, a management distraction. For a local founder, that same adaptation is the entire product. You're not maintaining a deviation from a global standard. You're building the standard for your market. The incumbent's weakness is structural, not strategic, which makes it durable.

"We didn't copy Uber. We built what Uber would have built if Uber understood Indonesia."
— Nadiem Makarim, Founder of Gojek

The framework operates on three layers of adaptation. Surface localisation — language, currency, UI conventions — is table stakes and insufficient on its own. Structural localisation — payment methods, logistics models, regulatory compliance — is where most value is created. Cultural localisation — trust signals, social dynamics, usage patterns — is what makes the product feel native rather than imported. The founders who win are the ones who go deep on all three layers simultaneously.

Localise apps

Continue exploring

How It Works

This connects to...

Continue exploring

Get playbooks like this in your inbox

How It Works

This connects to...