npx skills add https://github.com/borghei/claude-skills --skill cold-email生产级 B2B 冷邮件,听起来像是真人发出的,而非序列工具。
cold email, cold outreach, prospecting email, SDR email, sales email, first-touch email, follow-up sequence, email prospecting, outbound email, sales development, sequence building, email personalization, email deliverability, CAN-SPAM, GDPR, B2B outreach, email compliance, subject lines, reply rates, breakup email
步骤 1:收集背景信息
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
所需信息:
步骤 2:选择框架
| 框架 | 最佳适用场景 | 结构 |
|---|---|---|
| 问题优先 | 潜在客户有明显痛点 | 问题观察 > 相关性 > 请求 |
| 触发点驱动 | 存在特定事件(融资、招聘、新闻) | 触发点提及 > 与问题的关联 > 请求 |
| 共同联系人 | 有推荐人或共享网络 | 提及姓名 > 背景 > 请求 |
| 价值优先 | 你有真正有用的内容可以分享 | 见解/资源 > 简要背景 > 请求 |
| 直接请求 | 潜在客户意向强烈或资历很深 | 简要背景 > 直接提问 |
步骤 3:起草邮件
结构:
Subject: [2-4 个词,看起来像内部邮件]
[开场白:1 句关于他们世界的话——触发点、观察或问题]
[相关性:1-2 句话将他们的处境与你所做的事情联系起来]
[证明:1 句可信的证据——具体数字、指名客户、结果]
[请求:1 句话,包含一个单一、具体、低摩擦的行动号召]
[签名]
步骤 4:验证
步骤 1:撰写邮件 1(使用工作流 1)
步骤 2:规划跟进角度
每次跟进都需要一个独特的角度。在撰写前规划:
| 邮件 | 天数 | 角度 | 新内容 |
|---|---|---|---|
| 1 | 第 1 天 | 问题优先 | 初次触达 |
| 2 | 第 4 天 | 新证据 | 案例研究、数据点或近期结果 |
| 3 | 第 9 天 | 不同痛点 | 对他们世界的替代角度 |
| 4 | 第 16 天 | 行业洞察 | 关于他们领域的值得注意之处 |
| 5 | 第 25 天 | 直接提问 | 简单、清晰的请求,无需背景 |
| 6 | 第 35 天 | 告别 | 专业结束,请求推荐 |
步骤 3:撰写每次跟进邮件
每次跟进的规则:
步骤 4:撰写告别邮件
告别邮件结束循环。它表明这是最后一封,这反而会提高回复率。
模板:
Subject: closing the loop
[姓名],
这是我的最后一封邮件。如果 [具体问题] 成为优先事项,
请在此回复,我会跟进。
如果 [公司] 有其他人更适合此对话,
提供一个名字会很有帮助。
无论如何——[与具体事物相关的真诚祝愿]。
[签名]
步骤 1:诊断问题
| 症状 | 可能原因 | 修复方法 |
|---|---|---|
| 低打开率 (< 25%) | 主题行 | 测试新的主题行模式 |
| 打开但无回复 (< 2% 回复率) | 邮件正文 | 用更强的相关性和更低摩擦的行动号召重写 |
| 有回复但结果错误 | 行动号召不匹配 | 调整请求 |
| 高退回率 (> 5%) | 列表质量 | 发送前验证电子邮件地址 |
| 进入垃圾邮件 | 送达率 | 检查 SPF/DKIM/DMARC,减少发送量,预热域名 |
步骤 2:重写表现不佳的元素
一次只关注一个元素。当只有主题行是问题时,不要重写整个邮件。
步骤 3:测试和衡量
一旦你的邮件听起来像营销文案,就会被删除。
测试: 你会把这封邮件发给另一家公司的聪明同事吗?如果不会,就重写。
每句话必须完成以下工作之一:
如果一句话没有完成任何一项,就删掉它。
通用的个性化比没有更糟。
个性化必须与联系原因建立桥梁。
开场白应该是关于他们的处境、问题或背景。而不是关于你或你的产品。
不要要求他们预约通话、观看演示、阅读案例研究,并回复他们的时间表。只选一个。
| 受众 | 长度 | 语气 | 主题风格 | 有效方法 |
|---|---|---|---|---|
| 高管层 (CEO, CRO, CMO) | 3-4 句话 | 极其简短,同级水平,战略性 | 简短、模糊、看起来像内部邮件 | 重大问题 > 相关证明 > 一个问题 |
| 副总裁 / 总监 | 5-7 句话 | 直接,关注指标 | 稍微具体一些 | 具体观察 + 清晰的商业角度 |
| 经理 | 7-10 句话 | 实用,显示做过功课 | 可以是描述性的 | 具体问题 + 实用价值 + 简单的行动号召 |
| 技术人员 (工程师, 架构师) | 7-10 句话 | 精确,无废话 | 技术特异性 | 确切问题 > 精确解决方案 > 低摩擦请求 |
| 创始人 / 个人 | 5-7 句话 | 同理心,点对点 | 随意,人性化 | 共享经验 + 相关证明 + 对话式请求 |
规则:在组织架构中职位越高,你的邮件就需要越短。
主题行的目标是让邮件被打开。不是传达价值,不是显得聪明。只是被打开。
最好的冷邮件主题行看起来像内部邮件:简短,稍微模糊,有足够的好奇心让人点击。
| 模式 | 示例 | 为何有效 |
|---|---|---|
| 两到三个词 | "quick question" | 看起来像同事发的真实邮件 |
| 具体触发点 + 问题 | "your TechCrunch piece" | 足够具体,看起来不像垃圾邮件 |
| 共享背景 | "re: Series B" | 感觉像是跟进,而非冷邮件 |
| 观察 | "your ATS setup" | 相关,不像销售 |
| 推荐钩子 | "[mutual name] suggested I reach out" | 前置社交证明 |
| 角色特定 | "SDR team scaling" | 表明你知道他们是谁 |
| 邮件 | 发送日 | 间隔 | 备注 |
|---|---|---|---|
| 邮件 1 | 第 1 天 | — | 首次触达 |
| 邮件 2 | 第 4 天 | +3 天 | 新证据角度 |
| 邮件 3 | 第 9 天 | +5 天 | 不同痛点 |
| 邮件 4 | 第 16 天 | +7 天 | 行业洞察 |
| 邮件 5 | 第 25 天 | +9 天 | 直接提问 |
| 告别 | 第 35 天 | +10 天 | 结束循环 |
间隔时间随时间增加。坚持但不烦人。
| 角度类型 | 描述 | 示例 |
|---|---|---|
| 新证据 | 案例研究、数据点、近期结果 | "Since my last note, we helped [Company] reduce [metric] by [%]" |
| 不同痛点 | 他们世界中的替代问题 | "Setting aside [topic A] — are you dealing with [topic B]?" |
| 行业洞察 | 关于他们领域的值得注意之处 | "Saw [industry trend]. Most teams are responding by [approach]" |
| 直接提问 | 简单的请求,无需铺垫 | "[Name], quick one: who handles [function] at [Company]?" |
| 反向请求 | 请求推荐 | "If this isn't your area, who would you point me to?" |
| 社交证明 | 相关同行正在做 | "[Similar company] just went through this — here's what worked" |
层级 1:细分市场级(最低要求)
层级 2:公司级(标准)
层级 3:个人级(高级)
| 来源 | 你能找到什么 | 如何使用 |
|---|---|---|
| LinkedIn 个人资料 | 角色、任期、分享的内容 | 角色特定开场白,引用他们的帖子 |
| 公司博客 | 优先级、文化、技术选择 | 将你的解决方案与他们声明的优先级联系起来 |
| 招聘职位 | 增长领域、痛点、技术栈 | "You're hiring for X, which usually means..." |
| 新闻/媒体报道 | 融资、合作伙伴关系、发布 | 基于触发点的开场白 |
| GitHub/技术博客 | 技术决策、技术栈选择 | 技术相关性和可信度 |
| 播客/演讲 | 观点、专业领域 | "Your point about X in [talk] resonated..." |
| 组件 | 是什么 | 为什么 |
|---|---|---|
| 专用发送域名 | mail.yourdomain.com 或 outreach.yourdomain.com | 保护主域名声誉 |
| SPF 记录 | DNS TXT 记录,授权发送服务器 | 证明你有权发送 |
| DKIM 签名 | 电子邮件上的加密签名 | 证明邮件在传输过程中未被修改 |
| DMARC 策略 | DNS 记录,指定 SPF/DKIM 强制执行 | 告知接收服务器如何处理失败 |
| 域名预热 | 4-6 周逐渐增加发送量 | 与互联网服务提供商建立发件人声誉 |
| 周数 | 每日发送量 | 备注 |
|---|---|---|
| 1 | 10-20 | 仅发送给参与度高的联系人 |
| 2 | 20-40 | 混合暖联系人和冷联系人 |
| 3 | 40-70 | 以低量开始冷外联 |
| 4 | 70-100 | 密切关注退回率 |
| 5-6 | 100-150 | 如果退回率 < 3% 则增加 |
| 7+ | 150-200 最大值 | 冷外联的稳定状态 |
对所有发送给美国收件人的商业电子邮件的要求:
对发送给欧盟/欧洲经济区居民的电子邮件的要求:
对发送给加拿大收件人的商业电子信息的要求:
| 模式 | 为何失败 |
|---|---|
| "I hope this email finds you well" | 立即表明这是模板化的大规模外联 |
| "I wanted to reach out because..." | 在说任何实质内容之前的三字废话 |
| 以 "My name is X and I work at Y" 开头 | 他们能看到你的名字。从有用的内容开始。 |
| 在邮件 1 中罗列功能 | 当他们还不信任你时,没人关心功能 |
| 带有徽标和颜色的 HTML 模板 | 看起来像营销,被垃圾邮件过滤器拦截 |
| 假的 Re:/Fwd: 主题行 | 具有欺骗性,破坏信任 |
| "Just checking in" 跟进 | 不增加价值,削弱可信度 |
| 无背景的社交证明 | "We work with 500 companies" 没有相关性就毫无意义 |
| 在邮件 1 中使用长篇案例研究 | 留到跟进时使用 |
| 被动的行动号召 ("Let me know if you're interested") | 软弱。直接提问或提出具体步骤。 |
| 一封邮件中有多个行动号召 | 造成决策瘫痪。每封邮件一个请求。 |
| 从主域名发送 | 危及整个域名声誉 |
从真实个人发送,而非公司别名 — "sarah@mail.acme.com" 每次都优于 "sales@acme.com"。
发送前大声朗读邮件 — 如果你听到自己声音单调,就删减。如果听起来像宣传册,就重写。
安排发送时间 — 周二到周四,潜在客户时区的上午 8-10 点,对 B2B 产生最高的打开率。
活动前验证电子邮件 — 5% 的退回率会损害你的域名声誉。验证每个地址。
跟踪回复率,而非打开率 — 打开跟踪不可靠(隐私功能会阻止跟踪像素)。回复率才是重要的指标。
构建序列,而非单封邮件 — 大多数回复来自跟进,而非第一封邮件。在撰写前规划完整序列。
记录你的操作手册 — 每封成功的邮件、主题行和角度都应记录供团队使用。建立机构知识。
立即尊重退订请求 — 不仅是法律要求,也是专业必需。在 24 小时内处理。
轮换发送域名 — 使用 2-3 个发送域名来分配发送量并保护声誉。
无情地进行细分 — 发送给 1000 人的通用模板,其表现将不如发送给 50 个符合你理想画像的个性化邮件。
每周安装量
1
代码库
GitHub 星标数
29
首次出现
今天
安全审计
安装于
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
Production-grade B2B cold email that sounds like it came from a person, not a sequence tool.
cold email, cold outreach, prospecting email, SDR email, sales email, first-touch email, follow-up sequence, email prospecting, outbound email, sales development, sequence building, email personalization, email deliverability, CAN-SPAM, GDPR, B2B outreach, email compliance, subject lines, reply rates, breakup email
Step 1: Gather Context
Required information:
Step 2: Choose Framework
| Framework | Best When | Structure |
|---|---|---|
| Problem-First | Prospect has a visible pain point | Problem observation > Relevance > Ask |
| Trigger-Based | There is a specific event (funding, hiring, news) | Trigger reference > Connection to problem > Ask |
| Mutual Connection | Referral or shared network | Name drop > Context > Ask |
| Value-First | You have something genuinely useful to share | Insight/resource > Brief context > Ask |
| Direct Ask | Prospect is high-intent or very senior | Brief context > Direct question |
Step 3: Draft the Email
Structure:
Subject: [2-4 words, looks like an internal email]
[Opener: 1 sentence about their world — trigger, observation, or question]
[Relevance: 1-2 sentences connecting their situation to what you do]
[Proof: 1 sentence of credible evidence — specific number, named customer, result]
[Ask: 1 sentence with a single, specific, low-friction CTA]
[Sign-off]
Step 4: Validate
Step 1: Write Email 1 (Using Workflow 1)
Step 2: Plan Follow-Up Angles
Each follow-up needs a distinct angle. Plan before writing:
| Day | Angle | What is New | |
|---|---|---|---|
| 1 | Day 1 | Problem-first | Initial outreach |
| 2 | Day 4 | New evidence | Case study, data point, or recent result |
| 3 | Day 9 | Different pain point | Alternative angle on their world |
| 4 | Day 16 | Industry insight | Something notable about their space |
| 5 | Day 25 | Direct question | Simple, clear ask without context |
| 6 | Day 35 | Breakup | Professional close, referral ask |
Step 3: Write Each Follow-Up
Rules for every follow-up:
Step 4: Write the Breakup Email
The breakup email closes the loop. It signals this is the last one, which paradoxically increases reply rate.
Template:
Subject: closing the loop
[Name],
Last note from me. If [specific problem] becomes a priority,
reply here and I'll pick it up.
If there's someone else at [Company] better suited for this
conversation, a name would help.
Either way — [genuine well-wish related to something specific].
[Sign-off]
Step 1: Diagnose the Problem
| Symptom | Likely Cause | Fix |
|---|---|---|
| Low open rate (< 25%) | Subject lines | Test new subject line patterns |
| Opens but no replies (< 2% reply rate) | Email body | Rewrite with stronger relevance and lower-friction CTA |
| Replies but wrong outcome | CTA mismatch | Adjust the ask |
| High bounce rate (> 5%) | List quality | Verify email addresses before sending |
| Landing in spam | Deliverability | Check SPF/DKIM/DMARC, reduce send volume, warm domain |
Step 2: Rewrite the Underperforming Element
Focus on one element at a time. Do not rewrite the entire email when only the subject line is the problem.
Step 3: Test and Measure
The moment your email sounds like marketing copy, it is deleted.
Test: Would you send this to a smart colleague at another company? If not, rewrite.
Each sentence must do one of these jobs:
If a sentence does none of these, cut it.
Generic personalization is worse than none.
The personalization must bridge to the reason for reaching out.
The opener should be about their situation, problem, or context. Not about you or your product.
Do not ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one.
| Audience | Length | Tone | Subject Style | What Works |
|---|---|---|---|---|
| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem > relevant proof > one question |
| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
| Manager | 7-10 sentences | Practical, shows homework | Can be descriptive | Specific problem + practical value + easy CTA |
| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem > precise solution > low-friction ask |
| Founder / Solo | 5-7 sentences | Empathetic, peer-to-peer | Casual, human |
Rule: The higher up the org chart, the shorter your email needs to be.
The goal of a subject line is to get the email opened. Not to convey value, not to be clever. Just opened.
The best cold email subject lines look like internal emails: short, slightly vague, enough curiosity to click.
| Pattern | Example | Why It Works |
|---|---|---|
| Two or three words | "quick question" | Looks like a real email from a colleague |
| Specific trigger + question | "your TechCrunch piece" | Specific enough to not look like spam |
| Shared context | "re: Series B" | Feels like a follow-up, not cold |
| Observation | "your ATS setup" | Relevant, not salesy |
| Referral hook | "[mutual name] suggested I reach out" | Social proof front-loaded |
| Role-specific | "SDR team scaling" | Shows you know who they are |
| Send Day | Gap | Notes | |
|---|---|---|---|
| Email 1 | Day 1 | — | First touch |
| Email 2 | Day 4 | +3 days | New evidence angle |
| Email 3 | Day 9 | +5 days | Different pain point |
| Email 4 | Day 16 | +7 days | Industry insight |
| Email 5 | Day 25 | +9 days | Direct question |
| Breakup | Day 35 | +10 days | Close the loop |
Gaps increase over time. Persistent but not annoying.
| Angle Type | Description | Example |
|---|---|---|
| New evidence | Case study, data point, recent result | "Since my last note, we helped [Company] reduce [metric] by [%]" |
| Different pain | Alternative problem in their world | "Setting aside [topic A] — are you dealing with [topic B]?" |
| Industry insight | Something notable about their space | "Saw [industry trend]. Most teams are responding by [approach]" |
| Direct question | Simple ask without buildup | "[Name], quick one: who handles [function] at [Company]?" |
| Reverse ask | Request for referral | "If this isn't your area, who would you point me to?" |
| Social proof | Relevant peer doing it | "[Similar company] just went through this — here's what worked" |
Tier 1: Segment-Level (Minimum)
Tier 2: Company-Level (Standard)
Tier 3: Individual-Level (Premium)
| Source | What You Find | How to Use |
|---|---|---|
| LinkedIn profile | Role, tenure, content they share | Role-specific opener, reference their posts |
| Company blog | Priorities, culture, technology choices | Connect your solution to their stated priorities |
| Job postings | Growth areas, pain points, tech stack | "You're hiring for X, which usually means..." |
| Press/news | Funding, partnerships, launches | Trigger-based openers |
| GitHub/tech blogs | Technical decisions, stack choices | Technical relevance and credibility |
| Podcast/talks | Opinions, expertise areas | "Your point about X in [talk] resonated..." |
| Component | What | Why |
|---|---|---|
| Dedicated sending domain | mail.yourdomain.com or outreach.yourdomain.com | Protects primary domain reputation |
| SPF record | DNS TXT record authorizing sending servers | Proves you are authorized to send |
| DKIM signing | Cryptographic signature on emails | Proves emails were not modified in transit |
| DMARC policy | DNS record specifying SPF/DKIM enforcement | Tells receiving servers how to handle failures |
| Domain warmup | 4-6 weeks of gradually increasing volume | Builds sender reputation with ISPs |
| Week | Daily Volume | Notes |
|---|---|---|
| 1 | 10-20 | Send to engaged contacts only |
| 2 | 20-40 | Mix of warm and cold contacts |
| 3 | 40-70 | Begin cold outreach at low volume |
| 4 | 70-100 | Monitor bounce rates closely |
| 5-6 | 100-150 | Increase if bounce rate < 3% |
| 7+ | 150-200 max | Steady state for cold outreach |
Required for all commercial email to US recipients:
Required for email to EU/EEA residents:
Required for commercial electronic messages to Canadian recipients:
| Pattern | Why It Fails |
|---|---|
| "I hope this email finds you well" | Instant signal that this is templated mass outreach |
| "I wanted to reach out because..." | Three words of nothing before saying anything |
| Opening with "My name is X and I work at Y" | They can see your name. Start with something useful. |
| Feature dump in email 1 | Nobody cares about features when they do not trust you yet |
| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |
| Fake Re:/Fwd: subject lines | Deceptive, destroys trust |
| "Just checking in" follow-ups | Adds no value, removes credibility |
| Social proof without context | "We work with 500 companies" means nothing without relevance |
| Long-form case study in email 1 | Save it for follow-up |
| Passive CTAs ("Let me know if you're interested") | Weak. Ask a direct question or propose a specific step. |
| Multiple CTAs in one email | Creates decision paralysis. One ask per email. |
| Sending from your primary domain |
Send from a real person, not a company alias — "sarah@mail.acme.com" outperforms "sales@acme.com" every time.
Read the email aloud before sending — If you hear yourself droning, cut. If it sounds like a brochure, rewrite.
Time your sends — Tuesday through Thursday, 8-10 AM in the prospect's timezone, produces the highest open rates for B2B.
Verify emails before campaigns — A 5% bounce rate damages your domain reputation. Verify every address.
Track reply rate, not open rate — Open tracking is unreliable (privacy features block tracking pixels). Reply rate is the metric that matters.
Build sequences, not individual emails — Most replies come from follow-ups, not the first email. Plan the full sequence before writing.
Document your playbook — Every winning email, subject line, and angle should be documented for the team. Build institutional knowledge.
Respect opt-outs immediately — Not just legally required, but professionally essential. Process within 24 hours.
Rotate sending domains — Use 2-3 sending domains to distribute volume and protect reputation.
Segment relentlessly — A generic template sent to 1,000 people will underperform a personalized email sent to 50 who match your ideal profile.
Weekly Installs
1
Repository
GitHub Stars
29
First Seen
Today
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
zencoder1
amp1
cline1
openclaw1
opencode1
cursor1
社交媒体内容策略指南:创建、优化与互动全流程 | 营销技能
35,900 周安装
| Shared experience + relevant proof + conversational ask |
| Risks your entire domain reputation |