marketing-leads-generation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

LEAD GENERATION — PIPELINE OS (OPERATIONAL)

线索生成 — 销售管道操作系统(实操版)

Built as a no-fluff execution skill for revenue-aligned demand generation.
Structure: Core lead generation fundamentals first. AI-specific automation in clearly labeled "Optional: AI / Automation" sections.

这是一款无冗余的执行型工具,专为营收对齐的获客需求打造。
结构:先讲解核心线索生成基础原理,AI相关自动化内容会明确标注在「可选:AI / 自动化」章节中。

Core: Lead Type Definitions

核心:线索类型定义

Clear definitions prevent Sales/Marketing friction. Align on these before building pipeline.
Lead TypeDefinitionQualification CriteriaOwner
LeadAny identified contactHas email/phone, some interest signalMarketing
MQL (Marketing Qualified Lead)Fits ICP + engaged with marketingFirmographic fit + behavior thresholdMarketing
SQL (Sales Qualified Lead)Ready for sales conversationMQL + explicit buying signal or demo requestSales
PQL (Product Qualified Lead)Used product, shows upgrade potentialTrial/freemium + usage thresholdProduct + Sales
SAL (Sales Accepted Lead)SQL accepted by sales repSales confirms qualification after first contactSales
清晰的定义可避免销售与营销部门之间的摩擦。在构建销售管道前,请先对齐以下定义。
线索类型定义资质标准负责方
Lead(线索)任何已识别的联系人拥有邮箱/电话,且存在一定兴趣信号营销部
MQL(营销合格线索)符合客户理想画像(ICP)且与营销内容产生互动企业属性匹配 + 达到行为阈值营销部
SQL(销售合格线索)已准备好与销售对接MQL + 明确的购买信号或演示请求销售部
PQL(产品合格线索)已使用产品,且展现出升级潜力试用/免费版用户 + 达到使用阈值产品部 + 销售部
SAL(销售接受线索)销售代表确认接受的SQL销售首次联系后确认符合资质销售部

What “Good” Looks Like (Operational)

实操层面的“优秀”标准

Set targets from your own baseline, then improve stage-by-stage:
  • Sales acceptance rate (SQL → SAL)
  • Speed-to-lead (time to first touch)
  • Stage conversion rates and time-in-stage
  • Pipeline created per channel (not leads)

从自身基准数据设定目标,然后分阶段优化:
  • 销售接受率(SQL → SAL)
  • 线索响应速度(首次触达时间)
  • 阶段转化率及各阶段停留时长
  • 各渠道产生的销售管道数量(而非线索数量)

Core: Funnel Design Framework

核心:漏斗设计框架

StageUser StateContent/ActionGoal
AwarenessProblem-awareBlog, social, SEO, adsCapture attention
InterestSolution-curiousGuides, webinars, comparisonsCapture contact info
ConsiderationEvaluating optionsCase studies, demos, free toolsConvert to MQL
DecisionReady to buyPricing, proposals, trialsConvert to SQL → Opportunity
ActivationNew customerOnboarding, training, quick winsReduce churn, increase expansion
阶段用户状态内容/动作目标
认知阶段已意识到问题博客、社交媒体、SEO、广告吸引注意力
兴趣阶段对解决方案好奇指南、线上研讨会、竞品对比获取联系信息
考虑阶段正在评估选项案例研究、产品演示、免费工具转化为MQL
决策阶段准备购买定价、方案、试用转化为SQL → 销售机会
激活阶段新客户入职培训、快速上手教程降低 churn(客户流失),提升拓展营收

Funnel Diagnostic Questions

漏斗诊断问题

  1. Where is the biggest drop-off? (Measure stage-to-stage conversion)
  2. What's your time-in-stage for each? (Long times = friction)
  3. Are leads skipping stages? (May indicate misalignment)
  4. What percentage of MQLs get accepted by Sales? (Low = quality issue)
For full funnel setup including MQL/SQL criteria and SLAs, use lead-funnel-definition.md.

  1. 哪个阶段的流失率最高?(衡量阶段间转化率)
  2. 每个阶段的平均停留时长是多少?(时长过长意味着存在摩擦)
  3. 是否有线索跳过阶段?(可能表明部门间对齐不足)
  4. MQL的销售接受率是多少?(过低则说明线索质量存在问题)
如需完整的漏斗设置,包括MQL/SQL标准及服务水平协议(SLA),请参考lead-funnel-definition.md

Core: Gating Strategy

核心:内容 gated( gated 指需要填写信息才能获取)策略

Not all content should be gated. Use this decision framework:
Content TypeGate?Why
Blog posts, how-to guidesNoBuild SEO, trust, awareness
Comparison guides, buyers guidesLight gate (email only)High intent, worth capturing
Industry reports, original researchGateHigh value, worth exchange
ROI calculators, assessmentsGateStrong buying signals
Product demos, pricingGateDirect sales intent
Case studiesOptionalGate if detailed; ungate if brief
并非所有内容都需要设置 gated。请使用以下决策框架:
内容类型是否设置Gated?原因
博客文章、操作指南提升SEO效果,建立信任,扩大认知
对比指南、买家指南轻Gated(仅需邮箱)用户意向高,值得获取联系方式
行业报告、原创研究高价值内容,值得用户交换信息
ROI计算器、评估工具强烈的购买信号
产品演示、定价信息直接的销售意向
案例研究可选详细案例设置Gated;简短案例则无需

Do (Gating)

正确做法(Gated策略)

  • Ask only for fields you'll use (email + company is often enough)
  • Progressive profiling: collect more data over multiple interactions
  • A/B test gated vs ungated for the same content
  • Honor the value exchange: gated content must deliver real value
  • 仅索要你会实际使用的字段(通常邮箱+公司名称已足够)
  • 渐进式信息收集:通过多次互动逐步收集更多数据
  • 对同一内容进行 gated 与非 gated 的A/B测试
  • 确保价值对等:gated内容必须提供真正的价值

Avoid (Gating)

