draft-outreach

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Draft Outreach

草拟开发信

Research first, then draft. This skill never sends generic outreach - it always researches the prospect first to personalize the message. Works standalone with web search, supercharged when you connect your tools.

先调研，再草拟。本Skill绝不会生成通用开发信——它总会先研究潜在客户，再个性化定制消息。可独立搭配网络搜索使用，连接工具后功能更强大。

Connectors (Optional)

连接器（可选）

Connector	What It Adds
Enrichment	Verified email, phone, background details
CRM	Prior relationship context, existing contacts
Email	Create draft directly in your inbox

No connectors? Web research works great. I'll output the email text for you to copy.

连接器	新增功能
Enrichment	验证过的邮箱、电话、背景详情
CRM	过往合作关系背景、现有联系人信息
Email	直接在收件箱中创建草稿

未连接连接器？ 网络调研也能很好地工作。我会输出邮件文本供你复制使用。

How It Works

工作原理

+------------------------------------------------------------------+
|                      DRAFT OUTREACH                               |
|                                                                   |
|  Step 1: RESEARCH (always happens first)                         |
|  - Web search (default)                                           |
|  - + Enrichment (if enrichment tools connected)                  |
|  - + CRM (if CRM connected)                                      |
|                                                                   |
|  Step 2: DRAFT (based on research)                               |
|  - Personalized opening (from research)                          |
|  - Relevant hook (their priorities)                              |
|  - Clear CTA                                                      |
|                                                                   |
|  Step 3: DELIVER (based on connectors)                           |
|  - Email draft (if email connected)                              |
|  - Copy for LinkedIn (always)                                    |
|  - Output to user (always)                                        |
+------------------------------------------------------------------+

+------------------------------------------------------------------+
|                      DRAFT OUTREACH                               |
|                                                                   |
|  Step 1: RESEARCH (always happens first)                         |
|  - Web search (default)                                           |
|  - + Enrichment (if enrichment tools connected)                  |
|  - + CRM (if CRM connected)                                      |
|                                                                   |
|  Step 2: DRAFT (based on research)                               |
|  - Personalized opening (from research)                          |
|  - Relevant hook (their priorities)                              |
|  - Clear CTA                                                      |
|                                                                   |
|  Step 3: DELIVER (based on connectors)                           |
|  - Email draft (if email connected)                              |
|  - Copy for LinkedIn (always)                                    |
|  - Output to user (always)                                        |
+------------------------------------------------------------------+

Output Format

输出格式

markdown

undefined

markdown

undefined

Outreach Draft: [Person] @ [Company]

Generated: [Date] | Research Sources: [Web, Enrichment, CRM]

Research Summary

Target: [Name], [Title] at [Company] Hook: [Why reaching out now - the personalized angle] Goal: [What you want from this outreach]

Email Draft

To: [email if known, or "find email" note] Subject: [Personalized subject line]

[Email body]

Subject Line Alternatives:

[Option 2]
[Option 3]

To: [email if known, or "find email" note] Subject: [Personalized subject line]

[Email body]

Subject Line Alternatives:

[Option 2]
[Option 3]

LinkedIn Message (if no email)

Connection Request (< 300 chars): [Short, no-pitch connection request]

Follow-up Message (after connected): [Value-first message]

Connection Request (< 300 chars): [Short, no-pitch connection request]

Follow-up Message (after connected): [Value-first message]

Why This Approach

Element	Based On
Opening	[Research finding that makes it personal]
Hook	[Their priority/pain point]
Proof	[Relevant customer story]
CTA	[Low-friction ask]

Element	Based On
Opening	[Research finding that makes it personal]
Hook	[Their priority/pain point]
Proof	[Relevant customer story]
CTA	[Low-friction ask]

Email Draft Status

[Draft created - check ~~email] [Email not connected - copy email above] [No email found - use LinkedIn approach]

Follow-up Sequence (Optional)

Day 3 - Follow-up 1: [Short, new angle]

Day 7 - Follow-up 2: [Different value prop]

