mmcmedia

App Opportunity Research Skill

*Validated with McKinzie's feedback: audience-building advantage, 5% conversion assumption, focus on real pain over perfect fit*

mmcmedia 1 Updated 3mo ago
GitHub

Install

npx skillscat add mmcmedia/openclaw-agents/skills-app-opportunity-research

Install via the SkillsCat registry.

SKILL.md

App Opportunity Research Skill

Purpose: Find profitable app opportunities for McKinzie's audiences through rigorous validation.

Trigger: When McKinzie wants to find new app ideas, validate a market, or research competitive gaps.


๐ŸŽฏ Research Philosophy

Goal: Find real pain points with validated demand, not guesswork.

Key Insight: McKinzie's superpower isn't existing audience - it's ability to understand and build audiences quickly.

Success Criteria:

  • Real pain point (50+ mentions, desperate language)
  • Growing market (10%+ YoY)
  • People PAY for solutions
  • McKinzie can understand the audience
  • Reachable through channels she can master

๐Ÿ“‹ Research Methodology

Phase 0: Audience Audit (REQUIRED)

Before researching, understand McKinzie's reach:

Check:

  • Email list segments (which topics get engagement?)
  • Blog analytics (top performing content)
  • Social demographics per platform
  • Previous product launches (what worked?)

Output: "McKinzie has strongest reach with X, Y, Z niches + ability to build new audiences in 6 months"


Phase 1: Pain Point Discovery (Breadth)

Sources to Mine:

  1. Reddit (5-10 threads per niche)

    • r/homeschool, r/Parenting, r/mommit
    • r/TwoXChromosomes, r/beyondthebump
    • r/LDS, r/Christianity
    • Niche: r/homesteading, r/Frugal, r/haircare
  2. App Store Reviews (50+ per top 3 apps)

    • 1-star reviews: What makes people rage quit?
    • 5-star reviews: What do they love most?
    • Recent reviews: What's changed?
  3. Facebook Groups (if accessible)

    • "I wish someone would build..."
    • "Does anyone know an app that..."
    • "I'm so frustrated with..."
  4. Quora / Forums

    • "What is the best app for..."
    • Common follow-up complaints

Collection Target:

  • 100+ raw mentions
  • 20+ unique pain points
  • 5+ "I wish" statements
  • 3+ "I'd pay for this"

Phase 2: Pain Point Validation (Depth)

For EACH candidate pain point, verify:

Validation Criteria Evidence Needed Threshold
Frequency How often mentioned? 20+ unique mentions
Intensity Desperate vs mild annoyance "I'm desperate" language
Willingness to Pay Paid for workarounds? 5+ "I'd pay" or workaround mentions
Current Solutions Why do existing apps fail? Specific complaints, not vague

Red Flags (Auto-reject):

  • Mentioned <5 times
  • "Nice to have" language only
  • No one mentions paying
  • Solutions exist that people seem happy with

Phase 3: Market Validation

Quantitative Checks:

  1. Google Trends

    • Search: "best [niche] app"
    • Look for: 10%+ YoY growth
    • Seasonality: Spikes predictable?
  2. Reddit Growth

    • Subscriber growth rate
    • Engagement (comments per post)
    • New user questions
  3. App Store Data

    • Top apps: Download estimates
    • Revenue: Public data or estimates
    • Age: How long have leaders dominated?

Thresholds:

  • Market growing: 10%+ YoY minimum
  • Active community: 100K+ engaged users
  • Revenue signals: Existing paid apps making money

Phase 4: Competitive Reality Check

Research Questions:

  1. Why hasn't this been solved?

    • Incumbents are old/lazy?
    • Market too small?
    • Hard to reach users?
    • Technical complexity?
  2. Competitor Analysis:

    • Top 3 apps: Age, revenue, last update
    • Pricing: Free tier? Subscription? One-time?
    • Weaknesses: What do reviews consistently hate?
    • Red flag: All competitors <2 years old = unstable
  3. Differentiation Opportunity:

    • What's the angle they missed?
    • Underserved segment?
    • Simpler approach?

Phase 5: Strategic Fit Assessment

McKinzie's Angle:

Factor Question Score 1-5
Audience Understanding Can she relate to their pain?
Reachability Can she reach them via SEO/Pinterest/ads/influencers?
Content Flywheel Can blog content drive app downloads?
Launch Advantage Does she have unfair advantage (existing audience, partnerships)?
Complexity Can Dev build MVP in 2-4 weeks?
Retention Potential Daily use or one-time?

