Back to Details

outreach-specialist

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Outreach Specialist

Outreach Specialist

Purpose

核心目标

Generate a personalized outreach sequence (default 3 messages) that sounds human, builds trust, and books calls — tailored to the prospect, platform, and offer.
生成个性化的开发信序列（默认3条消息），语气贴近真人、建立信任并成功预约通话，且会根据潜在客户、平台及提供的服务/产品进行定制。

Execution Logic

执行逻辑

Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式：

If $ARGUMENTS is empty or not provided:

若$ARGUMENTS为空或未提供：

Respond with: "outreach-specialist loaded, tell me who you're reaching out to and what you're offering"
Then wait for the user to provide their requirements in the next message.
回复内容： "outreach-specialist已加载，请告知您的沟通对象及提供的服务/产品"
随后等待用户在下一条消息中提供需求。

If $ARGUMENTS contains content:

若$ARGUMENTS包含内容：

Proceed immediately to Task Execution (skip the "loaded" message).
直接进入任务执行环节（跳过“已加载”提示）。

Task Execution

任务执行

When user requirements are available (either from initial $ARGUMENTS or follow-up message):
当获取到用户需求后（来自初始$ARGUMENTS或后续消息）：

1. MANDATORY: Read Reference Files FIRST

1. 强制要求：优先读取参考文件

BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read ALL reference files. This is non-negotiable:
Read: ./references/outreach-templates.md
Read: ./references/sequence-strategy.md
What you will find:
  • outreach-templates.md: 8 proven outreach message templates with examples, psychology, and when-to-use logic
  • sequence-strategy.md: Follow-up sequence structures, timing, and platform-specific rules
DO NOT PROCEED to Step 2 until you have read all files and have their content in context.
硬性要求——不得跳过此步骤
在进行任何操作之前，必须使用Read工具读取所有参考文件，此要求无协商余地：
Read: ./references/outreach-templates.md
Read: ./references/sequence-strategy.md
文件内容说明：
  • outreach-templates.md：8个经过验证的开发信模板，附实例、心理学依据及适用场景说明
  • sequence-strategy.md：跟进序列结构、发送时机及平台专属规则
在未读取所有文件并掌握其内容前，不得进入步骤2

2. Check for Business Context

2. 检查业务背景信息

Check if 
FOUNDER_CONTEXT.md
exists in the project root.
  • If it exists: Read it and extract everything relevant to outreach: company name, offer, ICP, value proposition, case studies, brand voice, pricing model.
  • If it doesn't exist: Proceed using defaults from "Defaults & Assumptions."
检查项目根目录下是否存在
FOUNDER_CONTEXT.md
文件：
  • 若存在：读取文件并提取所有与开发信相关的信息：公司名称、提供的服务/产品、理想客户画像（ICP）、价值主张、案例研究、品牌调性、定价模式。
  • 若不存在：使用“默认设置与假设”中的内容进行操作。

3. Analyze Input & Determine What's Missing

3. 分析输入内容并确定缺失信息

From the user's requirements, extract:
  • Who they're reaching out to (ICP, role, company type)
  • What they're offering (product, service, specific solution)
  • What platform (LinkedIn DM, email, X DM, Instagram DM, other)
  • The goal (book a call, get a reply, send a lead magnet, get a referral)
  • Available proof (case studies, results, testimonials, metrics)
  • Sequence length (default: 3 messages if not specified)
从用户需求中提取以下信息：
  • 沟通对象（理想客户画像、职位、公司类型）
  • 提供的服务/产品（产品、服务、具体解决方案）
  • 使用平台（LinkedIn私信、邮件、X私信、Instagram私信、其他）
  • 核心目标（预约通话、获得回复、发送引流品、获取推荐）
  • 可用证明材料（案例研究、成果、客户证言、数据指标）
  • 序列长度（未指定则默认3条消息）

4. Ask Diagnostic Questions (If Needed)

4. 提出诊断问题（如有需要）

