c-level-advisor/skills/intl-expansion/SKILL.md
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.
npx skillsauth add alirezarezvani/claude-skills intl-expansionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Frameworks for expanding into new markets: selection, entry, localization, and execution.
international expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion
Decision sequence: Market selection → Entry mode → Regulatory assessment → Localization plan → GTM strategy → Team structure → Launch.
| Factor | Weight | How to Assess | |--------|--------|---------------| | Market size (addressable) | 25% | TAM in target segment, willingness to pay | | Competitive intensity | 20% | Incumbent strength, market gaps | | Regulatory complexity | 20% | Barriers to entry, compliance cost, timeline | | Cultural distance | 15% | Language, business practices, buying behavior | | Existing traction | 10% | Inbound demand, existing customers, partnerships | | Operational complexity | 10% | Time zones, infrastructure, payment systems |
| Mode | Investment | Control | Risk | Best For | |------|-----------|---------|------|----------| | Export (sell remotely) | Low | Low | Low | Testing demand | | Partnership (reseller/distributor) | Medium | Medium | Medium | Markets with strong local requirements | | Local team (hire in-market) | High | High | High | Strategic markets with proven demand | | Entity (full subsidiary) | Very high | Full | High | Major markets, regulatory requirement | | Acquisition | Highest | Full | Highest | Fast market entry with existing base |
Default path: Export → Partnership → Local team → Entity (graduate as revenue justifies).
| Mistake | Why It Happens | Prevention | |---------|---------------|------------| | Entering too many markets at once | FOMO, board pressure | Max 1-2 new markets per year | | Copy-paste GTM from home market | Assuming buyers are the same | Research local buying behavior | | Underestimating regulatory cost | "We'll figure it out" | Regulatory assessment BEFORE committing | | Hiring too early | Optimism | Prove demand before hiring local team | | Wrong pricing (just converting) | Laziness | Research willingness to pay locally |
| Role | Contribution | |------|-------------| | CEO | Market selection, strategic commitment | | CFO | Investment sizing, ROI modeling, entity structure | | CRO | Revenue targets, sales model adaptation | | CMO | Positioning, channel strategy, local brand | | CPO | Localization roadmap, feature priorities | | CTO | Infrastructure, data residency, scaling | | CHRO | Local hiring, employment law, comp | | COO | Operations setup, process adaptation |
references/market-entry-playbook.md — detailed entry playbook by market typereferences/regional-guide.md — specific considerations for key regions (EU, US, APAC, LATAM)tools
Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C#, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter. Analyzes PRs for complexity and risk, checks code quality for SOLID violations and code smells, generates review reports. Use when reviewing pull requests, analyzing code quality, identifying issues, generating review checklists.
tools
Use when planning, funding, scoping, or synthesizing enterprise research across workstreams — clinical study design, R&D program finance, market sizing/surveys, or product/user research. Triggers on "design this clinical study", "what sample size", "R&D budget", "burn rate", "capitalize or expense", "TAM SAM SOM", "market sizing", "survey design", "segment the market", "plan user interviews", "usability test", "synthesize research insights". Forks context to route to one of four Research-Operations sub-skills (clinical-research, research-finance, market-research, product-research) and returns a digest. Distinct from ra-qm-team (regulatory submission), finance (corporate close/valuation), research/grants (funding discovery), product-team (persona/journey/live experiments), and marketing-skill (campaign analytics).
development
Use when managing the money for an internal R&D program or portfolio — building a multi-period program budget with the F&A (indirect) split, tracking burn rate and runway against value-inflection milestones, or routing R&D cost items to a capitalize-vs-expense determination. Every budget output surfaces its assumptions block; capitalize-vs-expense is decision-support only and routes to a named finance owner — it never books an entry or decides accounting treatment. Distinct from finance/financial-analysis (corporate DCF, close, valuation) and research/grants (funding discovery — this manages money already won).
development
Use when planning and synthesizing product/user research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation/sample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team/ux-researcher-designer (persona/journey artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A/B) — this is the research-ops method + insight-repository layer.