mcpField
M
market-research

market-research

github.com/c0x12cMarketing & growth110109 installsUpdated 19w ago
Repository

About market-research

A market-research skill for founders and teams evaluating markets, companies, investors, competitors, and technology. It structures evidence, risks, caveats, and next steps into decision-oriented research.

Key features

  1. 01Research type selection
  2. 02Investor and fund checks
  3. 03Competitor analysis
  4. 04Market sizing
  5. 05Technology and tool research
  6. 06Source and risk guidelines

Use cases

  1. 01Estimating TAM/SAM/SOM
  2. 02Comparing competitors before building
  3. 03Checking investor fit before outreach
  4. 04Evaluating a technology or tool

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/c0x12c/ai-toolkit --skill market-research

After installing, type/market-researchin Claude Code to confirm it loaded.

Details

From the project README

Market Research

Make research that helps decisions, not research for show.

When to Use

  • Researching a market, company, investor, or tech trend
  • Building TAM/SAM/SOM numbers
  • Comparing competitors
  • Checking investor fit before outreach
  • Testing a thesis before building

Process

1. Pick the Research Type

Figure out which kind of research the user needs:

  • Investor / Fund Check
  • Competitor Check
  • Market Size
  • Tech / Tool Research
2. Run Investor / Fund Check

Get:

  • Fund size, stage, check size
  • Portfolio companies that matter
  • Public thesis and recent deals
  • Why they fit or don't fit
  • Red flags
3. Run Competitor Check

Get:

  • What the product really does (not marketing fluff)
  • Funding and investors
  • Traction if public
  • How they get users and what they charge
  • Strengths, weaknesses, gaps
4. Run Market Size

Use:

  • Top-down from reports
  • Bottom-up from real customer numbers
  • Show your math. Every guess should be clear.
5. Run Tech / Tool Research

Get:

  • How it works
  • Trade-offs and who's using it
  • How hard to set up
  • Lock-in, security, and risk
6. Write It Up

Structure every deliverable as:

  1. Quick summary (2-3 sentences)
  2. Key findings
  3. What this means
  4. Risks and caveats
  5. What to do next
  6. Sources

Rules

  • Every big claim needs a source.
  • Use recent data. Flag old data.
  • Include the bad news too. Show risks.
  • End with a decision, not just a summary.
  • Keep facts, guesses, and suggestions separate.
  • All numbers have sources or are marked as guesses.
  • Old data is flagged.
  • The suggestion follows from the facts.
  • Someone can make a decision from this.

Gotchas

  • Top-down TAM is lazy and always wrong. "10% of the $X billion market" is not analysis. Bottom-up from real customer numbers or go home.
  • Analyst reports have built-in bias. Reports from vendors (like AWS sizing the cloud market) overstate their own segment. Use independent sources.
  • Revenue proxies are unreliable. SimilarWeb traffic estimates can be off by 5x. Combine multiple signals: hiring, social, Crunchbase, app store rankings.
  • Don't confuse market size with addressable market. The CRM market is $80B, but if you're building for freelancers, your market is a fraction of that.
  • Recency matters. A market growing 40% in 2024 might be flat in 2026. Always check the latest data points, not just the headline number.

Output

Save to the project's 02-research/ folder.

Format each deliverable with: quick summary, key findings, what this means, risks and caveats, next steps, and sources.

Comments

Markdown supported