market-researcher
Use this skill when sizing a market, analyzing competitors, designing customer surveys, segmenting audiences, or synthesizing research into market insights. Trigger phrases: 'size the market for', 'analyze our competitors', 'who is our target customer', 'design a survey to understand', 'TAM/SAM/SOM for'. Not for building financial models, writing pitch decks, or conducting UX usability research.
What this skill does
# Market Researcher
## Overview
This skill guides structured market research—from estimating market size using TAM/SAM/SOM through primary and secondary research design, customer segmentation, survey construction, and competitive landscape analysis. It turns ambiguous market questions into defensible, data-backed conclusions that inform strategic decisions about where to play and how to win.
## When to Use
- Sizing a new market opportunity before investing in product development
- Analyzing competitor strengths, weaknesses, and positioning
- Designing a customer survey to understand needs or validate assumptions
- Segmenting a customer base to find the most valuable groups
- Preparing market analysis for a pitch deck, board presentation, or strategic plan
- Understanding why customers choose or leave a product
## When NOT to Use
- Conducting usability testing or user interviews about product UX (use ux-researcher skill)
- Building detailed financial models or revenue projections (use a finance skill)
- Writing the full pitch deck (use pitch-deck-writer skill)
- Real-time social media monitoring or sentiment analysis
## Quick Reference
| Research Task | Method | Time Required |
|--------------|--------|---------------|
| Market sizing | TAM/SAM/SOM (top-down + bottom-up) | 2–8 hours |
| Competitor analysis | Framework + web research | 4–12 hours |
| Customer needs | 8–12 in-depth interviews | 2–3 weeks |
| Hypothesis validation | Survey (n=200+) | 1–2 weeks |
| Customer segmentation | Survey + cluster analysis | 2–4 weeks |
| Positioning map | Perception survey or desk research | 1–3 days |
| Secondary research | Reports, databases, news | 2–8 hours |
## Instructions
### Step 1: Define the Research Question
Before gathering data, write a single crisp research question:
- "What is the addressable market for AI-powered legal contract review in the US?"
- "Why do users cancel within 30 days of signing up for our product?"
- "How does our product compare to competitors on features and pricing?"
Then list 3–5 sub-questions that, if answered, would answer the main question.
### Step 2: Market Sizing — TAM / SAM / SOM
**Definitions:**
- **TAM** (Total Addressable Market): Total revenue available if you captured 100% of the market
- **SAM** (Serviceable Addressable Market): The portion you can realistically target given your business model, geography, and product
- **SOM** (Serviceable Obtainable Market): What you can realistically capture in 3–5 years
**Two approaches to triangulate:**
**Top-Down (use industry reports):**
```
TAM: Find total industry revenue from analyst reports (Gartner, IDC, Statista)
Example: "Global legal tech market: $29B (2024)" → TAM = $29B
SAM: Apply your segment filters
"AI-specific legal tech, US only, mid-to-large law firms" = 15% of global market
SAM = $29B × 15% = $4.4B
SOM: Apply your achievable market share
"Realistic 3% capture in 5 years" → SOM = $4.4B × 3% = $132M
```
**Bottom-Up (use unit economics):**
```
# Count the buyers × their spend
Target customers: US law firms with 50+ attorneys = 8,000 firms
Average annual contract value (ACV): $25,000
Total SAM = 8,000 × $25,000 = $200M/year
SOM: Win 500 firms in 5 years → 500 × $25,000 = $12.5M ARR
```
> **Best practice**: Use both approaches; if they're within 2× of each other, your estimate is credible. If they diverge more, investigate why.
**Data sources for market sizing:**
- Gartner, Forrester, IDC, Grand View Research (paid)
- Statista, IBISWorld (paid, often available via library)
- Census Bureau, BLS, SEC filings (free)
- LinkedIn Sales Navigator (estimate company counts)
- Crunchbase, PitchBook (funding and revenue signals)
- Job posting counts (proxy for company growth in a segment)
### Step 3: Primary vs Secondary Research
**Secondary research** (desk research — start here):
- Industry analyst reports (Gartner Magic Quadrant, Forrester Wave)
- Competitor websites, pricing pages, job postings, press releases
- App store reviews of competitor products
- Reddit, Twitter, G2, Capterra, Trustpilot — customer voice
- Government databases (Census, USPTO, SEC EDGAR)
- Academic papers, conference proceedings
**Primary research** (you collect — for validation and nuance):
| Method | Best For | Sample Size |
|--------|----------|-------------|
| In-depth interviews | Deep understanding of motivations | 8–15 |
| Online surveys | Quantifying preferences, segmentation | 200–1,000+ |
| Focus groups | Concept testing, early ideation | 2 groups of 6–8 |
| Observational/ethnography | Understanding actual behavior | 5–10 sessions |
| A/B tests | Validating specific hypotheses | 1,000+ per variant |
### Step 4: Survey Design
A good survey:
1. Takes < 10 minutes (15 questions max)
2. Asks one thing per question
3. Progresses from general to specific
4. Uses consistent rating scales (always 1–5 or always 1–7; never mix)
5. Ends with demographics and open-ended "anything else?"
**Question type guide:**
- **Multiple choice (single)**: When answers are mutually exclusive ("Which best describes your role?")
- **Multiple choice (multi-select)**: "Which of these tools do you use?" (check all that apply)
- **Likert 1–5**: Agreement, satisfaction, frequency
- **Ranking**: "Rank these features from most to least important" (max 5 items)
- **NPS (0–10)**: "How likely are you to recommend us?"
- **Open-ended**: "What is the biggest challenge you face with X?" (use sparingly, 1–2 max)
**Sample survey structure:**
```
Section 1: Screener (1–2 questions to qualify respondents)
Section 2: Current behavior and pain (3–4 questions)
Section 3: Product/solution fit (3–4 questions)
Section 4: Competitive usage and preferences (2–3 questions)
Section 5: Willingness to pay / pricing (1–2 questions)
Section 6: Demographics (2–3 questions)
```
### Step 5: Customer Segmentation
Segment your market on dimensions that predict purchase behavior:
**B2B segmentation dimensions:**
- Company size (employees, revenue)
- Industry vertical
- Geography
- Tech stack / sophistication
- Buying process (self-serve vs sales-led)
- Use case (primary job to be done)
**B2C segmentation dimensions:**
- Demographics (age, income, education)
- Psychographics (values, lifestyle, attitudes)
- Behavioral (usage frequency, purchase history, NPS)
- Geography
**Segmentation output template:**
| Segment | Size | Description | Primary Need | Channel | ACV |
|---------|------|-------------|-------------|---------|-----|
| Enterprise Legal | 2,000 firms | 500+ attorneys, dedicated IT | Compliance automation | Sales-led | $80K |
| Mid-Market Legal | 6,000 firms | 50–500 attorneys, cost-sensitive | Time savings | PLG + inside sales | $20K |
| Solo/Small Firm | 50,000 firms | <50 attorneys, price-sensitive | Affordable AI assistance | Self-serve | $2K |
### Step 6: Competitive Landscape Analysis
Analyze 5–8 direct and indirect competitors across:
**Feature matrix:**
| Feature | Your Product | Competitor A | Competitor B | Competitor C |
|---------|-------------|-------------|-------------|-------------|
| Feature 1 | ✅ | ✅ | ❌ | ✅ |
| Feature 2 | ✅ | ❌ | ✅ | ❌ |
| Pricing | $X/mo | $Y/mo | $Z/mo | $W/mo |
| Target segment | Mid-market | Enterprise | SMB | Mid-market |
**Positioning map** (2×2 matrix with two dimensions):
- X-axis: Price (budget → premium)
- Y-axis: Ease of use (complex → simple)
- Plot each competitor as a dot; find whitespace = your opportunity
**SWOT analysis per competitor:**
- S: What do they do best? (customer reviews, investor narratives)
- W: Where do they fall short? (negative reviews, high churn signals)
- O: What market trends help them?
- T: What could hurt them (you, regulation, substitutes)?
## Examples
### Example 1: Size the US Online Education Market
**Research question:** What is the market size for AI-powered corporate learning platforms in the US?
**Top-down approach:**
```
Global corporate e-learning market (2024): $50B (Grand View Research)
US share: Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.