startup-launch

What this skill does

# Startup Launch

Comprehensive guide for launching a successful startup from idea to market.

## The Startup Journey

### Phase Overview

```
PHASE 1: IDEATION (1-2 weeks)
└─→ Problem identification, market research

PHASE 2: VALIDATION (2-4 weeks)
└─→ Customer discovery, problem-solution fit

PHASE 3: MVP DEVELOPMENT (4-12 weeks)
└─→ Minimum viable product, iteration

PHASE 4: LAUNCH PREPARATION (2-4 weeks)
└─→ Go-to-market strategy, pre-launch

PHASE 5: LAUNCH & ITERATE (Ongoing)
└─→ Public release, growth, optimization
```

---

## Phase 1: Ideation

### Problem Discovery

```
Ask yourself:
┌─────────────────────────────────────────┐
│ 1. What problem am I solving?           │
│ 2. Who has this problem?                │
│ 3. How painful is this problem?         │
│ 4. How are people solving it today?     │
│ 5. Why hasn't this been solved yet?     │
└─────────────────────────────────────────┘
```

### Problem Evaluation Matrix

| Criteria               | Score (1-5)                   | Notes        |
| ---------------------- | ----------------------------- | ------------ |
| **Frequency**          | How often does problem occur? | Daily = 5    |
| **Intensity**          | How painful is it?            | Critical = 5 |
| **Willingness to Pay** | Will people pay to solve?     | Yes = 5      |
| **Market Size**        | How many have this problem?   | Large = 5    |
| **Accessibility**      | Can you reach these people?   | Easy = 5     |

**Minimum viable score: 20/25**

### Idea Sources

```
HIGH-SIGNAL sources:
✓ Problems you personally experience
✓ Inefficiencies in your industry
✓ Complaints from friends/colleagues
✓ Existing solutions that frustrate users
✓ Emerging technology applications

LOW-SIGNAL sources:
✗ "Wouldn't it be cool if..."
✗ Building for imaginary users
✗ Copying without understanding
✗ Solutions looking for problems
```

---

## Phase 2: Validation

### Customer Discovery

```
The Mom Test Questions:
┌─────────────────────────────────────────┐
│ ✓ "Tell me about the last time you..."  │
│ ✓ "What have you tried to solve this?"  │
│ ✓ "How much does this cost you?"        │
│ ✓ "Who else should I talk to?"          │
├─────────────────────────────────────────┤
│ ✗ "Would you use this product?"         │
│ ✗ "Do you think this is a good idea?"   │
│ ✗ "How much would you pay?"             │
└─────────────────────────────────────────┘

Rule: Ask about their life, not your idea.
```

### Interview Framework

```
Structure (30-45 minutes):
1. Context (5 min)
   - Their role, situation
   - Relevant background

2. Problem Exploration (15 min)
   - Specific recent examples
   - Current workflow
   - Pain points and workarounds

3. Current Solutions (10 min)
   - Tools they use now
   - Satisfaction level
   - What's missing

4. Value (5 min)
   - Impact of solving this
   - Who else is affected
   - Budget/authority

5. Wrap-up (5 min)
   - Referrals
   - Follow-up permission
```

### Validation Metrics

| Signal                | Indicator           | Strength |
| --------------------- | ------------------- | -------- |
| **Time commitment**   | Agree to interview  | Low      |
| **Referrals**         | Introduce to others | Medium   |
| **Money commitment**  | Pre-order/deposit   | High     |
| **Work commitment**   | Use early prototype | High     |
| **Social commitment** | Public endorsement  | High     |

### Problem-Solution Fit

```
You have problem-solution fit when:
┌─────────────────────────────────────────┐
│ ✓ 10+ interviews with consistent pain   │
│ ✓ People are actively seeking solutions │
│ ✓ Current solutions are inadequate      │
│ ✓ Your solution resonates emotionally   │
│ ✓ People offer to pay or pre-order      │
└─────────────────────────────────────────┘
```

---

## Phase 3: MVP Development

### What is MVP?

