multithread-outreach

Name: multithread-outreach
Author: Salesably

40stars14forks

How to install multithread-outreach?

salesably/salesably-marketplace/multithread-outreach

$npx -y skills add Salesably/salesably-marketplace --skill multithread-outreach

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Multithread Outreach
2
3	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.
4
5	## Objective
6
7	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.
8
9	## Why Multithreading Matters
10
11	### The Problem with Single-Threading
12	- Deals stall when your champion leaves or goes dark
13	- You miss perspectives from key decision-makers
14	- No internal advocates beyond your main contact
15	- Limited visibility into the buying process
16
17	### Benefits of Multithreading
18	- Resilience: Deal survives if one contact goes dark
19	- Speed: Multiple parallel conversations accelerate decisions
20	- Intelligence: Learn about different perspectives and priorities
21	- Influence: Build coalition of supporters across the org
22
23	## Stakeholder Categories
24
25	### Executive Sponsors (C-Level, VP)
26	What They Care About:
27	- Business outcomes and ROI
28	- Strategic alignment
29	- Risk mitigation
30	- Competitive advantage
31	- Resource allocation
32
33	Messaging Approach:
34	- Lead with business impact
35	- Keep it brief and high-level
36	- Quantify value when possible
37	- Focus on outcomes, not features
38	- Respect their time
39
40	### Operational Leaders (Directors, Managers)
41	What They Care About:
42	- Team productivity and efficiency
43	- Implementation feasibility
44	- Day-to-day impact
45	- Change management
46	- Success metrics
47
48	Messaging Approach:
49	- Balance strategic and tactical
50	- Address implementation concerns
51	- Show understanding of their challenges
52	- Include relevant details
53	- Offer to support their team
54
55	### Technical Buyers (IT, Security, Architecture)
56	What They Care About:
57	- Integration requirements
58	- Security and compliance
59	- Technical architecture
60	- Maintenance overhead
61	- Vendor reliability
62
63	Messaging Approach:
64	- Lead with technical credibility
65	- Address integration and security early
66	- Provide technical resources
67	- Offer to connect with your tech team
68	- Respect their expertise
69
70	### End Users
71	What They Care About:
72	- Ease of use
73	- Daily workflow impact
74	- Training and adoption
75	- Current pain points
76	- Personal productivity
77
78	Messaging Approach:
79	- Focus on user experience
80	- Acknowledge their pain points
81	- Highlight ease of adoption
82	- Show empathy for their situation
83	- Offer hands-on demonstrations
84
85	### Economic Buyers (Finance, Procurement)
86	What They Care About:
87	- Total cost of ownership
88	- Pricing and terms
89	- Contract flexibility
90	- Budget timing
91	- Vendor risk
92
93	Messaging Approach:
94	- Lead with value and ROI
95	- Be transparent about pricing
96	- Address procurement concerns
97	- Highlight financial flexibility
98	- Provide case study ROI data
99
100	## Message Structure by Scenario
101
102	### Scenario 1: Initial Introduction (Never Met)
103	Someone your contact suggested you reach out to.
104
105	```
106	Subject: [Contact Name] suggested we connect
107
108	Hi [Name],
109
110	[Contact Name] mentioned you'd be a good person to include
111	in our conversation about [initiative].
112
113	We've been discussing [brief summary] with [their team/department],
114	and given your role in [their area], I thought you might find
115	[specific aspect] relevant.
116
117	[1-2 sentences on business impact specific to their role]
118
119	Would you be open to a brief conversation, or would you prefer
120	I keep you updated via email as things progress?
121
122	Best,
123	[Your name]
124	```
125
126	### Scenario 2: Post-Call Briefing (Wasn't on the Call)
127	Someone who should know about a conversation they weren't part of.
128
129	```
130	Subject: Update: [Company] and [Your Company] Discussion
131
132	Hi [Name],
133
134	I wanted to share a quick update from my conversation with
135	[their colleague] earlier this [day/week].
136
137	Key discussion points:
138	- [Point relevant to their role]
139	- [Another relevant point]
140	- [Outcome or next step]
141
142	Given your focus on [their area], I thought [specific aspect]
143	might be particularly relevant to you.
144
145	Happy to give you a brief overview if helpful-or simply keep
146	you in the loop as we progress. What works best?
147
148	Best,
149	[Your name]
150	```
151
152	### Scenario 3: Champion Enablement
153	Helping your champion sell internally.
154
155	```
156	Subject: Materials for your internal discussion
157
158	Hi [Name],
159
160	As promised, here are some resources for your conversation with
161	[other stakeholders]:
162
163	For [Stakeholder 1 - role]:
164	- [Relevant resource/talking point]
165
166	For [Stakeholder 2 - role]:
167	- [Relevant resource/talking point]
168
169	I've also attached [executive summary/one-pager] that you can
170	share or forward as needed.
171
172	Let me know if there's anything else I can prepare to help the
173	conversation go smoothly.
174
175	Best,
176	[Your name]
177	```
178
179	### Scenario 4: Executive Air Cover
180	Reaching up to get executive support

People who liked this also viewed

