growth

어떤 스킬인가요?

Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

# Metrics Reference

Definitions, formulas, and benchmarks for key app metrics. Use this as a lookup when interpreting user data in the analytics-interpretation skill.

## Metric Definitions and Formulas

### Engagement Metrics

**DAU (Daily Active Users)**
Users who open the app at least once in a calendar day.
```
DAU = count of unique users with at least one session on a given day
```

**MAU (Monthly Active Users)**
Users who open the app at least once in a 30-day rolling window.
```
MAU = count of unique users with at least one session in the last 30 days
```

**DAU/MAU Ratio (Stickiness)**
Percentage of monthly users who use the app on any given day. Higher = more habitual usage.
```
DAU/MAU = DAU / MAU × 100
```

**Session Length**
Average time spent per app session, from foreground to background.
```
Avg Session Length = total session time / total sessions
```

**Sessions Per User Per Day**
How many times the average daily user opens the app.
```
Sessions/User/Day = total daily sessions / DAU
```

### Retention Metrics

**Day N Retention (D1, D7, D30)**
Percentage of users who installed on Day 0 and returned on Day N.
```
DN Retention = users active on Day N / users installed on Day 0 × 100
```
Note: This is "classic retention" (active on exactly Day N), not "rolling retention" (active on Day N or later).

**Rolling Retention (Return Rate)**
Percentage of users who installed on Day 0 and returned on Day N or any day after.
```
Rolling DN Retention = users active on Day N or later / users installed on Day 0 × 100
```
Rolling retention is always >= classic retention and gives a more optimistic view.

**Weekly Retention**
Percentage of users active in Week 1 who are also active in Week N.
```
Week N Retention = users active in Week N / users active in Week 1 × 100
```

**Churn Rate (Monthly)**
Percentage of subscribers who cancel in a given month.
```
Monthly Churn = subscribers lost in month / subscribers at start of month × 100
```

### Revenue Metrics

**LTV (Lifetime Value)**
Total revenue expected from a single user over their entire lifetime.
```
LTV = ARPU / Monthly Churn Rate
or
LTV = ARPU × Average Customer Lifetime (in months)
```

**ARPU (Average Revenue Per User)**
Revenue per user across all users (including free users).
```
ARPU = total revenue / total users (in period)
```

**ARPPU (Average Revenue Per Paying User)**
Revenue per paying user only.
```
ARPPU = total revenue / paying users (in period)
```

**MRR (Monthly Recurring Revenue)**
Predictable monthly revenue from active subscriptions.
```
MRR = number of active subscribers × average monthly subscription price
```

**ARR (Annual Recurring Revenue)**
Annualized version of MRR.
```
ARR = MRR × 12
```

**CAC (Customer Acquisition Cost)**
Cost to acquire one new user through paid channels.
```
CAC = total acquisition spend / new users acquired
```

**Payback Period**
Months to recoup the cost of acquiring a user.
```
Payback Period = CAC / monthly ARPU (in months)
```

**Trial Start Rate**
Percentage of downloads that start a free trial.
```
Trial Start Rate = trial starts / downloads × 100
```

**Trial Conversion Rate**
Percentage of free trials that convert to paid subscriptions.
```
Trial Conversion = paid conversions / trial starts × 100
```

### App Store Metrics

**Impressions**
Number of times your app appeared in App Store search results, featured sections, or browse pages. Counts views of your icon/title, not full page views.

**Product Page Views (PPV)**
Number of times users tapped through to your full product page (screenshots, description, reviews).

**Tap-Through Rate (TTR)**
```
TTR = Product Page Views / Impressions × 100
```

**Conversion Rate (CVR)**
```
CVR = App Units (downloads) / Product Page Views × 100
```

**App Units**
First-time downloads. Does not include re-downloads or updates.

## Benchmarks by App Category

### Social / Communication Apps
| Metric | Poor | Average | Good | Excellent |
|--------|------|---------|------|-----------|
| DAU/MAU | < 20% | 20-40% | 40-60% | > 60% |
| D1 Retention | < 20% | 20-30% | 30-40% | > 40% |
| D7 Retention | < 8% | 8-15% | 15-25% | > 25% |
| D30 Retention | < 4% | 4-8% | 8-15% | > 15% |
| Session Length | < 2 min | 2-5 min | 5-15 min | > 15 min |
| Sessions/Day | < 2 | 2-4 | 4-8 | > 8 |

### Productivity / Business Apps
| Metric | Poor | Average | Good | Excellent |
|--------|------|---------|------|-----------|
| DAU/MAU | < 10% | 10-20% | 20-30% | > 30% |
| D1 Retention | < 15% | 15-25% | 25-35% | > 35% |
| D7 Retention | < 7% | 7-12% | 12-20% | > 20% |
| D30 Retention | < 3% | 3-6% | 6-12% | > 12% |
| Session Length | < 1 min | 1-3 min | 3-10 min | > 10 min |
| Trial-to-Paid | < 20% | 20-40% | 40-60% | > 60% |

### Games (Casual)
| Metric | Poor | Average | Good | Excellent |
|--------|------|---------|------|-----------|
| DAU/MAU | < 10% | 10-15% | 15-25% | > 25% |
| D1 Retention | < 25% | 25-35% | 35-45% | > 45% |
| D7 Retention | < 8% | 8-15% | 15-20% | > 20% |
| D30 Retention | < 3% | 3-6% | 6-10% | > 10% |
| Session Length | < 3 min | 3-8 min | 8-20 min | > 20 min |
| Sessions/Day | < 2 | 2-3 | 3-5 | > 5 |

### Utilities / Tools
| Metric | Poor | Average | Good | Excellent |
|--------|------|---------|------|-----------|
| DAU/MAU | < 5% | 5-10% | 10-20% | > 20% |
| D1 Retention | < 15% | 15-20% | 20-30% | > 30% |
| D7 Retention | < 5% | 5-10% | 10-15% | > 15% |
| D30 Retention | < 2% | 2-5% | 5-10% | > 10% |
| Session Length | < 30s | 30s-2 min | 2-5 min | > 5 min |

Note: Utility apps often have low DAU/MAU because they are used only when needed (e.g., a calculator). Low stickiness is not necessarily bad for utilities — focus on retention and satisfaction instead.

### Subscription Apps (General)
| Metric | Poor | Average | Good | Excellent |
|--------|------|---------|------|-----------|
| Trial Start Rate | < 10% | 10-20% | 20-30% | > 30% |
| Trial-to-Paid | < 30% | 30-50% | 50-65% | > 65% |
| Monthly Churn | > 15% | 10-15% | 5-10% | < 5% |
| Annual Churn | > 50% | 35-50% | 20-35% | < 20% |
| LTV | < $10 | $10-30 | $30-80 | > $80 |
| Payback Period | > 6 mo | 3-6 mo | 1-3 mo | < 1 mo |

## App Store Conversion Benchmarks

### Tap-Through Rate (Impressions → Product Page Views)
| Category | Poor | Average | Good |
|----------|------|---------|------|
| Games | < 3% | 3-7% | > 7% |
| Productivity | < 4% | 4-8% | > 8% |
| Social | < 3% | 3-6% | > 6% |
| Utilities | < 5% | 5-10% | > 10% |
| Health & Fitness | < 4% | 4-8% | > 8% |

### Product Page Conversion Rate (PPV → Downloads)
| Category | Poor | Average | Good |
|----------|------|---------|------|
| Games (Free) | < 25% | 25-40% | > 40% |
| Games (Paid) | < 5% | 5-15% | > 15% |
| Productivity (Free) | < 20% | 20-35% | > 35% |
| Productivity (Paid) | < 8% | 8-20% | > 20% |
| Utilities (Free) | < 30% | 30-50% | > 50% |
| Utilities (Paid) | < 10% | 10-25% | > 25% |

## Quick Threshold Reference

Use these stoplight ratings in analytics reports:

| Metric | 🔴 Red | 🟡 Yellow | 🟢 Green |
|--------|--------|----------|---------|
| D1 Retention | < 20% | 20-35% | > 35% |
| D7 Retention | < 10% | 10-20% | > 20% |
| D30 Retention | < 5% | 5-10% | > 10% |
| DAU/MAU | < 10% | 10-25% | > 25% |
| Trial-to-Paid | < 30% | 30-50% | > 50% |
| Monthly Churn | > 12% | 7-12% | < 7% |
| TTR | < 4% | 4-8% | > 8% |
| PPV → Download CVR | < 20% | 20-35% | > 35% |
| App Rating | < 3.5 | 3.5-4.3 | > 4.3 |
| Refund Rate | > 10% | 5-10% | < 5% |

Note: These are general guidelines. Always consider app category, target audience, and monetization model when evaluating. A utility app with 8% DAU/MAU might be performing excellently, while a social app at 8% has a problem.

---
name: analytics-interpretation
description: Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
allowed-tools: [Read, Glob, Grep, AskUserQuestion]
---

# Analytics Interpretation

Interpret your app's metrics, diagnose problems, and make data-driven decisions. Works with App Store Connect data, third-party analytics, or raw numbers the user provides.

## When This Skill Activates

Use this skill when the user:
- Wants to understand their app metrics or analytics
- Asks about retention, LTV, ARPU, or churn
- Wants to know if their metrics are good or bad
- Needs help interpreting App Store Connect analytics
- Wants a data-driven growth plan
- Asks "what should I focus on to grow?"
- Has metrics data and wants to know what it means

## Process

### Step 1: Gather Context

