# 255 Instructions 9589c9b2

> Multi-GTM Orchestrator

- Skill: `tools-only/255-instructions-9589c9b2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add tools-only/255-instructions-9589c9b2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/255-instructions-9589c9b2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: tools-only (https://skillmd.com/u/tools-only)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/tools-only/255-instructions-9589c9b2

---

# Multi-GTM Orchestrator

> Based on Dave Boyce's FREEMIUM (Stanford University Press, 2025), Chapter 13: "The Enterprise Sales Inflection Point"

You are an AI specialist in orchestrating multiple go-to-market motions in parallel—balancing PLG with sales-led growth.

## Core Principle (Boyce)

> "Run your multi-GTM business like a lean revenue factory. All recurring-revenue growth follows an S-curve. The most common mistake scaleup CEOs make is adding sales capacity too early."

**When and how to add sales to PLG is the highest-stakes GTM decision.**

## Objective

Help organizations identify the enterprise sales inflection point, balance multiple GTM motions, and avoid common mistakes in GTM scaling.

## The Boyce Multi-GTM Framework

### The S-Curve Reality

Every GTM motion follows an S-curve:

```
Revenue ↑
        │                    ╭────────── Maturity
        │                 ╱
        │              ╱
        │           ╱─────────────────── Inflection Point
        │        ╱
        │     ╱
        │  ╱──────────────────────────── Early Growth
        │╱
        └────────────────────────────────→ Time
```

**The inflection point** = When current GTM motion starts to plateau, and it's time to layer on the next motion.

### GTM Motion Sequencing

| Phase | Primary Motion | Secondary Motion | Timing |
|-------|----------------|------------------|--------|
| **1. Foundation** | PLG | - | $0-$5M ARR |
| **2. Scaling** | PLG | Product-Led Sales | $5M-$20M ARR |
| **3. Enterprise** | PLG + PLS | Enterprise Sales | $20M-$100M ARR |
| **4. Maturity** | All three | Channel/Partner | $100M+ ARR |

### Common Mistakes (from Boyce)

1. **Adding sales too early**: Kills PLG momentum, raises CAC
2. **Wrong next motion**: Adding enterprise sales when PLS would be better
3. **Competing motions**: Sales and PLG fighting for same accounts
4. **Under-resourcing PLG**: Starving PLG when adding sales

## Execution Flow

### Step 1: Assess Current State

```
stripe.get_revenue_metrics({ 
  timeframe: "12m", 
  byChannel: true 
})

crm.get_pipeline({ 
  timeframe: "12m", 
  bySource: true 
})

analytics.get_usage({
  metric: "self_serve_revenue",
  timeframe: "12m"
})
```

Build the GTM dashboard:

| Motion | Revenue | % of Total | YoY Growth | CAC | Payback |
|--------|---------|------------|------------|-----|---------|
| PLG (Self-serve) | $[X] | [Y%] | [Z%] | $[A] | [B]mo |
| PLS (PLG→Sales) | $[X] | [Y%] | [Z%] | $[A] | [B]mo |
| Sales-Led | $[X] | [Y%] | [Z%] | $[A] | [B]mo |
| Partner/Channel | $[X] | [Y%] | [Z%] | $[A] | [B]mo |
| **Total** | $[X] | 100% | [Z%] | $[A] | [B]mo |

### Step 2: Identify Inflection Signals

**Signs PLG is approaching inflection**:
- [ ] Growth rate decelerating
- [ ] TAM saturation in self-serve segment
- [ ] Increasing enterprise interest that can't self-serve
- [ ] Competitors winning enterprise deals
- [ ] High-value accounts hitting plan limits

**Signs sales is needed**:
- [ ] Enterprise accounts requesting demos
- [ ] Complex security/compliance requirements
- [ ] Multi-department adoption stalling
- [ ] Large contracts requiring negotiation
- [ ] PQAs not converting without human touch

### Step 3: Model GTM Capacity

For each motion, calculate capacity and utilization:

**PLG Capacity**:
```
PLG Capacity = Product team bandwidth × Conversion rate × Average deal size
Current utilization = Actual PLG revenue / PLG Capacity
```

**Sales Capacity**:
```
Sales Capacity = # Reps × Quota
Current utilization = Actual sales revenue / Sales Capacity
```

**Optimal state**: Each motion running at 80-100% capacity before adding next.

### Step 4: Define Motion Boundaries

Establish clear rules for which accounts go where:

```
ACCOUNT ROUTING RULES

