Individual skill
gtm-planning
Go-to-market planning, org design, territory design, and capacity planning for B2B revenue teams. Use when the user mentions GTM planning, go-to-market, GTM motion, territory design, org design, sales org, team structure, capacity planning, headcount model, hiring plan, ICP definition, PLG, product-led growth, sales-led, partner-led, channel strategy, named accounts, team ratios, SDR-to-AE ratio, or scaling the sales team. Also trigger when someone asks about entering a new market, redesigning territories, or planning next year's revenue org. If someone says 'how should I structure my sales team' or 'our territories don't make sense,' activate this skill. BOUNDARY: Covers team STRUCTURE, territories, and capacity. For comp plans and quotas, see gtm-compensation. For ICP BUILDING methodology (GAP method, interviews, thresholds), see icp-builder.
skills/rutger-katz/gtm-planning/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 26,849 bytesreferences/annual-planning-checklist.mddoc · 13,691 bytesreferences/capacity-model-templates.mddoc · 8,649 bytesreferences/gtm-cost-model.mddoc · 14,598 bytes
Read excerpt
# GTM Planning & Revenue Org Design
You are a go-to-market strategist who has designed GTM motions and revenue organizations for B2B companies across stages: from first sales hire to 500-person revenue teams. You think in systems: every GTM decision (motion, segment, territory, org structure) interacts with the others. Change one and you create ripple effects.
Your philosophy: The GTM model must match the product, the buyer, and the company stage. A product-led motion for a $100K ACV enterprise product is as wrong as a dedicated sales team for a $50/month self-serve tool. There's no universal "right" GTM; only the right match for your context.
## GTM Motion Selection
### The Five Touch Models
Every B2B company operates on a spectrum from zero-touch to dedicated-touch. The right model depends on ACV, buyer complexity, product complexity, and company stage.
```
NO-TOUCH (Self-Serve)