Business
Localization Plan AI Prompt Template
Create a localization plan for new markets with this AI prompt. Language, pricing, payments, and cultural adaptation checklist. Free to copy and use today.
The prompt
ROLE: You are a localization director who has launched products in 30+ markets. CONTEXT: Product: [PRODUCT]. Target market: [MARKET] ([LANGUAGE]). Current state: [CURRENT_STATE]. What must work on day one: [DAY_ONE_REQUIREMENTS]. Budget: [BUDGET]. TASK: Build a complete localization plan. FORMAT: 1. Localization Scope Table: area (UI, marketing site, help docs, support, legal, pricing, payments), current state, target state, effort (S/M/L). 2. Language Plan (what gets human translation vs machine + review, glossary needs). 3. Pricing and Payments (local currency, local payment methods, tax handling). 4. Cultural Adaptation (imagery, examples, colors, holidays, taboos to avoid). 5. QA Plan (linguistic testing, locale testing checklist). 6. Phased Timeline with milestones. End with 3 localization fails to avoid, with real-world style examples. CONSTRAINTS: Day-one requirements define MVP scope; everything else is phase 2. Machine translation alone is never acceptable for customer-facing legal or payment content. Keep the plan executable within the stated budget. If any variable is unclear or missing, ask up to 3 targeted clarifying questions before producing the output, and clearly mark every assumption you make with [ASSUMPTION].
Variables to fill in
Replace each [variable] in the prompt with your own details:
[PRODUCT] [MARKET] [LANGUAGE] [CURRENT_STATE] [DAY_ONE_REQUIREMENTS] [BUDGET]
Example input
PRODUCT=fitness coaching app, MARKET=Japan, LANGUAGE=Japanese, CURRENT_STATE=English-only iOS app, DAY_ONE_REQUIREMENTS=app UI, signup, payments, support email; BUDGET=$70k
How to use this prompt
Define day-one scope ruthlessly, get a native speaker to review the cultural section, and test payments with real local transactions before launch.
Tips for the best results
- Payment methods make or break launches; the best-translated app fails if customers cannot pay the way they expect.
- Build a term glossary before translating; inconsistent terminology looks unprofessional in every language.
- Localize examples and imagery, not just words; a US-centric example confuses more than a typo does.
Frequently asked questions
Human translation or AI translation?
AI plus human review for most content; pure human translation for brand, legal, and anything involving money or safety.
Should I localize pricing?
Yes: local currency, local purchasing power, and local payment methods. Straight currency conversion is not localization.