Intl Expansion

v2.1.1

International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding t...

0· 383·3 current·3 all-time
byAlireza Rezvani@alirezarezvani
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (international market expansion) matches the included materials (selection frameworks, entry playbooks, regional guides). There are no extraneous requirements (no env vars, no binaries) that would be unrelated to the stated purpose.
Instruction Scope
SKILL.md and the two reference documents are textual strategy checklists and timelines. They do not instruct the agent to read local files, access environment variables, call external endpoints, or collect/transmit user data. All runtime instructions are advisory and stay within the domain of market strategy.
Install Mechanism
No install spec and no code files: this is instruction-only. Nothing will be downloaded or written to disk by installation, which minimizes supply-chain risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. There is no request for secrets or unrelated service tokens; the required access is proportionate (none) to the strategy purpose.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent presence or modify other skills. Autonomous invocation is allowed by default but not combined with any privileged actions or credentials.
Assessment
This skill appears to be a plain-text market-expansion playbook and is internally consistent with its description: it asks for nothing and installs nothing. Before using, consider that the guidance is generic — verify regulatory, tax, and legal points with qualified counsel for your specific product and jurisdictions. Also remember that, although the skill itself is harmless, an autonomous agent using it could act on its recommendations; ensure any agent actions (contracts, payments, entity formation) require human approval.

Like a lobster shell, security has layers — review code before you run it.

latestvk97914v8h9tqt1mc80e2sx9fax82qzvn
383downloads
0stars
2versions
Updated 1mo ago
v2.1.1
MIT-0

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

FactorWeightHow to Assess
Market size (addressable)25%TAM in target segment, willingness to pay
Competitive intensity20%Incumbent strength, market gaps
Regulatory complexity20%Barriers to entry, compliance cost, timeline
Cultural distance15%Language, business practices, buying behavior
Existing traction10%Inbound demand, existing customers, partnerships
Operational complexity10%Time zones, infrastructure, payment systems

Entry Modes

ModeInvestmentControlRiskBest For
Export (sell remotely)LowLowLowTesting demand
Partnership (reseller/distributor)MediumMediumMediumMarkets with strong local requirements
Local team (hire in-market)HighHighHighStrategic markets with proven demand
Entity (full subsidiary)Very highFullHighMajor markets, regulatory requirement
AcquisitionHighestFullHighestFast 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

MistakeWhy It HappensPrevention
Entering too many markets at onceFOMO, board pressureMax 1-2 new markets per year
Copy-paste GTM from home marketAssuming buyers are the sameResearch local buying behavior
Underestimating regulatory cost"We'll figure it out"Regulatory assessment BEFORE committing
Hiring too earlyOptimismProve demand before hiring local team
Wrong pricing (just converting)LazinessResearch willingness to pay locally

Integration with C-Suite Roles

RoleContribution
CEOMarket selection, strategic commitment
CFOInvestment sizing, ROI modeling, entity structure
CRORevenue targets, sales model adaptation
CMOPositioning, channel strategy, local brand
CPOLocalization roadmap, feature priorities
CTOInfrastructure, data residency, scaling
CHROLocal hiring, employment law, comp
COOOperations 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)

Comments

Loading comments...