Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Gtm Strategy

ASecurity

Go-to-market strategy: ICP × motion × channels × messaging × success metrics × launch plan. Distinct from individual marketing or sales skills by being the integrated cross-functional strategy spanning product, marketing, sales, CS, and finance. Use when launching a new product, entering a new segment, or auditing why an existing GTM isn't working.

847 stars
0 votes
0 copies
2 views
Added 5/29/2026
ai-agentspythongobashsqlperformance

Security Analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned 5/29/2026

$npx -y skills add borghei/Claude-Skills --skill gtm-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gtm Strategy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Gtm Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/borghei-gtm-strategy/badge)](https://www.skillsdirectory.com/skills/borghei-gtm-strategy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: gtm-strategy
description: >
  Go-to-market strategy: ICP × motion × channels × messaging × success
  metrics × launch plan. Distinct from individual marketing or sales
  skills by being the integrated cross-functional strategy spanning
  product, marketing, sales, CS, and finance. Use when launching a
  new product, entering a new segment, or auditing why an existing
  GTM isn't working.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: project-management
  domain: go-to-market
  updated: 2026-05-27
  python-tools: gtm_strategy_validator.py
  tech-stack: gtm, go-to-market, motion, launch, beachhead
---

# GTM Strategy

A complete go-to-market strategy is the integrated cross-functional plan:
ICP, motion, channels, messaging, success metrics, and launch sequence.

## When to use this skill

- **New product launch** (full product or major feature)
- **New segment entry** (SMB → ENT; new geography; new vertical)
- **GTM refresh** (current motion stalling)
- **Repositioning** after pivot
- **Pre-fundraise** GTM narrative for investors
- **Post-mortem** on why a launch didn't take

## The 7 components

1. **ICP (Ideal Customer Profile)** — who specifically, why now
2. **Beachhead segment** — first concentrated market
3. **Motion** — PLG / sales-led / hybrid / channel-led
4. **Channels** — how customers find + buy
5. **Messaging + positioning** — what we say
6. **Success metrics** — what we measure
7. **Launch sequence** — what happens in what order

## Workflow

### Step 1 — Define ICP precisely
- Industry / vertical
- Size band (employees / revenue)
- Geography
- Buyer persona (role, level)
- Tech stack signals
- Job-to-be-done
- Trigger event (why now)

See `project-management/gtm/ideal-customer-profile`.

### Step 2 — Pick the beachhead
Start narrow:
- 1 segment, 1 vertical, 1 geography
- Concentrated enough to develop reference customers
- Reachable via clear channels
- Big enough to learn from but small enough to dominate

Reference: Crossing the Chasm. Don't try to sell to everyone Day 1.

### Step 3 — Pick the motion

| Motion | When | Cost structure |
|--------|------|----------------|
| **PLG (product-led)** | Self-serve product; low ACV ($0-$5K); strong activation | Low CAC; high product investment |
| **Sales-led** | High ACV ($25K+); complex buying committees | High CAC; sales team needed |
| **Marketing-led / inbound** | Mid-ACV ($5K-$25K); content-driven | Medium CAC; content + ops team |
| **Channel-led** | Wide distribution via partners | Medium CAC; partner program needed |
| **Community-led** | Strong category with passionate users | Long ramp; high ongoing investment |
| **Hybrid (PLG + sales)** | PLG to capture; sales to expand | Most modern SaaS; complex to coordinate |

Don't try to run all motions Day 1.

### Step 4 — Channels per motion

| Motion | Primary channels |
|--------|------------------|
| PLG | Web direct, SEO, viral, content, app stores |
| Sales-led | Outbound SDR, AE outbound, events, account-based |
| Marketing-led | SEO, paid, content syndication, webinar |
| Channel-led | Partner program, marketplace |
| Community-led | Open source, community events, integrations |

### Step 5 — Messaging + positioning
- **Positioning:** "[Product] is [category] for [target] who [JTBD], unlike [alternative]"
- **Hero message:** outcome customers want (not feature)
- **Differentiation:** clear "why us vs them"
- **Talk track per segment:** different ICPs need different framing

### Step 6 — Success metrics

| Motion | KPI focus |
|--------|-----------|
| PLG | Signups, activation, free-to-paid conversion, NRR |
| Sales-led | Pipeline coverage, win rate, ACV, cycle time, NRR |
| Marketing-led | MQL → SQL conversion, CPA, content engagement |
| Channel-led | Partner-sourced revenue, partner activity |

Set targets; track weekly; tune.

### Step 7 — Launch sequence
- **T-90:** ICP locked; positioning v1; channels chosen; team aligned
- **T-60:** Sales/marketing collateral ready; pilot customers identified
- **T-30:** Internal training; lighthouse customer commitments
- **T-7:** Launch comms prepped; press / analyst briefed
- **T-0:** Launch
- **T+30:** Iterate based on early signal
- **T+90:** GTM v2 incorporating learnings

### Step 8 — Run `gtm_strategy_validator.py`
Audit GTM doc for: ICP specificity, motion fit, channel coherence,
messaging clarity, metric definition, sequence realism.

```bash
python3 project-management/gtm/gtm-strategy/scripts/gtm_strategy_validator.py \
  --input gtm.json --format markdown
```

## Decision frameworks

### Motion fit by ACV

| ACV | Likely motion |
|-----|---------------|
| < $1K | PLG; consumer-style |
| $1K-$10K | PLG-led; light sales-assist |
| $10K-$50K | Marketing-led + inside sales |
| $50K-$250K | Sales-led with marketing support |
| $250K+ | Enterprise sales-led; long cycle |

Cross these and economics break.

### Beachhead vs broad

Going broad Day 1:
- Diluted messaging
- No reference customers
- Sales motion thinly stretched
- No moat in any segment

Beachhead first:
- Win the segment
- Build reference customers
- Develop battle-tested motion
- Then expand adjacent

Geoffrey Moore: cross the chasm one bowling pin at a time.

### Channel-product fit

Each channel has product-fit assumptions:
- SEO: long content; SERP-able problem
- Paid: clear high-intent keywords; LTV > 2-3x CAC
- Outbound: defined ICP; AE can articulate value in 30 seconds
- Channel: partners economically incentivized; product fits their offering
- Community: passionate users + room to participate
- Viral: collaboration / sharing built into product

If channel-product fit is off, channel won't deliver regardless of effort.

## Common engagements

### "Help us launch product X in market Y"
1. Confirm ICP precision (or sharpen).
2. Pick beachhead segment.
3. Choose motion based on ACV + product complexity.
4. Map channels to motion.
5. Draft positioning + messaging.
6. Define success metrics + targets.
7. Build T-90 → T+90 launch sequence.

### "Our GTM is stalling — what's wrong?"
1. Audit each component for clarity + execution.
2. Common failures:
   - ICP too broad
   - Motion mismatch with ACV
   - Channels not delivering pipeline
   - Messaging not differentiated
   - Metrics not tracked
3. Identify the breakpoint; fix one at a time.

### "Should we move from PLG to sales-led?"
1. Look at ACV trend: rising with enterprise = yes
2. Look at pipeline: enterprise inquiries unanswered = yes
3. Look at unit economics: PLG CAC payback < sales CAC payback?
4. Plan hybrid: PLG capture + sales expansion (most common path)

## Anti-patterns to avoid

- **ICP = "everyone."** Diluted strategy.
- **Motion mismatched with ACV.** Sales motion on $50/mo = unit economics broken.
- **Channels listed; not invested.** Knowing channels doesn't activate them.
- **Generic messaging.** "Faster, better, cheaper."
- **No success metrics.** Can't tune what you can't measure.
- **Launch sequence = "ship and see."** Predictable underperformance.
- **All motions at once.** Try one; succeed before adding.

## References

- `references/gtm-components-deep.md` — ICP, motion, channels, messaging deep
- `references/launch-sequence-playbook.md` — T-90 → T+90 playbook
- `references/gtm-anti-patterns.md` — common failures + fixes

## Related skills

- `project-management/gtm/ideal-customer-profile` — ICP definition
- `project-management/strategy-frameworks/business-model-canvas` — model behind GTM
- `marketing/launch-strategy` — marketing execution layer
- `business-growth/customer-success-manager` — post-sale GTM
- `c-level-advisor/cro-advisor` — sales / revenue strategy
- `c-level-advisor/cmo-advisor` — marketing strategy

Attribution

borgheiborghei
View sourceSee grades on GitHubMore from borghei →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →