market-research

Use this skill when the user needs to size a market, analyze competitors, calculate TAM/SAM/SOM, or validate a business idea. Covers market sizing, competitive analysis frameworks, napkin math, and bottom-up revenue estimation.

157 stars

Best use case

market-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use this skill when the user needs to size a market, analyze competitors, calculate TAM/SAM/SOM, or validate a business idea. Covers market sizing, competitive analysis frameworks, napkin math, and bottom-up revenue estimation.

Teams using market-research should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/market-research/SKILL.md --create-dirs "https://raw.githubusercontent.com/whawkinsiv/solo-founder-superpowers/main/skills/market-research/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/market-research/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How market-research Compares

Feature / Agentmarket-researchStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use this skill when the user needs to size a market, analyze competitors, calculate TAM/SAM/SOM, or validate a business idea. Covers market sizing, competitive analysis frameworks, napkin math, and bottom-up revenue estimation.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Market Research & Competitive Analysis

Markets matter more than ideas. This skill helps you evaluate whether your market is worth entering — and how to validate demand before you build.

## Core Principles

- A mediocre product in a great market beats a brilliant product in a dead one.
- All market sizing is wrong. The goal is order-of-magnitude clarity, not decimal precision.
- Competitors are evidence that demand exists. Zero competitors is a warning sign, not an advantage.
- The best solo-founder markets have high pain, fragmented incumbents, and willingness to pay — not the biggest TAM.
- Research is only useful if it changes a decision. Every analysis should end with a clear recommendation.

---

## Early Validation: Before You Build Anything

### Finding Your First 10 People to Talk To

Before doing market sizing, validate that real people have this problem.

**Method 1: Cold Outreach (Fastest — 1-2 weeks)**
- LinkedIn: Search for your ICP's job title → send connection request with a note
- Twitter/X: Search hashtags related to the problem → DM active posters
- Reddit: Find niche subreddits → comment helpfully → DM engaged users
- Email: Find company websites of target customers → reach out to founders/decision-makers

**Cold outreach template:**
```
Subject: Quick question about [problem area]

Hi [Name],

I'm researching how [ICP role] handles [specific problem]. I noticed you [signal that they have this problem — e.g., posted about it, work in relevant role, use a competing tool].

Would you be open to a 15-minute call this week? I'm not selling anything — just trying to understand the problem better before I build a solution.

Happy to share what I learn from the research as a thank you.

[Your name]
```

**Method 2: Communities (Higher quality — 2-4 weeks)**
- Indie Hackers: Search for threads where your ICP discusses the problem
- Facebook Groups: Search for niche groups (e.g., "Freelance Copywriters", "SaaS Founders")
- Slack communities: Industry-specific channels, FounderPath, etc.
- Discord: More engaged than most channels for technical audiences

**Method 3: Landing Page Test (Lowest effort — 2-3 weeks)**
1. Build a simple landing page describing the problem you solve (use Lovable or Claude Code)
2. Drive 100-200 visits via communities, social posts, or $100-200 in ads
3. Measure: Signups / Visitors = interest rate
4. Below 5% signup rate → positioning is unclear or demand is weak

### After 5 Conversations, Ask Yourself

- Did 3+ people independently describe the same pain? → Demand likely real
- Would they pay? Did anyone name a price unprompted? → Market likely exists
- Do they already use 2+ workarounds? → Problem is acute
- Did you learn something that surprised you? → Explore it in conversations 6-10

**Decision threshold:**
- 3+ people confirm the problem AND 2+ say they'd pay → proceed to market sizing and build
- Mixed signals after 10 conversations → either pivot your hypothesis or try a different ICP segment
- Nobody cares after 10 conversations → this isn't a real problem. Pick a different idea.

### Avoiding Analysis Paralysis

5 conversations reveal 80% of what you need to know. The other 20% you learn by building and shipping. Don't wait for certainty — it never comes.

---

## Market Sizing (Napkin Math That Matters)

