skills/market-researcher/SKILL.md
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.
npx skillsauth add nickcrew/claude-cortex market-researcherInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
| 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 |
Before gathering data, write a single crisp research question:
Then list 3–5 sub-questions that, if answered, would answer the main question.
Definitions:
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:
Secondary research (desk research — start here):
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 |
A good survey:
Question type guide:
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)
Segment your market on dimensions that predict purchase behavior:
B2B segmentation dimensions:
B2C segmentation dimensions:
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 |
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):
SWOT analysis per competitor:
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: ~35% → $17.5B US market
AI-enhanced segment: ~20% of corporate e-learning → $3.5B SAM
Target: Mid-to-large enterprises (1,000+ employees) = 40% of market → $1.4B
Realistic 4-year market capture at 2% = $28M ARR
Bottom-up approach:
US companies with 1,000+ employees: ~19,000 (BLS data)
Estimated 25% currently buying L&D platforms: 4,750 companies
Average L&D platform spend: $80K/year
Total SAM: 4,750 × $80K = $380M (conservative; AI premium not modeled)
SOM at 1.5% capture: ~70 companies → $5.6M ARR in Year 3
Synthesis: Top-down gives $28M, bottom-up gives $5.6M—roughly a 5× gap. Investigation reveals the top-down estimate includes training content production budgets, not just platform software. Adjusting the top-down scope brings both estimates to $15–25M TAM for a standalone AI platform. Credible SOM: $5–10M ARR by Year 4.
Research question: How does our new project management tool compare to Asana, Monday.com, and Linear?
Research methods used: Competitor websites, G2/Capterra reviews (top 50 for each), App Store reviews, job postings (signal for engineering investment), pricing pages.
Findings summary:
| Dimension | Our Tool | Asana | Monday.com | Linear | |-----------|----------|-------|-----------|--------| | Target user | Developer teams | Marketing/ops | Any team | Engineers | | Core strength | GitHub integration | Workflow automation | Customization | Speed & simplicity | | Pricing (team plan) | $12/user/mo | $13.49/user/mo | $12/user/mo | $8/user/mo | | Key complaint (G2) | "Missing Gantt view" | "Too complex" | "Expensive at scale" | "Too dev-focused" | | AI features | ✅ native | ⚠️ limited | ⚠️ limited | ❌ |
Positioning gap identified: No competitor strongly serves mixed teams (engineering + product + design) with deep GitHub integration + non-developer accessibility. This is the whitespace.
Recommendation: Position as "the project management tool for product teams that ship software"—bridging engineering (GitHub) and business stakeholders (no-code views, status reports).
development
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
development
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
development
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
tools
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.