Launch in any overseas market with a complete GTM playbook — market assessment, channel strategy, launch timeline, pricing localization, and 90-day execution...
--- name: Overseas Go-to-Market Launch Playbook description: Launch in any overseas market with a complete GTM playbook — market assessment, channel strategy, launch timeline, pricing localization, and 90-day execution plan. Go from "we should launch in X" to "here's the exact plan, budget, and timeline." --- # Overseas Go-to-Market Launch Playbook ## Overview An end-to-end descriptive launch planning framework for overseas market entry, aligning positioning, channels, content, partnerships, operations, and learning loops. This is a pure descriptive OpenClaw skill for overseas expansion planning. It provides frameworks, templates, checklists, decision criteria, and risk reminders. It does **not** execute code, call APIs, access the network, scrape websites, submit forms, make purchases, send messages, or perform any external action. ## When to Use Use this skill when the user needs structured help with overseas go-to-market launch playbook in a cross-border or international expansion context. Typical trigger phrases include: - overseas go to market - international launch plan - foreign market launch playbook - global GTM strategy - cross-border product launch ## Target Users Founders, country managers, growth leads, marketing leaders, and cross-functional launch teams. ## Inputs to Collect Ask for or infer the following context before producing the final framework: - Target market or list of candidate markets - Product, service, category, or business model - Current business stage and domestic traction, if any - Target customer segment and purchase context - Expansion goal, timeline, budget range, and constraints - Existing assets such as brand story, content, team, channels, customer data, or partners - Known risks, assumptions, compliance concerns, and decision deadlines If important inputs are missing, state the assumptions clearly and provide a version that can be refined later. ## Workflow 1. Define launch objective, target segment, market scope, offer, success metrics, budget, timeline, and cross-functional owners. 2. Check launch readiness across positioning, product localization, content, channel plan, support, payment, delivery, compliance review, and partner dependencies. 3. Build a phased launch plan covering pre-launch validation, soft launch, public launch, post-launch optimization, and scale decision. 4. Create a risk register for operational failure, cultural misread, channel underperformance, compliance delay, support overload, and reputation issues. 5. Run a post-launch learning review that converts market feedback into positioning, product, channel, and operations changes. ## Output Modules ### Launch objective and scope brief - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ### Market readiness checklist - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ### Channel and campaign plan - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ### Cross-functional launch timeline - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ### Risk and contingency plan - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ### Post-launch learning review - Purpose: turn the user's market context into a structured planning component. - Include: assumptions, recommended actions, decision criteria, and questions that require local validation. - Output style: concise tables, checklists, and bullet-point rationale rather than generic advice. ## Example Prompts Try these real-world scenarios to see what this skill can produce: **Prompt 1: Full GTM Launch Plan** > "We're a DTC sustainable fashion brand (US-based, $5M ARR) launching in South Korea. We have no local presence. Our US channels: Shopify + Instagram + influencer collabs. Korean market is different: Naver dominates, KakaoTalk for communication, and fashion trends move faster. Build the complete GTM launch plan with a 90-day roadmap." > → Output: Market opportunity assessment (TAM/SAM/SOM, competitive landscape, Korean fashion consumer profile), channel strategy (Naver Smart Store setup guide, KakaoTalk channel strategy, Korean influencer tier system — mega/macro/micro with cost estimates), pricing strategy (localized pricing with purchasing-power parity adjustment, Korean price-ending norms), launch timeline (90-day phased: pre-launch → soft launch → scale), budget estimate breakdown (setup, marketing, ops, contingency), success metrics and leading indicators, risk register (logistics, returns culture, competition response) **Prompt 2: B2B SaaS Market Entry** > "We're a $10M ARR DevOps tool company entering the DACH region (Germany, Austria, Switzerland). We have 2 enterprise customers from inbound but no go-to-market motion. Build a DACH GTM plan: direct sales + channel partners + events, with a focus on mid-market manufacturing companies." > → Output: DACH DevOps market sizing (TAM for mid-market manufacturing), buyer persona (German IT-Leiter, procurement process map), channel mix strategy (direct sales team profile + hiring plan, system integrator partner criteria and outreach, event strategy: Hannover Messe, it-sa), pricing localization (EUR pricing, German payment terms — 30-day vs 60-day norms), 12-month ramp plan (Q1: hire + partner recruiting, Q2: pipeline build, Q3: first deals, Q4: scale), pipeline model with conversion assumptions, localization checklist (website, sales collateral, contracts) **Prompt 3: Quick-Test Market Entry** > "We want to test the Canadian market for our meal-kit subscription service before committing to a full launch. We're US-based. Canada is similar but has different food regulations (bilingual labeling), different logistics, and lower population density. Build a 'lean launch' GTM plan — minimum viable launch with $50K budget." > → Output: Lean-market-entry framework (test city: Toronto, 3-month pilot), MVP launch scope (minimal product adaptation: 5 best-selling kits + bilingual packaging), logistics partner options, regulatory checklist (CFIA bilingual labeling, provincial differences), marketing plan (budget-constrained: Meta ads geo-targeted Toronto, micro-influencer seeding, PR outreach to Canadian food media), success criteria (pilot KPIs: 500 subscribers, 60% retention, <$80 CAC), go/no-go decision framework with thresholds, scale plan if pilot succeeds ## Getting Started 👋 **cb-go-to-market-launch-playbook installed!** I build complete launch plans for any market — from market sizing and channel strategy to 90-day execution timelines and budgets. Launch something: > "Build a GTM launch plan for [product/brand] entering [market]. Our home market is [home]. Budget: [$X]. Timeline: [Y months]." Describe what you're launching and where, and I'll give you the full playbook. ## Safety and Limitations Launch planning is strategic support only; legal, tax, employment, logistics, and regulated-market decisions need local expert review. Additional limitations: - No professional legal, tax, financial, medical, employment, investment, or compliance advice. - No guarantee of market success, conversion improvement, legal compliance, or platform acceptance. - Verify local laws, platform policies, consumer expectations, and current market facts with qualified professionals and reliable sources. - Avoid stereotyping cultures or users; treat all cultural observations as hypotheses requiring local validation. ## Acceptance Criteria - Produces a phased launch timeline - Aligns positioning, channels, content, and operations - Includes owner and dependency checkpoints - Defines risks and contingency actions - Adds post-launch learning metrics - Provides structured, market-aware outputs rather than generic overseas expansion advice. - Includes explicit assumptions, evidence gaps, and validation steps. - Stays pure descriptive with no code execution, API calls, browsing, network access, or external side effects.
don't have the plugin yet? install it then click "run inline in claude" again.