Sales Tools & Stack
A stack that serves the process — not the other way round.
Workflow
Step 1Needs Assessment
ObjectiveDefine the real need.
InputProcess, pain points
OutputNeeds brief
Key activities
Map what the process actually needs
Decision points
Is there a process problem to fix?
Tools: AssessmentRoles: RevOps
Success: Needs clear
Quality gate: Go: needs defined. Loop back: tool-first.
Why it matters
- Tool sprawl is GTM debt. The rule: don't automate bad GTM — automate a good process. Tools should serve, never define.
Best practices
- Define the process first, then the tool.
- Evaluate against the process, not the demo.
- Drive adoption — a tool nobody uses is a license fee.
- Refresh the stack deliberately; kill what's redundant.
Common mistakes
- Buying tools to fix process problems.
- Overlapping tools with no single source of truth.
- Stack that grows until it breaks the budget.
Key questions
- What process problem does this tool actually solve?
- Is the stack lean enough to be mastered?
Agents that drive this
Hygiene
Tools we use · alternates in [ ]
Notion[ Confluence, Obsidian ]n8n[ Zapier, Make, Airflow ]Slack[ Teams, Discord ]