tool-selection-stack

Featured

Build the right GTM tool stack for any stage — solo founder ($100/mo), small team ($500/mo), growth team ($2K/mo), and enterprise ($10K+/mo). With cost breakdowns, tool comparisons, and stack architecture. Use when choosing GTM tools, building a tech stack, comparing platforms, or optimizing tool spend. Triggers on: "tool stack", "tech stack", "GTM tools", "which tool", "compare tools", "tool budget", "stack for my stage", or any tool selection request.

AI & Automation 54 stars 16 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
58
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Tool Selection & Stack Builder ## Overview Choosing GTM tools is the most expensive decision most teams make — not because tools are expensive, but because the wrong stack wastes months of productivity. This skill builds stage-appropriate tool stacks with cost breakdowns and clear rationale for every choice. **Automation strategy:** Load `references/gtm-automation-expert-playbook.md` (Jen Igartua) for maturity assessment before adding tools. Clay = enrichment; n8n = orchestration; Cargo category = persistent routing at scale — see playbook decision matrix. ## Authoritative Foundations - **Jen Igartua (Go Nimbly) — Must-have basics / performance boosters / delighters stack layering** — Must-have basics / performance boosters / delighters stack layering - **Jesse Ouellette Lean Stack** — Named methodology governing recommendations in this skill's process. - **Eric Nowoslawski Agency Stack** — Cold email infra at scale — 2 inboxes/domain, backup inboxes, Creative Ideas testing. - **HubSpot Academy — CRM Automation** — Lifecycle stages, object model, and workflow enrollment patterns. ## When to Use - "What tools do I need for cold email?" - "Build my GTM stack" - "Compare [Tool A] vs [Tool B]" - "What should I buy at $X MRR?" - "Audit my current tool stack" - "Optimize our tool spend" ## Step-by-Step Process ### Phase 1: Stage Assessment Determine the user's stage: Solo Founder (<$10K MRR), Small Team ($10-50K MRR), Growth ($50K-2M ARR), Scale ($2-10M ARR), Enterprise ($1...

Details

Author
LeadMagic
Repository
LeadMagic/gtm-skills
Created
3 months ago
Last Updated
2 weeks ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

pick-gtm-stack

Use when choosing which GTM tools to use for a task, play, or client engagement — "what tools should I use for X", "build a stack for this play", "which tool does Y", or when designing an outbound, inbound, nurture, or retention motion and the tool choices aren't settled. Recommends from the mapped Bowtie Funnel tool stack instead of guessing from training data.

1 Updated 2 days ago
bowtiefunnel
AI & Automation Listed

revops-stack-rationalization

Run a macro, periodic review of the full RevOps/GTM tool stack against the revenue workflows it serves and decide, tool by tool, what to keep, consolidate, replace, or cut - four-channel inventory, function-level overlap map, TIME scoring, a renewal-triggered action calendar, and re-sprawl governance. Use whenever the user mentions stack rationalization, GTM tool consolidation, a revops stack audit, a GTM stack review, SaaS sprawl, too many sales and marketing tools, cutting tooling spend, redundant GTM tools, or platform vs point solutions - even if they never say "rationalization". Covers B2B sales-led and B2C/e-commerce GTM stacks. Portfolio-level and periodic - not a pre-purchase checklist for one candidate tool, and not contract or legal negotiation.

0 Updated 1 weeks ago
mbfinotti
AI & Automation Listed

stack

Choose the tech stack or target platform and make the project idiomatic for it. Covers classic code stacks and hosted/low-code platforms alike (own servers, Microsoft Power Platform/Dataverse, ServiceNow, Salesforce, Google, or whatever exists by then). Use when the target platform/stack must be decided, when generating docs/standards/<stack>.md, or when wiring stack-specific quality gates into CI and hooks. Requires live research. Never stack facts from model memory.

2 Updated today
Tradebaas