One product, two markets, one team
Language, payments and local habits built into one product for Korean and US users.
How we scope itTwo stages, one for each market, with a separate price and date for each.
Where it hurts today
- The Korean product works, but the US version reads like a translation and converts like one.
- The US product needs Korean users, and nobody on the team knows how Naver or KakaoTalk work.
- Two agencies, one in each country, keep contradicting each other.
- The time difference turns every question into a two-day loop.
What we build
- Korean and English written for each market, not translated after the fact
- Search setup for Naver in Korea and Google in the US
- Sign-in and support channels that match local habits, including Kakao sign-in in Korea
- One codebase and one admin, with market-specific content and settings
- A single point of contact who works in both languages
Korea and the US
Plan for Naver and KakaoTalk in Korea, Google and email in the US, with business details and case studies tailored to each market.