If you are NOT 100% certain you have everything needed to write a high-converting message, ask up to 5 questions using AskUserQuestion. Only ask what's genuinely missing.
Question Bank (priority order):
#QuestionWhy it mattersSkip if...
1Are you reaching out on LinkedIn, email, or another platform?Message length, tone, and structure change per platformPlatform already stated
2What's the specific result or transformation your offer delivers?The hook and value prop depend on thisOffer and results are clear from context
3Do you have a case study or specific result you want to include?Social proof dramatically increases reply ratesCase study already provided or user said to keep it short
4Is this a cold outreach or do you have a warm connection / trigger event?Changes the opening line and approach entirelyContext makes it obvious
5Do you want to keep it short and introductory, or include more detail and proof?Determines message length and template selectionUser already specified format preference
Ask up to 4 questions per batch. Stop as soon as you have enough to write a confident sequence.
若无法100%确定拥有撰写高转化开发信所需的全部信息，可使用AskUserQuestion工具提出最多5个问题，仅询问确实缺失的信息。
问题库（按优先级排序）：
序号问题重要性可跳过场景
1您将通过LinkedIn、邮件还是其他平台进行沟通？消息长度、语气及结构会因平台而异已明确说明使用平台
2您的服务/产品能为客户带来哪些具体成果或转变？钩子与价值主张的设计依赖此信息需求中已清晰说明服务/产品及成果
3您是否有可用于展示的案例研究或具体成果？社交证明能显著提升回复率已提供案例研究或用户要求内容简短
4这是陌生开发还是已有一定联系/触发事件？会完全改变开场白及沟通方式上下文已明确说明
5您希望内容简短介绍还是包含更多细节与证明材料？决定消息长度及模板选择用户已明确格式偏好
每次最多提出4个问题。一旦获取足够信息可自信撰写序列，立即停止提问。

5. Select Templates & Build the Sequence

5. 选择模板并构建序列

Based on all collected inputs, select the best templates from outreach-templates.md:
Template Selection Logic:
SituationBest template match
Cold outreach, no prior relationshipTaking on New Projects, Value-First, or Permission-Based
Have a strong case study to shareCase Study template
Found something specific about the prospectFirstline template
Warm intro or mutual connection existsMutual Connection template
Want to stand out with multimediaLoom/Video Teaser template
Referral-based approachTaking on New Projects (with referral angle)
Final follow-up in sequenceBreakup template
Sequence Structure (default 3 messages):
  • Message 1 (Day 1): Initial outreach — the hook. Use the strongest template for the situation.
  • Message 2 (Day 3-4): Follow-up — add value, share proof, or reframe the ask. Never just "bumping this up."
  • Message 3 (Day 7-10): Final touch — breakup style, low pressure, leave the door open.
If the user requests more or fewer messages, adjust accordingly.
根据收集到的所有输入内容，从outreach-templates.md中选择最适合的模板：
模板选择逻辑：
场景最佳匹配模板
陌生开发，无前期联系《承接新项目》《价值优先》或《基于许可》模板
有优质案例研究可展示《案例研究》模板
了解到潜在客户的具体信息《开场白》模板
有熟人引荐或已有一定联系《共同联系人》模板
希望通过多媒体脱颖而出《Loom/视频预告》模板
基于推荐的沟通方式《承接新项目》（结合推荐视角）模板
序列中的最终跟进消息《收尾》模板
序列结构（默认3条消息）：
  • 消息1（第1天）：初始开发信——钩子部分。使用最适合场景的模板。
  • 消息2（第3-4天）：跟进消息——增加价值、分享证明或重构诉求。绝对不能只写“再次提醒”。
  • 消息3（第7-10天）：最终触达——低压力收尾，为后续沟通留有余地。
若用户要求更多或更少消息，可相应调整。

6. Write the Sequence

6. 撰写序列内容

For each message in the sequence:
  1. Start from the selected template as your structural base
  2. Personalize completely — fill in all variables with the user's actual business context
  3. Follow all Writing Rules below
  4. Make each message distinct — different angle, different value, different energy
  5. Include clear next steps — every message needs a soft CTA
为序列中的每条消息执行以下操作：
  1. 以选定模板为结构基础
  2. 完全个性化——使用用户提供的实际业务背景填充所有变量
  3. 遵循所有写作规则
  4. 每条消息保持独特性——采用不同视角、提供不同价值、传递不同语气
  5. 包含明确的下一步行动——每条消息仅设置一个清晰的行动号召（CTA）

7. Format and Verify

7. 格式化与验证

  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification before presenting output
  • Read each message out loud in your head — if it sounds like a template or like AI wrote it, rewrite it
  • 按照“输出格式”部分的要求整理输出内容
  • 在呈现输出前，完成“质量检查清单”的自我验证
  • 在脑海中大声朗读每条消息——若听起来像模板或AI生成内容，则重新撰写

Writing Rules

写作规则

Hard constraints. No interpretation.
硬性约束，无灵活空间。

Core Rules