Day 14 - Break-up: [Final attempt]

---

Day 3 - Follow-up 1: [Short, new angle]

Day 7 - Follow-up 2: [Different value prop]

Day 14 - Break-up: [Final attempt]

---

Execution Flow

执行流程

Step 1: Parse Request

步骤1：解析请求

Input patterns:
- "draft outreach to John Smith at Acme" → Person + company
- "write cold email to Acme's CTO" → Role + company
- "reach out to sarah@acme.com" → Email provided
- "LinkedIn message to [LinkedIn URL]" → Profile provided

Input patterns:
- "draft outreach to John Smith at Acme" → Person + company
- "write cold email to Acme's CTO" → Role + company
- "reach out to sarah@acme.com" → Email provided
- "LinkedIn message to [LinkedIn URL]" → Profile provided

Step 2: Research First (Always)

步骤2：优先调研（必选）

Use research-prospect skill internally:

1. Web search for company + person
2. If Enrichment connected: Get verified contact info, background
3. If CRM connected: Check for prior relationship

Must find before drafting:

Who they are (title, background)
What the company does
Recent news or trigger
Personalization hook

内部调用research-prospect skill：

1. Web search for company + person
2. If Enrichment connected: Get verified contact info, background
3. If CRM connected: Check for prior relationship

草拟前必须明确：

对方身份（职位、背景）
公司业务
近期动态或触发点
个性化切入点

Step 3: Identify Hook

步骤3：确定切入点

Priority order for hooks:
1. Trigger event (funding, hiring, news) → Most timely
2. Mutual connection → Social proof
3. Their content (post, article, talk) → Shows you did research
4. Company initiative → Relevant to their priorities
5. Role-based pain point → Least personal but still relevant

切入点优先级：
1. 触发事件（融资、招聘、新闻）→ 时效性最强
2. 共同联系人 → 社交背书
3. 对方发布的内容（帖子、文章、演讲）→ 体现你做了调研
4. 公司项目 → 契合对方优先级
5. 岗位相关痛点 → 个性化最弱但仍相关

Step 4: Draft Message

步骤4：草拟消息

Email Structure (AIDA):

SUBJECT: [Personalized, <50 chars, no spam words]

[Opening: Personal hook - shows you researched them]

[Interest: Their problem/opportunity in 1-2 sentences]

[Desire: Brief proof point - similar company result]

[Action: Clear, low-friction CTA]

[Signature]

LinkedIn Connection Request (<300 chars):

Hi [Name], [Mutual connection/shared interest/genuine compliment].
Would love to connect. [No pitch]

LinkedIn Follow-up Message:

Thanks for connecting! [Value-first: insight, article, observation]

[Soft transition to why you reached out]

[Question, not pitch]

邮件结构（AIDA模型）：

SUBJECT: [Personalized, <50 chars, no spam words]

[Opening: Personal hook - shows you researched them]

[Interest: Their problem/opportunity in 1-2 sentences]

[Desire: Brief proof point - similar company result]

[Action: Clear, low-friction CTA]

[Signature]

LinkedIn连接请求（<300字符）：

Hi [Name], [Mutual connection/shared interest/genuine compliment].
Would love to connect. [No pitch]

LinkedIn跟进消息：

Thanks for connecting! [Value-first: insight, article, observation]

[Soft transition to why you reached out]

[Question, not pitch]

Step 5: Create Email Draft

步骤5：创建邮件草稿

If email connector available:
1. Create draft with to, subject, body
2. Return draft link
3. Note: "Draft created - review and send"

If not available:
1. Output email text
2. Note: "Copy to your email client"

If email connector available:
1. Create draft with to, subject, body
2. Return draft link
3. Note: "Draft created - review and send"

If not available:
1. Output email text
2. Note: "Copy to your email client"

Capability by Connector

按连接器划分的功能

Capability	Web Only	+ Enrichment	+ CRM	+ Email
Personalized opening	Basic	Deep	With history	Same
Verified email	No	Yes	Yes	Yes
Background details	Public only	Full	Full	Full
Prior relationship	No	No	Yes	Yes
Auto-create draft	No	No	No	Yes

