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.

references/gtm-anti-patterns.md

View on GitHub
# GTM Anti-Patterns + Fixes

## A1 — ICP = "everyone"
**Symptom:** "We help businesses..." with no further specificity.

**Fix:** Sharp ICP (size, vertical, role, JTBD, trigger). See ICP skill.

## A2 — Motion mismatch with ACV
**Symptom:** AE-led sales motion for $500/mo product (unit economics broken).

**Fix:** Match motion to ACV. < $1K = PLG; $250K+ = enterprise sales.

## A3 — Channels listed; not invested
**Symptom:** GTM doc lists 8 channels; budget on 2.

**Fix:** Pick 2-3 channels with real investment. Test before scaling.

## A4 — Generic messaging
**Symptom:** "AI-powered platform for businesses."

**Fix:** Specific outcome + segment + differentiator. Test with 5 ICP customers; iterate.

## A5 — No success metrics
**Symptom:** Launch executed; no agreed success criteria.

**Fix:** Pre-launch agreed metrics (pipeline, signups, NPS, etc.) + targets + tracking.

## A6 — All motions at once
**Symptom:** PLG + sales-led + channel-led from Day 1.

**Fix:** Pick one primary. Add others after primary proves.

## A7 — Launch = press release
**Symptom:** Strategy = "send press release on date X."

**Fix:** Launch is a campaign T-90 → T+90. Multiple touches, multiple audiences.

## A8 — Marketing + sales misaligned
**Symptom:** Marketing generates volume; sales says quality is bad.

**Fix:** Shared MQL/SQL definition. Closed-loop reporting. Weekly sync.

## A9 — Lighthouse customers not engaged
**Symptom:** Launch day without case studies, references, testimonials.

**Fix:** Sign lighthouse customers T-90. Their stories drive launch.

## A10 — No competitive battlecards
**Symptom:** Sales loses deals to known competitors; doesn't know why.

**Fix:** Battlecards per primary competitor with objection handling + win themes.

## A11 — Sales kickoff day-of-launch
**Symptom:** Sales team learns about new offering Day 1.

**Fix:** Sales kickoff T-30. Practice. Test pitches before customer exposure.

## A12 — Post-launch silence
**Symptom:** Launch day spike; nothing in week 2-4.

**Fix:** Drumbeat content + customer stories + paid sustain T+30.

## A13 — Beachhead too broad
**Symptom:** "Mid-market companies in North America" — too broad.

**Fix:** "Mid-market SaaS HR teams (200-2000 EE) in US using Workday" — sharp.

## A14 — No iteration mechanism
**Symptom:** Launch v1 frozen; no plan to learn + iterate.

**Fix:** Pre-commit to GTM v2 at T+90 incorporating learnings.

## A15 — Underestimated launch cost
**Symptom:** Launch budget runs out at T-15 days.

**Fix:** Realistic launch budget T-90. PR + paid + content + events + enablement.

## Worked example — bad → good GTM

### Bad

```
GTM for Acme HR Analytics:
- ICP: HR teams
- Motion: sales
- Channels: marketing
- Messaging: AI HR analytics for everyone
- Metrics: signups
- Launch: blog post on Apr 15
```

Nothing specific. Will underperform.

### Good

```
GTM for Acme HR Analytics — Q3 launch

ICP (beachhead):
- Mid-market US SaaS companies, 200-2000 EE
- HR Director or VP People decision-maker
- Using Workday or BambooHR + ADP/Gusto
- Pain: 40+ hours/month on board HR reports; 8% error rate
- Trigger: just-finished annual reporting cycle; pain fresh

Motion: Sales-led (ACV target $25-100K) + content marketing for inbound

Channels:
- Outbound SDR: 30% (target list: 800 mid-market HR leaders)
- SHRM events: 20% (2 events Q3)
- Content + SEO: 25% (5 articles, focused on board-reporting pain)
- Webinars: 15% (3 webinars Q3 with industry voices)
- Partners: 10% (Workday + BambooHR partner program in pipeline)

Messaging:
- Hero: "Turn 40-hour HR board reports into 30 minutes."
- Per-persona:
  - HR Director: "Stop being the bottleneck on board reporting"
  - CFO: "Reduce HR reporting error rate from 8% to <1%"
  - CHRO: "Strategic HR analytics without hiring a data analyst"
- Positioning vs Workday Insights: "purpose-built for mid-market; ROI in 60 days"
- Positioning vs Excel + analyst: "automated + governed + audit-ready"

Success metrics:
- Pipeline generated: $5M in 90 days (target)
- Closed-won: $1M in 90 days (target)
- Demos to opportunities: 30% (target)
- Lighthouse customers: 3 (signed; references-OK)
- NPS from new customers: 50+ (target)
- CAC payback: <12 months

Launch sequence:
- T-90 (Apr 15): Foundation lock — ICP, pricing, positioning. Lighthouse customers engaged (5 candidates, 3 sign by T-60).
- T-60 (May 15): Collateral ready (deck, demo, ROI calc, 1-pager, battlecards). Sales playbook v1. Webinar scheduled.
- T-30 (Jun 14): Sales kickoff. Pre-briefings with 5 analysts. Press kit ready. Internal all-hands.
- T-7 (Jul 7): Final comms reviewed. Lighthouse customer quotes locked. Crisis comms drafted.
- T-0 (Jul 14): Launch day — press release, blog, social, email, paid push. War room active.
- T+7 (Jul 21): First week review. Quick collateral fixes.
- T+30 (Aug 14): First-wave learnings. Channel reallocation. Sales playbook v2.
- T+90 (Oct 14): GTM v2. Beachhead success review. Next beachhead identified.

Budget: $400K (Q3)
- PR + analyst: $80K (20%)
- Paid acquisition: $140K (35%)
- Content + video: $80K (20%)
- Events: $60K (15%)
- Enablement + tooling: $40K (10%)

Risks:
- Workday launches competing module (mitigation: speed + mid-market focus)
- Sales team ramp slow (mitigation: pre-launch coaching + lighthouse references)
- Pipeline slow to materialize (mitigation: outbound + paid as fast levers)

Cross-functional alignment:
- PM owns roadmap + positioning + lighthouse customer success
- Marketing owns demand gen + content + PR
- Sales owns pipeline + close + customer reference development
- CS owns onboarding + reference customer maintenance
- CEO owns analyst relationships + 1-2 lighthouse customer execs
- Finance owns budget + metric tracking + forecast

Mid-quarter check-ins: weekly cross-functional GTM standup, Mondays 9am.
```

The good version answers all the questions. The bad version is a wish.

## Validation checklist

Before declaring a GTM strategy ready:

- [ ] ICP is sharp (size + vertical + role + JTBD + trigger)
- [ ] Beachhead segment named + small enough to dominate
- [ ] Motion matches ACV
- [ ] 2-3 channels with budget + ownership
- [ ] Messaging tested with target customers
- [ ] Per-persona talk tracks
- [ ] Competitive battlecards
- [ ] Success metrics + targets + tracking
- [ ] T-90 → T+90 sequence
- [ ] Budget allocated
- [ ] Risks identified + mitigation
- [ ] Cross-functional alignment (PM + marketing + sales + CS + CEO)
- [ ] Lighthouse customers engaged (T-90)
- [ ] GTM v2 commitment at T+90
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