避免做法(Gated策略)

  • Gating everything (kills organic discovery)
  • Long forms for top-of-funnel content (start with the minimum fields you will use)
  • Requiring phone number for early-stage content
  • Gating content that's freely available elsewhere

  • 所有内容都设置gated(会扼杀自然流量发现)
  • 对漏斗顶部内容使用长表单(从最少的必填字段开始)
  • 要求早期阶段的用户提供电话号码
  • 对其他渠道可免费获取的内容设置gated

Core: Attribution Fundamentals + Limitations

核心:归因分析基础与局限性

Attribution Models

归因模型

ModelHow It WorksBest ForLimitation
First-touch100% credit to first interactionUnderstanding awareness sourcesIgnores nurture journey
Last-touch100% credit to final touchUnderstanding closing sourcesIgnores awareness
LinearEqual credit to all touchesSimple multi-touchOver-credits low-value touches
Time-decayMore credit to recent touchesLong sales cyclesComplex to implement
Position-based40/20/40 to first/middle/lastBalanced viewStill somewhat arbitrary
模型工作原理适用场景局限性
首次触达归因100% credit归给首次互动了解认知来源忽略培育旅程
末次触达归因100% credit归给最终互动了解转化闭合来源忽略认知阶段
线性归因所有互动均分credit简单的多触点场景过度低价值触点的credit
时间衰减归因近期互动获得更多credit长销售周期场景实施复杂
基于位置的归因40/20/40分配给首次/中间/末次互动平衡视角仍存在一定主观性

What Attribution Cannot Tell You

归因分析无法告知你的信息

  • Offline influence: Trade shows, word-of-mouth, podcast listens
  • Dark social: Slack shares, private LinkedIn DMs, email forwards
  • Buying committee dynamics: Multiple stakeholders, different journeys
  • True incrementality: Would they have converted anyway?
  • 线下影响:展会、口碑传播、播客收听
  • 暗社交:Slack分享、LinkedIn私信、邮件转发
  • 采购委员会动态:多个利益相关方,不同的决策旅程
  • 真实增量:无论是否有该触点,用户都会转化吗?

Do (Attribution)

正确做法(归因分析)

  • Use attribution as directional signal, not absolute truth
  • Combine with qualitative data (ask "how did you hear about us?")
  • Focus on trends over time, not single-touchpoint credit
  • Match attribution model to your sales cycle length
  • 将归因作为方向性信号,而非绝对事实
  • 结合定性数据(询问“你是如何了解到我们的?”)
  • 关注长期趋势,而非单个触点的credit
  • 根据销售周期长度选择合适的归因模型

Avoid (Attribution)

避免做法(归因分析)

  • Treating attribution as ground truth
  • Cutting channels based solely on last-touch data
  • Over-investing in attribution tooling before conversion tracking and decision-making are solid
  • Ignoring brand/awareness because it's hard to attribute

  • 将归因分析视为绝对真理
  • 仅基于末次触达数据砍掉渠道
  • 在转化追踪和决策流程稳定前,过度投资归因工具
  • 因难以归因而忽略品牌/认知建设

Core: Lead Quality vs Volume Tradeoffs

核心:客户账户销售(ABS)

The 2025 reality: precision > volume. Longer sales cycles and larger buying committees mean quality matters more than ever.
StrategyQualityVolumeBest When
Volume playLowerHigherNew market, testing channels, brand building
Precision playHigherLowerKnown ICP, limited SDR capacity, high ACV
BalancedMediumMediumMost B2B companies
当针对高价值客户且采购流程涉及多个利益相关方时,ABS在B2B场景中通常非常有效。

Quality Signals (Prioritize These)

何时使用ABS

  • ICP firmographic match (industry, size, geo)
  • Explicit intent signals (demo request, pricing page, competitor comparison)
  • Engagement depth (multiple pages, return visits, long time on site)
  • Decision-maker title
标准阈值原因
ACV(年度合同价值)>$25K值得投入研究成本
TAM(目标市场规模)<5,000个客户有限的、可精准定位的市场
采购委员会3+利益相关方需要多线程对接方式
销售周期>60天有时间培育客户关系

Warning Signs (Low Quality)

ABS执行框架

  • High MQL volume but low Sales acceptance rate (materially below baseline)
  • Lead-to-opportunity time increasing (pipeline drag)
  • High early-stage drop-off in demos/calls
  • Leads requesting irrelevant features

要素执行细节资源
目标客户列表50-200个指定客户,分 tier(Tier 1:20个,Tier2:50个,Tier3:130个)
assets/channel-plan-30-60-90.md
客户研究痛点、技术栈、近期动态、组织架构Tier1客户每个投入30分钟
多线程对接每个客户对接3-5个不同角色的联系人内部支持者 + 经济决策者 + 实际用户
定制内容针对不同tier的痛点定制信息Tier1:完全定制;Tier2:半定制
跨渠道协同协调邮件 + LinkedIn + 广告 + 活动全渠道联动
衡量指标客户互动评分、每个客户产生的销售管道添加至
assets/lead-scoring-model.md

Core: Account-Based Sales (ABS)

正确做法(ABS)

ABS is often effective in B2B when targeting high-value accounts with complex buying committees.
  • 从Tier1(最高价值客户)开始,验证该模式的有效性
  • 销售与营销部门共同确定客户选择和信息传递策略
  • 使用意向数据优先定位显示出购买信号的客户
  • 追踪客户层面的指标,而非仅线索层面

When to Use ABS

避免做法(ABS)

CriteriaThresholdWhy
ACV>$25KWorth the research investment
TAM<5,000 accountsFinite, targetable market
Buying committee3+ stakeholdersMulti-threaded approach needed
Sales cycle>60 daysTime to nurture relationships
  • 针对超过200个客户运行ABS(会变成广撒网)
  • 将ABS视为“只是个性化邮件”(它是全渠道协同的策略)
  • 跳过客户研究(通用的触达会失去意义)
  • 单线程对接客户(内部支持者离职则交易失败)

ABS Execution Framework

何时使用本工具