功能	仅网络调研	+ Enrichment	+ CRM	+ Email
个性化开头	基础版	深度定制	包含历史关系	相同
验证过的邮箱	无	有	有	有
背景详情	仅公开信息	完整信息	完整信息	完整信息
过往合作关系	无	无	有	有
自动创建草稿	无	无	无	有

Message Templates by Scenario

不同场景的消息模板

Cold Outreach (No Prior Relationship)

陌生开发（无过往关系）

Subject: [Their initiative] + [your angle]

Hi [Name],

[Personal hook based on research - news, content, mutual connection].

[1 sentence on their likely challenge based on role/company].

[Brief proof: "We helped [Similar Company] achieve [Result]".]

Worth a 15-min call to see if relevant?

[Signature]

Subject: [Their initiative] + [your angle]

Hi [Name],

[Personal hook based on research - news, content, mutual connection].

[1 sentence on their likely challenge based on role/company].

[Brief proof: "We helped [Similar Company] achieve [Result]".]

Worth a 15-min call to see if relevant?

[Signature]

Warm Outreach (Have Met / Mutual Connection)

半熟开发（见过面/有共同联系人）

Subject: Following up from [context]

Hi [Name],

[Reference to how you know them / who connected you].

[Why reaching out now - their trigger].

[Specific value you can offer].

[CTA]

Subject: Following up from [context]

Hi [Name],

[Reference to how you know them / who connected you].

[Why reaching out now - their trigger].

[Specific value you can offer].

[CTA]

Re-Engagement (Went Dark)

重新激活（对方无回应）

Subject: [Short, curiosity-driven]

Hi [Name],

[Acknowledge time passed without being guilt-trippy].

[New reason to reconnect - their news or your news].

[Simple question to re-open dialogue].

[Signature]

Subject: [Short, curiosity-driven]

Hi [Name],

[Acknowledge time passed without being guilt-trippy].

[New reason to reconnect - their news or your news].

[Simple question to re-open dialogue].

[Signature]

Post-Event Follow-up

活动后跟进

Subject: Great meeting you at [Event]

Hi [Name],

[Specific memory from conversation].

[Value-add: article, intro, resource related to what you discussed].

[Soft CTA for next conversation].

Subject: Great meeting you at [Event]

Hi [Name],

[Specific memory from conversation].

[Value-add: article, intro, resource related to what you discussed].

[Soft CTA for next conversation].

Email Style Guidelines

邮件风格指南

Be concise but informative — Get to the point quickly. Busy people skim.
No markdown formatting — Never use asterisks, bold (text), or other markdown. Write plain text that looks natural in any email client.
Short paragraphs — 2-3 sentences max per paragraph. White space is your friend.
Simple lists — If listing items, use plain dashes. No fancy formatting.

Good:

Here's what I can share:
- Case study from a similar company
- 15-min intro call this week
- Quick demo if helpful

Bad:

**What I Can Offer:**
- **Case study** from a similar company
- **Intro call** this week

简洁且信息完整——尽快切入主题。忙碌的人只会快速浏览。
不使用Markdown格式——绝不要用星号、粗体（text）或其他Markdown格式。使用纯文本，确保在任何邮件客户端中显示自然。
短段落——每段最多2-3句话。留白很重要。
简单列表——如果需要列项，使用普通短横线。不要用复杂格式。

正确示例：

Here's what I can share:
- Case study from a similar company
- 15-min intro call this week
- Quick demo if helpful

错误示例：

**What I Can Offer:**
- **Case study** from a similar company
- **Intro call** this week

What NOT to Do

切勿做以下事项

Generic openers:

"I hope this email finds you well"
"I'm reaching out because..."
"I wanted to introduce myself"

Feature dumps:

Long paragraphs about your product
Multiple value props at once
No clear CTA

Fake personalization:

"I noticed you work at [Company]" (obviously)
"Congrats on your role" (without context)

Markdown in emails:

