Overseas Expansion Framework
Activate when: user says 'we want to go global' or 'expand internationally', founder is choosing between opening a local office vs. going digital-first in a...
deciqAI
@deciqai
What This Skill Does
Strategic framework that helps founders choose between digital-first (Spirit) and entity-based (Physical) international expansion models. Guides users through a structured process to score their product, select the right mode, and stress-test their plan against common failure modes.
Replaces guesswork and expensive trial-and-error in international expansion by providing a systematic decision framework that prevents costly mode-selection mistakes.
When to Use It
- Decide whether to open a local office or go digital-first in a new country
- Score your product's physical vs. digital expansion signals using the 4-criteria matrix
- Stress-test a planned international expansion against the three most common failure modes
- Identify the validation trigger needed before committing to a physical entity
- Diagnose why a previous international expansion attempt failed
Install
$ openclaw skills install @deciqai/overseas-expansion-frameworkOverseas Expansion Framework
Overview
International expansion forks into two models: Spirit Expansion (精神出海) — product/IP travels digitally or via exported goods, no local presence required — and Physical Expansion (实体出海) — the company establishes entities, hires locally, and embeds operations in-market. Wrong mode selection is among the most expensive strategic errors in international growth. Related: second-order-thinking before mode selection · lean-startup for minimum viable expansion · pareto-principle to prioritize markets.
When to Use / When NOT
Use when: "we want to go global" without specifying mode · designing first international expansion (digital-first vs. entity-first) · investor asks whether overseas revenue is Spirit or Physical · diagnosing a past international expansion failure.
Do NOT use when: no home-market PMF (run pmf-crossing-the-chasm) · entity already operational · purely local service with no digital component · already have established presence in the target market.
Coaching Novices (Adaptive Front Door)
- Engine mode: concrete expansion case → run The Process directly.
- Coach mode: unfamiliar or no concrete case → guide step by step.
In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.
- Ask: "In 12 months, does your team in [target market] include local hires?" Name the implicit mode assumption.
- Check: does the product require local trust, local license, local logistics, or real-time local-language support? ≥2 yes → Physical likely; 0–1 → Spirit default.
- Introduce Spirit/Physical vocabulary using the mode the founder already implicitly holds.
[WAIT — do not advance until user responds]
- Map the 3 most common failure modes for the selected mode; stress-test the plan.
[WAIT — do not advance until user responds]
- Ask: "What would you need to see from Spirit before committing to Physical?" Surface the validation trigger gap as the key insight.
[WAIT — do not advance until user responds]
The Process
Stop-rule: If the product requires a local licensed entity to operate at all (financial services, healthcare, telecom), skip Steps 1–3 — Physical is mandatory; go directly to Step 4.
Step 1 — Score the product (0–4 Physical signals).
| Criteria | Spirit Signal | Physical Signal |
|---|---|---|
| Trust | Product/brand trust | Relationship trust via local people |
| Regulatory | None / passported | Local license or entity required |
| Distribution | Digital (app, web, API) | Physical (retail, logistics, field sales) |
| Customer service | Async / automated | Real-time, local language |
0–1 Physical → default Spirit. 3–4 → default Physical. 2 → deeper analysis required.
Step 2 — Select mode. Spirit: no local entity needed to generate revenue (SaaS, content, API, hardware via global platforms). Physical: local entity + headcount + licensing required. Hybrid: Spirit first to validate, Physical to scale — define the validation trigger before beginning.
Step 3 — Spirit Risk Audit (Spirit or Hybrid): assess platform dependency · brand localization · invisible regulatory creep · support gap · distribution assumption. Each "yes" → mitigation plan before launch.
Step 4 — Physical Pre-Expansion Checklist (12): local regulatory opinion · distribution validated · willingness-to-pay tested locally · talent plan · entity structure · transfer pricing · local banking · IP/trademark registered · local UX test · exit plan + wind-down cost · founder presence assessed · capital commitment with go/no-go trigger.
Step 5 — Validation trigger + review cadence. Define observable signals for (a) Spirit→Physical escalation, (b) Physical footprint expansion, (c) withdrawal. Set 90-day and 180-day review dates.
Output: Expansion Mode Decision Record
Company / Market / Product | Signal count: [0–4] | Mode: [Spirit/Physical/Hybrid] | Rationale | Validation trigger | Risk audit status | Capital: budget · ceiling · go/no-go · exit cost | Review: 90-day · 180-day · escalation · withdrawal triggers
→ Method in Action: Nintendo's Spirit-First, Physical-Second US Market Entry (1985)
Expansion Mode Packs
A Pack adds market-specific calibration: default mode bias, regulatory classification, key distribution channels, entity structure norms, checklist additions, Spirit-phase benchmarks. Existing: Southeast Asia (SaaS) — Spirit-friendly B2B SaaS, Physical for fintech/healthcare. Middle East (Consumer) — Physical preferred by enterprise, Spirit viable for consumer apps.
Applying It Well
- Mode selection precedes market selection — mode determines which markets are accessible at a given capital level.
- Spirit Expansion is not "doing nothing" — deliberate localization, distribution, and support are still required.
- Write the validation trigger before the Spirit phase; post-hoc triggers are subject to motivated reasoning.
- Physical Expansion costs are always underestimated 2–3×; items 7–12 of the checklist are consistently forgotten.
- Regulatory misread is the top Physical Expansion killer — local counsel opinion is non-negotiable; use
margin-of-safetyon timeline and cost.
→ Primary sources: references/sources.md
Common Rationalizations
[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.
| Fake Move | Reality |
|---|---|
| [D] "We need to be on the ground to really understand the market" | Spirit Expansion generates equally rich signal through user data and digital engagement — often faster and cheaper. |
| [D] "Our competitors have a physical office there, so we need one" | Their mode selection is not a prescription for yours. |
| [D] "Setting up an entity is cheap and easy" | Ongoing compliance, banking, payroll, and wind-down are the actual cost; items 7–12 of the checklist are consistently forgotten. |
| [D] "We'll hire a Country Manager and they'll figure it out" | Without a mode-matched strategy and pre-funded capital, a Country Manager spends 6 months on decisions the company should have made before hiring. |
| [D] "We got inbound — we should open an office" | Inbound is a Spirit validation signal, not a Physical trigger. |
| [D] "Spirit Expansion means we're not serious" | Nintendo's US entry — most successful consumer electronics expansion of the 20th century — was Spirit-first. |
| [D] "We'll figure out regulations once we're in the market" | Regulatory misread after entity establishment is among the most expensive international errors. |
| [D] "We can always pull out if it doesn't work" | Exit often costs 12–24 months of entity run-rate plus severance and compliance wind-down. |
| → Add [O] entries here after each real use — paste the actual failure pattern | What went wrong and why |
Red Flags / Verification
Red Flags: plan names activities without specifying mode · Physical plan has no go/no-go trigger or exit plan · validation trigger is "sufficient traction" not a specific metric · local knowledge is only a research report + 3-day site visit · capital commitment omits wind-down cost.
Verification:
- Product scored on all 4 criteria; Physical signal count documented
- Mode (Spirit / Physical / Hybrid) named with rationale; validation trigger written down before launch
- Spirit: 5 Risk Audit items assessed; mitigation for each "yes"
- Physical: all 12 checklist items answered — none deferred to post-entity
- Exit plan, wind-down cost, and 90-/180-day review dates documented
- Stop-rule applied: regulated market → Physical-required, Steps 1–3 skipped
Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/overseas-expansion-framework · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/overseas-expansion-framework.json
Top skills in this category
API Gateway
@byungkyuCall third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, run a query through a connected
Marketing Mode
@thesethroseMarketing Mode combines 23 comprehensive marketing skills covering strategy, psychology, content, SEO, conversion optimization, and paid growth. Use when users need marketing strategy, copywriting, SEO help, conversion optimization, paid advertising, or any marketing tactic.
Blogwatcher
@steipeteMonitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
Marketing Skills
@jchopard69Access 23 marketing modules offering checklists, frameworks, and ready-to-use deliverables for CRO, SEO, copywriting, analytics, launches, ads, and social me...
diagram-generator
@matthewyinGenerate and edit diagrams with the mcp-diagram-generator MCP server. Use this skill for new diagrams, existing .drawio/.mmd/.excalidraw edits, network topology, architecture, flowchart, swimlane, sequence, class, ER, and Excalidraw whiteboard work. Always use this skill when the user asks to draw,