The right tool stack at Seed is wrong at Series B. Learn how to design, evaluate, and evolve a GTM stack that matches company stage, team size, and motion complexity.
GA-6 · GTM Architect · 150 XP · ~20 min
There is no universal “best GTM stack.” The right stack depends on company stage, team size, ICP complexity, and motion type. A 10-person company with one founder doing outbound needs different tools than a 200-person company with a 20-rep SDR team.This module teaches you to design stacks that match context — and to know when a stack needs to evolve.
When evaluating any tool for your GTM stack, score it on six dimensions:
Evaluate this tool for our GTM stack:Tool name: {{tool_name}}Use case: {{intended_use_case}}Company stage: {{company_stage}}Score 1-5 on each dimension:1. Coverage: Does it cover our ICP well?2. Accuracy: Is the data/output reliable?3. Integration: Does it connect cleanly to our existing stack?4. Cost efficiency: Value relative to price at our volume?5. Time to value: How quickly can we operationalize it?6. Scalability: Will it still work 2x our current volume?Calculate total score (max 30). Recommend: adopt / trial / defer / reject.Return as JSON.
Run a quarterly stack review: for each tool, document utilization, actual cost, and whether you’d buy it again today.
Quick Check: What are the three company stages and their primary GTM stack needs? What six dimensions should you evaluate when selecting a tool? Name three signals that indicate your stack needs to evolve.