Total: /30

Scoring:

  • 25-30: Strong fit, recommend build
  • 20-24: Good fit, consider build
  • 15-19: Marginal, need differentiator
  • <15: Skip

Phase 6: Revenue Projection

Conservative Math:

Addressable Market: X people
McKinzie's Reach (Year 1): X ร— 0.02 = Y people
Conversion (freeโ†’paid): Y ร— 0.03 = Z paid users
Price: $X/month
Annual Revenue: Z ร— $X ร— 12 = $____

Thresholds:

  • Year 1: $10K minimum, $50K ideal
  • Year 2: $100K+ for sustainability

๐Ÿ“ Output Template

Opportunity Report

# App Opportunity: [Name]

## 1. Pain Point
**Problem Statement:** [One sentence]

**Evidence:**
- "[Direct quote from user]" (Reddit r/XXX)
- "[Direct quote from user]" (App Store review)
- [5+ quotes total]

**Frequency:** Mentioned X times across Y sources

**Intensity:** [Desperate / Frustrated / Mildly annoyed]

## 2. Market Validation
- **Google Trends:** X% growth YoY
- **Community Size:** X subscribers (growing Y%/month)
- **Search Volume:** X monthly searches
- **Existing Revenue:** Top app makes $X (estimated)

## 3. Competitive Analysis
| App | Age | Price | Weakness | Users |
|-----|-----|-------|----------|-------|
| [Name] | 5yr | $5/mo | [Specific complaint] | X |
| [Name] | 2yr | Freemium | [Specific complaint] | Y |

**Gap:** [What they're missing]

## 4. Strategic Fit
| Factor | Score | Notes |
|--------|-------|-------|
| Audience Understanding | X/5 | |
| Reachability | X/5 | |
| Content Flywheel | X/5 | |
| Launch Advantage | X/5 | |
| Complexity | X/5 | |
| Retention | X/5 | |
| **TOTAL** | **X/30** | |

## 5. Revenue Projection
- **Year 1:** $X (X users ร— $X/month ร— 12)
- **Year 2:** $X (growth assumptions)
- **Break-even:** X months

## 6. Recommendation
**[BUILD / SKIP / RESEARCH MORE]**

**Why:** [2-3 sentences]

**MVP Features:**
1. [Feature]
2. [Feature]
3. [Feature]

**Next Steps:**
- [ ] Validate with 5 potential users
- [ ] Build landing page for interest
- [ ] Competitive teardown
- [ ] Technical feasibility check with Dev

๐Ÿš€ Quick-Start Commands

Research a Niche

Research app opportunities in [NICHE] for McKinzie.
Follow the validation methodology in SKILL.md.
Deliver 3-5 opportunities with full reports.

Validate Specific Idea

Validate if "[IDEA]" is a viable app opportunity.
Check: pain frequency, willingness to pay, competition, strategic fit.
Deliver go/no-go recommendation with evidence.

Competitive Teardown

Analyze top 3 apps in [NICHE].
Find their weaknesses and gaps.
Identify differentiation opportunity.

โš ๏ธ Common Mistakes to Avoid

  1. One review = pain point โŒ

    • Need 20+ mentions across multiple sources
  2. "I wish" = willingness to pay โŒ

    • Look for actual spending or desperate workarounds
  3. Ignoring why competitors haven't won โŒ

    • If no one dominates, ask why. Hard to reach? Low retention?
  4. Assuming McKinzie's current audience โŒ

    • She can build new audiences. Focus on reachability, not current list.
  5. Skipping market size validation โŒ

    • Small passionate market > Large indifferent market

๐Ÿ“š Resources

Tools:

  • Google Trends (trends.google.com)
  • Reddit (reddit.com)
  • App Store / Google Play reviews
  • Sensor Tower / App Annie (if available)

Research Avenues:

  • r/SideProject (what people are building)
  • r/SaaS (business models)
  • r/Entrepreneur (validation stories)
  • Indie Hackers (revenue transparency)

โœ… Success Metrics

Quality Research:

  • 3-5 opportunities with full validation
  • Each backed by 20+ data points
  • Clear go/no-go recommendations
  • MVP feature sets ready for Dev

Timeline:

  • 1 niche: 2-3 hours
  • 3 niches: 6-8 hours
  • Full report: Deliver within 24 hours of starting

Last updated: Feb 15, 2026
Validated with McKinzie's feedback: audience-building advantage, 5% conversion assumption, focus on real pain over perfect fit