中文译文

潜在客户生成与跟踪（WordPilot.pro）

使用本操作手册为 WordPilot.pro 研究、筛选、跟踪并专业地转化潜在客户——WordPilot.pro 是一款 AI 驱动的写作工作空间。本技能以每日节奏运行：每天你签到时，WordPilot 会汇报进展、研究新潜在客户、推进现有潜在客户，并生成更新后的每日看板。

本技能专为持续、专业的潜在客户生成而设计——而非群发轰炸。每个潜在客户都有背景信息，每次触达都让人感觉真诚，每次跟进都有记录。

核心理念

先研究，再触达。 绝不在不了解对方背景、工作内容以及 WordPilot 为何可能真正帮到他们的情况下冷启动联系。
价值优先，绝不推销。 将 WordPilot 定位为解决真实问题的工具——而不是一个要赶紧抓住的「交易」。
慢即是稳。 转化漏斗有 5 个阶段；潜在客户在表现出真实兴趣时推进，而不是在计时器到期时推进。
一切皆有记录。 /leads/ 工作空间文件夹是唯一的事实来源。
每日问责。 每次会话都会对每日看板产生一次具体更新。

适用场景

用户说「潜在客户开发进展如何？」、「给我看今天的潜在客户」、「找新潜在客户」、「检查漏斗」或类似的话。
用户打开工作空间，且每日看板需要更新。
用户要求研究某个特定细分市场、行业或用户画像。
用户想为某个特定潜在客户或阶段起草触达内容。
用户想查看转化指标或漏斗健康状况。

前提条件

Gmail 应已连接（通过 Integrations → Composio）以便触达和跟踪。若未连接，研究和筛选仍可进行——但触达步骤将起草为待审阅，而非直接发送。
Google Sheets 或 Notion 为可选项，但推荐用于外部 CRM 同步。若已连接，潜在客户可双向同步。
Composio Search 和 Browser Tool 用于深度潜在客户研究——两者在 WordPilot 上均已预连接。

转化流程（6 个阶段）

每条线索都会经历这些阶段。阶段之间的推进是刻意的，而非自动的。

阶段 1 — 已发现

线索已通过调研被识别出来。已捕获基本信息：姓名、职位、公司、为什么他们可能需要 WordPilot。尚未进行外联。

阶段 2 — 已调研

已收集深度背景：近期工作、痛点、公开内容、团队规模、技术栈、当前使用的工具。已识别出一个「钩子」——某个能将他们的工作与 WordPilot 的价值联系起来的具体切入点。

阶段 3 — 已确认资格

线索符合资格标准：拥有决策权或影响力、活跃于相关领域（写作、文档、内容、开发工具）、公司有预算信号，且契合度是真实的——而非牵强附会。

阶段 4 — 已联系

已发送首次外联（邮件、社交媒体或其他渠道）。消息是个性化的，引用了具体的调研内容，并开启一段对话——而非推销。

阶段 5 — 培育中

线索已回复或表现出兴趣。正处于积极对话中。跟进及时且能带来价值。目标：让他们试用 WordPilot.pro。

阶段 6 — 已转化

线索已注册、加入等待名单，或承诺试用 WordPilot。交接完成。持续跟踪以获取推荐和案例研究。

工作区结构

所有线索相关工作都存放在 /leads/ 下。保持此结构整洁并始终更新：

/leads/
├── daily-board.md          ← Today's todos, progress, and session log
├── pipeline.md             ← Full pipeline view: all leads by stage
├── research-methods.md     ← Research playbooks by persona/industry
├── templates.md            ← Outreach templates, follow-up patterns, DM scripts
├── archive/                ← Converted, dead, or dormant leads
│   └── 2026-05/
└── leads/                  ← Individual lead files (one per lead)
    └── john-doe.md

每日节奏（循环）

当用户每天签到（或你被调用来处理线索工作）时，遵循以下循环：

1）了解现状

阅读 /leads/daily-board.md，了解昨天的状态和今天待办事项。
阅读 /leads/pipeline.md，查看当前管道健康状况。
检查 Gmail/Sheets/Notion 是否已连接（如需用于今天的工作，请让用户连接）。

2）处理昨天遗留事项

今天有到期的跟进吗？起草它们。
有线索在某个阶段停留过久吗？记录下来并建议下一步行动。
自上次会话以来收到任何回复吗？处理它们。

3）研究新线索（如果管道需要补充）

选择 1–2 个研究细分（按人物画像、行业或用例）。
使用 Composio Search Web 查找匹配的人/团队。
对有潜力的线索，使用 Fetch URL Content 或 Browser Tool 进行深度研究。
在 /leads/leads/ 中创建单独的线索文件。
以阶段 1（已发现）添加到管道。

4）推进现有线索

对于已研究的线索：根据标准进行资格评估。移至阶段 3，或注明原因。
对于已确认资格的线索：起草首次外联。如果 Gmail 已连接，提议发送。
对于已联系的线索：检查跟进是否到期。如到期则起草。
对于培育中的线索：建议下一个增值内容（案例研究、功能亮点、直接邀请）。

5）更新每日看板

将今天的会话摘要写入 /leads/daily-board.md。
更新管道各阶段计数。
设定明天的优先事项。
将待办事项标记为已完成。

6）向用户汇报

总结：今天完成了什么、管道健康状况（各阶段计数）、前 3 个优先线索，以及明天排队的事项。保持简洁但完整。

研究方法论

寻找线索（Composio Search Web）

按细分搜索。示例：

"technical writing" team lead "documentation" site:linkedin.com/in
content strategist "AI writing" OR "AI content" startup
developer advocate documentation tool "dev experience"
head of content OR director of content SaaS 2025 2026
"documentation as code" engineer OR architect OR lead 始终结合时效性和角色限定词进行搜索。核查引用来源是否为真实人物，而非泛泛的清单文章。

深度研究（抓取 URL 内容 / 浏览器工具）

对于有潜力的线索，研究他们的：

当前职位和公司：他们做什么？团队规模？公开项目？
痛点：他们是否被文档淹没？正在迁移工具？正在扩展内容？
当前技术栈：他们提到哪些工具？Notion、Confluence、Google Docs、GitBook？
公开内容：博客文章、演讲、推文、GitHub 仓库，这些能展现他们的思考。
切入点：找到一个具体的、真实的与 WordPilot 价值的连接点。

资格标准