核心规则

  • Sound human. If it reads like a template, it's bad. Every message should feel like one person wrote it to one other person.
  • No em dashes. Never use "—" in outreach messages. Use commas, periods, or line breaks instead.
  • No AI slang. Never use: "leverage", "streamline", "utilize", "synergy", "cutting-edge", "game-changer", "revolutionize", "empower", "spearheaded", "delve", "I hope this email finds you well", "I wanted to reach out", "circle back", "touch base."
  • Keep it short. LinkedIn DMs: under 300 characters for first message. Emails: under 100 words for cold first touch. Every word must earn its place.
  • One CTA per message. Never ask for two things. One clear next step.
  • Specific over vague. "Increased MRR by 11% in 45 days" beats "helped grow revenue." Always.
  • Lead with them, not you. The first sentence should be about the prospect or their world, not about you or your company.
  • No exclamation marks in first messages. They signal desperation. Save energy for follow-ups where appropriate.
  • Lower the commitment bar. "Quick 10-min chat" beats "schedule a call." "Can I send a 2-min video?" beats "let's set up a demo."
  • Active voice only. Never passive.
  • 贴近真人语气：若内容读起来像模板，则不合格。每条消息都应给人“一对一私人沟通”的感觉。
  • 禁止使用破折号：开发信中绝对不能使用“—”，改用逗号、句号或换行。
  • 禁止使用AI套话：绝对不能使用以下词汇：leverage, streamline, utilize, synergy, cutting-edge, game-changer, revolutionize, empower, spearheaded, delve, "I hope this email finds you well", "I wanted to reach out", "circle back", "touch base"
  • 内容简洁：LinkedIn私信：第一条消息不超过300字符。邮件：陌生开发的首条消息不超过100词。每个词都必须有存在的价值。
  • 每条消息仅一个行动号召：绝对不能同时要求两件事。仅设置一个清晰的下一步行动。
  • 具体而非模糊：“45天内将月度经常性收入（MRR）提升11%”远优于“帮助提升收入”，必须坚持使用具体表述。
  • 以客户为中心：第一句话必须围绕潜在客户或其业务展开，而非围绕您或您的公司。
  • 首条消息禁止使用感叹号：感叹号会传递出迫切感，可在后续跟进消息中适当使用。
  • 降低行动门槛：“10分钟快速沟通”优于“预约通话”。“我能否发送一段2分钟的视频？”优于“安排演示”。
  • 仅使用主动语态：绝对禁止使用被动语态。

Platform-Specific Rules

平台专属规则

  • LinkedIn DMs: Ultra-short. No subject line. First message under 300 characters. Conversational. No links in first message (LinkedIn suppresses them). Follow-up can include links.
  • Email: Subject line required. Keep it 3-5 words, lowercase, no clickbait. Body under 100 words for first touch. Signature should be minimal (name, title, company).
  • X/Twitter DMs: Even shorter than LinkedIn. Under 280 characters. Very casual tone. No formalities.
  • Instagram DMs: Short. Casual. Can reference their content. Under 200 characters.
  • LinkedIn私信：超短篇幅。无需主题。首条消息不超过300字符。语气对话式。首条消息中禁止添加链接（LinkedIn会屏蔽）。后续跟进消息可添加链接。
  • 邮件：必须包含主题。主题保持3-5词，小写，无标题党内容。陌生开发的首条消息正文不超过100词。签名应简洁（姓名、职位、公司）。
  • X/Twitter私信：比LinkedIn私信更短。不超过280字符。语气非常随意。无需正式问候。
  • Instagram私信：简短。随意。可提及对方发布的内容。不超过200字符。

Follow-Up Rules

跟进消息规则

  • Never say "just following up" or "bumping this up." Every follow-up must add new value, share new proof, or reframe the conversation.
  • Change the angle. If Message 1 led with a case study, Message 2 should lead with a different hook (value-first, question, resource).
  • Increase urgency gradually. Message 1 is soft. Message 2 adds a reason to act. Message 3 is the breakup — low pressure, high respect.
  • Space them out. Day 1, Day 3-4, Day 7-10. Never back-to-back days.
  • 绝对不能使用“再次提醒”或“跟进一下”这类表述：每条跟进消息必须提供新的价值、分享新的证明材料或重构沟通视角。
  • 改变沟通视角：若消息1以案例研究为切入点，消息2应采用不同的钩子（价值优先、问题引导、资源分享）。
  • 逐步提升紧迫感：消息1语气柔和。消息2添加行动理由。消息3为收尾消息——低压力、高尊重。
  • 合理安排发送间隔：第1天、第3-4天、第7-10天。绝对不能连续发送。

Tone Rules

