compose-outreach
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCompose Outreach
撰写开发信
Generate three personalized outreach formats — email, call script, and LinkedIn message — grounded in Common Room signals for a specific company or contact.
基于Common Room信号,为特定公司或联系人生成三种个性化开发信格式——邮件、电话脚本和LinkedIn消息。
Outreach Process
开发信撰写流程
Step 1: Look Up the Target
步骤1:查找目标对象
Use Common Room MCP tools to find and retrieve data for the target (company and/or specific contact). Pull:
- Recent product activity and engagement signals
- Community activity (posts, questions, reactions)
- 3rd-party intent signals (job postings, news, funding)
- Relationship history (prior contact, meetings, email opens)
If the user specified a person, run contact-level research. If only a company was given, identify the best contact to target based on title, engagement, and role.
使用Common Room MCP工具查找并获取目标对象(公司和/或特定联系人)的数据。提取:
- 近期产品活动和参与信号
- 社区活动(发帖、提问、互动)
- 第三方意向信号(招聘信息、新闻、融资动态)
- 合作历史(过往联系、会议、邮件打开记录)
如果用户指定了具体联系人,开展联系人层面的调研。若仅提供了公司信息,则根据职位、参与度和角色确定最佳联系对象。
Step 2: Web Search for External Hooks (If CR Signals Are Thin)
步骤2:网络搜索外部切入点(若Common Room信号不足)
If CR returned strong signals (recent activity, engagement, product usage), those should drive personalization — skip web search. If CR signals are thin or the prospect has little CR activity, run a web search for external hooks:
What to search:
- — last 30 days
"[company name]" funding OR acquisition OR launch OR announcement - — look for recent articles, interviews, LinkedIn posts, or conference talks
"[contact full name]" "[company name]"
Prioritize external hooks that are:
- Very recent (< 2 weeks) — the prospect is likely still thinking about it
- Publicly visible — they know you could have seen it
- Change-signaling — growth, new role, new product, new market
If the user explicitly asks for web search or external hooks, run it regardless of CR signal richness.
若Common Room返回了明确的信号(近期活动、参与度、产品使用情况),则以此为个性化依据——跳过网络搜索。若Common Room信号有限或潜在客户在平台上的活动较少,则通过网络搜索寻找外部切入点:
搜索内容:
- —— 近30天内的信息
"[公司名称]" funding OR acquisition OR launch OR announcement - —— 查找近期文章、访谈、LinkedIn帖子或会议演讲内容
"[联系人全名]" "[公司名称]"
优先选择以下类型的外部切入点:
- 时效性极强(近2周内)—— 潜在客户大概率仍在关注相关内容
- 公开可见——他们知道你可能会看到这些信息
- 具有变革信号——业务增长、新岗位、新产品、新市场
若用户明确要求进行网络搜索或寻找外部切入点,则无论Common Room信号是否充足,都执行该操作。
Step 3: Spark Enrichment (If Available)
步骤3:Spark增强数据(若可用)
If Spark is available, run enrichment on the target contact to get persona classification, background, and influence signals. Use this to calibrate tone and message angle.
若Spark可用,针对目标联系人开展enrichment处理,获取其角色分类、背景资料以及影响力相关信号。以此调整沟通语气和消息角度。
Step 4: Identify the Best Hooks
步骤4:筛选最佳切入点
From the signal data, identify the 1–3 strongest personalization hooks. Rank by:
- Recency — happened in the last 7–14 days
- Specificity — a concrete action they took, not a general trend
- Relevance — connects directly to a value your product delivers
Good hooks: posted a question in the community about X, just hired 5 engineers, recently started using [feature], company just raised Series B, trial nearing expiration, champion just changed jobs.
Bad hooks: "I noticed you're a customer" or generic industry trends.
从信号数据中筛选1-3个最有效的个性化切入点,排序优先级为:
- 时效性——发生在过去7-14天内
- 针对性——具体的行为动作,而非普遍趋势
- 相关性——直接关联你的产品能提供的价值
优质切入点示例:在社区中发布了关于X的问题、刚招聘了5名工程师、近期开始使用[功能]、公司刚完成B轮融资、试用即将到期、关键对接人更换了工作。
劣质切入点示例:“我注意到您是我们的客户”或通用行业趋势。
Step 5: Generate All Three Formats
步骤5:生成三种格式的内容
Use the strongest hooks to write all three formats. Each format has different constraints and conventions — follow the format-specific guidelines in .
references/outreach-formats-guide.mdAlways produce all three, clearly labeled.
When the user's company context is available (see ), ground the value bridge and pitch in the user's specific product and positioning.
references/my-company-context.md借助最佳切入点撰写三种格式的内容。每种格式有不同的限制和规范——请遵循中的格式特定指南。
references/outreach-formats-guide.md务必生成全部三种格式,并清晰标注。
若用户公司的背景信息可用(详见),则将价值衔接和推销内容与用户的具体产品及定位相结合。
references/my-company-context.mdStep 6: Annotate Your Choices
步骤6:标注选择依据
After the three drafts, include a brief note (2–4 sentences) explaining:
- Which signals were used and why they were chosen
- Any assumptions made (e.g., inferred call objective)
- Alternative angles if the primary hook doesn't land
在三份草稿后,添加一段简短说明(2-4句话),解释:
- 使用了哪些信号及选择原因
- 做出的任何假设(例如,推断的通话目标)
- 若主要切入点无效,可替代的沟通角度
Output Format
输出格式
undefinedundefinedOutreach for [Name / Company]
开发信:[姓名/公司]
📧 邮件
Subject: [Subject line]
[Email body — 3–5 sentences]
主题: [主题行]
[邮件正文——3-5句话]
📞 Call Script
📞 电话脚本
Opening:
[Opening line — conversational, 1–2 sentences]
Value Bridge:
[Why you're calling and why now — 2–3 sentences tied to a signal]
Ask:
[Single, low-friction ask — e.g., 15-minute call, specific question]
开场:
[开场语——口语化,1-2句话]
价值衔接:
[致电原因及时机——2-3句话,关联相关信号]
请求:
[单一、低门槛的请求——例如,15分钟通话、特定问题咨询]
💼 LinkedIn Message
💼 LinkedIn消息
[Under 300 characters. Warm, personal, no pitch.]
[不超过300字符。语气亲切、个性化,无推销内容。]
Signal Notes
信号说明
[2–4 sentences: which signals were used, why, and any alternative angles]
undefined[2-4句话:使用的信号、选择原因及替代角度]
undefinedWhen Signal Data Is Sparse
信号数据不足时的处理方式
If Common Room returns minimal data on the target (e.g., just name, title, tags — no activity, no scores, no Spark):
- Do not draft outreach from thin air. Outreach grounded in fabricated signals is worse than no outreach.
- Run web search first — this becomes your primary personalization source. Look for recent news, LinkedIn posts, conference talks, company announcements.
- If web search also returns little, present what you have honestly and ask the user for context:
undefined若Common Room返回的目标对象数据极少(例如,仅姓名、职位、标签——无活动记录、无评分、无Spark数据):
- 切勿凭空草拟开发信。基于虚构信号撰写的开发信效果还不如不写。
- 优先执行网络搜索——以此作为主要的个性化信息来源。查找近期新闻、LinkedIn帖子、会议演讲、公司公告。
- 若网络搜索也未获得有效信息,如实告知用户现有情况,并请求补充上下文:
undefinedOutreach for [Name / Company] — Limited Data
开发信:[姓名/公司]——数据有限
What I found:
[Only the real data from CR and web search]
I don't have enough signal to draft personalized outreach yet. To write something strong, I'd need:
- Recent activity or engagement signals
- Context you have from prior conversations
- A specific reason for reaching out now
Can you share any of the above?
undefined已获取信息:
[仅来自Common Room和网络搜索的真实数据]
目前信号不足,无法草拟个性化开发信。 要撰写高质量的开发信,我需要:
- 近期活动或参与信号
- 您与对方过往沟通的背景信息
- 此次联系的具体原因
能否提供以上任意一项信息?
undefinedQuality Standards
质量标准
- Every message must reference something specific — generic outreach is not acceptable output
- Match tone to context: warm and conversational for inbound/community signals; more formal for cold/executive outreach
- The LinkedIn message must be under 300 characters — no exceptions
- The call script must be speakable naturally — read it aloud mentally to check rhythm
- Never fabricate signals — only reference data retrieved from Common Room or web search
- 每一条消息都必须提及具体内容——通用开发信不属于合格输出
- 语气匹配场景:针对 inbound/社区信号,语气亲切自然;针对陌生开发/高管沟通,语气更正式
- LinkedIn消息必须控制在300字符以内——无例外
- 电话脚本必须符合自然口语习惯——可以默读检查语句节奏
- 切勿虚构信号——仅引用来自Common Room或网络搜索的数据
Reference Files
参考文件
- — detailed format rules, examples, and tone guidelines for each channel
references/outreach-formats-guide.md
- —— 各渠道的详细格式规则、示例及语气指南
references/outreach-formats-guide.md