Back to articles
Market Expansion Product Strategy Business Strategy

The New Market is a Design Problem

Expanding into a new market isn't just a distribution problem. The defaults, assumptions, and mental models that work in your home market often actively fail somewhere new. The win comes from treating the new market as its own design problem.

March 8, 2026

The playbook for market expansion usually starts with distribution: find local partners, translate the product, adjust pricing for local purchasing power. This is necessary. It is not sufficient.

The harder problem is the one that comes before distribution: what does the market actually need, and is your product capable of meeting that need?

The localization trap

Localization is not adaptation. Translating your interface into Bahasa Indonesia doesn’t make your product relevant to Indonesian users. Adjusting pricing doesn’t change the underlying value proposition.

The localization trap is treating a new market as a scaled-down or translated version of your existing market. It usually fails because markets differ not just in language and price sensitivity, but in:

  • Trust infrastructure: Who do users trust, and how do they verify that trust?
  • Workflow patterns: How do users accomplish the job your product is designed to do?
  • Constraint profiles: Bandwidth, device capability, payment infrastructure, regulatory environment.
A street market in Southeast Asia, showing local commerce patterns
Local commerce patterns reveal trust and workflow assumptions that global products often miss.

Designing for the market

The approach that works is to treat the new market as its own design problem. This means:

Starting with observation, not assumption. What do users currently do? What are the friction points? What workarounds have they invented? The workarounds are especially valuable — they’re evidence of demand that existing products haven’t met.

Testing your core assumptions. Every product has assumptions baked into its design. Which of yours don’t hold in the new market? Find out before you’ve committed to a localization roadmap.

Identifying what has to change versus what can stay. Not everything needs to be rebuilt. The discipline is in figuring out which parts of your product are genuinely portable and which parts need to be rethought.

Team doing user research in a local context
Field research in the target market surfaces assumptions the home market made invisible.

Thinking in systems

Market entry isn’t a one-time event — it’s the beginning of a learning loop. The companies that get it right build feedback mechanisms that surface market-specific signals continuously, not just at launch.

This talk by Oren Cass on institutional constraints is a useful frame for thinking about why policies and products that work in one context often fail when transplanted:

The opportunity in the gap

The gap between what users need and what existing products provide is the opportunity. But it’s only accessible if you’ve done the work to understand the gap accurately.

In practice, this means spending time in the market before building for it. Talking to users. Watching how they work. Being wrong about your initial hypotheses and updating accordingly.

This is slower than just translating the product and adjusting the pricing. It’s also the version that tends to work.