**Tell AI:**
```
Help me size the market for my SaaS idea:
- Product: [what it does]
- Target customer: [who — job title, company size, industry]
- Problem it solves: [the pain point]

Do a bottom-up calculation:
1. Estimate how many potential buyers exist (use industry data, LinkedIn job title counts)
2. Multiply by a realistic price point for this type of tool
3. Apply a 1-3% capture rate for a new entrant
4. Tell me: does this math support a solo-founder business ($200K-500K ARR)?
```

### Bottom-Up (The Only Method That Matters for Solo Founders)

```
1. How many potential buyers exist?
   [Industry size] × [% that match your ICP]
   Example: 500,000 US marketing agencies × 12% that are 5-20 person = 60,000

2. What will each pay annually?
   [Price point] × [12 months]
   Example: $49/month × 12 = $588/year

3. Realistic addressable market:
   [Buyers] × [Annual price] × [Capture rate]
   Example: 60,000 × $588 × 2% = $705,600/year achievable

4. Sanity check: Does that number fund the business you want?
   Solo founder needs $200K-$500K ARR to replace income + reinvest.
   If max realistic capture is $100K, the market is too small.
```

### Top-Down (Sanity Check Only)

```
TAM = Total market revenue (all possible buyers globally)
SAM = Segment you can serve (geography, vertical, size)
SOM = What you can realistically capture in 3 years

Rule of thumb: SOM is 1-5% of SAM for a new entrant.
If SOM doesn't fund your business, stop here.
```

### Volume Estimation Sources

- Government data: Census Bureau, BLS (industry counts)
- Industry reports: IBISWorld, Statista (skim free summaries)
- LinkedIn: Search ICP job titles → count results
- Job boards: Volume of relevant roles = proxy for market size
- Competitor traffic: SimilarWeb free tier → estimate active users
- Subreddits/communities: Member counts = demand signal

---

## Competitive Analysis

**Tell AI:**
```
Analyze the competitive landscape for my product:
- My product: [what it does]
- My target customer: [who]
- Known competitors: [list any you know, or "not sure"]

For each competitor, find: pricing, target audience, strengths, weaknesses
(check G2/Capterra reviews for complaints). Then build a 2x2 positioning
matrix showing where I could differentiate.
```

### Substitute Mapping

Every product competes with four types:

1. **Direct competitors** — Same solution, same audience (Basecamp vs. Asana)
2. **Indirect competitors** — Different solution, same problem (spreadsheets vs. project tool)
3. **DIY / manual process** — They do it by hand (Post-its, email threads)
4. **Do nothing** — They tolerate the pain (this is your real enemy)

### Competitor Research Template

For each direct competitor:

```
## [Competitor Name]

**What they do**: One sentence.
**Target audience**: Who they sell to.
**Pricing**: Tiers and price points.
**Strengths**: 2-3 things they do well.
**Weaknesses**: 2-3 gaps, complaints, or underserved areas.
**Positioning**: Homepage headline — how they describe themselves.
**Traffic/Scale**: Monthly visits (SimilarWeb), review count (G2/Capterra).

### Where You Win
What specific thing will you do 10x better?
```

### Research Sources

- **Pricing**: Visit their pricing page. Screenshot it.
- **Positioning**: Read their homepage headline and subheadline.
- **Weaknesses**: G2, Capterra, Product Hunt, Reddit threads, Twitter complaints.
- **Traffic**: SimilarWeb (free tier).
- **Features**: Their docs/changelog reveal what they've built and haven't.
- **Hiring**: Job postings reveal strategic direction.

### Competitive Positioning Matrix

Build a 2×2 matrix with the two dimensions your ICP cares most about:

```
Example axes:
  X: Simple ←————→ Powerful
  Y: Cheap  ←————→ Premium

Plot competitors on this grid. Find the empty quadrant. That's your positioning opportunity.
```

---

## Solo-Founder Market Fit Assessment

Score each criterion 1-5. Minimum viable total: 25/40.