对每条线索按每项 1–5 分打分（总体目标为 3 分以上）：

相关性：他们的工作是否与写作、文档、内容或开发者工具交叉？
权威性：他们是否对工具有决策权或影响力？
触达面：他们是否有受众、团队或公开影响力？
时机：是否有信号表明他们正在寻找新东西？（职位变动、工具迁移、扩展痛点）
契合度：WordPilot 是否真能帮到他们？不要强行套用。

外联原则

语气与语调

专业、温暖、好奇——绝不推销。
以你注意到的关于他们工作的内容开头。
把 WordPilot 定位为「我觉得你可能会感兴趣的东西」——而不是「你需要买的东西」。
尊重他们的时间。简短的消息。清晰的价值。容易忽略。

首次联系模板（改编，不要复制粘贴）

Subject: Your [specific work / post / talk] on [topic]

Hi [Name],

I came across your [post/talk/repo/work] on [specific topic] — really enjoyed 
[one specific insight you genuinely appreciated].

I work on WordPilot, an AI workspace for writing and documentation. Given your 
work on [their domain], I thought you might find it interesting — especially 
[one specific feature or angle that connects to their work].

No pitch — just wanted to share in case it's useful. Happy to give you early 
access if you'd like to try it.

Best,
[Your name]

跟进原则

等待 5–7 天后再跟进。
每次都要增加新价值——功能更新、案例研究、相关文章。
绝不「只是来看看」或「顶一下」。
3 条消息未获回复后，转入休眠。2–3 个月后带着新背景重新联系。

每日看板格式

/leads/daily-board.md 是系统的核心。每天都有自己独立的部分：

# Daily Lead Board

## YYYY-MM-DD (Today)

### Today's Focus
- Priority 1
- Priority 2
- Priority 3

### Research Queue
- [ ] Segment: [description] — target [N] leads
- [ ] Deep research on [lead name]

### Outreach Queue
- [ ] Draft first contact for [lead name]
- [ ] Follow-up for [lead name] (day [N])

### Completed Today
- [x] Researched 3 leads in [segment]
- [x] Sent outreach to [lead name]
- [x] Qualified [lead name] → Stage 3

### Pipeline Snapshot
| Stage | Count |
|---|---|
| Discovered | X |
| Researched | X |
| Qualified | X |
| Contacted | X |
| Nurturing | X |
| Converted | X |

### Tomorrow's Priority
- [ ] Item 1
- [ ] Item 2

### Notes
Any observations, blockers, or strategy adjustments.

管道格式

/leads/pipeline.md 是主列表。每当线索变更阶段时，更新它。

# Lead Pipeline

Last updated: YYYY-MM-DD

## Stage 1 — Discovered
| Lead | Role | Company | Source | Found | Score |
|---|---|---|---|---|---|
| Name | Title | Co | LinkedIn | YYYY-MM-DD | — |

## Stage 2 — Researched
| Lead | Role | Company | Hook | Score |
|---|---|---|---|---|
| Name | Title | Co | Specific angle | 3/5 |

## Stage 3 — Qualified
| Lead | Role | Company | Why Qualified | Score |
|---|---|---|---|---|
| Name | Title | Co | Reason | 4/5 |

## Stage 4 — Contacted
| Lead | Role | Company | Contacted On | Channel | Response? |
|---|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Email | Pending |

## Stage 5 — Nurturing
| Lead | Role | Company | Last Contact | Next Step |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Send case study |

## Stage 6 — Converted
| Lead | Role | Company | Converted On | Notes |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Signed up |

单个线索文件格式

每个线索对应一个文件：/leads/leads/firstname-lastname.md

# [Full Name]

- **Role**: [Title] at [Company]
- **Location**: [City/Region]
- **Pipeline Stage**: [1–6]
- **Discovered**: YYYY-MM-DD
- **Source**: [LinkedIn / Twitter / Conference / Referral / Search]
- **Score**: [N]/5

## Context
[2–3 sentences about who they are and what they do]

## Research Notes
- Pain point 1
- Pain point 2
- Current tools
- Public content / talks

## Hook
[The specific, genuine connection to WordPilot]

## Contact Log
| Date | Channel | Type | Notes |
|---|---|---|---|
| YYYY-MM-DD | Email | First contact | Sent |
| YYYY-MM-DD | Email | Follow-up 1 | Drafted |

## Notes
[Any other observations]

按人物画像划分的研究方法

按人物画像定制搜索和外联方式。详细操作手册见 /leads/research-methods.md。快速参考：

人物画像	在哪里找到	用什么打动他们
技术文档工程师	Write the Docs、LinkedIn、GitHub 文档仓库	WordPilot 的 MDX 区块、图表支持、版本控制
内容策略师	内容营销社区、Twitter/X、Medium	AI 辅助起草、内容流水线、团队工作区
开发者关系工程师	DevRel 社区、会议演讲、YouTube	文档生成、GitHub 集成、API 文档
工程经理	工程博客、HN、LinkedIn	文档工作流、团队入职、知识管理
创始人 / 独立开发者	Product Hunt、Indie Hackers、Twitter/X	一体化写作工作区、速度、更快发布内容
技术产品经理	LinkedIn、产品社区、Medium	规格到文档的流水线、PRD、跨职能文档

工具参考

Composio Search Web（主要研究工具）

COMPOSIO_SEARCH_WEB with query strings targeting specific personas and segments.
Review response.data.citations for real people/companies.

Composio 获取 URL 内容（深度研究）

COMPOSIO_SEARCH_FETCH_URL_CONTENT on specific About/Team/Blog pages.
Extract context, not just contact info.

浏览器工具（用于复杂网站）

BROWSER_TOOL_CREATE_TASK for LinkedIn profiles, dynamic pages, or sites 
that block simple fetches. Use WatchTask to poll results.

Gmail（外联）

GMAIL_CREATE_EMAIL_DRAFT → review with user → GMAIL_SEND_EMAIL or GMAIL_SEND_DRAFT.
Always draft first, never auto-send without user review.

Google Sheets / Notion（外部 CRM 同步）

GOOGLESHEETS_UPSERT_ROWS for spreadsheet-based CRM.
NOTION_UPSERT_ROW_DATABASE for Notion-based tracking.
Sync pipeline data when these are connected.

反模式（不要做）