ElementExecutionResource
Target list50-200 named accounts, tiered (Tier 1: 20, Tier 2: 50, Tier 3: 130)
assets/channel-plan-30-60-90.md
Account researchPain points, tech stack, recent news, org chart30 min per Tier 1 account
Multi-threading3-5 contacts per account across rolesChampion + economic buyer + user
Custom contentPain-specific messaging per tierTier 1: fully custom; Tier 2: semi-custom
OrchestrationCoordinated email + LinkedIn + ads + eventsSequence all channels
MeasurementAccount engagement score, pipeline per accountAdd to
assets/lead-scoring-model.md
  • 销售管道构建/修复:新增SQL目标、激活停滞的漏斗、重新平衡渠道组合
  • outbound( outbound指主动触达)动作:冷邮件/LinkedIn消息、电话脚本、回复处理、异议反驳
  • 着陆页/CRO(转化率优化):优化头部内容/方案/CTA、表单、信任背书、点击后路由
  • 线索评分/分配:MQL/SQL阈值、SDR/AE(销售开发代表/客户成功代表)交接、SLA设计
  • 实验节奏:30/60/90天测试计划、ICE/PIE评分、停止/扩大规模规则
  • 合规/送达率:CAN-SPAM/GDPR合规、域名预热、退订、DKIM/SPF/DMARC设置
  • 客户账户销售(ABS):指定客户定位、多线程触达、客户评分

Do (ABS)

何时不使用本工具

  • Start with Tier 1 (highest value) to prove the motion
  • Coordinate Sales + Marketing on account selection and messaging
  • Use intent data to prioritize accounts showing buying signals
  • Track account-level metrics, not just lead-level
以下场景请使用相关工具替代:
  • 有机内容策略marketing-social-media
  • 着陆页SEOmarketing-seo-complete
  • AI搜索优化marketing-ai-search-optimization
  • 产品驱动增长运营product-management
  • 付费媒体采购/优化marketing-paid-advertising

Avoid (ABS)

