intl-expansion
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.
What this skill does
# International Expansion Frameworks for expanding into new markets: selection, entry, localization, and execution. ## Keywords international expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion ## Quick Start **Decision sequence:** Market selection → Entry mode → Regulatory assessment → Localization plan → GTM strategy → Team structure → Launch. ## Market Selection Framework ### Scoring Matrix | 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 | ### Entry Modes | 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). ## Localization Checklist ### Product - [ ] Language (UI, documentation, support content) - [ ] Currency and pricing (local pricing, not just conversion) - [ ] Payment methods (varies wildly by market) - [ ] Date/time/number formats - [ ] Legal requirements (data residency, privacy) - [ ] Cultural adaptation (not just translation) ### Go-to-Market - [ ] Messaging adaptation (what resonates locally) - [ ] Channel strategy (channels differ by market) - [ ] Local case studies and social proof - [ ] Local partnerships and integrations - [ ] Event/conference presence - [ ] Local SEO and content ### Operations - [ ] Legal entity (if required) - [ ] Tax compliance - [ ] Employment law (if hiring locally) - [ ] Customer support (hours, language) - [ ] Banking and payments ## Key Questions - "Is there pull from the market, or are we pushing?" - "What's the cost of entry vs the 3-year revenue opportunity?" - "Can we serve this market from HQ, or do we need boots on the ground?" - "What's the regulatory timeline? Can we launch before the paperwork is done?" - "Who's winning in this market and what would it take to displace them?" ## Common Mistakes | 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 | ## Integration with C-Suite Roles | 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 | ## Resources - `references/market-entry-playbook.md` — detailed entry playbook by market type - `references/regional-guide.md` — specific considerations for key regions (EU, US, APAC, LATAM)
Related 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.