6 picks

Type

multithread-outreach

40stars14forks

View on GitHub

How to install multithread-outreach?

salesably/salesably-marketplace/multithread-outreach

$npx -y skills add Salesably/salesably-marketplace --skill multithread-outreach

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Multithread Outreach
2
3	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.
4
5	## Objective
6
7	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.
8
9	## Why Multithreading Matters
10
11	### The Problem with Single-Threading
12	- Deals stall when your champion leaves or goes dark
13	- You miss perspectives from key decision-makers
14	- No internal advocates beyond your main contact
15	- Limited visibility into the buying process
16
17	### Benefits of Multithreading
18	- Resilience: Deal survives if one contact goes dark
19	- Speed: Multiple parallel conversations accelerate decisions
20	- Intelligence: Learn about different perspectives and priorities
21	- Influence: Build coalition of supporters across the org
22
23	## Stakeholder Categories
24
25	### Executive Sponsors (C-Level, VP)
26	What They Care About:
27	- Business outcomes and ROI
28	- Strategic alignment
29	- Risk mitigation
30	- Competitive advantage
31	- Resource allocation
32
33	Messaging Approach:
34	- Lead with business impact
35	- Keep it brief and high-level
36	- Quantify value when possible
37	- Focus on outcomes, not features
38	- Respect their time
39
40	### Operational Leaders (Directors, Managers)
41	What They Care About:
42	- Team productivity and efficiency
43	- Implementation feasibility
44	- Day-to-day impact
45	- Change management
46	- Success metrics
47
48	Messaging Approach:
49	- Balance strategic and tactical
50	- Address implementation concerns
51	- Show understanding of their challenges
52	- Include relevant details
53	- Offer to support their team
54
55	### Technical Buyers (IT, Security, Architecture)
56	What They Care About:
57	- Integration requirements
58	- Security and compliance
59	- Technical architecture
60	- Maintenance overhead
61	- Vendor reliability
62
63	Messaging Approach:
64	- Lead with technical credibility
65	- Address integration and security early
66	- Provide technical resources
67	- Offer to connect with your tech team
68	- Respect their expertise
69
70	### End Users
71	What They Care About:
72	- Ease of use
73	- Daily workflow impact
74	- Training and adoption
75	- Current pain points
76	- Personal productivity
77
78	Messaging Approach:
79	- Focus on user experience
80	- Acknowledge their pain points
81	- Highlight ease of adoption
82	- Show empathy for their situation
83	- Offer hands-on demonstrations
84
85	### Economic Buyers (Finance, Procurement)
86	What They Care About:
87	- Total cost of ownership
88	- Pricing and terms
89	- Contract flexibility
90	- Budget timing
91	- Vendor risk
92
93	Messaging Approach:
94	- Lead with value and ROI
95	- Be transparent about pricing
96	- Address procurement concerns
97	- Highlight financial flexibility
98	- Provide case study ROI data
99
100	## Message Structure by Scenario
101
102	### Scenario 1: Initial Introduction (Never Met)
103	Someone your contact suggested you reach out to.
104
105	```
106	Subject: [Contact Name] suggested we connect
107
108	Hi [Name],
109
110	[Contact Name] mentioned you'd be a good person to include
111	in our conversation about [initiative].
112
113	We've been discussing [brief summary] with [their team/department],
114	and given your role in [their area], I thought you might find
115	[specific aspect] relevant.
116
117	[1-2 sentences on business impact specific to their role]
118
119	Would you be open to a brief conversation, or would you prefer
120	I keep you updated via email as things progress?
121
122	Best,
123	[Your name]
124	```
125
126	### Scenario 2: Post-Call Briefing (Wasn't on the Call)
127	Someone who should know about a conversation they weren't part of.
128
129	```
130	Subject: Update: [Company] and [Your Company] Discussion
131
132	Hi [Name],
133
134	I wanted to share a quick update from my conversation with
135	[their colleague] earlier this [day/week].
136
137	Key discussion points:
138	- [Point relevant to their role]
139	- [Another relevant point]
140	- [Outcome or next step]
141
142	Given your focus on [their area], I thought [specific aspect]
143	might be particularly relevant to you.
144
145	Happy to give you a brief overview if helpful-or simply keep
146	you in the loop as we progress. What works best?
147
148	Best,
149	[Your name]
150	```
151
152	### Scenario 3: Champion Enablement
153	Helping your champion sell internally.
154
155	```
156	Subject: Materials for your internal discussion
157
158	Hi [Name],
159
160	As promised, here are some resources for your conversation with
161	[other stakeholders]:
162
163	For [Stakeholder 1 - role]:
164	- [Relevant resource/talking point]
165
166	For [Stakeholder 2 - role]:
167	- [Relevant resource/talking point]
168
169	I've also attached [executive summary/one-pager] that you can
170	share or forward as needed.
171
172	Let me know if there's anything else I can prepare to help the
173	conversation go smoothly.
174
175	Best,
176	[Your name]
177	```
178
179	### Scenario 4: Executive Air Cover
180	Reaching up to get executive support

People who liked this also viewed

6 picks

Type