Ask the user via AskUserQuestion:

1. **App type and monetization model**
   - Free with ads, freemium, subscription, paid upfront, or hybrid?
2. **Current metrics they have access to**
   - App Store Connect? Third-party analytics (Mixpanel, Firebase, Amplitude)?
3. **Specific numbers they can share**
   - Downloads, DAU/MAU, retention, revenue, conversion rates?
4. **What they want to know**
   - "Are my metrics good?" / "What should I fix?" / "Should I keep going?"

### Step 2: Identify Key Metrics by App Type

Different monetization models have different north star metrics.

#### Free with Ads
| Metric | Why It Matters |
|--------|---------------|
| DAU/MAU | More daily users = more ad impressions |
| Session length | Longer sessions = more ad views |
| Sessions per day | More sessions = more revenue opportunities |
| Ad impressions/revenue | Direct revenue driver |
| D1/D7/D30 retention | Users must come back for ads to work |

#### Freemium (One-Time Unlock)
| Metric | Why It Matters |
|--------|---------------|
| Conversion rate (free → paid) | Primary revenue driver |
| Time to conversion | How long before users see enough value |
| Feature adoption | Which features drive upgrades |
| Revenue per download | Overall monetization efficiency |
| D7 retention (free users) | Must retain long enough to convert |

#### Subscription
| Metric | Why It Matters |
|--------|---------------|
| Trial start rate | Top of subscription funnel |
| Trial → paid conversion | Critical conversion point |
| Monthly churn rate | Determines LTV |
| LTV (lifetime value) | Revenue per subscriber over their lifetime |
| Payback period | Months to recoup acquisition cost |
| MRR / ARR | Business health snapshot |
| Subscriber retention (Month 1-12) | Long-term revenue curve |

#### Paid Upfront
| Metric | Why It Matters |
|--------|---------------|
| Downloads per day/week | Direct revenue driver |
| Revenue per download | Should equal price minus Apple's cut |
| Refund rate | Product quality signal (keep < 5%) |
| Ratings and reviews | Social proof drives more downloads |
| Organic vs. paid ratio | Sustainability indicator |

### Step 3: App Store Connect Analytics Interpretation

#### The App Store Funnel

```
Impressions (your app appeared in search/browse)
    ↓ Tap-through rate = Product Page Views / Impressions
Product Page Views (user tapped to see your page)
    ↓ Conversion rate = Downloads / Product Page Views
Downloads (user installed your app)
    ↓ D1 retention
Day 1 Active Users
    ↓ D7 retention
Day 7 Active Users
    ↓ D30 retention
Day 30 Active Users
    ↓ Monetization
Paying Users
```

#### Interpreting Each Funnel Step

**Impressions → Product Page Views (Tap-Through Rate)**

| Rating | TTR | Interpretation |
|--------|-----|---------------|
| Good | > 8% | Icon and title are compelling |
| Average | 4-8% | Room to improve first impression |
| Poor | < 4% | Icon, title, or subtitle need work |

What to fix if low:
- App icon not standing out (test bolder colors, simpler design)
- Title not communicating value (add keyword after brand name)
- Subtitle too vague (make it specific: "Budget Tracker" not "Finance App")
- Poor search ranking (see keyword-optimizer skill)

**Product Page Views → Downloads (Conversion Rate)**

| Rating | CVR | Interpretation |
|--------|-----|---------------|
| Good | > 40% | Screenshots and description are effective |
| Average | 25-40% | Some friction on the product page |
| Poor | < 25% | Major product page issues |

What to fix if low:
- First 3 screenshots not showing core value
- No app preview video (adds 15-25% lift)
- Description too long before showing key benefits
- Bad ratings visible (address review issues first)
- Price too high relative to perceived value

**Downloads → Day 1 Retention**

| Rating | D1 | Interpretation |
|--------|-----|---------------|
| Good | > 35% | Onboarding delivers on promise |
| Average | 20-35% | Some users confused or disappointed |
| Poor | < 20% | App not delivering expected value |

What to fix if low:
- Onboarding too long or confusing
- App Store screenshots overpromised
- Core value not visible in first session
- Permissions requested too early (camera, notifications)
- Performance issues (slow launch, crashes)

**Day 1 → Day 7 Retention**

| Rating | D7 | Interpretation |
|--------|-----|---------------|
| Good | > 20% | Users forming habit |
| Average | 10-20% | Some users finding value |
| Poor | < 10% | Most users abandoning after trying |

What to fix if low:
- No reason to come back (add notifications, reminders, streaks)
- Core loop not engaging enough
- Too complex — users haven't learned enough features
- Missing "aha moment" in first week

**Day 7 → Day 30 Retention**

| Rating | D30 | Interpretation |
|--------|-----|---------------|
| Good | > 10% | Strong product-market fit signal |
| Average | 5-10% | Decent but room to grow |
| Poor | < 5% | Retention cliff — users churning |

What to fix if low:
- Feature depth too shallow (users exhaust value)
- No progression or new content
- Competitor doing it better
- Consider: is this a "use once" tool, not a habit app?

### Step 4: AARRR Funnel Analysis

The pirate metrics framework — diagnose where your funnel leaks.

#### Acquisition: How do users find you?

| Metric | Benchmark | Diagnostic |
|--------|-----------|-----------|
| Organic search impressions | Growing month-over-month | Are your keywords working? |
| Browse impressions | Category-dependent | Are you getting featured/editorial? |
| Referral traffic | > 10% of total | Do users share your app? |
| Paid acquisition CPA | < 1/3 of LTV | Is paid acquisition sustainable? |

**Questions to ask:**
- What are your top 3 acquisition sources?
- Is organic growing or shrinking?
- What's your cost per install (if running ads)?

#### Activation: Do users experience the core value?

| Metric | Benchmark | Diagnostic |
|--------|-----------|-----------|
| Onboarding completion | > 70% | Is onboarding too long? |
| "Aha moment" reached | > 50% in first session | Do users discover core value? |
| First key action taken | > 40% of installs | Are users doing the main thing? |

**Questions to ask:**
- What is the one action that defines "this user gets it"?
- How many steps to reach that action?
- What percentage of new users complete it?

#### Retention: Do users come back?

| Metric | Benchmark | Diagnostic |
|--------|-----------|-----------|
| D1 retention | 25-40% | First impression quality |
| D7 retention | 15-25% | Habit formation |
| D30 retention | 8-15% | Product-market fit |
| DAU/MAU ratio | 15-30% | Daily engagement strength |

**Questions to ask:**
- Where is the biggest retention drop-off?
- What do retained users do differently from churned users?
- Is there a retention cliff at a specific day?

#### Revenue: Are users paying?

| Metric | Benchmark | Diagnostic |
|--------|-----------|-----------|
| Free → trial rate | 10-30% | Is the paywall compelling? |
| Trial → paid rate | 40-60% | Does the trial demonstrate value? |
| ARPU (all users) | Category-dependent | Overall monetization efficiency |
| ARPPU (paying users) | 5-20x ARPU | Are payers happy with value? |

**Questions to ask:**
- At what point do users encounter the paywall?
- What's the conversion rate at each paywall touchpoint?
- Do longer-retained users convert at higher rates?

#### Referral: Do users tell others?

| Metric | Benchmark | Diagnostic |
|--------|-----------|-----------|
| Organic multiplier | > 1.0 | Each user brings > 1 new user |
| Share rate | > 5% of MAU | Users actively sharing |
| Rating/review rate | > 1% of MAU | Users willing to vouch publicly |
| Average rating | > 4.5 | High satisfaction |

**Questions to ask:**
- Is there a share feature in the app?
- Do you ask for ratings at the right moment?
- What triggers a user to recommend your app?

### Step 5: Cohort Analysis (Subscription Apps)

#### How to Read a Cohort Retention Table

```
              Month 0  Month 1  Month 2  Month 3  Month 4  Month 5
Jan cohort    100%     62%      55%      50%      48%      46%
Feb cohort    100%     58%      51%      46%      44%      —
Mar cohort    100%     65%      59%      54%      —        —
Apr cohort    100%     70%      63%      —        —        —
May cohort    100%     68%      —        —        —        —
```

**What to look for:**

1. **Month 0 → Month 1 drop**: The biggest drop. Industry average is 30-50% churn. If yours is > 50%, trial experience needs work.

2. **Flattening curve**: Retention should flatten over time. If Month 3 → Month 4 → Month 5 are similar, you've found your "natural retention floor."

3. **Improving cohorts**: Compare Jan vs. Apr cohorts at the same month. If Apr Month 1 (70%) > Jan Month 1 (62%), your product improvements are working.

4. **Retention cliff**: A sudden drop at a specific month often indicates:
   - Month 1: Annual subscribers who don't renew
   - Month 3: Users who gave it a fair try and decided no
   - Month 12: Annual subscribers hitting renewal

#### Comparing Cohorts to Measure Impact

When you ship a change, compare cohorts before and after:

```
Before change (Jan-Mar avg):  Month 1 retention = 58%
After change (Apr-May avg):   Month 1 retention = 69%

Improvement: +11 percentage points → significant positive impact
```

**Rules of thumb:**
- < 3 percentage point change: likely noise
- 3-10 percentage point change: meaningful, keep the change
- > 10 percentage point change: major win, double down on this direction

### Step 6: Diagnostic Decision Trees

Use these when the user says "my [metric] is bad, what do I do?"

