tool-selection-stack
FeaturedBuild 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.
Install
Quality Score: 89/100
Skill Content
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
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.
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.
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.