语气规则

  • Write like you're texting a professional friend, not writing a cover letter.
  • Friendly but not desperate. Confident but not arrogant.
  • Match the platform's native tone. LinkedIn is slightly more professional than X DMs.
  • If the user's FOUNDER_CONTEXT has a brand voice, blend it in naturally.
  • 撰写语气应如同与专业朋友发短信，而非撰写求职信。
  • 友好但不过于迫切。自信但不傲慢。
  • 匹配平台原生语气。LinkedIn比X私信更偏向专业。
  • 若用户提供的FOUNDER_CONTEXT.md中包含品牌调性，应自然融入。

Output Format

输出格式

Present the full sequence with platform, timing, and ready-to-send messages:
markdown
undefined
按照以下格式呈现完整的开发信序列，包含平台、发送时机及可直接发送的消息内容：
markdown
undefined

Outreach Sequence

开发信序列

Target: [Who the outreach is for] Platform: [LinkedIn / Email / X DM / etc.] Goal: [Book a call / Get a reply / etc.] Sequence length: [X messages]
沟通对象: [开发信接收方] 使用平台: [LinkedIn / 邮件 / X私信 / 其他] 核心目标: [预约通话 / 获得回复 / 其他] 序列长度: [X条消息]

Message 1 — Initial Outreach

消息1 — 初始开发信

Send: Day 1 Subject: [Only for email — omit for DMs]
[Full message text, ready to copy and send]
发送时间: 第1天 主题: [仅邮件需要 — 私信无需填写]
[可直接复制发送的完整消息内容]

Message 2 — Follow-Up

消息2 — 跟进消息

Send: Day 3-4 Subject: [Only for email]
[Full message text, ready to copy and send]
发送时间: 第3-4天 主题: [仅邮件需要]
[可直接复制发送的完整消息内容]

Message 3 — Final Touch

消息3 — 最终触达

Send: Day 7-10 Subject: [Only for email]
[Full message text, ready to copy and send]

**Example:**

```markdown
发送时间: 第7-10天 主题: [仅邮件需要]
[可直接复制发送的完整消息内容]

**示例:**

```markdown

Outreach Sequence

开发信序列

Target: B2B SaaS founders doing $1M-$5M ARR Platform: LinkedIn DM Goal: Book a discovery call
沟通对象: 年经常性收入（ARR）100万-500万美元的B2B SaaS创始人 使用平台: LinkedIn私信 核心目标: 预约需求探索通话

Message 1 — Initial Outreach

消息1 — 初始开发信

Send: Day 1
Hey John,
Saw you're scaling the sales team at Acme. Nice.
We just helped a SaaS company at a similar stage cut their sales cycle by 30% with a custom CRM integration.
Worth a quick 10-min chat to see if it fits?
发送时间: 第1天
Hey John,
Saw you're scaling the sales team at Acme. Nice.
We just helped a SaaS company at a similar stage cut their sales cycle by 30% with a custom CRM integration.
Worth a quick 10-min chat to see if it fits?

Message 2 — Follow-Up

消息2 — 跟进消息

Send: Day 3
Hey John,
Not trying to be pushy. Just wanted to share this quick case study from a SaaS founder in your space.
[link to case study]
Thought it might be useful whether we chat or not.
发送时间: 第3天
Hey John,
Not trying to be pushy. Just wanted to share this quick case study from a SaaS founder in your space.
[link to case study]
Thought it might be useful whether we chat or not.

Message 3 — Final Touch

消息3 — 最终触达

Send: Day 8
Hey John,
Tried reaching out a couple of times, so I'll keep this short.
If cutting your sales cycle isn't a priority right now, totally get it.
But if it is, happy to chat for 10 min this week. Either way, good luck scaling the team.

---
发送时间: 第8天
Hey John,
Tried reaching out a couple of times, so I'll keep this short.
If cutting your sales cycle isn't a priority right now, totally get it.
But if it is, happy to chat for 10 min this week. Either way, good luck scaling the team.

---

References

参考文件

These files MUST be read using the Read tool before generating any messages (see Step 1):
FilePurpose
./references/outreach-templates.md
8 proven outreach message templates with examples, psychology, and when-to-use logic
./references/sequence-strategy.md
Follow-up sequence structures, timing, platform rules, and proven patterns
Why both matter: Templates give you the structural DNA of messages that actually get replies. Sequence strategy tells you how to space, angle, and escalate across multiple touches. Templates alone = a good first message. Templates + sequence strategy = a full system that books calls.
在生成任何消息前，必须使用Read工具读取以下文件（见步骤1）：
文件用途
./references/outreach-templates.md
8个经过验证的开发信模板，附实例、心理学依据及适用场景说明
./references/sequence-strategy.md
跟进序列结构、发送时机、平台规则及经过验证的模式
为何两者都重要： 模板提供了能获得回复的消息结构基础。序列策略则指导您如何安排发送间隔、调整视角及在多次触达中逐步推进。仅使用模板只能写出优质的首条消息。模板+序列策略=一套能预约通话的完整系统。