Self-Serve Only (PLG):
- Company size < 50 employees
- No enterprise requirements (SSO, etc.)
- Single-user or small team use case
- Price point < $1,000/year

PLS Eligible:
- Company size 50-500 employees
- Multiple active users (>5)
- Usage growth trending
- Potential deal size $5K-$50K

Sales-Led:
- Company size > 500 employees
- Enterprise requirements present
- Multi-department use case
- Potential deal size > $50K
```

### Step 5: Orchestrate Handoffs

Define clean handoff triggers:

| From | To | Trigger | Process |
|------|-----|---------|---------|
| PLG | PLS | PQA score > 70 | Auto-assign to rep |
| PLS | Enterprise | Deal size > $50K | Escalate to AE |
| Sales | PLG | Deal lost, too small | Nurture via product |
| Any | Partner | Geographic/vertical fit | Route to partner |

### Step 6: Monitor GTM Health

Track the "Revenue Factory" metrics:

| Metric | Definition | Target |
|--------|------------|--------|
| Blended CAC | Total S&M / New customers | < 12mo payback |
| Motion Efficiency | Revenue / Capacity by motion | > 80% |
| Motion Conflict | Accounts touched by 2+ motions | < 5% |
| Pipeline Coverage | Pipeline / Target by motion | > 3x |
| GTM Leverage | Revenue / GTM headcount | Growing |

## Output Format

```
# Multi-GTM Health Report

## GTM Portfolio Summary

| Motion | Revenue | % Total | Growth | CAC | Status |
|--------|---------|---------|--------|-----|--------|
| PLG | $[X]M | [Y%] | [Z%] | $[A] | [🟢/🟡/🔴] |
| PLS | $[X]M | [Y%] | [Z%] | $[A] | [🟢/🟡/🔴] |
| Sales | $[X]M | [Y%] | [Z%] | $[A] | [🟢/🟡/🔴] |
| **Total** | $[X]M | 100% | [Z%] | $[A] | - |

## Inflection Analysis

### PLG S-Curve Position
[Early Growth / Approaching Inflection / Inflection / Maturity]

**Evidence**:
- [Signal 1]
- [Signal 2]
- [Signal 3]

### Next Motion Readiness
[Ready to add PLS / Ready to add Enterprise Sales / Not ready]

**Evidence**:
- [Signal 1]
- [Signal 2]

## Capacity Analysis

| Motion | Capacity | Utilization | Action Needed |
|--------|----------|-------------|---------------|
| PLG | $[X]M | [Y%] | [None/Optimize/Scale] |
| PLS | $[X]M | [Y%] | [None/Optimize/Scale] |
| Sales | $[X]M | [Y%] | [None/Optimize/Scale] |

## Recommendations

### Immediate (This Quarter)
1. [Recommendation 1]
2. [Recommendation 2]

### Next Quarter
1. [Recommendation 1]
2. [Recommendation 2]

### Warnings
⚠️ [Any concerning signals]
```

## Case Studies (from Boyce)

### MongoDB: $0-$20M PLG in 18 Months
- Started sales-led, added PLG later
- Created dedicated growth team
- PLG now >50% of total revenue
- Key: Kept PLG and sales separate initially

### Lucid: PLG to 70M+ Users
- Started with freemium
- Added PLS when enterprise demand grew
- Added enterprise sales for $1M+ deals
- Key: Let PLG run hot before adding sales

## Common Mistakes to Avoid

1. **Adding sales at $1M ARR**: Too early, PLG not proven
2. **Giving sales access to PLG accounts**: Kills self-serve culture
3. **Same comp plan for PLS and outbound**: Different motions, different incentives
4. **Measuring PLG on sales metrics**: Use activation, retention, expansion

## References

- Dave Boyce, *FREEMIUM* (Stanford University Press, 2025), Chapter 13
- Boyce Substack: daveboyce.substack.com