Systematic market analysis skill for understanding market size, segmentation, trends, and opportunities. Produces quantified market intelligence.
Conducts systematic market analysis to quantify size, segmentation, trends, and opportunities.
/plugin marketplace add lerianstudio/ring/plugin install ring-pmm-team@ringThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Systematic market analysis to understand size, segmentation, trends, and opportunities.
Market analysis provides the foundation for ALL subsequent PMM activities:
HARD GATE: Do NOT proceed to positioning or messaging without market analysis.
Define the market boundaries:
## Market Definition
**Product/Feature:** [What you're analyzing]
**Market Category:** [Existing category or new category creation]
**Geographic Scope:** [Global, regional, specific countries]
**Time Horizon:** [Current, 1-3 years, 5+ years]
### Market Boundaries
- **Included:** [What's in scope]
- **Excluded:** [What's explicitly out of scope]
- **Adjacent Markets:** [Related but distinct markets]
Quantify the market opportunity:
## Market Sizing
### Total Addressable Market (TAM)
**Definition:** Total market demand if 100% market share
**Size:** $X billion
**Calculation Method:** [Top-down/Bottom-up/Value theory]
**Sources:** [List data sources]
### Serviceable Addressable Market (SAM)
**Definition:** Portion of TAM you can actually serve
**Size:** $X million
**Limiting Factors:**
- Geographic: [Regions you can serve]
- Technical: [Segments your product can address]
- Go-to-market: [Segments you can reach]
### Serviceable Obtainable Market (SOM)
**Definition:** Realistic market share in 1-3 years
**Size:** $X million
**Assumptions:**
- Market share: X%
- Growth rate: X%
- Competitive dynamics: [Key assumptions]
Identify distinct market segments:
## Market Segmentation
### Segment 1: [Name]
**Size:** $X million (X% of SAM)
**Characteristics:**
- Company size: [Range]
- Industry: [Verticals]
- Pain points: [Top 3 pain points]
- Buying behavior: [How they buy]
**Attractiveness:** HIGH/MEDIUM/LOW
**Fit Score:** X/10
**Priority:** PRIMARY/SECONDARY/TERTIARY
### Segment 2: [Name]
[Repeat structure]
Analyze market dynamics:
## Market Trends
### Growth Drivers
| Driver | Impact | Timeline | Confidence |
|--------|--------|----------|------------|
| [Trend 1] | HIGH/MEDIUM/LOW | Near/Mid/Long | HIGH/MEDIUM/LOW |
| [Trend 2] | ... | ... | ... |
### Headwinds
| Challenge | Impact | Mitigation |
|-----------|--------|------------|
| [Challenge 1] | HIGH/MEDIUM/LOW | [How to address] |
| [Challenge 2] | ... | ... |
### Technology Trends
- [Emerging tech affecting market]
- [Adoption curves]
- [Disruption potential]
### Regulatory Trends
- [Current regulations]
- [Expected changes]
- [Compliance requirements]
Understand the target customer:
## Customer Analysis
### Ideal Customer Profile (ICP)
**Company Characteristics:**
- Size: [Employee count, revenue]
- Industry: [Verticals]
- Geography: [Regions]
- Tech stack: [Required technologies]
- Maturity: [Growth stage]
**Behavioral Indicators:**
- [Signal that indicates fit]
- [Signal that indicates readiness to buy]
### Buyer Personas
**Primary Buyer: [Title]**
- Role: [Responsibilities]
- Goals: [What they want to achieve]
- Pain points: [What keeps them up at night]
- Success metrics: [How they're measured]
- Objections: [Common concerns]
**Economic Buyer: [Title]**
[Repeat structure]
**Technical Evaluator: [Title]**
[Repeat structure]
# Market Analysis: [Product/Feature]
## Executive Summary
- **Market Size:** $X SAM, $X SOM
- **Growth Rate:** X% CAGR
- **Key Segments:** [Top 3 segments]
- **Primary Opportunity:** [One sentence]
- **Key Risk:** [One sentence]
## Market Definition
[Phase 1 output]
## Market Sizing
[Phase 2 output]
## Segmentation
[Phase 3 output]
## Trends
[Phase 4 output]
## Customer Analysis
[Phase 5 output]
## Recommendations
1. **Target Segment:** [Primary segment to pursue]
2. **Positioning Implications:** [What this means for positioning]
3. **GTM Implications:** [What this means for go-to-market]
4. **Risks to Monitor:** [Key uncertainties]
## Sources
- [Source 1]
- [Source 2]
| Blocker | Action |
|---|---|
| No TAM data available | STOP. Define methodology and assumptions. Request validation. |
| Market definition unclear | STOP. Clarify boundaries before sizing. |
| Conflicting market data | STOP. Document sources. Recommend reconciliation approach. |
| No ICP definition | STOP. Cannot proceed without target customer clarity. |
See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
| Rationalization | Why It's WRONG | Required Action |
|---|---|---|
| "TAM is just a big number game" | TAM informs investment decisions and positioning scope | Calculate with methodology and sources |
| "Segmentation is obvious" | Obvious segments miss nuanced opportunities | Analyze systematically |
| "User knows their market" | User knowledge + analysis > either alone | Augment with structured research |
| "Market data is stale" | Stale data + analysis > no data | Document recency, proceed with caveats |
See shared-patterns/pressure-resistance.md for universal pressure scenarios.
| Pressure Type | Request | Agent Response |
|---|---|---|
| "Skip to positioning" | "We know the market, just position" | "Positioning without market analysis is guessing. Completing market analysis." |
| "Use competitor's TAM" | "Just use what [competitor] published" | "Competitor TAM serves their narrative. Calculating independent estimate." |
| "Rough estimate is fine" | "Just ballpark it" | "Ballpark estimates cause bad decisions. Providing methodology-backed estimate." |
Base metrics per shared-patterns/execution-report.md:
| Metric | Value |
|---|---|
| Duration | Xm Ys |
| Iterations | N |
| Result | PASS/FAIL/PARTIAL |
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.