快速参考

  • Running ABS on >200 accounts (becomes spray-and-pray)
  • Treating ABS as "just personalized email" (it's full orchestration)
  • Skipping account research (generic outreach defeats the purpose)
  • Single-threading accounts (champion leaves = deal dies)

任务SOP/模板位置使用场景
定义ICP + 方案ICP & 方案快速迭代查看实操SOP → ICP & 方案信息传递、竞价或列表构建前
30/60/90天渠道计划测试计划网格查看实操SOP → 渠道计划新市场拓展或季度重置
邮件/LinkedIn触达序列5触点框架(优先CTA)查看实操SOP → 邮件/LinkedIn序列冷触达/潜在客户培育
冷电话脚本带发现环节的话术查看实操SOP → 冷电话脚本主动外呼、活动跟进
着陆页优化头部内容/方案/信任背书/CTA/表单检查清单查看实操SOP → 着陆页优化转化率低或广告与页面不匹配
线索评分与分配评分规则 + SLA查看实操SOP → 线索评分与分配SDR/AE交接、CAC/SQL偏离
线索响应速度操作系统回复 + 提醒查看实操SOP → 线索响应速度回复/未到场问题、收件箱响应速度
实验矩阵ICE/PIE + 停止/扩大规模规则查看实操SOP → 实验矩阵每周优先级排序
合规/送达率认证 + 退订查看实操SOP → 合规与送达率冷邮件/域名健康
2025邮件送达率指南批量发送要求
assets/email-deliverability-2025.md
批量发送(每日5000+至Gmail)、新域名
LinkedIn触达安全指南符合条款的触达规则
assets/linkedin-automation-safety-2025.md
降低LinkedIn触达风险

When to Use This Skill

决策树(销售管道诊断)

  • Pipeline build/rehab: net-new SQL targets, revive stalled funnels, rebalance channel mix
  • Outbound motions: cold email/LinkedIn, call scripts, reply handling, objection rebuttals
  • Landing/CRO: fix hero/offer/CTA, forms, proof, trust, and post-click routing
  • Lead scoring/routing: MQL/SQL thresholds, SDR/AE handoff, SLA design
  • Experiment cadence: 30/60/90 test plans, ICE/PIE scoring, stop/scale rules
  • Compliance/deliverability: CAN-SPAM/GDPR hygiene, domain warmup, opt-out, DKIM/SPF/DMARC
  • Account-based sales (ABS): named account targeting, multi-threaded outreach, account scoring
text
线索数量不足?
├─ 客户理想画像(ICP)/方案不清晰 → 启动ICP与方案快速迭代 → 输出3个钩子(痛点/风险/价值) → 重新测试
├─ 渠道单一 → 添加第二个渠道(LinkedIn + 邮件 或 再营销) → 小预算测试
└─ 数量充足但质量低 → 收紧筛选条件 + 线索评分 → 重新分配路由 + 新CTA

回复率低?
├─ 打开率显著低于基准(或退信/投诉率上升) → 优化列表质量 + 认证 + 主题/钩子
└─ 打开率正常但回复率低 → 重写CTA(单一动作),添加信任背书/触发点,缩短至≤120字

回复率不错但成单率低? → 提升线索响应速度 + 2次跟进 + 日历链接 + 摩擦点审计

流量充足但转化率低?
├─ 信息不匹配 → 重写头部内容/CTA以匹配广告/痛点
├─ 信任背书不足 → 添加3种类型的信任背书(数据案例、品牌logo、客户 testimonial)
└─ 表单摩擦大 → 减少字段,添加多步骤或聊天表单,突出隐私/信任

When NOT to Use This Skill

实操SOP(快速执行)

ICP与方案快速迭代(90分钟)

Use related skills instead for:
  • Organic content strategymarketing-social-media
  • SEO for landing pagesmarketing-seo-complete
  • AI search optimizationmarketing-ai-search-optimization
  • Product-led growth ownershipproduct-management
  • Paid media buying/optimizationmarketing-paid-advertising

  • 提取前10个成功/失败案例;总结企业属性 + 触发点 + 异议模式。
  • 起草3个方案:痛点解决型速度/自动化型风险逆转型。每个方案配1个量化信任背书 + 1个紧迫感杠杆。
  • 输出3个LinkedIn/邮件钩子:痛点风险/不作为的成本更好的未来。保持CTA单一(适配性检查/演示/审计)。

Quick Reference

销售管道健康检查清单(每周)

TaskSOP/TemplateLocationWhen to Use
Define ICP + OfferICP & Offer SprintSee Operational SOPs → ICP & OfferBefore messaging, bidding, or list-building
Channel Plan 30/60/90Test Plan GridSee Operational SOPs → Channel PlanNew market motion or quarterly reset
Email/LinkedIn Cadence5-touch skeleton (CTA-first)See Operational SOPs → Email/LinkedIn CadencesCold/prospecting or nurture
Cold Call ScriptTalk track w/ discoverySee Operational SOPs → Cold Call ScriptLive outbound, event follow-up
Landing FixHero/offer/proof/CTA/form checklistSee Operational SOPs → Landing Page FixLow CVR or ad-to-page mismatch
Lead Scoring & RoutingPoints + SLASee Operational SOPs → Lead Scoring + RoutingSDR/AE handoff, CAC/SQL drift
Speed-to-Lead OSResponse + remindersSee Operational SOPs → Speed-to-LeadReply/no-show issues, inbox speed
Experiment MatrixICE/PIE + stop/scaleSee Operational SOPs → Experiment MatrixWeekly prioritization
Compliance/DeliverabilityAuthentication + opt-outSee Operational SOPs → Compliance & DeliverabilityCold email/domain health
Email Deliverability 2025Bulk sender requirements
assets/email-deliverability-2025.md
Bulk sending (5,000+/day to Gmail), new domains
LinkedIn Outreach SafetyTerms-compliant outreach guardrails
assets/linkedin-automation-safety-2025.md
LinkedIn outreach risk reduction

  • 确认阶段定义(MQL/SQL/SAL)未变更(无隐性偏离)。
  • 对比SQL → SAL接受率与基准;若下降则调查主要拒绝原因。
  • 检查线索响应速度的中位数和p90与SLA对比;若违反则优化路由/提醒。
  • 查看退信/投诉/退订趋势;若投诉率飙升则暂停发送。
  • 验证列表卫生:屏蔽退信/退订/投诉用户;必要时移除角色账户。
  • 对照对照组验证2个 outbound序列(基于回复率和成单率,而非打开率/点击率)。
  • 按主要流量来源查看着陆页转化率与基准对比;标记信息不匹配的页面。
  • 确认表单仅收集实际使用的字段;移除任何未使用的“可选”字段。
  • 审核路由规则:高意向线索优先分配给人工;机器人/自动化仅作为辅助。
  • 确认本周归因模型一致(中期无报告变更)。
  • 查看各渠道产生的销售管道数量(而非线索数量),并将精力重新分配给前2个有效渠道。
  • 查看到场率和未到场原因;若下降则添加提醒或优化摩擦点。
  • 提取5个近期成功案例和5个失败案例;相应更新ICP触发点/异议。
  • 与销售部对齐下周目标客户(ABS)及各细分群体的主要CTA。
  • 记录每个渠道(邮件/LinkedIn/着陆页)的一个变更,包含假设和停止/扩大规模规则。

Decision Tree (Pipeline Triage)

30/60/90天渠道计划

text
Leads low?
├─ ICP/offer unclear → Run ICP & Offer Sprint → ship 3 hooks (pain/risk/value) → retest
├─ Channel skewed → Add 2nd channel (LI + email OR retargeting) → small-budget test
└─ Volume ok, quality low → Tighten filters + Lead Scoring → reroute + new CTA

Replies low?
├─ Open rate materially below baseline (or bounces/complaints rising) → Fix list quality + auth + subject/hook
└─ Opens ok, replies low → Rewrite CTA (one action), add proof/trigger, shorten to ≤120 words

Bookings low but replies? → Add Speed-to-Lead + 2 follow-ups + calendar drop + friction audit

Traffic ok, CVR low?
├─ Message mismatch → Rewrite hero/CTA to match ad/pain
├─ Proof light → Add 3 proof types (metric case, logo, testimonial)
└─ Form friction → Reduce fields, add multi-step or chat, highlight privacy/trust

  • 30天:在邮件 + LinkedIn(连接 + 私信) + 1种再营销格式中验证2个钩子。目标:基于自身基准设定回复率 + CPL(线索获取成本)阈值;保障线索质量(销售接受率、SQL转化率)。
  • 60天:保留有效钩子;添加线上研讨会/工作坊或合作伙伴/推荐渠道。增加培育内容(价值输出) + 再营销。
  • 90天:扩大前2个有效渠道的投入;添加线索评分 + SDR服务水平协议;停止未达约定阈值的低效渠道。审查CAC、SQL→机会→成单率。

Operational SOPs (Fast Execution)

邮件/LinkedIn触达序列(3–6个触点)

ICP & Offer Sprint (90 minutes)

  • Pull top 10 wins/losses; extract firmographic + trigger + objection patterns.
  • Draft 3 offers: pain-killer, speed/automation, risk reversal. Each with 1 quantified proof + 1 urgency lever.
  • Ship 3 hooks for LI/email: pain, risk/cost of inaction, better future. Keep CTA singular (fit check/demo/audit).
  • 触点1:痛点钩子 + 信任背书 + 单一CTA + 退订选项。70–120字。
  • 触点2:迷你案例(前后对比数据) + 成单日历链接CTA。
  • 触点3:异议处理(安全/集成/预算) + 适配性快速检查CTA。
  • 触点4–6:不作为的成本计算、社交证明、温和提醒。始终包含退订选项和合规 footer。
  • LinkedIn:连接(无推销) → 价值输出(帖子/私信) → 软CTA(基准测试/迷你审计) → 提醒。高意向客户可添加语音消息。

Pipeline Health Checklist (Weekly)

冷电话脚本(话术)

  • Confirm stage definitions (MQL/SQL/SAL) are unchanged (no silent drift).
  • Check SQL → SAL acceptance rate vs baseline; investigate top rejection reasons if down.
  • Check speed-to-lead median and p90 vs SLA; fix routing/alerts if breached.
  • Review bounce/complaint/unsubscribe trends; pause sends if complaints spike.
  • Verify list hygiene: suppress bounces/unsubs/complaints; remove role accounts where required.
  • Validate 2 outbound sequences against a control (reply rate and meeting rate), not opens/clicks.
  • Review landing page CVR vs baseline by top traffic sources; flag message mismatch.
  • Confirm forms capture only fields in use; remove any unused “nice-to-have” fields.
  • Audit routing: highest-intent leads go to humans first; bots/automation only assist.
  • Confirm attribution model is consistent this week (no reporting changes mid-period).
  • Inspect pipeline created per channel (not leads) and reallocate effort to top 2 plays.
  • Review show rate and no-show reasons; add reminders or friction fixes if slipping.
  • Pull 5 recent wins and 5 losses; update ICP triggers/objections accordingly.
  • Align with Sales on next-week target accounts (ABS) and the primary CTA per segment.
  • Document one change per channel (email/LI/landing) with a hypothesis and stop/scale rule.
  • 开场白:一句话说明权限 + 价值;避免“我打扰到你了吗…”。
  • 发现环节:3个问题(当前工具/流程、痛点数据、触发点/优先级)。
  • 价值传递:匹配核心痛点;引用一个信任背书;提出下一步动作。
  • 异议处理:认可 → 简短信任背书 → 微小承诺(分享技术栈/预约15分钟沟通)。
  • 收尾:限时CTA(本周) + 通话中发送日历链接。

Channel Plan (30/60/90)

着陆页优化(方案优先)

  • 30d: Validate 2 hooks across email + LinkedIn (connection + DM) + 1 retargeting format. Targets: reply rate + CPL guardrails set from your baseline; protect lead quality (Sales acceptance, SQL rate).
  • 60d: Keep winners; add webinar/workshop or partner/referral. Layer nurture (value drops) + remarketing.
  • 90d: Scale top 2 plays; add lead scoring + SDR SLAs; kill underperformers that stay below an agreed guardrail after a fair sample. Review CAC, SQL→opp→win.
  • 头部内容:问题 + 结果 + 信任背书;CTA置于首屏。与广告/序列语言保持一致。
  • 方案:3个要点(价值、速度、风险逆转)。必要时添加价格提示。
  • 信任背书:品牌logo条 + 1个数据案例 + 1个客户 testimonial;添加合规/信任标识(安全认证)。
  • 表单:减少字段;添加多步骤或聊天表单;自动发送邮件/SMS确认;展示隐私/退订政策。
  • 测试:头部内容变体(痛点 vs 结果)、CTA文本、社交证明模块、表单长度、风险逆转。

Email/LinkedIn Cadences (3–6 touches)

线索评分与分配

  • Touch 1: Pain hook + proof + single CTA + opt-out. 70–120 words.
  • Touch 2: Mini-case (before/after metric) + CTA to booking link.
  • Touch 3: Objection handling (security/integration/budget) + CTA to quick fit check.
  • Touch 4–6: Cost-of-inaction math, social proof, light bump. Always include opt-out and compliance footer.
  • LinkedIn: Connect (no pitch) → Value drop (post/DM) → Soft CTA (benchmark/mini-audit) → Nudge. Add voice note if high-intent.
  • 评分维度:适配性(行业/规模/角色)、意向(页面深度、回复)、行为(演示请求、资源下载)。
  • [示例] 分数:适配性(0–40)、意向(0–40)、行为(0–20)。MQL≥60;SQL≥75且为决策角色或有演示意向。
  • 路由规则:MQL → SDR在15分钟内;SQL → AE预留日历。SLA:首次触达<15分钟,第二次触达<2小时,第三次触达当天完成。

Cold Call Script (Talk Track)

线索响应速度操作系统

  • Opener: Permission + value in one line; avoid “Did I catch you…”.
  • Discovery: 3 questions (current tool/flow, pain metric, trigger/priority).
  • Value hits: Match top pain; cite one proof; propose next step.
  • Objections: Acknowledge → brief proof → micro-commit (share stack/book 15m).
  • Close: Time-bound CTA (this week) + send calendar while on call.
  • 收件箱+CRM提醒(邮件、Slack、移动端)。自动回复附带日历链接。
  • 序列:T0分钟:回复/确认;T+15分钟:价值输出 + 预约链接;T+4小时:提醒 + 社交证明;T+24小时:电话 + SMS(若获同意)。
  • 追踪:响应时间、成单率、未到场率;若无回复则添加提醒 + 备用代表。

Landing Page Fix (Offer-First)

实验矩阵

  • Hero: Problem + outcome + proof; CTA above fold. Mirror ad/sequence language.
  • Offer: 3 bullets (value, speed, risk reversal). Add pricing cue if helpful.
  • Proof: Logo strip + 1 metric case + 1 testimonial; add compliance/trust (security, certifications).
  • Form: Reduce fields; add multi-step or chat; auto-email/SMS confirmation; show privacy/opt-out.
  • Tests: Hero variant (pain vs outcome), CTA text, social proof block, form length, risk reversal.
  • 每周用ICE/PIE评分筛选创意。最多运行3–5个测试;限制影响范围(预算/数量)。
  • 若达到最小样本量后仍未达约定阈值则停止;仅在连续检查中看到可重复提升时扩大规模。
  • 记录:假设、负责人、开始/结束时间、样本量、指标、决策(停止/扩大/迭代)。

Lead Scoring + Routing

合规与送达率(实操检查清单)

  • Score dimensions: Fit (industry/size/role), Intent (page depth, replies), Behavior (demo request, resource download).
  • [Inference] Example points: Fit (0–40), Intent (0–40), Behavior (0–20). MQL ≥60; SQL ≥75 with decision role or demo intent.
  • Routing: MQL → SDR within 15 minutes; SQL → AE calendar hold. SLA: first touch <15m, 2nd touch <2h, 3rd touch same day.
目标:在运行 outbound和培育活动时维持送达率并保护品牌信任。
垃圾邮件率阈值(关键 — 2025年强制执行)
  • Gmail/Yahoo/Microsoft硬上限:**0.3%**投诉率
  • 推荐目标:**<0.1%**以保障收件箱投递
  • Gmail(2025年11月):不合规发送者将收到永久5xx拒绝
  • Microsoft(2025年5月):未认证的批量发送者在消费者邮箱将被直接拒绝
详见
assets/email-deliverability-2025.md
获取完整执行细节。
认证(必填)
退订(批量发送者必填)
合规基础
列表卫生(执行)
  • 绝不购买线索列表;使用已验证的来源并在必要时获取明确同意。
  • 屏蔽:硬退信、退订、投诉信号。
  • 清理不活跃收件人(在声誉受损前减少发送量)。
发送实践(执行)
  • 保持发送身份稳定(发件域名/名称);避免频繁切换域名。
  • 新域名需预热并逐步提升发送量;若投诉率飙升则停止。
  • 保持邮件可读性:清晰的方案、最少的链接、真实的回复路径、纯文本版本。

Speed-to-Lead OS

指标与质量保证

  • Inbox+CRM alerts (email, Slack, mobile). Auto-response with calendar link.
  • Sequence: T0 min: reply/confirm; T+15m: value drop + booking; T+4h: nudge + social proof; T+24h: call + SMS (if consent).
  • Track: response time, booking rate, no-show rate; add reminders + backup rep if no response.
  • 核心指标:回复率、成单率、到场率、SQL数量、销售机会、成单率、CAC、投资回收期。
  • 次要指标:收件箱投递率、退信率、投诉信号、打开率(仅作方向参考)、点击到成单率、首次触达时间。
  • 每个迭代周期的质量保证:信息/方案匹配、CTA清晰度、信任背书强度、合规性、路由速度。

Experiment Matrix

导航:来源与资源

  • Score ideas weekly (ICE/PIE). Run 3–5 tests max; cap blast radius (budget/volume).
  • Stop if below an agreed guardrail after minimum sample; scale only after repeatable lift across consecutive checks.
  • Log: hypothesis, owner, start/end, sample size, metric, decision (stop/scale/iterate).
  • 实操模式:
    references/operational-patterns.md
  • 核心模板:邮件(
    assets/email-sequence.md
    )、LinkedIn(
    assets/linkedin-sequence.md
    )、冷电话(
    assets/cold-call-script.md
    )、着陆页审计(
    assets/landing-audit-checklist.md
    )、线索评分(
    assets/lead-scoring-model.md
    )、渠道计划(
    assets/channel-plan-30-60-90.md
    )、线索响应速度(
    assets/speed-to-lead-playbook.md
    )、实验矩阵(
    assets/experiment-matrix.md
    )、线索漏斗定义(assets/lead-funnel-definition.md
  • 附加模板:邮件送达率(
    assets/email-deliverability-2025.md
    )、LinkedIn触达安全(
    assets/linkedin-automation-safety-2025.md
  • 可选:AI / 自动化:AI个性化(
    assets/ai-personalization-playbook.md
  • 网络来源:
    data/sources.json
  • 线索生成策略师提示词:
    custom-gpt/productivity/Lead-generation/01_lead-generation.md
  • 线索生成策略师来源:
    custom-gpt/productivity/Lead-generation/02_sources-lead-generation.json
  • 书籍(实操要点):
    • Urbanski —
      custom-gpt/productivity/Lead-generation/sources/Ancient_Secrets_of_Lead_Generation_-_Daryl_Urbanski.pdf
      (漏斗、数据、自动化)
    • Turner —
      custom-gpt/productivity/Lead-generation/sources/Connect_The_Secret_LinkedIn_Playbook_To_Generate_Leads_Build_Relationships_And_Dramatically_Increase_Your_Sales_-_Josh_Turner.pdf
      (LinkedIn触达/序列)
    • Brock —
      custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Authority_-_David_Brock.pdf
      (企业级销售严谨性)
    • Gilbert —
      custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Unlocked_-_Joe_Gilbert.pdf
      (方案 + outbound转型)
    • Shapiro —
      custom-gpt/productivity/Lead-generation/sources/Rethink_Lead_Generation_-_Tom_Shapiro.pdf
      (差异化定位)
    • Tsai —
      custom-gpt/productivity/Lead-generation/sources/The_Digital_Real_Estate_Marketing_Playbook_How_to_generate_more_leads_close_more_sales_and_even_become_a_millionaire_real_estate_agent_with_the_power_of_internet_marketing_-_Nick_Tsai.pdf
      (垂直/本地线索流程)
    • Harasty —
      custom-gpt/productivity/Lead-generation/sources/Turning_Your_Business_into_a_Success_Monster_-_Chris_Harasty.pdf
      (方案叠加、思维模式到实操)

Compliance & Deliverability (Operational Checklist)

相关工具

Goal: Sustain deliverability and protect brand trust while running outbound and nurture.
Spam Rate Thresholds (Critical — 2025 Enforcement)
  • Gmail/Yahoo/Microsoft hard ceiling: 0.3% complaint rate
  • Recommended target: <0.1% for reliable inbox placement
  • Gmail (Nov 2025): Non-compliant senders receive permanent 5xx rejections
  • Microsoft (May 2025): Bulk senders without auth are rejected outright on consumer mailboxes
See
assets/email-deliverability-2025.md
for full enforcement details.
Authentication (Required)
Unsubscribe (Required for bulk senders)
Compliance Basics
List Hygiene (Execution)
  • Never buy lists; use verified sources and documented consent where required.
  • Suppress: hard bounces, unsubscribes, and complaint signals.
  • Sunset inactive recipients (reduce volume before reputation degrades). [Inference]
Sending Practices (Execution)
  • Keep sending identity stable (From domain/name); avoid frequent domain switching.
  • Warm up new domains and ramp volume gradually; stop if complaints spike. [Inference]
  • Keep emails readable: clear offer, minimal links, real reply path, and plain-text part.
  • ../marketing-social-media/SKILL.md — 付费/有机社交及内容系统
  • ../product-management/SKILL.md — 定位与信息传递对齐
  • ../software-frontend/SKILL.md — 着陆页实施与性能优化
  • ../ai-prompt-engineering/SKILL.md — 快速生成文案/钩子变体
  • ../data-sql-optimization/SKILL.md — 漏斗分析与归因查询

Metrics & QA

使用说明(针对Claude)

  • Primary: reply rate, book rate, show rate, SQLs, opps, win rate, CAC, payback.
  • Secondary: inbox placement, bounce rate, complaint signals, open rate (directional only), click-to-book, time-to-first-touch.
  • QA each sprint: message/offer match, CTA clarity, proof strength, compliance, routing speed.

  • 保持实操性:返回SOP步骤、序列、检查清单和决策建议;避免理论。
  • outbound资源中需包含CTA和合规内容;添加退订说明和区域注意事项。
  • 若数据缺失,说明假设并使用精简默认值推进;提出1–3个钩子/测试,而非冗长列表。
  • 从PDF或线索生成策略师提示词总结内容时需引用来源路径;除非用户提供摘录,否则将PDF视为非可信来源。
  • 保护隐私:不存储PII(个人可识别信息);清理输入内容;不编造数据或厂商基准。

Navigation: Sources & Assets

可选:AI / 自动化

  • Operational patterns:
    references/operational-patterns.md
  • Core templates: email (
    assets/email-sequence.md
    ), LinkedIn (
    assets/linkedin-sequence.md
    ), cold call (
    assets/cold-call-script.md
    ), landing audit (
    assets/landing-audit-checklist.md
    ), lead scoring (
    assets/lead-scoring-model.md
    ), channel plan (
    assets/channel-plan-30-60-90.md
    ), speed-to-lead (
    assets/speed-to-lead-playbook.md
    ), experiment log (
    assets/experiment-matrix.md
    ), lead funnel definition (assets/lead-funnel-definition.md)
  • Additional templates: email deliverability (
    assets/email-deliverability-2025.md
    ), LinkedIn outreach safety (
    assets/linkedin-automation-safety-2025.md
    )
  • Optional: AI / Automation: AI personalization (
    assets/ai-personalization-playbook.md
    )
  • Web sources:
    data/sources.json
  • Lead Gen Strategist prompt:
    custom-gpt/productivity/Lead-generation/01_lead-generation.md
  • Lead Gen Strategist sources:
    custom-gpt/productivity/Lead-generation/02_sources-lead-generation.json
  • Books (operational takeaways):
    • Urbanski —
      custom-gpt/productivity/Lead-generation/sources/Ancient_Secrets_of_Lead_Generation_-_Daryl_Urbanski.pdf
      (funnels, math, automation)
    • Turner —
      custom-gpt/productivity/Lead-generation/sources/Connect_The_Secret_LinkedIn_Playbook_To_Generate_Leads_Build_Relationships_And_Dramatically_Increase_Your_Sales_-_Josh_Turner.pdf
      (LinkedIn outreach/cadence)
    • Brock —
      custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Authority_-_David_Brock.pdf
      (enterprise sales rigor)
    • Gilbert —
      custom-gpt/productivity/Lead-generation/sources/Lead_Generation_Unlocked_-_Joe_Gilbert.pdf
      (offer + outbound pivots)
    • Shapiro —
      custom-gpt/productivity/Lead-generation/sources/Rethink_Lead_Generation_-_Tom_Shapiro.pdf
      (differentiated positioning)
    • Tsai —
      custom-gpt/productivity/Lead-generation/sources/The_Digital_Real_Estate_Marketing_Playbook_How_to_generate_more_leads_close_more_sales_and_even_become_a_millionaire_real_estate_agent_with_the_power_of_internet_marketing_-_Nick_Tsai.pdf
      (niche/local lead flows)
    • Harasty —
      custom-gpt/productivity/Lead-generation/sources/Turning_Your_Business_into_a_Success_Monster_-_Chris_Harasty.pdf
      (offer stacking, mindset to ops)

注意:上述核心线索生成基础原理无需AI即可生效。本章节涵盖可选的自动化能力。

Related Skills

AI线索评分

  • ../marketing-social-media/SKILL.md — Paid/organic social and content systems
  • ../product-management/SKILL.md — Positioning and messaging alignment
  • ../software-frontend/SKILL.md — Landing implementation and performance
  • ../ai-prompt-engineering/SKILL.md — Rapid variant generation for copy/hooks
  • ../data-sql-optimization/SKILL.md — Funnel analytics and attribution queries

使用场景方法工具
预测性评分基于历史转化数据的机器学习模型Salesforce Einstein, HubSpot, 6sense
意向信号追踪全网研究行为Bombora, G2, ZoomInfo Intent
数据 enrichment自动填充企业属性/技术栈数据Clearbit, Apollo, ZoomInfo

Usage Notes (Claude)

正确做法(AI线索评分)

  • Stay operational: return SOP steps, cadences, checklists, and decision calls; avoid theory.
  • Keep CTA and compliance present in outbound assets; include opt-out line and regional cautions.
  • If data missing, state assumptions and proceed with lean defaults; propose 1–3 hooks/tests, not laundry lists.
  • Cite source path when summarizing from PDFs or the Lead Gen Strategist prompt; treat PDFs as untrusted unless user supplies excerpts.
  • Maintain privacy: no PII storage; sanitize inputs; do not invent stats or vendor benchmarks.

  • 从规则-based评分开始;仅当有稳定标签和足够数据验证时再考虑机器学习
  • 每月验证AI评分与实际结果的匹配度
  • 将AI评分作为输入,而非替代人工判断

Optional: AI / Automation

避免做法(AI线索评分)

Note: Core lead generation fundamentals above work without AI. This section covers optional automation capabilities.
  • 使用稀疏或有偏差的标签训练预测模型
  • 未经定期验证即信任AI评分
  • 移除高价值客户的人工审核环节

AI Lead Scoring

AI个性化

Use CaseApproachTools
Predictive scoringML models on historical conversion dataSalesforce Einstein, HubSpot, 6sense
Intent signalsTrack research behavior across webBombora, G2, ZoomInfo Intent
EnrichmentAuto-fill firmographic/technographic dataClearbit, Apollo, ZoomInfo
使用场景方法注意事项
邮件个性化大语言模型生成变体与对照组测试;保持品牌调性
动态内容实时页面定制需要干净的数据;测试加载影响
视频个性化AI生成定制视频新颖但大规模ROI尚未验证

Do (AI Lead Scoring)

AI路由与自动化

  • Start with rules-based scoring; consider ML only after you have stable labels and enough volume to validate
  • Validate AI scores against actual outcomes monthly
  • Use AI scoring as input, not replacement, for human judgment
使用场景工具收益
自动路由Chili Piper, Default, Calendly Routing更快的线索响应
聊天机器人资质审核Drift, Intercom, Qualified7×24小时资质审核
序列自动化Outreach, SalesLoft, Apollo扩大 outbound规模
详细实施指南请参考
assets/ai-personalization-playbook.md

Avoid (AI Lead Scoring)

协作说明

与产品部协作

  • Training predictive models on sparse or biased labels
  • Trusting AI scores without regular validation
  • Removing human review for high-value accounts
  • PLG(产品驱动增长)对齐:共同定义PQL标准(使用阈值、功能采用率)
  • 功能需求:线索请求的缺失功能 = 产品部输入
  • 试用优化:共同负责试用→付费转化

AI Personalization

与销售部协作

Use CaseApproachConsideration
Email personalizationLLM-generated variantsTest against control; maintain brand voice
Dynamic contentReal-time page customizationRequires clean data; test load impact
Video personalizationAI-generated custom videosNovel but unproven ROI at scale
  • SLA文档:共同创建线索交接SLA及响应时间承诺
  • 反馈循环:每周/每两周召开会议讨论线索质量和拒绝原因
  • 评分校准:每季度与销售部一起审核评分模型
  • 成功/失败分析:共同复盘已关闭交易以优化ICP定义

AI Routing & Automation

与工程部协作

Use CaseToolsBenefit
Auto-routingChili Piper, Default, Calendly RoutingFaster lead response
Chatbot qualificationDrift, Intercom, Qualified24/7 qualification
Sequence automationOutreach, SalesLoft, ApolloScale outbound
See
assets/ai-personalization-playbook.md
for detailed implementation guidance.

  • 表单实施:与工程部协作实现渐进式信息收集、多步骤表单
  • 分析追踪:确保正确的UTM处理、事件追踪、转化归因
  • 集成维护:CRM/MAP同步、webhook可靠性、数据卫生
  • 页面性能:着陆页加载速度直接影响转化率

Collaboration Notes

国际市场

With Product

  • PLG alignment: Define PQL criteria together (usage thresholds, feature adoption)
  • Feature requests: Leads requesting missing features = Product input
  • Trial optimization: Joint ownership of trial→paid conversion
本工具默认使用美英市场规则。针对国际线索生成:
需求参考工具
区域采购委员会动态marketing-geo-localization
区域渠道偏好marketing-geo-localization
合规(GDPR, CASL, LGPD)marketing-geo-localization
文化适配的触达方式marketing-geo-localization
若你的需求涉及国际合规或区域触达规范,请同时使用marketing-geo-localization获取区域特定的约束和适配方案。

With Sales

反模式

  • SLA document: Co-create lead handoff SLAs with response time commitments
  • Feedback loop: Weekly/bi-weekly meeting on lead quality and rejection reasons
  • Scoring calibration: Review scoring model quarterly with sales input
  • Win/loss analysis: Joint review of closed deals to improve ICP definition
反模式失败原因替代方案
以MQL数量为成功指标高数量 ≠ 有效销售管道追踪MQL → SQL接受率
购买线索列表质量差、合规风险、损害域名声誉构建有机 + outbound到已验证联系人
忽略销售部反馈MQL被拒绝,信任受损每周同步线索质量
过度自动化通用触达,回复率低自动化机械流程,个性化信息
单一渠道依赖算法变更会摧毁销售管道至少2-3个渠道
所有内容设置Gated扼杀SEO,惹恼潜在客户高价值内容设置Gated,认知内容不设置
追逐虚荣指标打开率/点击率高但无转化关注回复率、成单率、SQL数量
无归因模型无法优化投入从简单模型开始,逐步迭代

With Engineering

  • Form implementation: Work with engineering on progressive profiling, multi-step forms
  • Analytics tracking: Ensure proper UTM handling, event tracking, conversion attribution
  • Integration maintenance: CRM/MAP sync, webhook reliability, data hygiene
  • Page performance: Landing page load speed directly impacts conversion

International Markets

This skill uses US/UK market defaults. For international lead generation:
NeedSee Skill
Regional buying committee dynamicsmarketing-geo-localization
Regional channel preferencesmarketing-geo-localization
Compliance (GDPR, CASL, LGPD)marketing-geo-localization
Cultural outreach adaptationmarketing-geo-localization
If your query involves international compliance or regional outreach norms, also use marketing-geo-localization for region-specific constraints and adaptations.

Anti-Patterns

Anti-PatternWhy It FailsInstead
MQL volume as success metricHigh volume ≠ pipelineTrack MQL → SQL acceptance rate
Buying lead listsPoor quality, compliance risk, damages domainBuild organic + outbound to verified contacts
Ignoring Sales feedbackMQLs rejected, trust erodesWeekly sync on lead quality
Over-automationGeneric outreach, low reply ratesAutomate mechanics, personalize message
Single-channel dependencyAlgorithm changes kill pipeline2-3 channel minimum
Gating everythingKills SEO, frustrates prospectsGate high-value, ungate awareness
Chasing vanity metricsOpens/clicks without conversionsFocus on reply rate, book rate, SQL
No attribution modelCan't optimize spendStart with simple model, iterate