绝不在未经用户审核的情况下自动发送邮件。 起草、展示、获得批准。
绝不从未经授权的来源抓取个人邮箱。 只使用公开可得的职业联系信息，或对方为职业目的主动公开邮箱的平台。
绝不发送千篇一律的群发消息。 每一次外联都必须引用具体调研。
绝不在单个线索上过度调研。 每个线索的深度调研最多 15–20 分钟。然后继续推进。
绝不让每日看板留空。 每次会话都要产出更新——即使是「今天没有新线索，推进了 2 个现有线索」。
绝不强行硬套线索。 如果 WordPilot 对某个人并非真正有用，记录下来并将其移出管道。
绝不纠缠或过度联系。 最多 3 条未回复消息，然后转入休眠。

质量标准

每个线索文件都有一个真实的钩子——而不只是「他们写东西」。
管道计数准确，并在同一会话内更新。
外联草稿读起来像人写的——专门为那个人而写。
每日看板的写法要能让用户在 60 秒内扫完。
调研要有文档记录，而不只是记在脑子里。
如果 Gmail/Sheets/Notion 未连接，要说明——并在没有它们的情况下仍然尽力完成一切。

入门（首次会话）

当此技能首次被调用且尚无 /leads/ 文件夹时：

在 /leads/ 下创建完整的工作区结构。
写入初始的 /leads/daily-board.md，带上今天的日期。
写入初始的 /leads/pipeline.md，包含空的阶段表格。
写入 /leads/research-methods.md，包含详细的人物画像操作手册。
写入 /leads/templates.md，包含外联模式。
询问用户：「我应该先调研哪个细分群体或人物画像？」——然后开始。

FILE:research-methods.md

按人物画像划分的调研方法

针对每个角色定制搜索、调研和外联策略。把这份文档当作一份持续更新的实战手册——把有效的做法补充进去。

技术文档工程师

去哪里找

Write the Docs 社区（论坛、Slack、会议）
LinkedIn："technical writer" OR "documentation engineer" team lead OR manager
GitHub：主要文档仓库的贡献者
Twitter/X：#TechComm #WriteTheDocs #documentation

调研什么

他们的文档技术栈（静态站点生成器、docs-as-code 工具）
痛点：版本管理、评审工作流、协作瓶颈
关于文档实践的公开演讲或博客文章

用什么切入

WordPilot 的 MDX 高级块，用于构建丰富的文档
Markdown 原生编辑，支持图表（Mermaid / Kroki）
版本控制和 GitHub 集成，适配 docs-as-code 工作流
“我注意到你关于[主题]的演讲——WordPilot 正好能解决[具体痛点]”

搜索查询

"technical writer" "documentation" team lead OR manager 2025 2026 site:linkedin.com/in
"documentation engineer" OR "docs engineer" "developer experience"
"write the docs" speaker OR organizer

内容策略师 / 内容负责人

去哪里找

LinkedIn："head of content" OR "director of content" OR "VP of content" SaaS
内容营销社区（Superpath、Content Marketing Institute）
Medium 和 Substack：内容策略类出版物
Twitter/X：#contentstrategy #contentmarketing

调研什么

内容产量和团队规模
当前使用的内容工具（Google Docs、Notion、WordPress）
内容运营痛点（工作流、审批、SEO、内容复用）
近期的营销活动或内容项目

用什么切入

面向内容团队的 AI 辅助起草和编辑
面向编辑工作流的 Workspace 协作
内容流水线功能（草稿 → 评审 → 发布）
“你关于[内容挑战]的那篇文章很有共鸣——WordPilot 用[功能]解决了这个问题”

搜索查询

"head of content" OR "director of content" SaaS "content strategy" site:linkedin.com/in
"VP of content" OR "content lead" startup OR scaleup
"content operations" manager OR lead

开发者布道师 / DevRel

在哪里寻找

DevRel 社区（DevRel Collective、DevRelX）
会议演讲嘉宾名单（KubeCon、React Conf、Write the Docs）
YouTube：开发者工具评测与教程
LinkedIn："developer advocate" OR "developer relations"

需要调研什么

他们的内容产出（博客文章、演讲、视频、教程）
他们目前推荐或使用的工具
在创作开发者内容时的痛点
社区互动风格与渠道

开场切入点

从代码和 GitHub 仓库生成文档
面向教程和指南的强大 markdown 能力
面向技术内容的嵌入式图表和公式
“很喜欢你关于[主题]的教程——WordPilot 的[功能]可以简化那套工作流程”

搜索查询

"developer advocate" OR "devrel" "documentation" OR "developer experience"
"developer relations" engineer OR lead "content" OR "docs"
devrel speaker "developer tools" OR "developer experience"

工程经理 / 技术负责人

在哪里寻找

LinkedIn："engineering manager" OR "engineering lead" documentation OR "knowledge management"
工程博客（公司博客、Medium 工程出版物）
Hacker News 和 Reddit（r/ExperiencedDevs、r/engineering）
会议演讲嘉宾名单（QCon、LeadDev、StrangeLoop）

需要调研什么

团队规模与结构
文档实践与痛点
入职流程与知识管理挑战
技术栈与工具偏好

开场切入点

不会拖慢工程进度的文档工作流程
知识管理与团队入职功能
面向工程驱动型文档的 GitHub 集成
“你们团队在[工程实践]上的做法很有意思——WordPilot 可以在[具体需求]上帮上忙”

搜索查询

"engineering manager" OR "engineering lead" "documentation" OR "knowledge management" site:linkedin.com/in
"VP of engineering" OR "director of engineering" "developer productivity"
engineering "internal documentation" OR "technical documentation" manager

创始人 / 独立黑客

在哪里寻找

Product Hunt：创客和创始人
Indie Hackers 社区
Twitter/X：#buildinpublic #indiehacker
Hacker News：Show HN、发布帖
LinkedIn："founder" OR "co-founder" content OR writing OR documentation

需要调研什么

他们的产品和阶段
内容策略和产出量
团队规模（单人？小团队？）
当前的写作和发布工作流
公开路线图或挑战

用什么切入

一体化写作工作空间，取代碎片化工具
为小团队提供速度与简洁
加速内容创作的 AI 功能
“在 [平台] 上关注你的构建之旅——WordPilot 可能是适合你技术栈的实用写作工具”

搜索查询

"founder" OR "co-founder" "content" OR "writing" OR "documentation" SaaS site:linkedin.com/in
"indie hacker" OR "solopreneur" "writing" OR "content creation"
site:indiehackers.com "looking for" writing OR content tool

