Skip to content

borghei/Claude-Skills / project-management/gtm/gtm-strategy

gtm-strategy

Verified

Builds and audits a go-to-market plan: beachhead, motion matched to ACV, funded channels, tested messaging, owned metrics and a T-90 launch sequence. Use when launching a product, entering a segment or fixing a stalled GTM.

assets/gtm_strategy_template.md

View on GitHub
# GTM Strategy — Template

**GTM name:** [product / launch]
**Target launch date:** [date]
**Strategy version:** [vN]
**As of:** [date]

---

## 1. ICP

- **Size band:**
- **Vertical:**
- **Geography:**
- **Buyer role:**
- **JTBD:**
- **Trigger event (why now):**
- **Tech-stack signals:**
- **Specific enough?** yes / no

## 2. Beachhead segment

> [Sharp description of the first concentrated market]

Why this beachhead:
- Concentrated:
- Reachable:
- Underserved:
- Pain magnitude:
- Big-enough:
- Small-enough-to-dominate:

## 3. Motion

- **Primary motion:** PLG / sales-led / marketing-led / channel-led / community-led / hybrid
- **Avg ACV (target):** $
- **Why this motion:** [match to ACV + complexity + buyer]

## 4. Channels

| Channel | Owner | Budget allocated | Test plan |
|---------|-------|------------------|-----------|
| | | yes/no | |
| | | | |

(2-4 channels max with real investment)

## 5. Messaging

- **Hero message:** [1 sentence, outcome-focused, < 120 chars]
- **Differentiator vs alternative(s):** [specific]
- **Tested with N customers?** [interview / paid test]

### Per-persona talk tracks

| Persona | Talk track |
|---------|------------|
| | |
| | |

### Competitive battlecards

| Competitor | Win themes | Common objections | Response |
|------------|-----------|-------------------|----------|
| | | | |

## 6. Success metrics

| Metric | Target | Owner | Cadence |
|--------|--------|-------|---------|
| Pipeline generated | $ in N days | | weekly |
| Closed-won | $ in N days | | weekly |
| Conversion (stage → stage) | % | | weekly |
| NPS from new customers | | | monthly |
| CAC payback | < N months | | quarterly |

## 7. Launch sequence (T-90 → T+90)

### T-90
- [ ] ICP locked
- [ ] Positioning v1
- [ ] Pricing finalized
- [ ] Lighthouse customer pipeline (5+ candidates)
- [ ] Press / analyst targets identified

### T-60
- [ ] Collateral ready (deck, demo, 1-pager, battlecards, ROI calc)
- [ ] Sales playbook v1
- [ ] Lighthouse customers signed up (3+)
- [ ] Webinar / event scheduled

### T-30
- [ ] Sales kickoff complete
- [ ] Analyst pre-briefings
- [ ] Press kit + embargoed releases
- [ ] Internal all-hands

### T-7
- [ ] Final comms reviewed
- [ ] War room set up
- [ ] Dashboards live
- [ ] Crisis comms drafted

### T-0
- [ ] Launch executes
- [ ] Real-time monitoring active

### T+7
- [ ] First-week review
- [ ] Quick collateral fixes

### T+30
- [ ] First-wave learnings
- [ ] Channel reallocation
- [ ] Sales playbook v2

### T+90
- [ ] GTM v2 incorporating learnings
- [ ] Beachhead success review
- [ ] Next beachhead identified

## 8. Budget

| Category | Amount | % |
|----------|--------|---|
| PR + analyst | $ | |
| Paid acquisition | $ | |
| Content + video | $ | |
| Events | $ | |
| Enablement + tooling | $ | |
| **Total** | $ | 100% |

## 9. Risks + mitigation

| Risk | Likelihood | Severity | Mitigation | Owner |
|------|-----------|----------|------------|-------|
| | | | | |

## 10. Cross-functional alignment

| Function | Owner | Role |
|----------|-------|------|
| Product | | Roadmap + positioning + lighthouse success |
| Marketing | | Demand gen + content + PR |
| Sales | | Pipeline + close + reference development |
| CS | | Onboarding + reference maintenance |
| Finance | | Budget + metric tracking + forecast |
| CEO | | Analyst + 1-2 lighthouse exec relationships |

Weekly GTM standup: [day + time]

## 11. Approval

- [ ] PM
- [ ] Marketing
- [ ] Sales
- [ ] CS
- [ ] Finance
- [ ] CEO
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall