Skip to content
FunCoding

Search

Search docs, Skills and MCP

market-entry

Decides whether and how to enter a new market — sizing demand from the bottom up rather than from a market report, testing whether your advantage transfers, choosing between organic entry, partnership and acquisition, sequencing the operational and regulatory work that entry actually requires, and setting the criteria that would tell you to stop. Use this to evaluate a new geography, segment or vertical, pressure-test an entry plan, or work out why a launched market never reached scale.

测试2kplugins/corporate-strategy/skills/market-entry/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/cbrock84/headcount/market-entry/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Market entry

Entry decisions are usually made on the size of the opportunity and lost on the cost of serving it. The market was real; what was underestimated was everything required to operate there.

Size from the bottom up, then check it against the top down

A market report gives you a number that includes companies who will never buy from you. Build the estimate from countable things: how many organizations fit your profile, how many have the problem acutely, what they spend on it today, what share you could plausibly hold in a defined period.

Use a top-down figure only as a sanity check. If bottom-up and top-down differ by an order of magnitude, one of them contains an assumption nobody has stated, and finding it is the most valuable hour in the analysis.

Test whether the advantage actually transfers

The question is not whether the market is attractive — attractive markets are attractive to everyone, including incumbents already there. The question is what you have that wins.

Advantages transfer unevenly. Product capability usually transfers. Brand rarely does across geographies. Distribution and relationships almost never do. Cost structure may invert entirely. An entry justified by "we are strong in the adjacent market" needs to name the specific thing that carries over, and it is usually less than assumed.

Ask why the incumbent has not already done what you plan to do. Either they cannot, which is your advantage, or they have found it does not work, which is your warning.

Choose the entry mode against speed, control and reversibility

  • Organic — full control, slowest, and every local capability has to be built. Right when the advantage is the product and the market is reachable with your existing motion.
  • Partnership or distribution — fast and cheap, and you learn less. Right when local relationships are the barrier and you can accept less control of the customer relationship.
  • Acquisition — buys presence and capability immediately, at the highest price and with the integration risk. Right when time matters more than money and the target has something you cannot build quickly.

Ask what each mode costs to unwind. Organic entry can be stopped. A distribution agreement with a long term and exclusivity cannot, and a bad partner can foreclose the market for years.

Scope the operating cost honestly, including the parts that are not strategy

This is where entry plans are optimistic. Entity setup and tax registration, employment obligations, data residency and privacy regimes, sector licensing, payment methods and currency, local-language support hours, contract terms that differ from your standard, and localized documentation.

Each is individually manageable and collectively a program. Get someone who has actually operated in the market to review the list before committing, because the item you have not thought of is usually the expensive one.

Sequence for a real test, not for a full launch

Enter narrowly enough that failure is affordable and informative: one segment, one channel, a small number of reference customers. A full launch commits the spend before you know whether the thesis holds.

Define what you are trying to learn and what result would count as the thesis failing. Entry without a disconfirming condition becomes a market you stay in because you are already there.

Set the stopping criteria before you start

Write down what would have to be true by when, and what you will do if it is not. Markets rarely fail loudly; they underperform quietly while absorbing management attention that the core business was producing better returns on.

Review against the criteria on the date, not when someone finally raises it.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Size a market from a published figure without building it up from countable units.
  • Justify entry on an advantage nobody has named specifically.
  • Sign an exclusive distribution agreement before you understand the market.
  • Enter without a written condition that would tell you to stop.

Similar Skills

skill-creator
anthropics/skills180k

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Testing

ponytail-audit
DietrichGebert/ponytail158k

ponytail-audit

Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.

Testing

ponytail-audit
DietrichGebert/ponytail158k

ponytail-audit

Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.

Testing

ponytail-review
DietrichGebert/ponytail158k

ponytail-review

Quality review of a diff: bugs, security, real load, missing tests, speed, and what to delete. Each finding says what goes wrong and how to fix it.

Testing

ci-cd-and-automation
addyosmani/agent-skills103k

ci-cd-and-automation

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Testing

idea-refine
addyosmani/agent-skills103k

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

Testing