技术产品经理

在哪里寻找

LinkedIn："technical product manager" OR "product manager" documentation OR specs
产品管理社区（Mind the Product、Product School）
Medium：产品管理出版物
会议演讲嘉宾名单（Industry、ProductCon）

需要调研什么

产品文档实践
PRD 和规格文档的写作工作流
跨职能沟通挑战
用于产品文档的工具

用什么切入

从规格到文档的流水线
用于 PRD 和技术规格的富 markdown
PM、工程和设计之间的协作
“你对 [产品实践] 的方法很敏锐——WordPilot 能处理 [具体工作流需求]”

搜索查询

"technical product manager" OR "product manager" "documentation" OR "specs" site:linkedin.com/in
"product manager" "PRD" OR "product requirements" SaaS
"senior product manager" "technical writing" OR "documentation"

所有人物画像的注意事项

始终核实此人是否活跃 —— 近期发帖、演讲或求职动态。
优先选择公开分享自己工作的人 —— 他们更有可能回应。
寻找触发事件：新职位、公司转型、工具迁移、规模化挑战。
调整外联语言以匹配其人物画像的词汇 —— 不要对工程经理使用“内容流水线”。

FILE:templates.md

外联模板与模式

将这些作为起点 —— 始终针对每条线索进行具体研究并定制。绝不复制粘贴。

首次联系模板

面向技术文档撰写者

Subject: Your [talk/post] on [specific documentation topic]

Hi [Name],

I caught your [talk/post] on [topic] — the point about [specific insight] 
really landed. Documentation teams deal with that exact tension between 
richness and maintainability.

I'm working on WordPilot, an AI writing workspace that handles that well — 
it supports advanced MDX blocks (diagrams, equations, columns) in plain 
markdown, so docs stay readable AND rich. No lock-in, no proprietary format.

No pitch — just thought you might find the approach interesting given your 
work. Happy to share more if you're curious.

Best,
[Your name]

面向内容策略师

Subject: Your piece on [content challenge]

Hi [Name],

Really enjoyed your piece on [specific content challenge] — the [specific 
point] matches what a lot of content teams are running into right now.

I work on WordPilot, an AI workspace that helps content teams draft, review, 
and publish faster. The AI doesn't replace writers — it handles the 
repetitive parts so strategists can focus on strategy.

Would be happy to show you how it works if you're interested. No sales 
pressure — just thought it aligned with your thinking.

Best,
[Your name]

面向开发者布道师

Subject: Your tutorial on [topic] — sharp work

Hi [Name],

Your tutorial on [topic] was excellent — particularly the [specific part]. 
Creating that kind of content at quality takes real time.

I'm building WordPilot, and one thing we focused on was making technical 
content creation faster: diagrams right in markdown (Mermaid/Kroki), 
GitHub-integrated docs, and AI that actually understands code.

Given how much technical content you produce, I thought you might find it 
useful. Happy to give you early access if you want to try it.

Cheers,
[Your name]

面向工程经理

Subject: Documentation workflows and developer experience

Hi [Name],

I read about [company/team]'s approach to [engineering practice] — 
impressive how you handle [specific challenge] at scale.

One area I've been thinking about is documentation friction in engineering 
teams. We built WordPilot specifically so docs don't feel like a separate 
chore — markdown-native, GitHub-connected, with AI that helps without 
getting in the way.

No pitch — just curious if documentation workflow is something on your radar. 
Happy to share what we're building if relevant.

Best,
[Your name]

面向创始人 / 独立开发者

Subject: Writing tool you might find useful

Hi [Name],

Been following your build on [platform] — really impressive progress on 
[product]. The way you handle [specific thing] is smart.

I built WordPilot as an AI writing workspace — it replaces the patchwork of 
Google Docs, Notion, and markdown editors with one tool that actually works 
for real writing. Might be useful for your content, docs, or even product specs.

No pressure — just thought it might save you some tool-switching time. Happy 
to share access if you want to kick the tires.

Cheers,
[Your name]

面向技术产品经理

Subject: Your approach to [product practice]

Hi [Name],

Enjoyed reading about how you handle [specific product workflow] at 
[company] — the [specific insight] is something more teams should adopt.

I work on WordPilot, an AI writing workspace. One thing it handles 
particularly well is the spec-to-documentation pipeline — rich markdown 
with diagrams and equations, collaboration built in, and no proprietary 
format lock-in.

Thought it might be relevant given your focus on [their domain]. Happy to 
show you if you're interested.

Best,
[Your name]

跟进模式

跟进 1（首次接触后 5–7 天）

Subject: Re: Your [original topic]

Hi [Name],

Just following up on my previous note — I know inboxes get busy.

I also wanted to mention [one new specific thing] about WordPilot since I 
last wrote: [feature update, new capability, relevant case study].

No rush — just wanted to keep it on your radar in case it's useful.

Best,
[Your name]

跟进 2（跟进 1 之后 5–7 天）

Subject: Quick thought on [their domain]

Hi [Name],

I came across [relevant article / trend / insight] and immediately thought of 
your work on [their topic]. [One sentence connecting the insight to them].

WordPilot handles this well — specifically [relevant feature]. I won't keep 
following up after this, but wanted to share the connection.

If it ever becomes relevant, my inbox is open.

Best,
[Your name]

跟进 3 — 最终（跟进 2 之后 5–7 天）

Subject: Re: Quick thought on [their domain]

Hi [Name],

Last note from me — I'll leave you be after this.

If you ever want to explore WordPilot, the door's open. We're building 
something genuinely useful for [their persona], and I think you'd find it 
interesting.

No reply needed — just wanted to leave that on the table.

Best,
[Your name]

私信 / 社交拓展（Twitter、LinkedIn）

LinkedIn 连接请求附言

Hi [Name] — I came across your [work/talk/post] on [topic] and was really 
impressed by [specific insight]. I work on an AI writing tool that touches 
similar ground. Would love to connect.

Twitter 私信（如果已连接）

Hey [Name] — loved your [post/thread] on [topic]. Working on an AI writing 
workspace that handles [related thing] really well. Thought you might find 
it interesting: [link]. No pitch — just sharing.

回复处理

如果他们回复“不感兴趣”

Thanks for letting me know, [Name]. Totally understand — appreciate you 
taking the time to reply. All the best with [their work/company].

如果他们回复“告诉我更多”

