
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.
- Installs
- 61
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill market-research- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads market-research automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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)
- Build a simple landing page describing the problem you solve (use Lovable or Claude Code)
- Drive 100-200 visits via communities, social posts, or $100-200 in ads
- Measure: Signups / Visitors = interest rate
- 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:
- Direct competitors — Same solution, same audience (Basecamp vs. Asana)
- Indirect competitors — Different solution, same problem (spreadsheets vs. project tool)
- DIY / manual process — They do it by hand (Post-its, email threads)
- 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:
- Controls budget? If they need 3 levels of approval, you lose.
- Below "just expense it" threshold? ($50-100/mo for individuals, $500-1K for teams)
- Can adopt without IT? Self-serve SaaS with optional SSO wins.
- Low switching cost? If migration takes weeks, adoption stalls.
- 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
FAQ
What does the market-research 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.
How do I install market-research?
Run npx skills add https://github.com/whawkinsiv/solo-founder-skills --skill market-research in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/market-research/ (personal) or .claude/skills/market-research/ (project).
Which AI agents can use market-research?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is market-research safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains market-research?
It is published by whawkinsiv in whawkinsiv/solo-founder-skills. It has 61 recorded installs.
More from whawkinsiv/solo-founder-skills
accounting
whawkinsiv/solo-founder-skills
Use this skill when the user needs to set up bookkeeping, track revenue and expenses, prepare for taxes, choose accounting software, understand SaaS revenue recognition, or manage the financial operations of their bootstrapped business. Covers bookkeeping setup, tax preparation, accounting tools, and financial hygiene for solo founders.
secure
whawkinsiv/solo-founder-skills
Use this skill to find and fix the security holes that AI-built apps most often ship with: 'is my app secure,' 'security check,' 'check my app for security holes,' 'can users see each other's data,' 'did I leak my API keys,' or 'I'm worried about hackers.' Claude runs the audit on the codebase: exposed keys, data isolation between users, auth on every route, webhook signatures, rate and spend limits, and dependencies. Not for the full pre-launch checklist (use go-live) or for privacy policy and legal terms (use legal).
monitor
whawkinsiv/solo-founder-skills
Use this skill when the user needs to set up production monitoring, track app health, configure error alerts, or respond to incidents. Also use when the user says 'my app went down,' 'how do I know if something breaks,' 'set up alerts,' 'is my app healthy,' or 'I found out from a user that my site was down.' Covers error tracking, uptime monitoring, performance metrics, and incident response for SaaS applications.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。