Using bold or italic asterisks
Headers or formatted lists that won't render

Instead:

Lead with something specific you learned
One clear value prop
One clear ask
Plain text formatting only

通用开头：

"I hope this email finds you well"
"I'm reaching out because..."
"I wanted to introduce myself"

堆砌功能：

长篇大论介绍你的产品
同时提及多个价值主张
没有明确的行动号召（CTA）

虚假个性化：

"我注意到你在[公司]工作"（这是显而易见的）
"恭喜你获得新职位"（无上下文）

邮件中使用Markdown：

使用粗体或斜体星号
使用无法正常显示的标题或格式化列表

正确做法：

从你调研到的具体信息入手
明确一个核心价值主张
明确一个行动请求
仅使用纯文本格式

Channel Selection

渠道选择

IF verified email available:
  → Email preferred (higher response rate)
  → Also provide LinkedIn backup

IF no email:
  → LinkedIn connection request
  → Follow-up message template for after connection

IF warm intro possible:
  → Suggest mutual connection outreach first

IF verified email available:
  → Email preferred (higher response rate)
  → Also provide LinkedIn backup

IF no email:
  → LinkedIn connection request
  → Follow-up message template for after connection

IF warm intro possible:
  → Suggest mutual connection outreach first

Company Configuration [CUSTOMIZE]

公司配置【可自定义】

markdown

undefined

markdown

undefined

Outreach Settings

My name: [Your Name]
My title: [Your Title]
My company: [Company Name]
Value prop: [One sentence - what you help with]

My name: [Your Name]
My title: [Your Title]
My company: [Company Name]
Value prop: [One sentence - what you help with]

Signature

[Your preferred email signature]

Proof Points

CTA Options

Default: "Worth a 15-min call?"
Softer: "Open to learning more?"
Specific: "Can I send over a quick demo?"

Default: "Worth a 15-min call?"
Softer: "Open to learning more?"
Specific: "Can I send over a quick demo?"

Tone

[Professional / Casual / Direct]
Industry-specific language: [Yes/No]

---

[Professional / Casual / Direct]
Industry-specific language: [Yes/No]

---

Example

示例

Input: "draft outreach to the Head of Engineering at Notion"

Research finds:

Name: David Tibbitts
Recent news: Notion launched AI features
Hiring: 5 ML engineer roles open
Background: Ex-Facebook, Stanford CS

Output:

markdown

undefined

输入： "draft outreach to the Head of Engineering at Notion"

调研结果：

姓名：David Tibbitts
近期新闻：Notion推出AI功能
招聘信息：开放5个机器学习工程师岗位
背景：前Facebook员工，斯坦福大学计算机科学专业

输出：

markdown

undefined

Outreach Draft: David Tibbitts @ Notion

Research Summary

Target: David Tibbitts, Head of Engineering at Notion Hook: They're scaling AI features and hiring ML talent Goal: Intro call about AI infrastructure

Email Draft

To: david@notion.so Subject: Notion's AI scaling + a thought

Hi David,

Saw Notion's AI rollout is gaining serious traction - congrats. With 5 ML roles open, seems like you're scaling fast.

Curious how you're thinking about inference infrastructure as usage grows. We helped [Similar Company] cut their AI serving costs 40% while improving latency.

Worth a 15-min call to see if relevant to your roadmap?

Best, [Name]

Subject Alternatives:

Notion AI + scaling question
Quick thought on Notion's ML hiring

To: david@notion.so Subject: Notion's AI scaling + a thought

Hi David,

Saw Notion's AI rollout is gaining serious traction - congrats. With 5 ML roles open, seems like you're scaling fast.

Curious how you're thinking about inference infrastructure as usage grows. We helped [Similar Company] cut their AI serving costs 40% while improving latency.

Worth a 15-min call to see if relevant to your roadmap?

Best, [Name]

Subject Alternatives:

Notion AI + scaling question
Quick thought on Notion's ML hiring

Email Draft Status

Draft created - check ~~email

undefined

Draft created - check ~~email

undefined