发送一段简洁的 3–4 句话的 WordPilot 概述，并附上一项与其工作相关的具体功能。最后邀请他们试用或安排一次简短的演示。

如果他们回复“正在试用”

在内心庆祝（进入第 5 阶段——培育）。发送一封热情的欢迎邮件，附上与其使用场景相关的入门提示。主动提出可以解答问题。

反模式（绝不要做这些）

❌ “只是跟进一下！”却没有任何新价值
❌ “我们正在颠覆 [X] 领域”这类行话
❌ 冗长的邮件——保持在 150 词以内
❌ HTML 过多或图片过多的邮件
❌ 在第一条消息中就要求通话
❌ “限时优惠”或制造紧迫感的手段
❌ 未经许可就提及他人姓名
❌ 未经调研就假设他们的痛点

English original

Lead Generator & Tracker (WordPilot.pro)

Use this playbook to research, qualify, track, and professionally convert leads for WordPilot.pro — an AI-powered writing workspace. This skill operates on a daily cadence: each day you check in, WordPilot reports progress, researches new leads, advances existing ones, and produces an updated daily board.

This skill is designed for sustained, professional lead generation — not mass blasting. Every lead gets context, every outreach feels human, and every follow-up is tracked.

Core Philosophy

Research before reaching out. Never cold-contact someone without understanding their context, work, and why WordPilot might genuinely help them.
Value-first, never salesy. Position WordPilot as a tool that solves real problems — not a "deal" to jump on.
Slow is smooth. The conversion pipeline is 5 stages; leads advance when they show real interest, not when a timer expires.
Everything is tracked. The /leads/ workspace folder is the single source of truth.
Daily accountability. Every session produces a concrete update to the daily board.

When to Apply

User says "how's lead gen going?", "show me today's leads", "find new leads", "check the pipeline", or similar.
User opens the workspace and the daily board needs updating.
User asks to research a specific segment, industry, or persona.
User wants to draft outreach to a specific lead or stage.
User wants to review conversion metrics or pipeline health.

Preconditions

Gmail should be connected (via Integrations → Composio) for outreach and tracking. If not connected, research and qualification still proceed — but outreach steps will be drafted for review rather than sent.
Google Sheets or Notion are optional but recommended for external CRM sync. If connected, leads can sync bidirectionally.
Composio Search and Browser Tool are used for deep lead research — both are pre-connected on WordPilot.

Conversion Pipeline (6 Stages)

Every lead moves through these stages. Movement between stages is deliberate, not automatic.

Stage 1 — Discovered

Lead has been identified through research. Basic info captured: name, role, company, why they might need WordPilot. No outreach yet.

Stage 2 — Researched

Deep context gathered: recent work, pain points, public content, team size, tech stack, current tools. A "hook" identified — something specific that connects their work to WordPilot's value.

Stage 3 — Qualified

Lead meets qualification criteria: decision-making authority or influence, active in relevant space (writing, documentation, content, dev tools), company has budget signals, and the fit is genuine — not forced.

Stage 4 — Contacted

First outreach sent (email, social, or other channel). Message is personalized, references specific research, and opens a conversation — not a pitch.

Stage 5 — Nurturing

Lead has responded or shown interest. In active conversation. Follow-ups are timely and value-adding. Goal: get them to try WordPilot.pro.

Stage 6 — Converted

Lead has signed up, joined a waitlist, or committed to trying WordPilot. Hand-off complete. Track for referrals and case studies.

Workspace Structure

All lead work lives under /leads/. Keep this structure clean and always up to date:

/leads/
├── daily-board.md          ← Today's todos, progress, and session log
├── pipeline.md             ← Full pipeline view: all leads by stage
├── research-methods.md     ← Research playbooks by persona/industry
├── templates.md            ← Outreach templates, follow-up patterns, DM scripts
├── archive/                ← Converted, dead, or dormant leads
│   └── 2026-05/
└── leads/                  ← Individual lead files (one per lead)
    └── john-doe.md

Daily Cadence (The Loop)

When the user checks in each day (or you're invoked for lead work), follow this loop:

1) READ THE ROOM

Read /leads/daily-board.md to understand yesterday's state and today's open items.
Read /leads/pipeline.md to see current pipeline health.
Check if Gmail/Sheets/Notion are connected (ask user to connect if needed for today's work).

2) PROCESS YESTERDAY'S OUTSTANDING

Any follow-ups due today? Draft them.
Any leads stuck in a stage too long? Note them and suggest next action.
Any responses received since last session? Process them.

3) RESEARCH NEW LEADS (if pipeline needs filling)

Pick 1–2 research segments (by persona, industry, or use case).
Use Composio Search Web to find people/teams that match.
For promising leads, deep-research with Fetch URL Content or Browser Tool.
Create individual lead files in /leads/leads/.
Add to pipeline at Stage 1 (Discovered).

4) ADVANCE EXISTING LEADS

For Researched leads: qualify them against criteria. Move to Stage 3 or note why not.
For Qualified leads: draft first outreach. If Gmail connected, offer to send.
For Contacted leads: check if follow-up is due. Draft if so.
For Nurturing leads: suggest next value-add (case study, feature highlight, direct invite).

5) UPDATE THE DAILY BOARD

Write today's session summary to /leads/daily-board.md.
Update pipeline stage counts.
Set tomorrow's priority items.
Mark todos as done.

6) REPORT TO USER

Summarize: what was done today, pipeline health (counts per stage), top 3 priority leads, and what's queued for tomorrow. Keep it concise but complete.

Research Methodology

Finding Leads (Composio Search Web)

Search by segment. Examples:

"technical writing" team lead "documentation" site:linkedin.com/in
content strategist "AI writing" OR "AI content" startup
developer advocate documentation tool "dev experience"
head of content OR director of content SaaS 2025 2026
"documentation as code" engineer OR architect OR lead

Always search with recency and role qualifiers. Review citations for real people, not generic listicles.

Deep Research (Fetch URL Content / Browser Tool)

For promising leads, research their:

Current role and company: What do they do? Team size? Public projects?
Pain points: Are they drowning in docs? Migrating tools? Scaling content?
Current stack: What tools do they mention? Notion, Confluence, Google Docs, GitBook?
Public content: Blog posts, talks, tweets, GitHub repos that show their thinking.
Hook: Find one specific, genuine connection to WordPilot's value.

Qualification Criteria

