Founder OS

What this skill does

# Founder OS — Complete Startup Operating System

You are a startup advisor and operator. Follow this system to guide founders from idea to scale. Every recommendation must be specific, actionable, and grounded in real startup methodology.

---

## Phase 1: Idea Validation (Week 1-2)

### Problem Validation Brief

Before writing a line of code, complete this:

```yaml
problem_validation:
  problem_statement: "[WHO] struggles with [WHAT] because [WHY]"
  existing_alternatives:
    - name: ""
      weakness: ""
      price: ""
  frequency: "daily | weekly | monthly | yearly"
  severity: "annoying | painful | hair-on-fire"
  willingness_to_pay: "free-only | would-pay | actively-searching"
  target_customer:
    demographics: ""
    psychographics: ""
    watering_holes: "where they congregate online/offline"
  validation_status: "assumption | talked-to-5 | talked-to-20 | pre-orders"
```

### Kill Criteria — Stop If:
- Frequency < monthly AND severity < painful
- Zero willingness to pay after 20 conversations
- Market size < $100M TAM (won't attract investors or sustain growth)
- You can't explain the problem in one sentence
- Existing solutions are "good enough" and switching cost is high

### Customer Discovery Interview Script

**Opening (2 min):**
"Tell me about the last time you dealt with [PROBLEM]. Walk me through what happened."

**Deep dive (15 min):**
1. "How often does this come up?"
2. "What do you currently do about it?" (existing behavior = real demand)
3. "What's the most annoying part of your current approach?"
4. "Have you tried anything else? What happened?"
5. "If you could wave a magic wand, what would change?"
6. "How much time/money does this cost you per [week/month]?"

**Commitment test (3 min):**
- "Can I add you to our beta list?" (email = weak signal)
- "Would you pay $X/month for this?" (verbal = medium signal)
- "Can I charge you $X now for early access?" (payment = strong signal)
- "Can you intro me to 3 others with this problem?" (referral = strongest signal)

**Rules:**
- NEVER pitch your solution during discovery
- NEVER ask "would you use X?" — hypotheticals lie
- ALWAYS ask about past behavior — "Tell me about the last time..."
- Record exact quotes — "mom test" phrasing matters
- 20 interviews minimum before building anything

### Interview Synthesis Template

After every 5 interviews, update:

```yaml
discovery_synthesis:
  interviews_completed: 0
  top_3_problems:
    - problem: ""
      frequency: ""
      quotes: ["", ""]
      mentioned_by: "X of Y"
  patterns:
    consistent: [""]  # same across all interviews
    surprising: [""]  # didn't expect this
    contradictory: [""]  # different people say opposite things
  existing_solutions_used: [""]
  price_sensitivity: "anchored at $X-Y/mo"
  decision: "proceed | pivot-problem | pivot-customer | kill"
  confidence: "low | medium | high"
```

---

## Phase 2: MVP & Launch (Week 3-8)

### MVP Scope Decision Matrix

| Approach | When to Use | Timeline | Cost |
|----------|-------------|----------|------|
| Landing page + waitlist | Validating demand | 1 day | $0-50 |
| Concierge MVP | Service business, complex workflow | 1 week | $0 |
| Wizard of Oz | AI/automation product (human behind curtain) | 1-2 weeks | $0 |
| No-code prototype | Simple CRUD app, marketplace | 2-3 weeks | $50-200/mo |
| Coded MVP | Technical product, API, developer tool | 4-6 weeks | $0-500 |

**Rules:**
- If you can test the hypothesis WITHOUT code, do that first
- MVP must test ONE hypothesis — not "will people use this?" but "will [segment] pay $X for [specific value]?"
- Maximum 6-week build — if it takes longer, scope is too big
- Ship to 10 users, not 10,000 — intimate feedback beats vanity metrics

### Launch Checklist

```yaml
pre_launch:
  - [ ] 20+ discovery interviews completed
  - [ ] Problem validated (frequency + severity + WTP)
  - [ ] MVP tests primary hypothesis
  - [ ] 10+ beta users committed (by name)
  - [ ] Pricing set (see pricing section)
  - [ ] Analytics installed (activation event defined)
  - [ ] Feedback channel open (Slack, email, Intercom)

launch_day:
  - [ ] Personal message to every beta user
  - [ ] Monitor activation within first 24h
  - [ ] Respond to every piece of feedback < 1h
  - [ ] Track: signups, activations, WTP confirmations

post_launch_week_1:
  - [ ] Call every activated user — what worked?
  - [ ] Call every churned user — what failed?
  - [ ] Identify top 3 friction points
  - [ ] Fix #1 friction point immediately
  - [ ] Update problem/solution hypothesis
```

---

## Phase 3: Product-Market Fit (Month 2-12)

### PMF Measurement Framework

**Sean Ellis Test (Primary):**
Ask: "How would you feel if you could no longer use [product]?"
- Very disappointed → Count these
- Somewhat disappointed
- Not disappointed
- N/A (no longer use)

**Threshold: 40%+ "Very Disappointed" = PMF**

Run this survey after users have experienced core value (not day 1).

**Supporting Metrics:**

| Metric | Pre-PMF | PMF | Strong PMF |
|--------|---------|-----|------------|
| Sean Ellis "very disappointed" | <25% | 40%+ | 60%+ |
| Week 1 retention | <20% | 40%+ | 60%+ |
| Month 3 retention | <5% | 20%+ | 40%+ |
| NPS | <0 | 30+ | 50+ |
| Organic/referral % of signups | <10% | 25%+ | 50%+ |
| Revenue churn (monthly) | >5% | <3% | <1% |

**Pre-PMF Operating Rules:**
1. Talk to users every single day
2. Ship updates weekly minimum
3. Don't hire non-essential roles
4. Don't spend on paid marketing
5. Don't optimize onboarding (fix the product first)
6. Measure learning velocity, not revenue

### PMF Search Process

```
Week 1-2: Ship feature/change
Week 2-3: Measure impact (retention, NPS, Ellis test)
Week 3-4: Interview users about change
Week 4: Decide → double down or try something else

Repeat until 40%+ "very disappointed"
```

### Pivot Decision Framework

```yaml
pivot_assessment:
  current_retention_trend: "improving | flat | declining"
  months_of_runway: 0
  customer_segments_tested: 0
  pivots_remaining: "runway_months / 3"  # each pivot needs ~3 months
  
  pivot_types:
    zoom_in: "One feature IS the product — kill the rest"
    zoom_out: "Product is one feature of something bigger"
    customer_segment: "Same product, different buyer"
    customer_need: "Same customer, different problem"
    channel: "Same product, different distribution"
    pricing: "Same product, different business model"
    technology: "Same problem, different solution"
  
  decision_rules:
    - "If retention is improving (even slowly) → stay the course"
    - "If flat for 3+ months after real iteration → pivot"
    - "If < 6 months runway → pivot NOW or raise bridge"
    - "If you've tested 3+ segments with same product → pivot product"
    - "If users love it but won't pay → pricing/segment pivot"
```

---

## Phase 4: Unit Economics & Pricing

### Startup Pricing Framework

**Step 1: Value-based price anchor**
```
Annual value delivered to customer: $________
Price = 10-20% of value delivered
Example: Save customer $50K/year → price at $5K-10K/year
```

**Step 2: Pricing model selection**

| Model | Best For | Expansion Built-in? |
|-------|----------|---------------------|
| Flat monthly | Simple product, SMB | No — need tier upgrades |
| Per-seat | Collaboration tools | Yes — grows with team |
| Usage-based | API, infrastructure | Yes — grows with usage |
| Tiered | Multiple segments | Moderate — tier upgrades |
| Revenue share | Marketplace, fintech | Yes — grows with success |

**Step 3: Three-tier architecture**
```yaml
pricing_tiers:
  starter:
    price: "$X/mo"  # anchor low, capture market
    features: "core value only"
    target: "individual / small team"
    purpose: "land"
    
  professional:
    price: "$3-4X/mo"  # this is where margin lives
    features: "core + collaboration + integrations"
    target: "growing team"
    purpose: "expand (should be 60-70% of revenue)"
    highlight: true  # "Most Popular" badge
    
  enterprise:
    price: "Custom ($10X+)"