| name | executive-outreach-drafter |
| description | Writes the initial outreach email to a senior stakeholder the CSM has not engaged before -- going high for the first time. Calibrates register, framing, and approach to executive communication standards. Use when asked to write an email to a VP, CRO, CFO, or C-suite contact at a customer account, draft an executive outreach, compose a going-high email, engage a new senior stakeholder, or when the CSM needs to establish a relationship at a level above their primary contacts. Also triggers for questions about executive email drafting, going high strategy, senior stakeholder engagement, or first-time executive outreach. |
| license | MIT |
| metadata | {"author":"Stephen Rogan","version":"1.0.0","standalone":true} |
Executive Outreach Drafter
Writes the first email to a senior stakeholder you have not engaged before. This is one of the highest-anxiety communications in CS because the stakes are real: a poorly written executive email can damage the relationship at the level that matters most, and a well-written one can unlock strategic partnership.
How to Use
Provide:
- Who you are emailing (name, title, function)
- Why you are reaching out (renewal, expansion, risk, introduction, value sharing, escalation follow-up)
- Who introduced you or how you identified them (champion referral, org chart, LinkedIn, stakeholder map)
- What you know about them (background, priorities, disposition toward your product if known)
- What you want from them (a meeting, awareness, a decision, nothing specific -- just establishing the relationship)
- Account context (ARR, health, tenure, recent events)
Executive Communication Principles
Executives receive 50-200 emails per day. Yours will get 5-10 seconds of attention before they decide to read, delegate, or delete. Every word must earn its place.
The rules:
- Subject line is everything. Specific, relevant to their priorities, under 50 characters. "[Their company] + [your company] -- [one topic]" format works. "Introduction" alone does not
- First sentence is the frame. Who you are, why you are writing, and why they should care. All in one sentence
- No more than 5 sentences total. If you need more, you are not ready for the email -- you need a meeting
- One clear ask or statement of purpose. Not two. Not "a few things I wanted to cover." One
- No jargon. Health scores, NPS, QBR, cadence -- these are CS terms. Translate to business language
- No false familiarity. "I hope this email finds you well" is filler. "I noticed your team has grown 40% this year" is specific and shows you did your homework
Approach by Context
Introduction via Champion
Best approach: Reference the champion by name and the specific reason they suggested the connection.
Example:
"Hi [name], [champion name] suggested I reach out. Your team has achieved [specific outcome] using [product] this quarter, and I wanted to make sure you had visibility into the value and how we are planning to support your growth next year. I would welcome a brief conversation at your convenience -- 20 minutes would be valuable."
Proactive Value Sharing
Best approach: Lead with a specific data point that matters to their function.
CFO example:
"Hi [name], I wanted to share a data point relevant to your team's investment in [product]. Your team saved an estimated [X hours/EUR/outcomes] this quarter, representing a [X]x return on the annual investment. Happy to walk through the methodology if useful -- I want to make sure this evidence is available for your planning."
VP Engineering example:
"Hi [name], your engineering team's adoption of [product] has put them in the top quartile among companies your size, particularly in [specific area]. I wanted to connect to ensure we are aligned on your team's priorities for the next quarter and supporting your technical roadmap."
Pre-Renewal Engagement
Best approach: Frame as alignment, not as a sales conversation.
"Hi [name], with the renewal of [product] approaching in [timeframe], I wanted to connect to make sure we are aligned on value delivered and your priorities for the next period. [Champion name] and I have been working closely on [specific initiative] and I would welcome your perspective on what matters most for [company] going forward. Would a brief call in the next two weeks work?"
Risk or Escalation Context
Best approach: Be direct about the situation. Executives respect honesty more than spin.
"Hi [name], I want to be transparent about a situation with your team's use of [product]. [One sentence on the issue]. We have [one sentence on what has been done]. I would like to discuss this with you directly to ensure we are addressing your team's needs at the right level. Can we schedule a brief call this week?"
What Not to Do
| Mistake | Why It Fails | Better Approach |
|---|
| "I hope this email finds you well" | Filler. Signals a templated email | Jump straight to the point. No preamble |
| Long introduction of yourself and your company | They can look you up in 10 seconds. Do not spend 3 sentences on what they can find on LinkedIn | One line: your name, your role, your relationship to their team |
| Multiple asks in one email | Dilutes the message. Executives process one item per email | One ask. If you need two things, send two emails (on different days) |
| CC'ing their reports without telling them | Feels like pressure. Executives notice and resent it | If you want others in the conversation, say so: "I have included [name] as they have context on the details" |
| Being vague about why you are writing | "I wanted to connect" -- about what? They will not make time for undefined conversations | Be specific: "I wanted to discuss the Q2 renewal and how we can support your expansion plans" |
| Writing more than 5 sentences | They will not read it. Full stop | If it takes more than 5 sentences, your thinking is not clear enough yet |
Output
For each outreach, the skill produces:
- Subject line (specific, under 50 characters)
- Email body (maximum 5 sentences)
- Approach rationale (which pattern was used and why)
- What to expect (likely response, likely timeline, what to do if no response)
- Follow-up plan (when to follow up, through what channel, whether to involve the champion)
Quality Gates
- Is the email under 5 sentences? Count them. Five is the maximum, not the target. Three is better
- Does the subject line work on a phone screen? (Under 50 characters, specific to them)
- Would you respond to this email if you were in their position? Read it through their eyes. If it sounds like vendor outreach, rewrite
- Is there exactly one ask? Identify it. If you cannot state the ask in one sentence, the email is unfocused
- Is the champion or context reference specific? "I work with your team" is generic. "Tom Chen suggested I reach out after our Q1 review" is specific
- Is the email free of CS jargon? No health scores, no NPS, no QBR references, no cadence talk. Business language only
Principles
- Executives respond to relevance, not persistence. One well-crafted email beats three generic ones
- The executive's time is the scarce resource, not yours. Respect it in the email length, the specificity of the ask, and the ease of responding
- Going high is a tool, not a habit. Use it when the situation warrants executive engagement (renewal, expansion, risk, strategic alignment). Using it for routine account matters devalues the channel
- If the champion can make an introduction, let them. An intro email from someone the executive trusts converts 5x better than a cold outreach from you. Your email should support the introduction, not replace it