Score leads 1–5 on each (aim for 3+ overall):

Relevance: Does their work intersect with writing, docs, content, or developer tools?
Authority: Do they have decision power or influence over tooling?
Reach: Do they have an audience, team, or public presence?
Timing: Is there a signal they're looking for something new? (job change, tool migration, scaling pain)
Fit: Would WordPilot genuinely help them? Don't force it.

Outreach Principles

Voice & Tone

Professional, warm, curious — never pitchy.
Lead with what you noticed about THEIR work.
Position WordPilot as "something I thought you might find interesting" — not "something you need to buy."
Respect their time. Short messages. Clear value. Easy to ignore.

First Contact Template (Adapt, Don't Copy-Paste)

Subject: Your [specific work / post / talk] on [topic]

Hi [Name],

I came across your [post/talk/repo/work] on [specific topic] — really enjoyed 
[one specific insight you genuinely appreciated].

I work on WordPilot, an AI workspace for writing and documentation. Given your 
work on [their domain], I thought you might find it interesting — especially 
[one specific feature or angle that connects to their work].

No pitch — just wanted to share in case it's useful. Happy to give you early 
access if you'd like to try it.

Best,
[Your name]

Follow-Up Principles

Wait 5–7 days before following up.
Add new value each time — a feature update, a case study, a relevant article.
Never "just checking in" or "bumping this."
After 3 unanswered messages, move to dormant. Revisit in 2–3 months with fresh context.

Daily Board Format

/leads/daily-board.md is the heart of the system. Each day gets its own section:

# Daily Lead Board

## YYYY-MM-DD (Today)

### Today's Focus
- Priority 1
- Priority 2
- Priority 3

### Research Queue
- [ ] Segment: [description] — target [N] leads
- [ ] Deep research on [lead name]

### Outreach Queue
- [ ] Draft first contact for [lead name]
- [ ] Follow-up for [lead name] (day [N])

### Completed Today
- [x] Researched 3 leads in [segment]
- [x] Sent outreach to [lead name]
- [x] Qualified [lead name] → Stage 3

### Pipeline Snapshot
| Stage | Count |
|---|---|
| Discovered | X |
| Researched | X |
| Qualified | X |
| Contacted | X |
| Nurturing | X |
| Converted | X |

### Tomorrow's Priority
- [ ] Item 1
- [ ] Item 2

### Notes
Any observations, blockers, or strategy adjustments.

Pipeline Format

/leads/pipeline.md is the master list. Update it whenever a lead changes stage.

# Lead Pipeline

Last updated: YYYY-MM-DD

## Stage 1 — Discovered
| Lead | Role | Company | Source | Found | Score |
|---|---|---|---|---|---|
| Name | Title | Co | LinkedIn | YYYY-MM-DD | — |

## Stage 2 — Researched
| Lead | Role | Company | Hook | Score |
|---|---|---|---|---|
| Name | Title | Co | Specific angle | 3/5 |

## Stage 3 — Qualified
| Lead | Role | Company | Why Qualified | Score |
|---|---|---|---|---|
| Name | Title | Co | Reason | 4/5 |

## Stage 4 — Contacted
| Lead | Role | Company | Contacted On | Channel | Response? |
|---|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Email | Pending |

## Stage 5 — Nurturing
| Lead | Role | Company | Last Contact | Next Step |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Send case study |

## Stage 6 — Converted
| Lead | Role | Company | Converted On | Notes |
|---|---|---|---|---|
| Name | Title | Co | YYYY-MM-DD | Signed up |

Individual Lead File Format

Each lead gets a file: /leads/leads/firstname-lastname.md

# [Full Name]

- **Role**: [Title] at [Company]
- **Location**: [City/Region]
- **Pipeline Stage**: [1–6]
- **Discovered**: YYYY-MM-DD
- **Source**: [LinkedIn / Twitter / Conference / Referral / Search]
- **Score**: [N]/5

## Context
[2–3 sentences about who they are and what they do]

## Research Notes
- Pain point 1
- Pain point 2
- Current tools
- Public content / talks

## Hook
[The specific, genuine connection to WordPilot]

## Contact Log
| Date | Channel | Type | Notes |
|---|---|---|---|
| YYYY-MM-DD | Email | First contact | Sent |
| YYYY-MM-DD | Email | Follow-up 1 | Drafted |

## Notes
[Any other observations]

Research Methods by Persona

Tailor search and outreach by persona. See /leads/research-methods.md for detailed playbooks. Quick reference:

Persona	Where to Find	What to Lead With
Technical Writer	Write the Docs, LinkedIn, GitHub docs repos	WordPilot's MDX blocks, diagram support, version control
Content Strategist	Content marketing communities, Twitter/X, Medium	AI-assisted drafting, content pipelines, team workspaces
Developer Advocate	DevRel communities, conference talks, YouTube	Documentation generation, GitHub integration, API docs
Engineering Manager	Engineering blogs, HN, LinkedIn	Documentation workflows, team onboarding, knowledge management
Founder / Indie Hacker	Product Hunt, Indie Hackers, Twitter/X	All-in-one writing workspace, speed, shipping content faster
Technical PM	LinkedIn, product communities, Medium	Spec-to-documentation pipeline, PRDs, cross-functional docs

Tools Reference

Composio Search Web (Primary Research)

COMPOSIO_SEARCH_WEB with query strings targeting specific personas and segments.
Review response.data.citations for real people/companies.

Composio Fetch URL Content (Deep Research)

COMPOSIO_SEARCH_FETCH_URL_CONTENT on specific About/Team/Blog pages.
Extract context, not just contact info.

Browser Tool (For Complex Sites)

BROWSER_TOOL_CREATE_TASK for LinkedIn profiles, dynamic pages, or sites 
that block simple fetches. Use WatchTask to poll results.

Gmail (Outreach)

GMAIL_CREATE_EMAIL_DRAFT → review with user → GMAIL_SEND_EMAIL or GMAIL_SEND_DRAFT.
Always draft first, never auto-send without user review.

Google Sheets / Notion (External CRM Sync)

GOOGLESHEETS_UPSERT_ROWS for spreadsheet-based CRM.
NOTION_UPSERT_ROW_DATABASE for Notion-based tracking.
Sync pipeline data when these are connected.

Anti-Patterns (Do Not Do)

Never auto-send emails without user review. Draft, show, get approval.
Never scrape personal emails from unauthorized sources. Only use publicly available professional contact info or platforms where the person has shared their email for professional purposes.
Never send generic blast messages. Every outreach must reference specific research.
Never over-research one lead. 15–20 minutes max per lead for deep research. Move on.
Never leave the daily board empty. Every session produces an update — even if it's "no new leads today, advanced 2 existing."
Never force-fit a lead. If WordPilot isn't genuinely useful for someone, note it and move them out of the pipeline.
Never stalk or over-contact. Max 3 unanswered messages, then move to dormant.

Quality Standards

Every lead file has a real hook — not just "they write things."
Pipeline counts are accurate and updated same-session.
Outreach drafts sound like a human wrote them — specifically for that person.
Daily board is written so the user can scan it in 60 seconds.
Research is documented, not just remembered.
If Gmail/Sheets/Notion aren't connected, say so — and still do everything possible without them.

Getting Started (First Session)

When this skill is first invoked and there's no /leads/ folder yet:

Create the full workspace structure under /leads/.
Write the initial /leads/daily-board.md with today's date.
Write the initial /leads/pipeline.md with empty stage tables.
Write /leads/research-methods.md with detailed persona playbooks.
Write /leads/templates.md with outreach patterns.
Ask the user: "What segment or persona should I research first?" — then begin.

FILE:research-methods.md

Research Methods by Persona

Tailor search, research, and outreach to each persona. Use this as a living playbook — update with what works.

Technical Writer

Where to Find

Write the Docs community (forum, Slack, conferences)
LinkedIn: "technical writer" OR "documentation engineer" team lead OR manager
GitHub: contributors to major documentation repos
Twitter/X: #TechComm #WriteTheDocs #documentation

What to Research

Their documentation stack (static site generators, docs-as-code tools)
Pain points: versioning, review workflows, collaboration bottlenecks
Public talks or blog posts on documentation practices

What to Lead With

WordPilot's MDX advanced blocks for rich documentation
Markdown-native editing with diagram support (Mermaid / Kroki)
Version control and GitHub integration for docs-as-code workflows
"I noticed your talk on [topic] — WordPilot handles [specific pain point]"

Search Queries

"technical writer" "documentation" team lead OR manager 2025 2026 site:linkedin.com/in
"documentation engineer" OR "docs engineer" "developer experience"
"write the docs" speaker OR organizer

Content Strategist / Head of Content

Where to Find

LinkedIn: "head of content" OR "director of content" OR "VP of content" SaaS
Content marketing communities (Superpath, Content Marketing Institute)
Medium and Substack: content strategy publications
Twitter/X: #contentstrategy #contentmarketing

What to Research

Content volume and team size
Current content tools (Google Docs, Notion, WordPress)
Content operations pain points (workflows, approvals, SEO, repurposing)
Recent campaigns or content initiatives

What to Lead With

AI-assisted drafting and editing for content teams
Workspace collaboration for editorial workflows
Content pipeline features (draft → review → publish)
"Your piece on [content challenge] resonated — WordPilot addresses that with [feature]"

Search Queries

"head of content" OR "director of content" SaaS "content strategy" site:linkedin.com/in
"VP of content" OR "content lead" startup OR scaleup
"content operations" manager OR lead

Developer Advocate / DevRel

Where to Find

DevRel communities (DevRel Collective, DevRelX)
Conference speaker lists (KubeCon, React Conf, Write the Docs)
YouTube: developer tooling reviews and tutorials
LinkedIn: "developer advocate" OR "developer relations"

What to Research

Their content output (blog posts, talks, videos, tutorials)
Tools they currently recommend or use
Pain points in creating developer content
Community engagement style and channels

What to Lead With

Documentation generation from code and GitHub repos
Rich markdown capabilities for tutorials and guides
Embedded diagrams and equations for technical content
"Love your tutorial on [topic] — WordPilot's [feature] would streamline that workflow"

Search Queries

"developer advocate" OR "devrel" "documentation" OR "developer experience"
"developer relations" engineer OR lead "content" OR "docs"
devrel speaker "developer tools" OR "developer experience"

Engineering Manager / Tech Lead

Where to Find

LinkedIn: "engineering manager" OR "engineering lead" documentation OR "knowledge management"
Engineering blogs (company blogs, Medium engineering publications)
Hacker News and Reddit (r/ExperiencedDevs, r/engineering)
Conference speaker lists (QCon, LeadDev, StrangeLoop)

What to Research

Team size and structure
Documentation practices and pain points
Onboarding processes and knowledge management challenges
Technical stack and tooling preferences

What to Lead With

Documentation workflows that don't slow down engineering
Knowledge management and team onboarding features
GitHub integration for engineering-driven documentation
"Your team's approach to [engineering practice] is interesting — WordPilot could help with [specific need]"

Search Queries

"engineering manager" OR "engineering lead" "documentation" OR "knowledge management" site:linkedin.com/in
"VP of engineering" OR "director of engineering" "developer productivity"
engineering "internal documentation" OR "technical documentation" manager

Founder / Indie Hacker

Where to Find

Product Hunt: makers and founders
Indie Hackers community
Twitter/X: #buildinpublic #indiehacker
Hacker News: Show HN, launch posts
LinkedIn: "founder" OR "co-founder" content OR writing OR documentation

What to Research

Their product and stage
Content strategy and volume
Team size (solo? small team?)
Current writing and publishing workflow
Public roadmap or challenges

What to Lead With

All-in-one writing workspace replacing fragmented tools
Speed and simplicity for small teams
AI features that accelerate content creation
"Following your build journey on [platform] — WordPilot could be a useful writing tool for your stack"

Search Queries

"founder" OR "co-founder" "content" OR "writing" OR "documentation" SaaS site:linkedin.com/in
"indie hacker" OR "solopreneur" "writing" OR "content creation"
site:indiehackers.com "looking for" writing OR content tool

Technical Product Manager

Where to Find

LinkedIn: "technical product manager" OR "product manager" documentation OR specs
Product management communities (Mind the Product, Product School)
Medium: product management publications
Conference speaker lists (Industry, ProductCon)

What to Research

Product documentation practices
PRD and spec writing workflows
Cross-functional communication challenges
Tools used for product documentation

What to Lead With

Spec-to-documentation pipeline
Rich markdown for PRDs and technical specs
Collaboration between PM, engineering, and design
"Your approach to [product practice] is sharp — WordPilot handles [specific workflow need]"

Search Queries

"technical product manager" OR "product manager" "documentation" OR "specs" site:linkedin.com/in
"product manager" "PRD" OR "product requirements" SaaS
"senior product manager" "technical writing" OR "documentation"

Notes for All Personas

Always verify the person is active — recent posts, talks, or job activity.
Prioritize people who publicly share their work — they're more likely to engage.
Look for trigger events: new role, company pivot, tool migration, scaling challenges.
Adapt outreach language to their persona's vocabulary — don't use "content pipeline" with an engineering manager.

FILE:templates.md

Outreach Templates & Patterns

Use these as starting points — always customize with specific research for each lead. Never copy-paste.

First Contact Templates

For Technical Writers

Subject: Your [talk/post] on [specific documentation topic]

Hi [Name],

I caught your [talk/post] on [topic] — the point about [specific insight] 
really landed. Documentation teams deal with that exact tension between 
richness and maintainability.

I'm working on WordPilot, an AI writing workspace that handles that well — 
it supports advanced MDX blocks (diagrams, equations, columns) in plain 
markdown, so docs stay readable AND rich. No lock-in, no proprietary format.

No pitch — just thought you might find the approach interesting given your 
work. Happy to share more if you're curious.

Best,
[Your name]

For Content Strategists

Subject: Your piece on [content challenge]

Hi [Name],

Really enjoyed your piece on [specific content challenge] — the [specific 
point] matches what a lot of content teams are running into right now.

I work on WordPilot, an AI workspace that helps content teams draft, review, 
and publish faster. The AI doesn't replace writers — it handles the 
repetitive parts so strategists can focus on strategy.

Would be happy to show you how it works if you're interested. No sales 
pressure — just thought it aligned with your thinking.

Best,
[Your name]

For Developer Advocates

Subject: Your tutorial on [topic] — sharp work

Hi [Name],

Your tutorial on [topic] was excellent — particularly the [specific part]. 
Creating that kind of content at quality takes real time.

I'm building WordPilot, and one thing we focused on was making technical 
content creation faster: diagrams right in markdown (Mermaid/Kroki), 
GitHub-integrated docs, and AI that actually understands code.

Given how much technical content you produce, I thought you might find it 
useful. Happy to give you early access if you want to try it.

Cheers,
[Your name]

For Engineering Managers

Subject: Documentation workflows and developer experience

Hi [Name],

I read about [company/team]'s approach to [engineering practice] — 
impressive how you handle [specific challenge] at scale.

One area I've been thinking about is documentation friction in engineering 
teams. We built WordPilot specifically so docs don't feel like a separate 
chore — markdown-native, GitHub-connected, with AI that helps without 
getting in the way.

No pitch — just curious if documentation workflow is something on your radar. 
Happy to share what we're building if relevant.

Best,
[Your name]

For Founders / Indie Hackers

Subject: Writing tool you might find useful

Hi [Name],

Been following your build on [platform] — really impressive progress on 
[product]. The way you handle [specific thing] is smart.

I built WordPilot as an AI writing workspace — it replaces the patchwork of 
Google Docs, Notion, and markdown editors with one tool that actually works 
for real writing. Might be useful for your content, docs, or even product specs.

No pressure — just thought it might save you some tool-switching time. Happy 
to share access if you want to kick the tires.

Cheers,
[Your name]

For Technical Product Managers

Subject: Your approach to [product practice]

Hi [Name],

Enjoyed reading about how you handle [specific product workflow] at 
[company] — the [specific insight] is something more teams should adopt.

I work on WordPilot, an AI writing workspace. One thing it handles 
particularly well is the spec-to-documentation pipeline — rich markdown 
with diagrams and equations, collaboration built in, and no proprietary 
format lock-in.

Thought it might be relevant given your focus on [their domain]. Happy to 
show you if you're interested.

Best,
[Your name]

Follow-Up Patterns

Follow-Up 1 (5–7 days after first contact)

Subject: Re: Your [original topic]

Hi [Name],

Just following up on my previous note — I know inboxes get busy.

I also wanted to mention [one new specific thing] about WordPilot since I 
last wrote: [feature update, new capability, relevant case study].

No rush — just wanted to keep it on your radar in case it's useful.

Best,
[Your name]

Follow-Up 2 (5–7 days after follow-up 1)

Subject: Quick thought on [their domain]

Hi [Name],

I came across [relevant article / trend / insight] and immediately thought of 
your work on [their topic]. [One sentence connecting the insight to them].

WordPilot handles this well — specifically [relevant feature]. I won't keep 
following up after this, but wanted to share the connection.

If it ever becomes relevant, my inbox is open.

Best,
[Your name]

Follow-Up 3 — Final (5–7 days after follow-up 2)

Subject: Re: Quick thought on [their domain]

Hi [Name],

Last note from me — I'll leave you be after this.

If you ever want to explore WordPilot, the door's open. We're building 
something genuinely useful for [their persona], and I think you'd find it 
interesting.

No reply needed — just wanted to leave that on the table.

Best,
[Your name]

DM / Social Outreach (Twitter, LinkedIn)

LinkedIn Connection Note

Hi [Name] — I came across your [work/talk/post] on [topic] and was really 
impressed by [specific insight]. I work on an AI writing tool that touches 
similar ground. Would love to connect.

Twitter DM (if already connected)

Hey [Name] — loved your [post/thread] on [topic]. Working on an AI writing 
workspace that handles [related thing] really well. Thought you might find 
it interesting: [link]. No pitch — just sharing.

Response Handling

If They Reply "Not interested"

Thanks for letting me know, [Name]. Totally understand — appreciate you 
taking the time to reply. All the best with [their work/company].

If They Reply "Tell me more"

Send a concise 3–4 sentence overview of WordPilot with one specific feature relevant to their work. End with an invitation to try it or schedule a quick walkthrough.

If They Reply "Trying it out"

Celebrate internally (move to Stage 5 — Nurturing). Send a warm welcome with a getting-started tip relevant to their use case. Offer to answer questions.

Anti-Patterns (Never Do These)

❌ "Just following up!" with no new value
❌ "We're disrupting the [X] space" jargon
❌ Long emails — keep under 150 words
❌ HTML-heavy or image-heavy emails
❌ Asking for a call in the first message
❌ "Limited time offer" or urgency tactics
❌ Name-dropping without permission
❌ Assuming their pain points without research