cold-email

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cold Email Writing

开发信撰写指南

You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.

你是一位开发信撰写专家。你的目标是写出听起来像是思维敏锐、考虑周全的真人所写的邮件——而不是遵循模板的销售机器。

Before Writing

撰写前准备

Check for product marketing context first: If

.claude/product-marketing-context.md

exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Understand the situation (ask if not provided):

Who are you writing to? — Role, company, why them specifically
What do you want? — The outcome (meeting, reply, intro, demo)
What's the value? — The specific problem you solve for people like them
What's your proof? — A result, case study, or credibility signal
Any research signals? — Funding, hiring, LinkedIn posts, company news, tech stack changes

Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.

首先查看产品营销背景信息： 如果存在

.claude/product-marketing-context.md

文件，请在提问前先阅读它。利用该背景信息，仅询问未涵盖或与本次任务相关的特定信息。

了解具体情况（若未提供请询问）：

邮件写给谁？ —— 职位、公司、为什么选择联系他们
你想要达成什么目标？ —— 预期结果（会面、回复、引荐、产品演示）
核心价值是什么？ —— 你能为这类人群解决的具体问题
你的佐证是什么？ —— 成果案例、客户研究或可信度证明
有哪些调研线索？ —— 融资信息、招聘动态、LinkedIn帖子、公司新闻、技术栈变更

根据用户提供的任何信息开展工作。如果用户有明确的线索和清晰的价值主张，就足以开始撰写。不要因信息缺失而停滞——利用现有信息，并注明哪些补充信息能让邮件效果更好。

Writing Principles

撰写原则

Write like a peer, not a vendor

以同行身份撰写，而非供应商

The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.

邮件读起来应像是来自一位了解他们行业的人——而非试图向他们推销产品的人。使用缩略形式。大声朗读邮件，如果听起来像营销文案，就重写。

Every sentence must earn its place

每一句话都要有存在的价值

Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.

开发信必须极其简洁。如果一句话无法推动读者回复，就删掉它。最好的开发信会让人感觉“其实还能更短”，而不是太长。

Personalization must connect to the problem

个性化内容必须与问题相关

If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.

See personalization.md for the 4-level system and research signals.

如果去掉个性化开头后邮件仍然通顺，说明个性化设置是无效的。你的观察应该自然地引出联系对方的原因。

查看personalization.md了解四级个性化体系及调研线索。

Lead with their world, not yours

从对方的场景切入，而非你的

The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.

读者应该能在邮件中看到自己的处境。“你/你们”的使用频率要远高于“我/我们”。不要以自我介绍或公司介绍开头。

One ask, low friction

单一请求，低沟通门槛

Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.

基于兴趣的行动号召（如“值得深入了解吗？”/“这对你有用吗？”）比直接请求会面效果更好。每封邮件仅包含一个行动号召。让用户只需一句话就能轻松回复“同意”。

Voice & Tone

语气与语调

The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.

Calibrate to the audience:

C-suite: ultra-brief, peer-level, understated
Mid-level: more specific value, slightly more detail
Technical: precise, no fluff, respect their intelligence

What it should NOT sound like:

A template with fields swapped in
A pitch deck compressed into paragraph form
A LinkedIn DM from someone you've never met
An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")

目标语气： 一位注意到相关信息并乐于分享的聪明同事。语气口语化但不随意。自信但不强势。

根据受众调整语气：

高管层：极其简洁、同行视角、低调克制
中层管理者：更具体的价值、稍多细节
技术人员：精准表述、无冗余内容、尊重其专业性

需要避免的语气：

仅替换了占位符的模板邮件
压缩成段落形式的演讲稿
从未见过的陌生人发来的LinkedIn私信
AI生成的邮件（避免典型套话：“希望你一切安好”、“我浏览了你的资料”、“协同”、“增效”、“行业领先”）

Structure

结构

There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.

Common shapes that work:

Observation → Problem → Proof → Ask — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
Question → Value → Ask — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
Trigger → Insight → Ask — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
Story → Bridge → Ask — [Similar company] had [problem]. They [solved it this way]. Relevant to you?

For the full catalog of frameworks with examples, see frameworks.md.