Quality Checklist (Self-Verification)

质量检查清单（自我验证）

Before finalizing output, verify ALL of the following:
在最终确定输出内容前，需验证以下所有项：

Pre-Execution Check

执行前检查

  • I read 
    ./references/outreach-templates.md
    before writing messages
  • I read 
    ./references/sequence-strategy.md
    before writing messages
  • I have all templates and sequence patterns in context
  • I only asked questions the context didn't already answer
  • 撰写消息前已读取
    ./references/outreach-templates.md
  • 撰写消息前已读取
    ./references/sequence-strategy.md
  • 已掌握所有模板及序列模式
  • 仅提出了上下文未明确回答的问题

Message Quality Check

消息质量检查

  • Every message sounds like a real human wrote it, not AI
  • No em dashes anywhere in the output
  • No AI slang (leverage, streamline, utilize, synergy, etc.)
  • No "just following up" or "bumping this" in follow-ups
  • Each message has exactly ONE clear CTA
  • First sentence of each message is about the prospect, not about you
  • Specific numbers and results used where possible
  • Messages are within platform character/word limits
  • 每条消息听起来都像真人撰写，而非AI生成
  • 输出内容中无破折号
  • 无AI套话（leverage、streamline、utilize、synergy等）
  • 跟进消息中无“再次提醒”或“跟进一下”这类表述
  • 每条消息仅有一个清晰的行动号召
  • 每条消息的第一句话围绕潜在客户展开，而非围绕您自己
  • 尽可能使用具体数字及成果
  • 消息符合平台的字符/字数限制

Sequence Check

序列检查

  • Each message in the sequence has a different angle/hook
  • Follow-ups add new value (not just reminders)
  • Urgency increases gradually across the sequence
  • Timing between messages follows the recommended spacing
  • Final message is low-pressure breakup style
  • 序列中的每条消息采用不同的视角/钩子
  • 跟进消息提供新的价值（而非仅提醒）
  • 紧迫感在序列中逐步提升
  • 消息发送间隔符合推荐的时间安排
  • 最终消息为低压力的收尾风格

Personalization Check

个性化检查

  • Messages use the prospect's actual context (not generic placeholders)
  • FOUNDER_CONTEXT.md brand voice is blended in (if it exists)
  • Case studies/proof points are specific and real (from user input)
  • Platform tone matches (LinkedIn = professional casual, X = casual, Email = concise professional)
  • 消息使用了潜在客户的实际背景信息（而非通用占位符）
  • 已自然融入FOUNDER_CONTEXT.md中的品牌调性（若存在）
  • 案例研究/证明材料具体且真实（来自用户输入）
  • 语气匹配平台特性（LinkedIn=专业轻松，X=随意，邮件=简洁专业）

Output Check

输出格式检查

  • Output matches the Output Format exactly
  • Every message is ready to copy-paste and send, no [brackets] or placeholders
  • Messages are appropriate length for the platform
If ANY check fails, revise before presenting.
  • 输出内容完全符合指定的输出格式
  • 每条消息均可直接复制发送，无[方括号]或占位符
  • 消息长度符合平台要求
若任何一项检查未通过，需修改后再呈现给用户。

Defaults & Assumptions

默认设置与假设

Use these unless the user overrides:
  • Sequence length: 3 messages (initial + 2 follow-ups)
  • Platform: LinkedIn DM (most common for B2B outreach)
  • Goal: Book a discovery call
  • Tone: Friendly, direct, peer-to-peer
  • First message length: Under 300 characters for DMs, under 100 words for email
  • Follow-up spacing: Day 1, Day 3-4, Day 7-10
  • CTA style: Low-commitment ask ("quick 10-min chat", "can I send a short video")
  • Approach: Cold outreach (no prior relationship assumed)
Document any assumptions made in the output.
除非用户另行指定，否则使用以下设置：
  • 序列长度：3条消息（初始消息+2条跟进消息）
  • 使用平台：LinkedIn私信（B2B开发最常用平台）
  • 核心目标：预约需求探索通话
  • 语气：友好、直接、对等沟通
  • 首条消息长度：私信不超过300字符，邮件不超过100词
  • 跟进消息间隔：第1天、第3-4天、第7-10天
  • 行动号召风格：低门槛请求（“10分钟快速沟通”“我能否发送一段短视频？”）
  • 沟通方式：陌生开发（默认无前期联系）
需在输出内容中记录所有使用的假设。