```
MVP = Minimum VIABLE Product

Minimum: Smallest possible scope
Viable: Actually solves the core problem

MVP is NOT:
✗ Prototype (doesn't need to work)
✗ Beta (feature-complete)
✗ v1.0 (polished)

MVP IS:
✓ Core value proposition only
✓ Works well enough to learn from
✓ Gets real user feedback fast
```

### MVP Types

| Type               | Description                         | Best For           |
| ------------------ | ----------------------------------- | ------------------ |
| **Concierge**      | Manual service disguised as product | Service businesses |
| **Wizard of Oz**   | Human behind automated facade       | Complex systems    |
| **Landing Page**   | Describe + capture interest         | Demand validation  |
| **Video Demo**     | Show concept in action              | Complex products   |
| **Piecemeal**      | Combine existing tools              | Quick market test  |
| **Single Feature** | One core feature, done well         | Software products  |

### MVP Scoping

```
Feature Prioritization Matrix:
                   HIGH IMPACT
                       │
                       │
    "NICE TO HAVE"     │     "MUST HAVE"
    (Maybe Later)      │     (MVP Core)
                       │
    ───────────────────┼───────────────────
                       │
    "DON'T DO"         │     "LOW-HANGING"
    (Never)            │     (If Time Permits)
                       │
                       │
                   LOW IMPACT
    HIGH EFFORT ───────────────── LOW EFFORT
```

### Development Approach

```
Build in iterations:
┌─────────────────────────────────────────┐
│ Week 1-2: Core flow (ugly but works)    │
│ Week 3-4: User feedback, fixes          │
│ Week 5-6: Polish critical path          │
│ Week 7-8: Prepare for launch            │
└─────────────────────────────────────────┘

Principles:
- Ship ugly, learn fast
- Manual before automated
- Fake it till you make it (but don't lie)
- Measure what matters
```

---

## Phase 4: Launch Preparation

### Pre-Launch Checklist

```
PRODUCT:
□ Core functionality works reliably
□ Critical bugs fixed
□ Basic analytics in place
□ Error handling and recovery
□ Onboarding flow tested

MARKETING:
□ Landing page live
□ Value proposition clear
□ Social proof (if available)
□ Email capture working
□ Launch announcement ready

OPERATIONS:
□ Customer support system
□ Payment processing tested
□ Legal basics (ToS, Privacy)
□ Monitoring/alerting set up
□ Rollback plan ready

COMMUNITY:
□ Early access list built
□ Social media accounts ready
□ Launch partners confirmed
□ Press/influencer outreach done
□ Community channels set up
```

### Launch Strategy Options

| Strategy            | Description                | Best For          |
| ------------------- | -------------------------- | ----------------- |
| **Big Bang**        | Public launch with PR push | Strong network    |
| **Soft Launch**     | Quiet release, iterate     | Uncertain product |
| **Waitlist**        | Build anticipation         | High demand       |
| **Beta Program**    | Limited early access       | Complex products  |
| **Platform Launch** | Product Hunt, etc.         | Consumer products |

### Platform Launches

```
PRODUCT HUNT:
- Launch Tuesday-Thursday
- Ship 12:01 AM PST
- Prepare assets in advance
- Engage all day with comments
- Activate your network

HACKER NEWS:
- Show HN format
- Technical angle works best
- Timing matters less
- Be prepared for criticism
- Engage authentically

REDDIT:
- Find relevant subreddits
- Follow community rules
- Don't be promotional
- Add genuine value
- Use for feedback, not sales
```

---

## Phase 5: Launch & Growth

### Launch Day Checklist

```
MORNING:
□ Verify all systems operational
□ Team on standby for issues
□ Launch announcement posted
□ Monitor analytics dashboard

THROUGHOUT DAY:
□ Respond to all comments/questions
□ Fix critical issues immediately
□ Thank early users personally
□ Capture feedback systematically

EVENING:
□ Compile day's metrics
□ Document learnings
□ Plan next day's activities
□ Celebrate (briefly!)
```

### Key Metrics (Early Stage)

| Metric             | What It Measures        | Target          |
| -------------