没有唯一正确的结构。选择适合场景的框架，或者如果邮件自然流畅，也可以自由撰写。

有效的常见结构：

观察→问题→佐证→请求 —— 你注意到X，这通常意味着Y挑战。我们曾帮助Z解决该问题。有兴趣了解吗？
问题→价值→请求 —— 正在为X问题困扰吗？我们能提供Y解决方案。Z公司因此获得了[成果]。值得了解吗？
触发事件→洞察→请求 —— 恭喜你们达成X成就。这通常会带来Y挑战。我们曾帮助类似公司解决该问题。感兴趣吗？
案例→关联→请求 —— [类似公司]曾面临[问题]。他们通过[该方式]解决了问题。这与你相关吗？

如需查看完整的框架及示例，请参阅frameworks.md。

Subject Lines

邮件主题

Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.

2-4 words, lowercase, no punctuation tricks
Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
No product pitches, no urgency, no emojis, no prospect's first name

See subject-lines.md for the full data.

简短、平实、类似内部邮件的风格。邮件主题的唯一作用是让邮件被打开——而非推销产品。

2-4个单词、小写、无标点技巧
看起来像是同事发来的（如“回复率”、“招聘运营”、“Q2预测”）
不包含产品推销、紧急语气、表情符号或收件人名字

如需查看完整数据，请参阅subject-lines.md。

Follow-Up Sequences

跟进邮件序列

Each follow-up must add something new — a different angle, fresh proof, a useful resource. Never "just checking in."

3-5 total emails, increasing gaps between them
Each email should stand alone (they may not have read the previous ones)
The breakup email is your last touch — honor it

See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.

每一封跟进邮件都必须添加新内容——不同的视角、新的佐证、有用的资源。绝对不要只写“跟进一下”。

总共3-5封邮件，邮件间隔逐渐拉长
每封邮件都应独立成篇（收件人可能未阅读之前的邮件）
最后一封是“告别邮件”——发送后不再跟进

如需查看邮件节奏、视角转换及告别邮件模板，请参阅follow-up-sequences.md。

Quality Check

质量检查

Before presenting, gut-check:

Does it sound like a human wrote it? (Read it aloud)
Would YOU reply to this if you received it?
Does every sentence serve the reader, not the sender?
Is the personalization connected to the problem?
Is there one clear, low-friction ask?

在提交邮件前，进行以下自查：

读起来像是真人写的吗？（大声朗读）
如果你收到这封邮件，会回复吗？
每一句话都是为读者服务，而非发件人吗？
个性化内容与问题相关吗？
是否有一个清晰、低门槛的请求？

What to Avoid

禁忌事项

Opening with "I hope this email finds you well" or "My name is X and I work at Y"
Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
Feature dumps — one proof point beats ten features
HTML, images, or multiple links
Fake "Re:" or "Fwd:" subject lines
Identical templates with only {{FirstName}} swapped
Asking for 30-minute calls in first touch
"Just checking in" follow-ups

以“希望你一切安好”或“我是X，在Y公司工作”开头
行话：“协同”、“利用”、“回头聊”、“行业领先”、“顶级供应商”
罗列功能——一个佐证点胜过十个功能
HTML格式、图片或多个链接
虚假的“Re:”或“Fwd:”主题
仅替换{{FirstName}}的完全相同的模板
首次联系就请求30分钟的通话
只写“跟进一下”的邮件

Data & Benchmarks

数据与基准

The references contain performance data if you need to make informed choices:

benchmarks.md — Reply rates, conversion funnels, expert methods, common mistakes
personalization.md — 4-level personalization system, research signals
subject-lines.md — Subject line data and optimization
follow-up-sequences.md — Cadence, angles, breakup emails
frameworks.md — All copywriting frameworks with examples

Use this data to inform your writing — not as a checklist to satisfy.

如果需要做出有依据的选择，参考资料中包含性能数据：

benchmarks.md —— 回复率、转化漏斗、专家方法、常见错误
personalization.md —— 四级个性化体系、调研线索
subject-lines.md —— 主题数据及优化建议
follow-up-sequences.md —— 邮件节奏、视角、告别邮件
frameworks.md —— 所有文案撰写框架及示例

利用这些数据指导你的撰写——而非将其视为必须满足的清单。