market-research
Deep market analysis for iOS/macOS apps including market sizing (TAM/SAM/SOM), growth trends, market maturity, entry barriers, distribution channels, and revenue potential. Use when user asks for market research, market size, market opportunity, growth potential, TAM/SAM/SOM, or market trends.
What this skill does
# Market Research Skill
Performs deep market research for iOS/macOS app ideas. Provides market sizing, growth analysis, and opportunity assessment.
## When This Skill Activates
Use this Skill when the user wants to:
- Understand market size and potential
- Analyze market growth trends
- Calculate TAM/SAM/SOM
- Assess market maturity
- Identify entry barriers
- Understand distribution channels
- Estimate revenue potential
- Deep-dive after initial problem discovery
**This is a follow-up to the product-agent skill** — use this when you need market depth.
## What This Skill Does
### 1. Market Sizing (TAM/SAM/SOM)
- **TAM (Total Addressable Market):** Total revenue opportunity if you captured 100% of the market
- **SAM (Serviceable Available Market):** Segment of TAM you can reach with your product/distribution
- **SOM (Serviceable Obtainable Market):** Realistic share you can capture in near term (1-3 years)
### 2. Growth Analysis
- Historical growth rates
- Future projections (3-5 years)
- Growth drivers
- Market trends
### 3. Market Maturity Assessment
- Stage: Emerging, Growing, Mature, or Declining
- Market lifecycle position
- Implications for new entrants
### 4. Entry Barriers
- Technical barriers
- Brand/network effects
- Regulatory requirements
- Capital requirements
- Customer acquisition costs
### 5. Distribution Channels
- How apps in this category reach users
- App Store dynamics
- Alternative channels (web, enterprise, etc.)
### 6. Revenue Potential
- Average revenue per user (ARPU)
- Conversion rates
- LTV (Lifetime Value)
- Revenue models in use
## Output Structure
```json
{
"market_category": "Task Management",
"market_sizing": {
"tam": {
"value": "$4.5B",
"description": "Global productivity software market",
"methodology": "Total potential revenue if product served all users globally"
},
"sam": {
"value": "$900M",
"description": "iOS/macOS task management apps (20% of TAM)",
"methodology": "Addressable via App Store distribution on Apple platforms"
},
"som": {
"value": "$45M",
"description": "Realistic 3-year capture (5% of SAM)",
"methodology": "Based on typical indie app market share penetration"
}
},
"market_growth": {
"historical_growth": "12% CAGR (2021-2025)",
"projected_growth": "10% CAGR (2026-2030)",
"growth_drivers": [
"Remote work adoption",
"Increased digital task management",
"Mobile-first workflows"
],
"headwinds": [
"Market saturation",
"Consolidation toward major players"
]
},
"market_maturity": {
"stage": "Mature",
"characteristics": [
"Established leaders (Todoist, Things)",
"Clear product categories",
"Slowing growth rate",
"Focus on feature differentiation"
],
"implications": "Differentiation critical. Hard to compete on basics. Must have unique angle."
},
"entry_barriers": {
"low": [
"Technical implementation (task management is straightforward)"
],
"medium": [
"Building user base in crowded market",
"Achieving reliable sync across devices"
],
"high": [
"Brand recognition (Todoist, Things have 10+ years)",
"Network effects (team collaboration features)",
"Customer switching costs (data lock-in)"
],
"overall_assessment": "Medium-High - Technical execution is achievable, but market position is difficult"
},
"distribution_channels": {
"primary": {
"channel": "App Store",
"percentage": "75%",
"dynamics": "Discoverability challenging. ASO critical. Top charts dominated by established apps."
},
"secondary": [
{
"channel": "Direct website",
"percentage": "15%",
"dynamics": "For power users. Allows higher pricing. Better for subscription retention."
},
{
"channel": "Word of mouth / Communities",
"percentage": "10%",
"dynamics": "Productivity communities, Reddit, Twitter. High-intent users."
}
]
},
"revenue_potential": {
"arpu": {
"freemium": "$12/year (5% convert at $20/year)",
"paid_only": "$30-40/year",
"premium": "$60-100/year"
},
"conversion_rates": {
"free_to_paid": "3-7% industry average",
"trial_to_paid": "15-25% with 14-day trial"
},
"ltv": "$150-300 (2-5 year user lifecycle)",
"realistic_year_1": "$50K-200K (1K-5K users at $40 ARPU)",
"realistic_year_3": "$500K-2M (10K-50K users with growth)",
"path_to_scale": "Requires strong differentiation, word-of-mouth growth, and retention >85%"
},
"market_opportunity_score": "6/10 - Moderate",
"reasoning": "Large market with growth, but mature and competitive. Success requires clear differentiation and excellent execution. Not a 'gold rush' market, but sustainable business possible for well-positioned product."
}
```
## How to Perform Market Research
### Step 1: Define Market Scope
```
Question: What exact market are you analyzing?
- "Task management apps" (broad)
- "iOS task management apps" (narrower)
- "AI-powered task management for Apple users" (specific)
Start specific for better analysis.
```
### Step 2: Size the Market (TAM/SAM/SOM)
**TAM Calculation:**
```
Method 1: Top-down
- Global productivity software market: $50B
- Task management segment: ~10% = $5B TAM
Method 2: Bottom-up
- Potential users globally: 500M knowledge workers
- Willing to pay for task management: 20% = 100M
- Average spend: $50/year
- TAM = 100M × $50 = $5B
```
**SAM Calculation:**
```
Filter TAM by what you can reach:
- TAM: $5B global
- Your distribution: iOS/macOS App Store only
- Apple users: ~30% of market = $1.5B
- Addressable via App Store: 60% = $900M SAM
```
**SOM Calculation:**
```
Realistic capture in 3 years:
- SAM: $900M
- New entrant market share: 0.5-2% realistic
- With strong differentiation: 5% optimistic
- SOM = $900M × 1-5% = $9M-45M
```
### Step 3: Assess Growth
Use WebSearch to find:
- Market research reports
- Growth rate data
- Trend articles
**Key searches:**
```
"[category] market size 2026"
"[category] growth rate"
"[category] market trends 2026"
```
### Step 4: Determine Maturity
**Indicators:**
**Emerging** (Good for new entrants):
- High growth (>20% CAGR)
- No clear leaders
- Rapid innovation
- Unclear best practices
**Growing** (Good opportunity):
- Strong growth (10-20% CAGR)
- Leaders emerging
- Product-market fit established
- Room for differentiation
**Mature** (Differentiation required):
- Moderate growth (5-10% CAGR)
- Clear leaders
- Established patterns
- Compete on specific niches
**Declining** (Avoid):
- Negative or flat growth
- Consolidation
- Commoditization
### Step 5: Identify Barriers
**Low barriers → Easier entry but more competition**
**High barriers → Harder entry but better moat if you succeed**
Assess:
- Technical complexity
- Brand importance
- Network effects
- Switching costs
- Capital needs
### Step 6: Map Distribution
**For iOS/macOS apps:**
- App Store (primary) - understand ranking factors
- TestFlight (beta)
- Direct website (for pro users)
- SetApp / Bundle services
- Enterprise/B2B channels
### Step 7: Estimate Revenue
**Key metrics to research:**
- Industry ARPU
- Typical conversion rates
- Churn rates
- User acquisition costs
**Reality check:**
```
Year 1: 1K-5K users (realistic for indie)
Year 2: 5K-20K users (with growth)
Year 3: 20K-100K users (if successful)
At $40 ARPU:
Year 1: $40K-200K
Year 2: $200K-800K
Year 3: $800K-4M
```
## Common Questions
### "How do I calculate TAM without market reports?"
**Bottom-up approach:**
1. Estimate target user count (e.g., "iOS users who manage tasks")
2. Research willingness to pay (look at competitor pricing)
3. Multiply: TAM = Users × Average Spend
**Proxy approach:**
1. Find similar market (e.g., "Calendar apps")
2. Adjust for your market differences
3. Validate with multiple sources
### "What's a 'good' market sizeRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".