analyzing-international-expansion-plans
Evaluates geographic expansion strategies with market entry sequencing, localization requirements, and international unit economics. Use when analyzing expansion plans, assessing international readiness, or modeling geo-expansion costs.
Best use case
analyzing-international-expansion-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Evaluates geographic expansion strategies with market entry sequencing, localization requirements, and international unit economics. Use when analyzing expansion plans, assessing international readiness, or modeling geo-expansion costs.
Teams using analyzing-international-expansion-plans should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyzing-international-expansion-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyzing-international-expansion-plans Compares
| Feature / Agent | analyzing-international-expansion-plans | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Evaluates geographic expansion strategies with market entry sequencing, localization requirements, and international unit economics. Use when analyzing expansion plans, assessing international readiness, or modeling geo-expansion costs.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Analyzing International Expansion Plans ## When To Use - A portfolio company or investment target presents a geographic expansion roadmap and the deal team needs to stress-test sequencing, cost assumptions, and market selection logic. - Diligence requires assessing whether a company's domestic unit economics can translate internationally given localization, regulatory, and go-to-market differences. - Evaluating an expansion capital or growth equity deployment where proceeds are earmarked for new-market entry. - Benchmarking a company's international readiness against comparable SaaS, marketplace, or consumer companies that have scaled across geographies. ## Inputs To Gather - **Expansion roadmap**: Target markets, proposed sequencing, and stated rationale for market prioritization. - **Domestic unit economics**: CAC, LTV, payback period, gross margin, and contribution margin at the business-unit level. - **Market sizing by geography**: TAM/SAM estimates for each target market with methodology notes. - **Localization scope**: Product (language, payments, compliance features), go-to-market (local sales teams, channel partners, marketing), and operational (entity formation, hiring, warehousing). - **Regulatory and compliance requirements**: Data residency, licensing, sector-specific regulations per target market. [VERIFY] specific regulatory regimes for each jurisdiction. - **Competitive landscape per market**: Incumbent strength, local alternatives, and switching costs. - **Historical international performance** (if any): Revenue ramp, churn, and margin data from prior market entries. - **Budget and headcount plan**: Projected investment by market and function, with timeline to breakeven. ## Workflow 1. **Validate market selection logic** - Score each target market on TAM, competitive intensity, regulatory complexity, cultural/language distance, and existing customer demand signals. - Flag markets where the company's stated rationale relies on anecdotal evidence rather than quantitative indicators. - Compare prioritization against peer company expansion patterns (e.g., English-speaking markets first for SaaS, adjacent geographies for logistics). 2. **Stress-test entry sequencing** - Assess whether the proposed cadence (e.g., two markets per year) is realistic given management bandwidth, hiring timelines, and capital reserves. - Identify dependencies between markets (shared language clusters, regulatory harmonization zones like the EU, shared payment infrastructure). - Model the cash burn curve under the proposed sequence vs. a slower or reordered alternative. 3. **Rebuild international unit economics** - Adjust domestic CAC for local channel costs, brand awareness gaps, and sales cycle differences. Typical international CAC inflation runs 1.3–2.5x domestic for B2B SaaS. [VERIFY] against company-specific data. - Adjust LTV for expected differences in ARPU (currency, pricing power, contract norms) and churn (competitive dynamics, support quality). - Calculate payback period and contribution margin per market; flag any market where payback exceeds 24 months without a clear strategic rationale. 4. **Assess localization depth and cost** - Categorize localization into tiers: light (translation + currency), medium (local payment methods, compliance features, regional support), heavy (local entity, dedicated team, product re-architecture). - Map each target market to the required tier and estimate one-time and ongoing costs. - Identify product architecture blockers (e.g., multi-tenancy, data residency, multi-currency billing) that could delay or inflate costs. 5. **Evaluate organizational readiness** - Assess whether the company has international management experience on the leadership team. - Review hiring plans for local GMs, sales leads, and support staff; benchmark against companies at similar scale. - Identify operational gaps: legal entity setup timelines, tax structuring, transfer pricing, IP holding considerations. [VERIFY] entity formation requirements by jurisdiction. 6. **Synthesize risk-adjusted expansion scenario** - Build a base case, upside, and downside scenario for the expansion plan with explicit assumptions for each. - Quantify the total capital required under each scenario, including contingency buffers (typically 20–30% above management estimates for first-time international expansions). - Identify the top 3–5 risks that could derail the plan and propose monitoring triggers. ## Output Produce an **International Expansion Analysis** structured as: - **Executive Summary**: One-paragraph investment view on the expansion plan's feasibility and capital efficiency. - **Market Prioritization Scorecard**: Table ranking target markets across TAM, competitive position, regulatory complexity, localization cost, and strategic fit, with a composite score. - **International Unit Economics Model**: Side-by-side comparison of domestic vs. projected per-market CAC, LTV, payback, and contribution margin. - **Localization Requirements Matrix**: Market-by-market breakdown of product, GTM, and operational localization needs with cost estimates. - **Scenario Analysis**: Base/upside/downside projections for revenue ramp, cash burn, and time to market-level profitability. - **Key Risks and Monitoring Triggers**: Prioritized risk register with specific thresholds that would prompt plan revision. - **Recommendations**: Sequencing adjustments, markets to defer or accelerate, and investment structuring considerations (e.g., tranche funding tied to market-entry milestones). ## Quality Checks - Every market-level metric traces back to a stated source or is flagged with [VERIFY]. - Unit economics adjustments use explicit multipliers with stated rationale, not blanket assumptions. - Scenario analysis includes at least three cases with clearly differentiated assumptions. - Localization cost estimates distinguish one-time setup from recurring operational spend. - Recommendations are specific and actionable (name markets, quantify dollars, propose timelines) rather than directional platitudes. - Regulatory and tax considerations are flagged for specialist review rather than treated as resolved.