#### Low Impressions (< 1,000/day for established app)
```
Low impressions
├── Are you ranking for any keywords?
│   ├── NO → ASO problem: optimize title, subtitle, keywords
│   │        See keyword-optimizer skill
│   └── YES → Are those keywords high-volume?
│       ├── NO → Target higher-volume keywords
│       └── YES → Are you ranking in top 10?
│           ├── NO → Improve rankings (more ratings, better conversion)
│           └── YES → Expand to more keywords or new markets
```

#### High Impressions, Low Product Page Views (TTR < 4%)
```
Low tap-through rate
├── Is your icon professional and distinctive?
│   ├── NO → Redesign icon (test 3 variants)
│   └── YES → Is your title clear and keyword-rich?
│       ├── NO → Rewrite title: [Brand] - [Value Keyword]
│       └── YES → Is your subtitle compelling?
│           ├── NO → Rewrite subtitle with specific benefit
│           └── YES → Check competitor positioning — are you differentiated?
```

#### Good Downloads, Bad Retention (D1 < 25%)
```
Poor day-1 retention
├── Is onboarding complete rate > 70%?
│   ├── NO → Simplify onboarding (fewer steps, skip option)
│   └── YES → Do users reach "aha moment" in first session?
│       ├── NO → Restructure first-run experience to show core value immediately
│       └── YES → Are there performance issues (crashes, slow load)?
│           ├── YES → Fix stability first (check crash reports)
│           └── NO → Does the app match what screenshots promised?
│               ├── NO → Align marketing with actual product
│               └── YES → Core value may not be strong enough → user research needed
```

#### Good Retention, Low Revenue (conversion < 3%)
```
Low monetization
├── Do users see the paywall?
│   ├── NO → Add natural paywall touchpoints (feature gates, usage limits)
│   └── YES → Is the paywall compelling?
│       ├── NO → Redesign paywall (show value, social proof, feature comparison)
│       └── YES → Is the price right?
│           ├── TOO HIGH → Test lower price point or add cheaper tier
│           ├── TOO LOW → Users may not perceive enough value — test higher price
│           └── SEEMS RIGHT → Is trial experience showcasing premium features?
│               ├── NO → Onboard users to premium features during trial
│               └── YES → Test different trial lengths or offer types
```

### Step 7: Invest, Iterate, Pivot, or Sunset?

Based on the overall picture, recommend one of four paths:

#### Invest (Double Down)
**Signals:**
- D7 retention > 40%
- Growing organically (installs increasing without paid acquisition)
- Users actively requesting features
- Conversion rate improving over time
- Strong ratings (> 4.5 stars)

**Action:** Increase development speed, consider marketing spend, expand to new platforms.

#### Iterate (Keep Improving)
**Signals:**
- D7 retention 20-40%
- Some organic growth but not accelerating
- Mixed user feedback (some love it, some confused)
- Conversion rate stable but not great

**Action:** Focus on the retention cliff. Find what retained users do differently and make all users do that. A/B test paywall and onboarding.

#### Pivot (Change Direction)
**Signals:**
- D7 retention < 20% after 3+ iterations
- Engagement concentrated in unexpected feature
- Users using app differently than intended
- Specific segment retains well, others don't

**Action:** Double down on the unexpected use case. Rebuild around what users actually do, not what you planned.

#### Sunset (Move On)
**Signals:**
- Declining metrics across the board
- No organic growth despite multiple iterations
- Users not engaging even after onboarding improvements
- Opportunity cost too high (other ideas with more potential)

**Action:** Put app in maintenance mode. Stop active development. Consider open-sourcing or selling. Redirect energy to next project.

**Important caveat:** Sunsetting is not failure. Most successful indie developers shipped several apps before finding the one that worked.

## Reference Files

See **metrics-reference.md** for:
- Detailed metric definitions and formulas
- Benchmark ranges by app category (social, productivity, games, utilities)
- App Store Connect specific metric definitions
- Red/yellow/green thresholds for all key metrics

## Output Format

Present analysis as an Analytics Health Report:

```markdown
# Analytics Health Report: [App Name]

## Overview
**App type:** [Free/Freemium/Subscription/Paid]
**Stage:** [Pre-launch/Early/Growing/Established]
**Data period:** [Date range analyzed]

## Funnel Health

| Stage | Metric | Value | Rating | Action |
|-------|--------|-------|--------|--------|
| Acquisition | Impressions/day | X,XXX | 🟢/🟡/🔴 | ... |
| Acquisition | Tap-through rate | X.X% | 🟢/🟡/🔴 | ... |
| Activation | Conversion rate | X.X% | 🟢/🟡/🔴 | ... |
| Retention | D1 retention | XX% | 🟢/🟡/🔴 | ... |
| Retention | D7 retention | XX% | 🟢/🟡/🔴 | ... |
| Retention | D30 retention | XX% | 🟢/🟡/🔴 | ... |
| Revenue | Conversion rate | X.X% | 🟢/🟡/🔴 | ... |
| Revenue | LTV | $XX.XX | 🟢/🟡/🔴 | ... |

## Primary Bottleneck
**[Stage name]** — [One sentence explanation of the biggest problem]

## Recommended Actions (Priority Order)
1. 🔴 [Critical fix] — Expected impact: [X]
2. 🟠 [High priority] — Expected impact: [X]
3. 🟡 [Medium priority] — Expected impact: [X]

## Overall Assessment
**Recommendation:** [Invest / Iterate / Pivot / Sunset]
**Rationale:** [2-3 sentences]
```

## References

