Creates role-specific messages for multiple stakeholders in a deal. Use this skill when engaging additional contacts, following up with people who weren't on calls, or executing account-based selling strategies.
View on GitHubJanuary 20, 2026
Select agents to install to:
npx add-skill https://github.com/Salesably/salesably-marketplace/blob/main/sales-skills/skills/multithread-outreach/SKILL.md -a claude-code --skill multithread-outreachInstallation paths:
.claude/skills/multithread-outreach/# Multithread Outreach This skill creates tailored outreach messages for different stakeholders within an account, enabling you to engage multiple decision-makers and influencers with role-specific messaging. ## Objective Generate personalized, role-appropriate messages for various stakeholders in a deal-ensuring each person receives communication relevant to their priorities while maintaining consistent core messaging. ## Why Multithreading Matters ### The Problem with Single-Threading - Deals stall when your champion leaves or goes dark - You miss perspectives from key decision-makers - No internal advocates beyond your main contact - Limited visibility into the buying process ### Benefits of Multithreading - **Resilience**: Deal survives if one contact goes dark - **Speed**: Multiple parallel conversations accelerate decisions - **Intelligence**: Learn about different perspectives and priorities - **Influence**: Build coalition of supporters across the org ## Stakeholder Categories ### Executive Sponsors (C-Level, VP) **What They Care About:** - Business outcomes and ROI - Strategic alignment - Risk mitigation - Competitive advantage - Resource allocation **Messaging Approach:** - Lead with business impact - Keep it brief and high-level - Quantify value when possible - Focus on outcomes, not features - Respect their time ### Operational Leaders (Directors, Managers) **What They Care About:** - Team productivity and efficiency - Implementation feasibility - Day-to-day impact - Change management - Success metrics **Messaging Approach:** - Balance strategic and tactical - Address implementation concerns - Show understanding of their challenges - Include relevant details - Offer to support their team ### Technical Buyers (IT, Security, Architecture) **What They Care About:** - Integration requirements - Security and compliance - Technical architecture - Maintenance overhead - Vendor reliability **Messaging Approach:** - Lead with technical credibility -