market-gap-analysis
Analyze market positioning, identify underserved segments, and map competitive gaps using systematic frameworks. Covers SWOT analysis, competitive landscape mapping, opportunity scoring, and positioning strategy. Triggers on market analysis, competitive research, or gap identification requests.
What this skill does
# Market Gap Analysis
Identify underserved markets and competitive positioning opportunities through systematic analysis.
## Analysis Framework
```
Market Scan → Competitor Map → Gap Identification → Opportunity Scoring → Strategy
│ │ │ │ │
│ │ │ │ └─ Positioning
│ │ │ └─ Prioritized gaps
│ │ └─ Unserved/underserved areas
│ └─ Feature/capability matrix
└─ Total landscape understanding
```
## Market Scanning
### TAM/SAM/SOM Analysis
```markdown
## Market Size
### Total Addressable Market (TAM)
- Market: {broad market definition}
- Size: ${amount} ({year})
- Growth: {CAGR}%
- Source: {citation}
### Serviceable Addressable Market (SAM)
- Segment: {specific segment you can reach}
- Size: ${amount}
- Criteria: {geographic, demographic, or technical constraints}
### Serviceable Obtainable Market (SOM)
- Realistic capture: ${amount} over {timeframe}
- Assumptions: {market share %, conversion rates}
```
### Market Segmentation
| Segment | Size | Growth | Competition | Fit |
|---------|------|--------|-------------|-----|
| Enterprise | $2B | 12% | High | Medium |
| SMB | $800M | 18% | Medium | High |
| Developer tools | $500M | 25% | Low | High |
| Education | $300M | 8% | Low | Medium |
## Competitive Landscape
### Feature Matrix
```markdown
| Capability | Us | Competitor A | Competitor B | Competitor C |
|------------|:--:|:-----------:|:-----------:|:-----------:|
| Core feature 1 | ● | ● | ◐ | ○ |
| Core feature 2 | ● | ○ | ● | ● |
| Feature 3 | ◐ | ● | ○ | ○ |
| Feature 4 | ○ | ○ | ○ | ○ |
| Integration X | ● | ◐ | ● | ○ |
● = Full support ◐ = Partial ○ = None
```
### Positioning Map
```
High Price
│
Enterprise │ Premium
Solutions │ Tools
│
Low ────────┼──────── High
Innovation │ Innovation
│
Legacy │ Open Source /
Tools │ Community
│
Low Price
```
### Competitor Profiles
```markdown
## {Competitor Name}
**Positioning:** {one-sentence positioning}
**Target:** {primary customer segment}
**Pricing:** {model and range}
**Strengths:** {2-3 key strengths}
**Weaknesses:** {2-3 key weaknesses}
**Recent moves:** {latest product/market changes}
**Threat level:** High / Medium / Low
```
## Gap Identification
### Gap Types
| Gap Type | Description | Signal |
|----------|-------------|--------|
| **Feature gap** | Missing capability | Feature requests, workarounds |
| **Segment gap** | Unserved customer type | Forums, job boards, community |
| **Price gap** | No option at price point | Customer complaints, DIY solutions |
| **Integration gap** | Missing connection | Stack compatibility issues |
| **Quality gap** | Poor existing solutions | Low satisfaction, high churn |
| **Geography gap** | Unserved region | Language/compliance gaps |
### Gap Discovery Methods
```markdown
### Direct Research
- Customer interviews (5-10 per segment)
- Support ticket analysis (top 20 requests)
- Feature request boards (competitor and own)
- App store reviews (1-star and 3-star)
### Indirect Research
- Job postings (what tools are companies hiring for?)
- Stack Overflow questions (what problems remain unsolved?)
- Reddit/community forums (what workarounds exist?)
- Conference talks (what problems are speakers addressing?)
```
## Opportunity Scoring
### ICE Framework
| Opportunity | Impact (1-10) | Confidence (1-10) | Ease (1-10) | Score |
|------------|:-----:|:-----:|:-----:|:-----:|
| Developer API | 9 | 7 | 5 | 7.0 |
| Mobile app | 6 | 8 | 3 | 5.7 |
| Enterprise SSO | 8 | 9 | 7 | 8.0 |
| Free tier | 7 | 6 | 8 | 7.0 |
Score = (Impact + Confidence + Ease) / 3
### RICE Framework
| Opportunity | Reach | Impact | Confidence | Effort | Score |
|------------|:-----:|:------:|:----------:|:------:|:-----:|
| Developer API | 500 | 3 | 80% | 3 months | 400 |
| Mobile app | 2000 | 1 | 60% | 6 months | 200 |
Score = (Reach × Impact × Confidence) / Effort
## Positioning Strategy
### Positioning Statement Template
```
For {target customer}
who {need/problem},
{product name} is a {category}
that {key benefit}.
Unlike {primary competitor},
we {key differentiator}.
```
### Strategic Options
| Strategy | When | Example |
|----------|------|---------|
| **Head-to-head** | Strong differentiator | Better UX than market leader |
| **Niche focus** | Underserved segment | "Built specifically for..." |
| **Blue ocean** | Category creation | New category definition |
| **Platform play** | Ecosystem potential | Extensibility as moat |
| **Price disruption** | Overpriced market | Free/open-source alternative |
## SWOT Analysis
```markdown
| | Positive | Negative |
|---|---------|----------|
| **Internal** | **Strengths** | **Weaknesses** |
| | • {strength 1} | • {weakness 1} |
| | • {strength 2} | • {weakness 2} |
| **External** | **Opportunities** | **Threats** |
| | • {opportunity 1} | • {threat 1} |
| | • {opportunity 2} | • {threat 2} |
```
## Anti-Patterns
- **Analysis paralysis** — Set a time-box; analysis that delays action costs more than imperfect analysis
- **Competitor obsession** — Focus on customer needs, not competitor features
- **Confirmation bias** — Seek disconfirming evidence, not just supporting data
- **Static analysis** — Markets change; revisit quarterly
- **Ignoring indirect competitors** — Spreadsheets, manual processes, and "do nothing" are competitors
- **Feature parity as strategy** — Matching competitors feature-for-feature is not differentiation
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.