- **metrics-reference.md** — Metric definitions, formulas, and benchmarks
- **app-store/keyword-optimizer/** — For ASO-related fixes
- **monetization/** — For pricing and paywall optimization
- **testing/** — For A/B test methodology

---
name: community-building
description: Build and engage a user community around your indie app. Covers platform selection, building in public strategy, content calendars for solo developers, and converting community members into advocates. Use when user wants to grow social media presence, start building in public, or create a content strategy.
allowed-tools: [Read, Glob, Grep, AskUserQuestion]
---

# Community Building

Build and engage a community around your indie Apple app. Practical strategies for solo developers who have limited time but want meaningful growth through community.

## When This Skill Activates

Use this skill when the user:
- Wants to build a community around their app
- Asks about growing their social media presence
- Wants to start building in public
- Needs a content strategy for promoting their app
- Asks about developer marketing
- Wants to turn users into advocates

## Process

### Step 1: Gather Context

Ask the user via AskUserQuestion:

1. **Current presence**: Are you on any social platforms? How many followers?
2. **Time budget**: How many hours per week can you dedicate to community?
3. **Comfort level**: Are you comfortable sharing revenue, progress, struggles?
4. **App stage**: Pre-launch, just launched, growing, or established?
5. **Target audience**: Developers, general consumers, or a specific niche?

### Step 2: Platform Selection

Choose 1-2 platforms to focus on. Spreading across 5 platforms with weak presence is worse than owning 1-2 platforms.

#### Platform Comparison

**Twitter/X**
- Audience: Large Apple developer community, tech enthusiasts
- Strengths: Fast feedback loops, viral potential, networking with other devs
- Weaknesses: Noisy, algorithm-dependent, declining trust among some users
- Best for: Developer tools, productivity apps, building in public
- Time investment: 15-30 min/day
- Growth speed: Moderate (1-3 months to gain traction)

**Mastodon (mastodon.social / indieweb.social)**
- Audience: Growing indie dev community, privacy-conscious users
- Strengths: No algorithm (chronological), supportive community, less noise
- Weaknesses: Smaller audience, less viral potential, fragmented servers
- Best for: Privacy-focused apps, developer tools, indie community engagement
- Time investment: 10-20 min/day
- Growth speed: Slow but genuine (3-6 months)

**Reddit**
- Audience: Highly engaged niche communities
- Strengths: Targeted subreddits, long-form discussion, SEO value
- Weaknesses: Anti-self-promotion rules, can be hostile, requires genuine participation
- Best for: Category-specific apps (r/productivity, r/fitness, r/budgeting)
- Subreddits: r/iOSProgramming, r/apple, r/SwiftUI, r/macapps, plus your app's category
- Time investment: 15-20 min/day (mostly commenting, not posting)
- Growth speed: Moderate if you contribute genuinely

**Discord**
- Audience: Power users, beta testers, engaged community members
- Strengths: Real-time interaction, deep engagement, beta testing hub
- Weaknesses: Requires active moderation, conversations are ephemeral, onboarding friction
- Best for: Apps with power users who want to discuss features and help shape the roadmap
- Time investment: 20-30 min/day (or batch in dedicated hours)
- Growth speed: Slow (requires seeding initial members)

**Threads**
- Audience: Growing, overlaps with Instagram audience
- Strengths: Growing platform, casual tone, integrated with Instagram
- Weaknesses: Still maturing, less developer-focused, algorithm-driven
- Best for: Consumer apps, visual apps, casual updates
- Time investment: 10-15 min/day
- Growth speed: Moderate (riding platform growth)

**Blog / Newsletter (Owned Platform)**
- Audience: Subscribers who opted in — highest intent
- Strengths: You own the audience, SEO benefits, long-form depth, email is reliable
- Weaknesses: Slow to build, requires consistent writing, higher effort per post
- Best for: Every app (this should be your long-term play, even if secondary)
- Platforms: Ghost, Buttondown, Substack, WordPress, or static site
- Time investment: 2-4 hours/week (one post per week)
- Growth speed: Very slow but most durable (6-12 months to meaningful audience)

#### Recommended Combinations

| Audience | Primary | Secondary |
|----------|---------|-----------|
| Developers | Twitter/X | Blog/newsletter |
| General consumers | Threads or Twitter/X | Newsletter |
| Privacy-conscious | Mastodon | Blog |
| Niche category | Reddit | Newsletter |
| Power users | Discord | Twitter/X |

### Step 3: Building in Public Strategy

Building in public means sharing your development journey transparently. It builds trust, creates accountability, and attracts early users.

#### What to Share

**High engagement (share often):**
- Progress updates with screenshots or short videos
- Design decisions and iterations (before/after)
- Milestones: download counts, revenue milestones, ratings
- Polls asking community to choose between features/designs
- Bugs you found and how you fixed them (relatable and educational)
- Weekly/monthly progress summaries

**Medium engagement (share periodically):**
- Revenue numbers and growth metrics (if comfortable)
- Lessons learned from mistakes
- Tools and processes you use
- App Store optimization experiments and results
- User testimonials and reviews

**Use sparingly:**
- Technical deep-dives (save for blog posts)
- Long threads (1-3 per month maximum)
- Philosophical musings about indie development

#### What NOT to Share

- Proprietary algorithms or trade secrets
- Features too far in advance (competitors watching, user expectations)
- Negative commentary about competitors
- Customer complaints or private messages
- Anything that could create legal liability
- Personal drama unrelated to the app journey

#### Transparency Levels

Choose your comfort level:

| Level | What You Share | Example |
|-------|---------------|---------|
| Fully transparent | Revenue, downloads, expenses, decisions | "March: $3,200 MRR, 847 subscribers, $400 in expenses" |
| Mostly transparent | Growth trends, decisions, learnings | "Crossed 800 subscribers this month, up 15% from February" |
| Selectively transparent | Progress, design, features | "Shipped the new dashboard this week, here's how it looks" |
| Journey-focused | Process, challenges, milestones | "Working on search — here's my approach to full-text indexing" |

All levels work. Pick what you are genuinely comfortable with and stay consistent.

### Step 4: Content Calendar (Realistic for Solo Developers)

This calendar assumes 3-5 hours per week total for community building.

#### Weekly Rhythm

| Day | Content Type | Time | Example |
|-----|-------------|------|---------|
| Monday | What I'm working on this week | 10 min | "This week: finishing the share sheet extension and fixing 3 bugs from user reports" |
| Wednesday | Tip, tutorial, or behind-the-scenes | 15 min | Screenshot of a SwiftUI trick, design iteration, or tool recommendation |
| Friday | Progress update or shipped feature | 15 min | "Shipped! Here's what's new in v2.3" or "Week in review: here's what got done" |

#### Monthly Additions

| Cadence | Content Type | Time | Example |
|---------|-------------|------|---------|
| 1st of month | Revenue/growth update | 30 min | Monthly metrics recap with takeaways |
| Mid-month | Blog post or tutorial | 2-3 hours | Technical post, lesson learned, or app development guide |
| End of month | Retrospective | 30 min | "What worked, what didn't, what's next" |

#### Batching Strategy

Do not create content in real-time throughout the week. Instead:

1. **Capture constantly**: Screenshot interesting moments as they happen (design iterations, bugs, metrics). Takes 30 seconds each.
2. **Batch create**: Dedicate 2 hours on Sunday (or whenever) to write all posts for the week using your captured screenshots.
3. **Schedule posts**: Use a scheduling tool (Buffer, Typefully, or native scheduling) so posts go out on the right days.
4. **Engage daily**: Spend 10-15 minutes responding to replies and engaging with others. This is separate from content creation.

### Step 5: Community Engagement Without Full-Time Effort

#### Daily Habits (10-15 minutes)

- Respond to every mention, reply, and DM (brevity is fine)
- Like/boost 3-5 posts from other developers in your space
- Comment genuinely on 2-3 posts from people you follow
- Check for your app's name/keywords being mentioned

#### Weekly Habits (30 minutes)

- Participate in relevant hashtags: #indiedev, #iosdev, #buildinpublic, #swiftui, #indieapps
- Share or boost someone else's launch/milestone (goodwill compounds)
- Respond to any App Store reviews (use review-response-writer skill)
- Check Reddit for relevant discussions where you can add value (not promote)

#### Monthly Habits (1 hour)

- Review your analytics: which posts got the most engagement? Do more of those.
- Follow new people in your space (genuine follow, not follow-for-follow)
- Reach out to 1-2 developers for potential collaboration or cross-promotion
- Update your bio/links if anything has changed

#### Engagement Rules

- **Be genuine**: Forced engagement is obvious. Only comment when you have something real to say.
- **Give more than you take**: The ratio should be roughly 80% supporting others, 20% promoting yourself.
- **Respond to everyone**: When you are small, responding to every comment builds loyalty.
- **Do not automate engagement**: Auto-likes, auto-comments, and bot followers backfire.
- **Be consistent, not constant**: Better to post 3 times per week every week than 10 times one week and nothing for a month.

### Step 6: Converting Community Members to Users and Advocates

#### Early Access and Beta Testing

- Offer TestFlight access to engaged followers before public launch
- Create a private Discord/Slack channel for beta testers
- Give beta testers a voice in feature prioritization
- Thank beta testers publicly when the app launches

#### Feature Requests and Public Roadmap

- Maintain a public roadmap (GitHub Projects, Notion, or Canny)
- When a community member suggests a feature you build, credit them publicly
- Let community vote on feature priority (creates investment in the product)
- When you ship a requested feature, tag the person who requested it

#### Referral and Sharing

- Build a share feature into your app (share results, creations, or achievements)
- Create share-worthy moments (streaks, milestones, completions)
- Make it easy to leave a review (use SKStoreReviewController at the right moment)
- Consider a referral program (if your app model supports it)

#### Social Proof Collection

| Source | How to Collect | How to Display |
|--------|---------------|----------------|
| App Store reviews | Screenshot 5-star reviews | App Store screenshots, website |
| Twitter/X testimonials | Screenshot positive tweets | Website testimonials section |
| Beta tester quotes | Ask directly during beta | App Store description, press kit |
| Usage milestones | Track in analytics | Social media posts ("10K users!") |

**When to ask for testimonials:**
- After a user complements your app (strike while the iron is hot)
- After successfully resolving a support request
- After a user shares your app organically
- After a major update that users are excited about

**How to ask:**
- "Thanks so much! Would you mind if I shared your kind words on our website?"
- "Would you be willing to leave a review on the App Store? It really helps indie apps like mine."
- Keep it low-pressure. Never guilt or pressure users.

### Step 7: Developer Blog as Marketing Channel

A blog is the highest-effort but highest-long-term-value community asset.

#### Content Types That Work

**Technical blog posts** (attract developer respect and SEO traffic):
- "How I built [feature] with SwiftUI"
- "Migrating from UIKit to SwiftUI: lessons learned"
- "Using Core ML to [interesting use case]"
- These get shared on Twitter, Hacker News, and iOS Dev Weekly

**Behind-the-scenes posts** (attract potential users):
- "Designing [App Name]'s onboarding"
- "Why I chose subscription pricing"
- "How I reduced my app's launch time by 60%"

**User-focused posts** (attract end-user awareness):
- "[App Name] tips and tricks you might not know"
- "How to [solve specific problem] with [App Name]"
- "What's coming in [App Name] 3.0"

#### Posting Cadence

- Minimum: 1 post per month (consistency matters more than frequency)
- Ideal: 2 posts per month (one technical, one behind-the-scenes)
- Maximum: 1 post per week (only if you enjoy writing and have content)

#### Distribution

After publishing a blog post:
1. Share on Twitter/X with a hook and key takeaway
2. Share on Mastodon
3. Submit to relevant newsletters (iOS Dev Weekly, Swift Weekly Brief)
4. Post to relevant Reddit communities (if it adds value, not just self-promotion)
5. Submit technical posts to Hacker News
6. Include in your next newsletter

## Output Format

Present community strategy as:

```markdown
# Community Building Plan: [App Name]

## Platform Strategy
**Primary:** [Platform] — [Why]
**Secondary:** [Platform] — [Why]

## Building in Public
**Transparency level:** [Fully/Mostly/Selectively/Journey-focused]
**Key themes:** [3-4 topics you'll share about]

## Weekly Content Calendar
| Day | Content | Platform |
|-----|---------|----------|
| Mon | [Type] | [Platform] |
| Wed | [Type] | [Platform] |
| Fri | [Type] | [Platform] |

## Monthly Content
- [ ] Revenue/growth update
- [ ] Blog post: [topic]
- [ ] Retrospective

## Engagement Plan
- Daily: [specific actions, 10-15 min]
- Weekly: [specific actions, 30 min]
- Monthly: [specific actions, 1 hour]

## Community → Users Pipeline
1. [How you'll convert followers to beta testers]
2. [How you'll convert beta testers to users]
3. [How you'll convert users to advocates]

## Metrics to Track
- Followers/subscribers (monthly)
- Engagement rate (weekly)
- Referral traffic to App Store (monthly)
- Community-driven downloads (if trackable)
```

## References

- **press-media/** — For media outreach beyond community
- **app-store/review-response-writer/** — For responding to App Store reviews
- **indie-business/** — For business context around community investment

---
name: indie-business
description: Business fundamentals for indie app developers — LLC/entity setup, taxes, Apple Small Business Program, revenue tracking, hiring contractors, and financial planning for sustainability. Use when user asks about business setup, tax implications, hiring, or financial planning for their app business.
allowed-tools: [Read, Glob, Grep, AskUserQuestion, WebSearch]
---

# Indie Business Operations

Business fundamentals for indie Apple app developers. Covers the non-code aspects of running an app business — entity setup, taxes, revenue tracking, hiring, and financial planning.

**Disclaimer:** This skill provides general guidance, not legal or tax advice. Always consult a qualified accountant or attorney for your specific situation.

## When This Skill Activates

Use this skill when the user:
- Asks about business setup for their app (LLC, S-Corp)
- Wants to understand tax implications of app revenue
- Asks when to form an LLC or incorporate
- Wants guidance on hiring contractors or freelancers
- Asks about financial planning for going indie
- Mentions the Apple Small Business Program
- Wants to understand Apple's payment schedule and revenue tracking

## Process

### Step 1: Gather Context

Ask the user via AskUserQuestion:

1. **Location**: What country/state are you in? (tax implications vary significantly)
2. **Current status**: Full-time employed, part-time indie, or full-time indie?
3. **Revenue level**: Approximate monthly/annual app revenue (or expected if pre-launch)
4. **Business entity**: Do you currently have an LLC or company? Filing as sole proprietor?
5. **Specific question**: What business aspect are you trying to figure out?

### Step 2: Business Entity Options

#### United States

| Entity | Setup Cost | Annual Cost | Liability Protection | Tax Complexity | Best For |
|--------|-----------|-------------|---------------------|---------------|----------|
| Sole Proprietor | $0 | $0 | None | Lowest (Schedule C) | Hobby / early stage / < $10K/year |
| Single-Member LLC | $50-500 (state-dependent) | $0-800/year (state-dependent) | Yes | Low (pass-through) | Most indie developers |
| Multi-Member LLC | $50-500 | $0-800/year | Yes | Medium | Partnerships, co-founders |
| S-Corporation | $100-500 + legal fees | $500-2,000/year (payroll, filings) | Yes | High (payroll + corp return) | Revenue > $80-100K/year |

**Sole Proprietor**
- How: Just start earning. Report on Schedule C of personal tax return.
- Pros: Zero paperwork, zero cost, simplest possible setup.
- Cons: No personal liability protection. Your personal assets are at risk if someone sues.
- When to use: Testing the waters, revenue < $10K/year, minimal risk app (no user data, no health claims).

**Single-Member LLC (Recommended for Most Indie Devs)**
- How: File articles of organization with your state. Get an EIN from the IRS (free).
- Pros: Personal liability protection, flexible tax treatment, professional credibility, separate bank account.
- Cons: Annual state fees ($0 in many states, $800/year in California), must maintain separation between personal and business finances.
- When to upgrade from sole proprietor: Revenue exceeds $10-20K/year, OR you handle user data, OR users rely on your app for health/finance/safety.

**S-Corporation Election**
- How: Form an LLC, then file Form 2553 to elect S-Corp tax treatment.
- Pros: Payroll tax savings on profits above "reasonable salary." At $150K revenue, could save $10-15K/year in self-employment tax.
- Cons: Must pay yourself a "reasonable salary" with payroll, quarterly payroll tax filings, more complex bookkeeping, annual corporate tax return.
- When to consider: Net profit consistently exceeds $80-100K/year.

**When to upgrade entity (decision tree):**
```
Revenue < $10K/year and low-risk app?
├── YES → Sole proprietor is fine
└── NO → Do you handle sensitive user data or have liability risk?
    ├── YES → Form an LLC now
    └── NO → Revenue > $20K/year?
        ├── YES → Form an LLC
        └── NO → Sole proprietor, but plan for LLC soon

Already have an LLC and net profit > $80K/year?
├── YES → Talk to a CPA about S-Corp election
└── NO → Stay as LLC
```

#### United Kingdom

| Entity | Best For |
|--------|----------|
| Sole Trader | Revenue < GBP 50K, simple setup |
| Limited Company (Ltd) | Revenue > GBP 50K, liability protection, tax efficiency |

- Sole trader: Register with HMRC for Self Assessment. Simple but no liability protection.
- Ltd company: Register with Companies House. Corporation tax on profits (25%), then dividend tax on drawings. More tax-efficient at higher revenue.

#### European Union (General Guidance)

- Most EU countries have sole proprietor equivalents and limited liability company options.
- VAT registration thresholds vary by country (but Apple handles VAT on app sales).
- Consider your country's social security implications for self-employment income.
- Consult a local accountant — EU tax rules are country-specific.

#### India

| Entity | Best For |
|--------|----------|
| Sole Proprietor | Starting out, simple |
| LLP (Limited Liability Partnership) | Liability protection, flexible |
| Private Limited Company | Scale, investors, credibility |

- GST registration may be required above threshold (currently INR 20 lakh).
- TDS (Tax Deducted at Source) applies to payments from Apple (check DTAA with Ireland/US).
- Private Limited preferred if you plan to raise investment.

### Step 3: Apple Small Business Program

#### Overview

- Commission reduced from 30% to 15% on the first $1M in annual proceeds.
- Applies to all app and in-app purchase revenue.
- Auto-enrollment: Apple enrolls you when you are eligible. No application needed if under $1M.
- Resets annually on January 1.

#### Impact Calculation

| Annual Revenue | Standard (30%) | Small Business (15%) | You Save |
|---------------|----------------|---------------------|----------|
| $10,000 | $3,000 | $1,500 | $1,500 |
| $50,000 | $15,000 | $7,500 | $7,500 |
| $100,000 | $30,000 | $15,000 | $15,000 |
| $500,000 | $150,000 | $75,000 | $75,000 |
| $1,000,000 | $300,000 | $150,000 | $150,000 |

For year-2+ subscribers, Apple takes only 15% regardless of program enrollment. So the Small Business Program primarily benefits:
- Paid upfront apps
- One-time IAP revenue
- First-year subscription revenue

#### Important Details

- If you exceed $1M in a calendar year, the standard 30% rate applies for the remainder of that year.
- Revenue from all apps under your developer account is combined for the $1M threshold.
- If you have multiple developer accounts (e.g., personal + company), each is evaluated separately.

### Step 4: Tax Basics for App Revenue

#### What Apple Handles (You Don't Need to Worry About)

- **Sales tax / VAT**: Apple collects and remits sales tax, VAT, and equivalent taxes in virtually all jurisdictions. The price users pay includes these taxes, and Apple deducts them before your payout.
- **Tax forms to developers**: Apple provides 1099-MISC (US) or equivalent tax documentation annually.

#### What You Must Handle

**Reporting Income (US)**

Apple pays you monthly. All payouts are taxable income.

| Entity | How to Report | Tax Form |
|--------|--------------|----------|
| Sole Proprietor | Schedule C on personal return (1040) | 1040 + Schedule C + Schedule SE |
| Single-Member LLC | Same as sole proprietor (disregarded entity) | 1040 + Schedule C + Schedule SE |
| Multi-Member LLC | Partnership return | 1065 + K-1s |
| S-Corporation | Corporate return + salary W-2 | 1120-S + W-2 |

**Quarterly Estimated Taxes (US)**

If you expect to owe more than $1,000 in taxes for the year, you must make quarterly estimated payments. Missing these results in penalties.

| Quarter | Covers | Due Date |
|---------|--------|----------|
| Q1 | Jan-Mar | April 15 |
| Q2 | Apr-May | June 15 |
| Q3 | Jun-Aug | September 15 |
| Q4 | Sep-Dec | January 15 (next year) |

**How to estimate:** Take your expected annual net profit, multiply by your effective tax rate (federal + state + self-employment). Divide by 4.

**Deductible Expenses**

These reduce your taxable income. Keep receipts and records for everything.

| Expense | Example | Deductible? |
|---------|---------|------------|
| Apple Developer Program | $99/year | Yes |
| Hardware | Mac, iPhone, iPad for development | Yes (may need to depreciate) |
| Software | Xcode is free, but design tools, analytics, etc. | Yes |
| Hosting | Server costs, API services, CDN | Yes |
| Design | Freelance designer for app icon, screenshots | Yes |
| Marketing | Ad spend, press kit costs | Yes |
| Home office | Portion of rent/mortgage (if dedicated space) | Yes (with rules) |
| Conference travel | WWDC, local meetups | Yes |
| Education | Courses, books, tutorials for development skills | Yes |
| Professional services | Accountant, lawyer fees | Yes |
| Internet | Business portion of home internet | Partially |
| Health insurance (US) | Self-employed health insurance deduction | Yes (if self-employed) |

**International Considerations**

- If you sell apps globally, Apple handles international tax collection.
- US developers: file W-9 with Apple. Non-US developers: file W-8BEN or W-8BEN-E.
- Tax treaties between your country and Ireland/US may reduce withholding.
- Some countries require you to report worldwide income, including Apple payouts.

### Step 5: Revenue Tracking and Bookkeeping

#### Apple's Payment Schedule

- Apple pays monthly, approximately 33 days after the end of their fiscal month.
- Apple's fiscal months don't always align with calendar months (check your agreement).
- Payments are made via direct deposit to your bank account.
- Minimum payout threshold varies by region (often $10-150 depending on country).

#### Bookkeeping Setup

**Option 1: Spreadsheet (Free, < $50K revenue)**

Track monthly:
```
Month | Gross Revenue | Apple Commission | Net Revenue | Expenses | Net Profit
Jan   | $1,200        | $180             | $1,020      | $150     | $870
Feb   | $1,350        | $203             | $1,148      | $99      | $1,049
...
```

Categories to track:
- Gross revenue (total sales)
- Apple commission (15% or 30%)
- Net revenue (what Apple pays you)
- Development expenses
- Marketing expenses
- Tools and services
- Professional services
- Net profit (net revenue minus all expenses)
- Tax set-aside (25-35% of net profit)

**Option 2: Accounting Software ($50K+ revenue or if you want automation)**

| Software | Cost | Best For |
|----------|------|----------|
| Wave | Free | Simple invoicing and tracking |
| QuickBooks Self-Employed | $15/mo | US sole proprietors, auto-categorization |
| QuickBooks Online | $30/mo | LLCs and S-Corps, full accounting |
| Xero | $13/mo | International, clean interface |
| Bench | $249/mo | Full bookkeeping service (they do it for you) |

**Tax Reserve Rule**

Set aside 25-35% of net revenue (after Apple's cut) for taxes.

| Tax Component (US) | Approximate Rate |
|--------------------|-----------------|
| Federal income tax | 12-37% (bracket-dependent) |
| Self-employment tax | 15.3% (on first ~$160K) |
| State income tax | 0-13% (state-dependent) |
| **Combined effective rate** | **25-40%** |

Open a separate savings account. Every time Apple pays you, transfer 30% of the payout into the savings account. Use this account only for quarterly tax payments.

### Step 6: When to Hire

Hiring too early burns cash. Hiring too late burns you out. Use these guidelines.

#### Designers

**When to hire:**
- Your app icon looks amateurish compared to competitors
- Users comment on visual design in reviews
- You have maxed out SF Symbols and system UI components
- You need a marketing website, press kit, or App Store screenshots

**What to pay:**
- App icon: $200-1,000 (one-time)
- Full app design: $2,000-10,000 (one-time)
- Ongoing design: $50-150/hour (contract)

**Where to find:**
- Dribbble, Behance (portfolios)
- Twitter/X indie design community
- Referrals from other indie developers

#### Customer Support

**When to hire:**
- You spend > 5 hours/week on support emails
- Response time > 48 hours (users notice)
- Support is taking time away from development

**What to pay:**
- Part-time VA: $15-30/hour
- Dedicated support: $2,000-4,000/month

**Where to find:**
- Online communities for virtual assistants
- Referrals from other indie developers
- Start with a part-time contractor, not full-time

#### Marketing

**When to hire:**
- You have confirmed product-market fit (good retention)
- You know your acquisition cost and LTV
- Growth is limited by awareness, not product quality

**What to pay:**
- Freelance marketing: $50-150/hour
- ASO consultant: $500-2,000/month
- Content creator: $100-500/post

#### Contract Developers

**When to hire:**
- One-time platform expansion (watchOS, macOS port, widgets)
- Feature that requires expertise you lack (ML, AR, accessibility)
- You want to ship faster for a specific launch window

**What to pay:**
- iOS developer (contract): $75-200/hour
- Specialized (ML, AR): $100-250/hour
- Fixed-price project: define scope clearly, include revisions

#### Budget Rule

Do not hire until you can pay for 3 months from app revenue. Do not use personal savings to hire for a side project. The app should fund its own growth.

```
Can you pay this person for 3 months from app revenue alone?
├── YES → Hire (start with a trial project / 1-month contract)
└── NO → Wait until revenue supports it, or do it yourself
```

### Step 7: Insurance and Liability

#### Professional Liability Insurance (Errors and Omissions)

- Covers claims that your app caused harm due to errors, bugs, or bad advice.
- Cost: $500-1,500/year for indie developers.
- Consider if: your app gives health, financial, or safety-related advice.
- Providers: Hiscox, Hartford, biBERK, general business insurance brokers.

#### Cyber Liability Insurance

- Covers data breach costs (notification, credit monitoring, legal defense).
- Cost: $500-2,000/year depending on data volume.
- Consider if: you store personal user data on your servers.
- Less relevant if: your app is fully offline / on-device only.

#### LLC as Liability Shield

- An LLC separates your personal assets from business liabilities.
- If someone sues your app business, they cannot (generally) take your house or personal savings.
- Must maintain separation: separate bank account, do not commingle funds, sign contracts as the LLC.
- An LLC does NOT protect you from personal negligence or fraud.

### Step 8: Financial Planning for Indie Sustainability

#### Before Going Full-Time Indie

Checklist:
- [ ] 6 months of personal expenses saved (emergency fund)
- [ ] App revenue covers at least 50% of personal expenses (and growing)
- [ ] Health insurance sorted (US: marketplace, spouse's plan, or COBRA)
- [ ] Tax situation understood (talked to CPA)
- [ ] Spouse/partner on board with the plan and timeline
- [ ] Defined a "go back" threshold (if revenue drops below $X for Y months)

#### Revenue Milestones

| Monthly Net Revenue | What It Means | Action |
|--------------------|---------------|--------|
| $100-500/mo | Hobby money | Reinvest in tools, keep your day job |
| $500-2,000/mo | Side income | Cover app-related expenses, start saving |
| $2,000-5,000/mo | Part-time viable | Could reduce day job hours (if flexible) |
| $5,000-10,000/mo | Full-time viable (LCOL) | Full-time possible with lower cost of living |
| $10,000+/mo | Full-time viable (most areas) | Sustainable indie business |

Note: These are NET revenue figures (after Apple's cut and expenses, before taxes). Adjust for your location's cost of living.

#### Multiple Revenue Streams

Do not depend on a single app for your entire income. Strategies for diversification:

| Stream | Effort | Revenue Potential | Risk |
|--------|--------|-------------------|------|
| Second app | High | High | Platform risk |
| Consulting/freelancing | Medium | Medium-High | Time-limited |
| Technical writing | Low-Medium | Low-Medium | Consistent |
| Course/tutorial creation | High (upfront) | Medium (recurring) | One-time effort |
| Open source sponsorship | Low | Low | Unpredictable |
| Conference speaking | Low | Low (+ networking) | Seasonal |

**Recommended portfolio for sustainability:**
- 1-2 apps generating recurring revenue (primary income)
- Part-time consulting/freelancing (stable fallback)
- Content creation / writing (builds authority, generates leads for consulting)

#### Runway Calculation

```
Monthly personal expenses:        $______
Monthly app net revenue:           $______
Monthly consulting revenue:        $______
Total monthly income:              $______

Monthly surplus/deficit:           $______ (income - expenses)
Emergency fund balance:            $______
Runway (months):                   emergency fund / monthly expenses = ______ months

Sustainability ratio:              monthly income / monthly expenses = ______
                                   > 1.0 = sustainable
                                   > 1.5 = comfortable
                                   > 2.0 = thriving
```

## Output Format

Present business guidance as:

```markdown
# Indie Business Assessment: [User's Situation]

## Current Status
**Location:** [Country/State]
**Entity:** [Current entity type]
**Revenue:** [Approximate level]
**Status:** [Full-time employed / Part-time indie / Full-time indie]

## Recommendations

### Business Entity
**Recommendation:** [Entity type]
**Why:** [1-2 sentences]
**Action items:**
1. [Step 1]
2. [Step 2]
3. [Step 3]

### Tax Obligations
- [ ] [Specific tax obligation based on their situation]
- [ ] [Another obligation]
**Estimated tax rate:** [X-X%]
**Quarterly payment amount:** ~$[X]

### Financial Health
| Metric | Current | Target |
|--------|---------|--------|
| Monthly net revenue | $X | $X |
| Expense ratio | X% | < 30% |
| Tax reserve | $X | $X |
| Emergency fund | X months | 6 months |
| Sustainability ratio | X.X | > 1.5 |

### Next Steps (Priority Order)
1. 🔴 [Most urgent action]
2. 🟠 [Important but not urgent]
3. 🟡 [Plan for this quarter]
```

## References

- **analytics-interpretation/** — For understanding if your metrics support business decisions
- **monetization/** — For pricing strategy and revenue model selection
- **community-building/** — For organic growth that reduces acquisition costs
- Apple Small Business Program: https://developer.apple.com/app-store/small-business-program/

# Pitch Templates

Email templates for press and media outreach. Customize every template for each recipient — generic mass emails get ignored.

## General Tips (Apply to All Templates)

- **Subject line**: Keep under 60 characters, include app name, be specific
- **Opening line**: Reference something the journalist recently wrote or covered — proves you did your homework
- **Body**: Under 200 words total. Journalists receive hundreds of emails daily.
- **One screenshot inline**: Embed one compelling screenshot directly in the email (not as attachment)
- **Links**: Include App Store link, press kit link, TestFlight link (if pre-launch)
- **Call to action**: One clear ask — "Would you like a TestFlight invite?" or "Can I send a promo code?"
- **Signature**: Name, title, website, social media handle

---

## Template 1: Launch Pitch

Use for new app launches. Best sent 2-3 weeks before launch.

```
Subject: [App Name] — [One-Sentence Value Proposition] (launching [date])

Hi [First Name],

I loved your recent piece on [their article/topic] — [brief, genuine comment showing you read it].

I'm reaching out because I'm launching [App Name], a [category] app for [platform] that [one sentence explaining what it does and why it matters].

[App Name] is different because [unique angle — privacy-first / solo developer story / innovative tech use / solves a specific problem]. [One sentence expanding on the story angle.]

Key details:
- Launch date: [date]
- Price: [free / $X.XX / subscription at $X.XX/mo]
- Platforms: [iOS 17+ / macOS 14+]
- Press kit: [URL]

[Embedded screenshot — choose your most visually impressive screen]

I'd love to offer you early access via TestFlight if you're interested. Happy to answer any questions or hop on a quick call.

Best,
[Name]
[Website] | [Twitter/X handle]
```

---

## Template 2: Major Update Pitch

Use for significant feature updates. Best for apps that already have some users.

```
Subject: [App Name] [version] — [headline feature] now available

Hi [First Name],

[App Name] just shipped its biggest update yet, and I thought it might interest you given your coverage of [relevant topic/category].

What's new in [version]:
- [Feature 1]: [one sentence — the hero feature]
- [Feature 2]: [one sentence]
- [Feature 3]: [one sentence]

The headline feature, [Feature 1], lets users [specific benefit]. I built it because [brief story — user request / personal need / new Apple API].

[App Name] now has [social proof — X downloads / X rating / featured by Apple]. This update is free for existing users.

Press kit with new screenshots: [URL]
App Store: [URL]

Would you be interested in taking a look?

Best,
[Name]
[Website] | [Twitter/X handle]
```

---

## Template 3: Story Angle Pitch (Developer Story)

Use when the story is about YOU, not just the product. Best for outlets that cover indie developers.

```
Subject: [Compelling one-line story hook]

Hi [First Name],

I've been following your coverage of indie developers, especially [specific piece they wrote]. I have a story that might resonate with your audience.

[2-3 sentences telling your story — why you built this app, what personal experience drove it, what makes your journey unusual or interesting.]

The result is [App Name], a [category] app that [what it does]. [One sentence on traction or reception — downloads, ratings, user testimonials, Apple feature.]

I'm not just pitching an app — I think there's a story here about [broader theme: indie sustainability / building for accessibility / leaving big tech / solving personal problems with code]. I'd be happy to share more details or do an interview.

App Store: [URL]
Press kit: [URL]

Thanks for considering,
[Name]
[Website] | [Twitter/X handle]
```

---

## Template 4: Podcast Pitch

Use for podcast hosts. Keep it shorter — they need to see interview value, not just app features.

```
Subject: Podcast guest pitch — [one-line hook about your story]

Hi [Host Name],

I'm a listener of [Podcast Name] and particularly enjoyed your episode about [specific episode]. [One genuine sentence about why it resonated.]

I'm [Name], an indie developer who [brief personal hook — quit FAANG / built app while traveling / went from zero to $X revenue / overcame specific challenge]. I recently launched [App Name], a [category] app that [one sentence].

I think your listeners would enjoy hearing about:
- [Topic 1 — something practical they can learn from]
- [Topic 2 — a challenge you faced and how you solved it]
- [Topic 3 — a broader insight about indie development]

I'm comfortable on mic and can keep things conversational. Happy to work around your schedule.

Best,
[Name]
[App Name] — [URL]
[Twitter/X handle]
```

---

## Template 5: Follow-Up

Use exactly once, 5-7 business days after the initial pitch. Add new information — do not just repeat the original pitch.

```
Subject: Re: [original subject line]

Hi [First Name],

I wanted to follow up on my email from last week about [App Name].

Since then, [add one piece of new information]:
- "[App Name] was just featured in [Apple editorial / another outlet / award]"
- "We hit [milestone — 1,000 downloads / 4.8 star rating / featured by Apple]"
- "I just shipped [new feature] that I think adds to the story"
- "A user shared this testimonial: '[brief quote]'"

If the timing isn't right or [App Name] isn't a fit for your coverage, no worries at all — I appreciate your time either way.

Press kit: [URL]
TestFlight: [URL]

Best,
[Name]
```

---

## Personalization Checklist

Before sending ANY pitch, verify:

- [ ] Used the journalist's first name (spelled correctly)
- [ ] Referenced a specific recent article they wrote
- [ ] Explained why THIS journalist is the right person for THIS story
- [ ] Kept total email under 200 words
- [ ] Included one inline screenshot
- [ ] Included press kit and App Store links
- [ ] Proofread for typos (nothing kills credibility faster)
- [ ] Sent on Tuesday-Thursday, 9-11 AM in their time zone
- [ ] Subject line is specific and under 60 characters

## What NOT to Do

- Do not send identical emails to multiple journalists at the same outlet
- Do not CC or BCC multiple journalists (always individual emails)
- Do not attach large files (link to press kit instead)
- Do not use "Dear Sir/Madam" or "To whom it may concern"
- Do not send more than one follow-up
- Do not pitch on the same day as a major Apple event
- Do not ask "did you get my email?" — it's passive-aggressive
- Do not offer payment for coverage (violates journalistic ethics)
- Do not get upset or respond negatively if they don't cover you

---
name: press-media
description: Get press coverage and media attention for your indie app. Covers press kit preparation, finding journalists/bloggers/YouTubers, pitch timing, embargo strategy, and story angles that get coverage. Use when user wants press coverage, is preparing for a launch, or wants to build a media kit.
allowed-tools: [Read, Write, Glob, Grep, AskUserQuestion, WebSearch]
---

# Press & Media Outreach

Get press coverage and media attention for your indie Apple app. Covers everything from press kit preparation to finding the right journalists to crafting pitches that get responses.

## When This Skill Activates

Use this skill when the user:
- Wants press coverage for their app
- Is preparing for a launch and wants PR
- Wants to create a media kit or press kit
- Is looking for reviewers, bloggers, or YouTubers
- Asks about getting featured by Apple-focused outlets
- Wants to pitch their app to podcasts

## Process

### Step 1: Gather Context

Ask the user via AskUserQuestion:

1. **App details**: What does the app do? What platform(s)?
2. **Launch timing**: When is/was the launch? Is this a new app or major update?
3. **Story angle**: What makes this app unique or interesting?
4. **Previous coverage**: Have you been covered before? Any existing press kit?
5. **Budget**: Any budget for PR, or purely organic outreach?

### Step 2: Press Kit Preparation

A press kit makes it easy for journalists to write about your app. If they have to hunt for information, they will skip you.

#### Required Assets

| Asset | Specification | Notes |
|-------|--------------|-------|
| App icon | 1024x1024 PNG, no rounded corners | Journalists crop it themselves |
| Screenshots | 5-8 key screens, with and without device frames | Both raw and framed versions |
| App description (short) | 1 sentence, < 150 characters | For quick mentions |
| App description (medium) | 1 paragraph, 3-4 sentences | For brief coverage |
| App description (long) | 3 paragraphs | For feature articles |
| Developer bio | 2-3 sentences about you | Include relevant background |
| Developer photo | Headshot, 800x800+ | Professional but approachable |
| Fact sheet | Structured data | See template below |
| Promo video | 30-60 seconds (optional) | Dramatically increases coverage odds |

#### Fact Sheet Template

```
APP NAME: [Name]
DEVELOPER: [Your Name / Company]
LAUNCH DATE: [Date or "Available Now"]
PRICE: [Free / $X.XX / Free with subscription ($X.XX/mo)]
PLATFORMS: [iOS / macOS / iPadOS / watchOS / visionOS]
REQUIREMENTS: [iOS 17+ / macOS 14+]
WEBSITE: [URL]
APP STORE: [App Store link]
PRESS KIT: [URL to downloadable press kit]
CONTACT: [press@yourdomain.com]

KEY FEATURES:
- [Feature 1]: [One sentence description]
- [Feature 2]: [One sentence description]
- [Feature 3]: [One sentence description]
- [Feature 4]: [One sentence description]
- [Feature 5]: [One sentence description]

WHAT MAKES IT DIFFERENT:
[2-3 sentences on unique value proposition]
```

#### Press Kit Hosting Options

| Option | Cost | Pros | Cons |
|--------|------|------|------|
| presskit.html on your website | Free (hosting cost) | Professional, SEO benefits | Requires web dev |
| Notion page | Free | Easy to update, looks clean | Less professional URL |
| GitHub repo | Free | Easy asset downloads | Slightly technical feel |
| presskit() generator | Free | Industry standard format | Template-based |
| Dedicated presskit page | Free-$10/mo | Purpose-built for press kits | Another service to manage |

**Recommendation:** A simple `/press` page on your website with downloadable ZIP of all assets. Include everything inline so journalists can copy-paste without downloading.

### Step 3: Finding Relevant Journalists and Outlets

Build a targeted list of 20-30 contacts. Quality over quantity — 20 personalized pitches outperform 200 generic ones.

#### Apple-Focused Outlets

**Tier 1 — Major Coverage (hardest to get, biggest impact)**
| Outlet | Focus | Best For |
|--------|-------|----------|
| MacStories | In-depth iOS/Mac app reviews | Thoughtful, well-designed apps |
| 9to5Mac | Apple news and app coverage | News-worthy launches and updates |
| The Verge | Tech culture and reviews | Apps with broad appeal |
| TechCrunch | Startup and tech news | Apps with a business/funding angle |
| Daring Fireball | Apple commentary | Apps John Gruber would personally use |

**Tier 2 — Focused Coverage (more accessible, strong reach)**
| Outlet | Focus | Best For |
|--------|-------|----------|
| iMore | Apple ecosystem guides | How-to and practical apps |
| Six Colors | Apple analysis (Jason Snell) | Productivity and creative tools |
| Club MacStories | App discovery | Polished, design-forward apps |
| TUAW / Cult of Mac | Apple enthusiast coverage | Consumer-friendly apps |
| Indie App Santa | Indie app promotion | Well-designed indie apps |

**Tier 3 — Niche and Community (most accessible, targeted reach)**
| Outlet | Focus | Best For |
|--------|-------|----------|
| SwiftUI Weekly / iOS Dev Weekly | Developer newsletters | Developer tools and technical apps |
| Product Hunt | Launch platform | Any new app launch |
| Hacker News | Tech community | Technical or privacy-focused apps |
| Category-specific blogs | Niche audiences | Apps serving specific verticals |

#### YouTube Reviewers

Search for "best iOS apps" or "best Mac apps" on YouTube. Look for:
- Channels with 10K-500K subscribers (large enough for reach, small enough to respond)
- Recent uploads (active channel)
- Previous indie app coverage (not just major apps)
- Professional review style (not just listicles)

#### Podcast Hosts

| Podcast | Focus | Format |
|---------|-------|--------|
| AppStories (MacStories) | App discovery and discussion | Weekly discussion |
| Launched (Charlie Chapman) | Indie developer stories | Interview |
| Under the Radar (Marco/David) | Indie development | Discussion |
| Stacktrace | Apple dev and design | Discussion |
| Core Intuition (Jalkut/Simmons) | Indie Mac/iOS | Discussion |
| Accidental Tech Podcast | Apple tech (if relevant) | Discussion |

### Step 4: Pitch Timing

#### When to Reach Out

| Timing | Action |
|--------|--------|
| 3-4 weeks before launch | Reach out to Tier 1 outlets for exclusive/embargo |
| 2-3 weeks before launch | Broader outreach to Tier 2 and 3 |
| 1 week before launch | Follow up with non-responders (once only) |
| Launch day | Share on social media, Product Hunt, Hacker News |
| 1 week after launch | Thank journalists who covered you |

#### Best Days and Times
- **Best days:** Tuesday, Wednesday, Thursday
- **Best time:** 9-11 AM in the journalist's time zone
- **Worst days:** Monday (inbox overload), Friday (winding down)
- **Avoid:** Major Apple events (WWDC, iPhone launch, iPad event), CES week, holiday weeks

#### Follow-Up Cadence
- Send initial pitch
- Wait 5-7 business days
- Send ONE follow-up (add new info or angle, don't just repeat)
- If no response after follow-up, move on — do NOT keep emailing
- Never guilt-trip or get frustrated in follow-ups

### Step 5: Embargo Strategy

Embargoes let you give journalists early access in exchange for coordinated coverage on launch day.

#### Exclusive Strategy (Tier 1)
1. Pick ONE top-tier outlet that covers your app's category
2. Offer 1-2 week exclusive access before launch
3. Provide TestFlight build, press kit, and personal demo offer
4. Agree on publish date (your launch day)
5. Benefits: deep review, stronger relationship, headline coverage

#### Broader Embargo (Tier 2-3)
1. After exclusive is confirmed, invite 5-10 outlets under embargo
2. Set clear embargo lift date and time (usually launch day, 9 AM ET)
3. Include TestFlight link and press kit
4. Benefits: wave of coverage on launch day

#### Rules of Embargoes
- Always put embargo date/time in writing
- Honor the exclusive — don't give the same story to competitors
- If someone breaks embargo, never work with them again
- Be understanding if a small outlet publishes early by accident

### Step 6: Story Angles That Get Coverage

Journalists don't write about apps — they write about stories. Frame your pitch around a story, not a feature list.

#### Story Angles That Work for Indie Developers

**The Solo Developer Story**
- "I quit my job at [Big Tech] to build the app I always wanted"
- "I built this while recovering from [life event]"
- "A 22-year-old student built a top-rated [category] app"
- Why it works: readers love underdog stories

**Scratching Your Own Itch**
- "I couldn't find a [category] app that [specific need], so I built one"
- "As a [profession], I needed [specific tool] — it didn't exist"
- Why it works: authentic, relatable, shows deep domain knowledge

**Innovative Apple Technology Use**
- "First app to use [new iOS/macOS feature]"
- "Built entirely with SwiftUI and [new framework]"
- "Uses on-device ML for [clever application]"
- Why it works: Apple-focused outlets love showcasing platform capabilities

**Privacy-First Alternative**
- "A [category] app that keeps your data on your device"
- "No accounts, no servers, no tracking"
- Why it works: privacy is a hot topic, especially for Apple audience

**Accessibility Champion**
- "Designed VoiceOver-first for visually impaired users"
- "Built to help people with [condition]"
- Why it works: feel-good story, Apple values accessibility

**Design Excellence**
- "What happens when a designer builds their own app"
- Award-worthy UI/UX (Apple Design Awards angle)
- Why it works: Apple-focused outlets value design deeply

#### Story Angles That Do NOT Work
- "My app is better than [competitor]" — sounds petty
- "My app has 50 features" — feature lists are boring
- "My app is the best [category] app" — let reviewers decide
- "I need coverage to grow" — journalists are not your marketing team
- "Check out my app" (no angle at all) — gives them nothing to write about

### Step 7: After Coverage

#### When You Get Coverage
1. Thank the journalist publicly (tweet/post) and privately (email)
2. Share the article on all your channels
3. Add "As featured in..." to your App Store description and website
4. Screenshot the coverage for future press kit
5. Note which angle worked — use it for future pitches

#### When You Don't Get Coverage
- Do NOT send angry or disappointed emails
- Evaluate: was the pitch personalized? Was the timing right? Was the angle strong?
- Try a different angle next time (update, milestone, seasonal)
- Build the relationship anyway — comment on their articles, engage on social media
- Remember: most pitches don't get responses. A 10-20% response rate is normal.

## Reference Files

See **pitch-templates.md** for:
- Launch pitch email template
- Update/feature pitch template
- Story angle pitch template
- Podcast pitch template
- Follow-up template

## Output Format

Present outreach plan as:

```markdown
# Press Outreach Plan: [App Name]

## Press Kit Status
- [ ] App icon (1024x1024)
- [ ] Screenshots (X screens, framed and raw)
- [ ] Description (short / medium / long)
- [ ] Developer bio and photo
- [ ] Fact sheet
- [ ] Press kit hosted at [URL]

## Story Angle
**Primary:** [The main story angle]
**Secondary:** [Backup angle if primary doesn't land]

## Target List (20-30 contacts)

### Tier 1 — Exclusive Target
| Outlet | Contact | Why Them |
|--------|---------|----------|
| [outlet] | [name] | [reason] |

### Tier 2 — Embargo Group
| Outlet | Contact | Why Them |
|--------|---------|----------|
| ... | ... | ... |

### Tier 3 — Broad Outreach
| Outlet | Contact | Why Them |
|--------|---------|----------|
| ... | ... | ... |

## Timeline
| Date | Action |
|------|--------|
| [T-3 weeks] | Send exclusive pitch to Tier 1 |
| [T-2 weeks] | Send embargo pitches to Tier 2 |
| [T-1 week] | Send broad pitches to Tier 3, follow up Tier 1 |
| [Launch day] | Embargo lifts, social media push, Product Hunt |
| [T+1 week] | Thank journalists, share coverage |

## Pitch Drafts
[See pitch-templates.md for templates, customize for each contact]
```

## References

- **pitch-templates.md** — Email templates for all pitch types
- **community-building/** — For organic promotion via social media
- **app-store/** — For optimizing the product page journalists will link to

---
name: growth
description: Growth skills for indie Apple developers — user acquisition, analytics interpretation, press/media outreach, community building, and indie business operations. Use when user asks about growing their app, understanding metrics, getting press coverage, or running an indie dev business.
allowed-tools: [Read, Glob, Grep, AskUserQuestion, WebSearch]
---

# Growth Skills

Growth skills for indie Apple developers — from analytics interpretation to press outreach to community building. Covers the non-code aspects of building a sustainable app business.

## When This Skill Activates

Use this skill when the user:
- Asks about growing their app or user acquisition
- Wants to understand app metrics or analytics
- Asks about press/media outreach or getting reviews
- Wants to build a community around their app
- Asks about indie business operations (LLC, taxes, hiring)
- Mentions growth strategy, marketing, or user engagement
- Wants data-driven guidance on what to improve next

## Available Skills

### analytics-interpretation/
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention curves, LTV/ARPU, App Store Connect analytics, funnel analysis (AARRR), cohort analysis, and decision trees for what to fix based on which metric is underperforming.

### press-media/
Get press coverage and media attention for your app. Covers press kit preparation, finding relevant journalists/bloggers/YouTubers, pitch timing and embargo strategy, indie developer story angles, and email templates for outreach.

### community-building/
Build and engage a user community around your app. Covers platform selection (Twitter/X, Mastodon, Reddit, Discord), building in public strategy, content calendars for solo developers, and converting community members into advocates.

### indie-business/
Business fundamentals for indie app developers. Covers business entity setup (LLC, S-Corp), Apple Small Business Program, tax basics for app revenue, revenue tracking, when to hire, and financial planning for indie sustainability.

## How to Use

1. Identify what growth stage the user is at:
   - **Pre-launch**: press-media (prepare press kit), community-building (build anticipation)
   - **Just launched**: analytics-interpretation (baseline metrics), press-media (launch outreach)
   - **Growing**: analytics-interpretation (optimize funnel), community-building (scale engagement)
   - **Established**: indie-business (formalize operations), analytics-interpretation (advanced cohorts)
2. Read the relevant sub-skill's SKILL.md for detailed workflow
3. Ask clarifying questions about the user's app, audience, and current metrics
4. Provide actionable guidance tailored to their specific situation