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)development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.