intl-expansion
International market expansion strategy for scaling companies. Covers market selection scoring, entry mode evaluation, localization requirements, regulatory compliance by region, go-to-market adaptation, team structure decisions, and launch planning. Use when expanding to new countries, evaluating international markets, planning localization, building regional teams, assessing regulatory requirements, or when user mentions international expansion, market entry, localization, regional strategy, global expansion, cross-border, or new market.
What this skill does
# International Expansion
Frameworks for expanding into new markets: selection, entry mode, localization, regulatory compliance, GTM adaptation, and execution. Every expansion is a bet -- this skill structures the bet to maximize signal before committing resources.
## Keywords
international expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion, EMEA, APAC, LATAM, data residency, local entity, regional hiring, currency, payment methods, regulatory compliance
---
## Decision Sequence
```
Market Selection --> Entry Mode --> Regulatory Assessment --> Localization Plan
--> GTM Strategy --> Team Structure --> Launch --> Scale or Exit
```
---
## Market Selection Framework
### Scoring Matrix
| Factor | Weight | Assessment Method | Score 1-5 |
|--------|--------|------------------|-----------|
| Market size (addressable) | 25% | TAM in target segment, willingness to pay, growth rate |
| Competitive intensity | 20% | Incumbent strength, number of alternatives, market gaps |
| Regulatory complexity | 20% | Barriers to entry, compliance cost, timeline to launch |
| Cultural distance | 15% | Language, business practices, buying behavior, sales cycle |
| Existing traction | 10% | Inbound demand, existing customers, partnership signals |
| Operational complexity | 10% | Time zones, infrastructure, payment systems, talent pool |
### Market Selection Decision Tree
```
START: Considering a new market
|
v
[Is there existing pull from this market?]
|
+-- YES (inbound demand, existing customers) --> Strong signal. Score and proceed.
|
+-- NO --> [Is there a strategic reason to enter?]
|
+-- YES (competitor pressure, investor expectation) --> Score carefully.
| Be honest about push vs. pull.
|
+-- NO --> Do not enter. Focus on existing markets.
```
### Regional Quick Reference
| Region | Market Size | Regulatory Complexity | Cultural Distance (from US) | Key Considerations |
|--------|------------|----------------------|---------------------------|-------------------|
| UK/Ireland | Large | Medium | Low | English-speaking, strong tech ecosystem, Brexit considerations |
| DACH (DE/AT/CH) | Large | High | Medium | Data privacy strict, enterprise-heavy, German language needed |
| Nordics | Medium | Medium | Low-Medium | Tech-savvy, English common, smaller market size |
| France | Large | High | Medium | Language required, strong labor laws, cultural nuances |
| Benelux | Medium | Medium | Low-Medium | Multilingual, hub for European operations |
| Japan | Very Large | Very High | High | Requires local partner, long sales cycles, relationship-heavy |
| Singapore/SEA | Medium-Large | Medium | Medium | Regional hub, English common, diverse sub-markets |
| Australia/NZ | Medium | Low | Low | English-speaking, similar business culture, timezone challenge |
| Brazil | Large | Very High | High | Portuguese required, complex tax, large opportunity |
| India | Very Large | High | Medium | Price-sensitive, English common, massive scale potential |
---
## Entry Mode Evaluation
### Entry Mode Comparison
| Mode | Investment | Control | Risk | Speed | Best For |
|------|-----------|---------|------|-------|----------|
| Remote sales (export) | Low ($10-50K) | Low | Low | Fast | Testing demand before committing |
| Partnership/reseller | Medium ($50-200K) | Medium | Medium | Medium | Markets with strong local requirements |
| Local hire (no entity) | Medium ($100-300K) | Medium-High | Medium | Medium | First boots on the ground |
| Full entity (subsidiary) | High ($200K-1M) | Full | High | Slow | Major markets with proven demand |
| Acquisition | Highest ($500K+) | Full | Highest | Fast (if done well) | Immediate market presence + customer base |
### Entry Mode Decision Tree
```
START: Market selected, entry mode needed
|
v
[Do you have existing customers in this market?]
|
+-- NO --> Start with Remote Sales
| Test demand for 3-6 months
| If revenue > $200K ARR from market --> Upgrade
|
+-- YES --> [Revenue from this market > $500K ARR?]
|
+-- NO --> Remote Sales or Local Hire (EOR)
|
+-- YES --> [Does the market require local entity?]
|
+-- YES (regulatory requirement) --> Full Entity
+-- NO --> [Revenue trajectory?]
|
+-- Growing fast --> Local Hire, plan Entity
+-- Stable --> Partnership or Local Hire
```
### Default Graduation Path
```
Stage 1: Remote Sales ($0-200K ARR from market)
- Sell remotely from HQ
- No local presence
- Test messaging, pricing, ICP fit
Stage 2: Local Hire ($200K-500K ARR)
- 1-2 people via EOR (Employer of Record)
- Sales + CS representative
- No legal entity yet
Stage 3: Local Entity ($500K-2M ARR)
- Establish legal entity
- Hire local team (3-8 people)
- Local banking, contracts, compliance
Stage 4: Regional Hub ($2M+ ARR)
- Full local team (10+ people)
- Regional leadership
- Market-specific product features
```
---
## Localization Framework
### Product Localization
| Layer | Must Have | Nice to Have | Cost Impact |
|-------|----------|-------------|-------------|
| Language (UI) | Full translation of core product | Marketing site in local language | $20-50K initial |
| Currency | Display and charge in local currency | Multi-currency invoicing | $10-30K engineering |
| Payment methods | Credit card + local preferred method | All local payment methods | $5-20K per method |
| Data formats | Date, time, number, address | Local units (km, kg, etc.) | $5-15K engineering |
| Data residency | If legally required | If customer-required | $50-200K infrastructure |
| Cultural adaptation | Avoid cultural missteps | Full cultural optimization | Variable |
### GTM Localization
| Element | Approach | Common Mistake |
|---------|----------|----------------|
| Messaging | Adapt value proposition for local pain points | Copy-paste from home market |
| Channel strategy | Research local channels (may differ significantly) | Assume same channels work everywhere |
| Case studies | Local customer references essential | Only showing US/UK case studies |
| Partnerships | Local integrations and ecosystem | Ignoring local tech ecosystem |
| Events | Regional conferences and meetups | Only attending global events |
| Content/SEO | Local language content, local domain | English-only content for non-English market |
### Operations Localization
| Area | Key Considerations |
|------|-------------------|
| Legal entity | Type, timeline, cost, ongoing compliance |
| Tax compliance | VAT/GST registration, transfer pricing, withholding |
| Employment law | At-will vs. strong protections, notice periods, benefits |
| Customer support | Hours, language, channels |
| Banking | Local bank account, payment processing |
| Insurance | Local requirements for entity and employees |
---
## Regulatory Compliance by Region
### Data Privacy Requirements
| Regulation | Region | Key Requirements | Penalty |
|-----------|--------|------------------|---------|
| GDPR | EU/EEA | Consent, data minimization, DPO, breach notification | Up to 4% annual revenue |
| UK GDPR | UK | Similar to GDPR, separate registration | Up to 4% annual revenue |
| LGPD | Brazil | Similar to GDPR, DPO required | Up to 2% revenue (capped R$50M) |
| PIPL | China | Data localization, consent, cross-border assessment | Up to 5% annual revenue |
| PIPA | South Korea | Consent, purpose limitation, data localization for some | Up to 3% of related revenue |
| APPI | Japan | Consent, purpose specification, cross-border transfer rules | Criminal penalties possible |
| Privacy Act | Australia | APPs, breach notificationRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.