| Criterion | Score | Notes |
|-----------|-------|-------|
| **Pain intensity** — Hair-on-fire problem? | /5 | 5 = actively searching for a fix |
| **Willingness to pay** — Already pay for substitutes? | /5 | 5 = pay $50+/mo for something worse |
| **Reachable audience** — Can you find and contact them? | /5 | 5 = concentrated in known communities |
| **Fragmented competition** — No dominant monopoly? | /5 | 5 = many small players, no clear winner |
| **Small enough for solo** — Can one person serve this? | /5 | 5 = low support burden, self-serve viable |
| **Recurring need** — Will they use it monthly? | /5 | 5 = daily/weekly active use |
| **Your unfair advantage** — Domain expertise or distribution? | /5 | 5 = deep insider knowledge |
| **Technical feasibility** — Build core in 4-8 weeks? | /5 | 5 = well-understood, no R&D needed |

**Scoring:**
- 35-40: Exceptional fit. Move fast.
- 25-34: Viable. Validate the weak spots.
- Below 25: Reconsider. Weak markets kill good products.

---

## Distribution Vector Analysis

| Channel | Cost to Test | Time to Signal | Scalable? |
|---------|-------------|----------------|-----------|
| Cold outreach | $0 (time only) | 2-4 weeks | Somewhat |
| Communities | $0 (time only) | 1-3 months | Somewhat |
| Paid search | $200-500 | 1-2 weeks | Yes (if CAC works) |
| SEO / Content | $0 (time only) | 3-6 months | Yes |
| Directories | $0-200 | 1-2 months | Yes (passive) |
| Partnerships | $0 (time only) | 2-6 months | Yes |

**Rule:** Pick the ONE channel you can test in <30 days with <$500. Prove it works before diversifying.

---

## Buyer Leverage Check

Confirm your ICP can actually buy:

1. **Controls budget?** If they need 3 levels of approval, you lose.
2. **Below "just expense it" threshold?** ($50-100/mo for individuals, $500-1K for teams)
3. **Can adopt without IT?** Self-serve SaaS with optional SSO wins.
4. **Low switching cost?** If migration takes weeks, adoption stalls.
5. **One person gets value alone?** Network effects help growth but hurt initial adoption.

All five should be "yes" for a solo-founder SaaS.

---

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Analysis paralysis — researching for months instead of shipping | 5 conversations + napkin math. Then build. |
| Inflating TAM to feel good ("it's a $10B market!") | Bottom-up only. TAM is a vanity metric for solo founders. |
| Ignoring "do nothing" as a competitor | Most of your market tolerates the pain. Your real competition is inertia. |
| Researching the wrong ICP | Talk to the person who writes the check, not the person who has the problem. |
| Only talking to people who confirm your idea | Seek disconfirming evidence. Ask "why wouldn't you use this?" |
| Skipping competitive pricing research | Visit every competitor's pricing page. Screenshot them. This is your anchor. |

---

## Related Skills

- **validate** — Test demand after market research confirms opportunity
- **customer-research** — Go deeper with customer interviews and personas
- **prioritize** — Use market research to prioritize what to build
- **pricing** — Use competitive analysis to inform pricing decisions

Related Skills

customer-research

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to understand their customers, create personas, conduct user interviews, apply the Jobs-to-be-Done framework, or create an ideal customer profile. Also use when the user says 'ICP,' 'ideal customer,' 'who is my customer,' 'customer profile,' or 'target audience.' Covers JTBD methodology, behavioral personas, interview techniques, and creates MY-ICP.md — a reference file that other skills use to personalize copy with customer language.

validate

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.

ux-design

157
from whawkinsiv/solo-founder-superpowers

Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.

ui-patterns

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.

translate

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.

test

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.

technical-seo

157
from whawkinsiv/solo-founder-superpowers

Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.

support

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.

social-media

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.

seo

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.

seo-content

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.

seo-audit

157
from whawkinsiv/solo-founder-superpowers

Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.