feat: ingest sales-outbound-strategist agent
- Source: Agent/agency-agents/sales/sales-outbound-strategist.md - Add wiki/sources/sales-outbound-strategist.md (source page) - Add 4 new concept pages: Signal-Based-Selling-Framework, ICP-Ideal-Customer-Profile, Multi-Channel-Sequence-Architecture, Account-Tiering-Model - Update overview.md: add Sales Outbound Methodology section - Update index.md: add source entry + concept entries - Update existing concepts: Challenger-Sales-Model, Land-and-Expand - Append log.md entry
This commit is contained in:
73
wiki/concepts/Account-Tiering-Model.md
Normal file
73
wiki/concepts/Account-Tiering-Model.md
Normal file
@@ -0,0 +1,73 @@
|
||||
---
|
||||
title: "Account Tiering Model"
|
||||
type: concept
|
||||
tags: [sales, outbound, account-based]
|
||||
sources: [sales-outbound-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
三层账户分级模型——根据 ICP 匹配度和战略价值将目标账户分为三个层级,每个层级采用不同的出站深度和个性化程度。
|
||||
|
||||
## Three Tiers
|
||||
|
||||
### Tier 1: Top 50-100 Accounts — Deep, Multi-Threaded, Highly Personalized
|
||||
|
||||
**目标**:最高价值账户的深度渗透
|
||||
|
||||
**策略**:
|
||||
- 全账户研究:10-K/年报、财报电话会议、战略举措
|
||||
- 多线程渗透:每账户 3-5 个联系人(经济决策者/Champion/影响者/终端用户/教练)
|
||||
- 每个 persona 定制消息,引用账户特定举措
|
||||
- 整合触达:直邮、热情引荐、活动触达
|
||||
- 专属销售拥有权,每周账户策略审查
|
||||
|
||||
### Tier 2: Next 200-500 Accounts — Semi-Personalized Sequences
|
||||
|
||||
**目标**:规模化与个性化的平衡
|
||||
|
||||
**策略**:
|
||||
- 行业特定消息 + 开场白账户级个性化
|
||||
- 每账户 2-3 个联系人(主要买家 + 一位额外利益相关者)
|
||||
- 信号触发的序列注册 + persona 匹配消息
|
||||
- 季度重新评估:根据互动情况晋升 Tier 1 或降级 Tier 3
|
||||
|
||||
### Tier 3: Remaining ICP-fit — Automated with Light Personalization
|
||||
|
||||
**目标**:最大化 ICP 覆盖率
|
||||
|
||||
**策略**:
|
||||
- 行业和角色级别序列 + 动态个性化 token
|
||||
- 每账户单一主要联系人
|
||||
- **仅信号触发注册**——无手动出站
|
||||
- 自动互动评分以识别晋升账户
|
||||
|
||||
## Tiering Criteria
|
||||
|
||||
| Criteria | Tier 1 | Tier 2 | Tier 3 |
|
||||
|----------|--------|--------|--------|
|
||||
| ACV 预期 | 最高 | 中 | 低-中 |
|
||||
| 战略契合度 | 完全匹配 | 高匹配 | 基本匹配 |
|
||||
| 联系人数量 | 3-5 | 2-3 | 1 |
|
||||
| 消息定制 | 完全定制 | 行业+账户 | 行业+角色 |
|
||||
| 手动出站 | ✅ | ✅ | ❌ |
|
||||
| 评估频率 | 每周 | 每月 | 每季度 |
|
||||
|
||||
## Tiering Dynamics
|
||||
|
||||
- Tier 1 和 Tier 2 是**手动管理**的
|
||||
- Tier 3 账户通过**自动化**运营
|
||||
- Tier 3 中互动达到阈值的账户自动**晋升**到 Tier 2
|
||||
- Tier 2 中持续无互动的账户降级到 Tier 3
|
||||
|
||||
## Key Metric: Pipeline per Rep
|
||||
|
||||
Tier 1 账户需要更多销售时间,但产生更高 ACV。销售需要深度拥有 50-80 个账户(Tier 1 + Tier 2),而非浅层拥有 500 个账户。
|
||||
|
||||
## Connections
|
||||
|
||||
- [[sales-outbound-strategist]] — 账户分级模型来源
|
||||
- [[ICP (Ideal Customer Profile)]] — 分级依据的匹配度判断
|
||||
- [[Signal-Based Selling Framework]] — 账户触发的信号来源
|
||||
- [[Multi-Channel Sequence Architecture]] — 不同层级对应不同序列深度
|
||||
58
wiki/concepts/Challenger-Sales-Model.md
Normal file
58
wiki/concepts/Challenger-Sales-Model.md
Normal file
@@ -0,0 +1,58 @@
|
||||
---
|
||||
title: "Challenger Sales Model"
|
||||
type: concept
|
||||
tags: ["sales", "methodology", "coaching"]
|
||||
sources: ["sales-coach", "sales-deal-strategist", "sales-outbound-strategist"]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Challenger Sales Model 是由 CEB(现 Gartner)开发的高绩效销售方法论,核心洞察是:**最优秀的销售代表通过商业洞察重新构建买家的思考方式**,而不是简单回应买家的已知需求。
|
||||
|
||||
## Core Principle
|
||||
|
||||
**"Teach, Tailor, Take Control"**
|
||||
|
||||
- **Teach for differentiation**: 通过独特的商业洞察引发买家对问题的重新思考
|
||||
- **Tailor for value**: 根据买家的具体情境定制信息
|
||||
- **Take Control of the sale**: 主动控制销售节奏和对话方向
|
||||
|
||||
## vs Traditional Selling
|
||||
|
||||
| 传统销售 | Challenger 销售 |
|
||||
|---------|----------------|
|
||||
| 倾听买家需求 | **重构**买家对问题的理解 |
|
||||
| 以产品功能回应 | 以商业洞察引领 |
|
||||
| 被动跟随买家节奏 | 主动控制销售过程 |
|
||||
| 提供解决方案 | 创造新的思考框架 |
|
||||
|
||||
## Application in Sales Coaching
|
||||
|
||||
[[sales-coach]] 使用 Challenger 模型作为辅导工具:
|
||||
|
||||
- 教导销售代表"以商业洞察引领对话",而非"回应已知需求"
|
||||
- 核心辅导问题:"你能提供什么买家还不知道的洞察?"
|
||||
- 区分"响应式销售"(买家的思路)和"重构式销售"(改变买家的思路)
|
||||
|
||||
## Key Insight
|
||||
|
||||
买家通常在接触销售之前已经对解决方案有了初步想法。Challenger 销售不是否定买家的想法,而是在买家思考的基础上添加新的维度,让他们以不同的方式看待自己的业务。
|
||||
|
||||
## Deal-Level Application([[sales-deal-strategist]])
|
||||
|
||||
[[sales-deal-strategist]] 将 Challenger 框架延伸为 **Commercial Teaching(商业教学)六步序列**:
|
||||
|
||||
1. **The Warmer**:展示对买方世界的理解,引用行业通用挑战作为信号
|
||||
2. **The Reframe**:引入挑战买方当前假设的洞察,"大多数公司用X方式处理这个问题,但数据显示为什么规模化后会失败"
|
||||
3. **Rational Drowning**:量化现状成本,堆叠证据直到当前方法变得不可持续
|
||||
4. **Emotional Impact**:让痛点个人化。谁每天承受这个痛苦?如果这事没解决,VP 的数字会怎样?
|
||||
5. **A New Way**:提出替代方法——还不是产品,而是方法论
|
||||
6. **Your Solution**:此时才连接到产品。"产品"应感觉像是必然结论而非销售话术
|
||||
|
||||
核心原则:**永远先重构理解,再展示方案**;决策在理性层面被论证,在感性层面被做出。
|
||||
|
||||
## Connections
|
||||
- [[sales-coach]] ← uses ← [[Challenger Sales Model]]
|
||||
- [[sales-deal-strategist]] ← uses ← [[Challenger Sales Model]](Commercial Teaching 六步序列)
|
||||
- [[MEDDPICC]] ← often used alongside ← [[Challenger Sales Model]]
|
||||
60
wiki/concepts/ICP-Ideal-Customer-Profile.md
Normal file
60
wiki/concepts/ICP-Ideal-Customer-Profile.md
Normal file
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: "ICP (Ideal Customer Profile)"
|
||||
type: concept
|
||||
tags: [sales, outbound, targeting]
|
||||
sources: [sales-outbound-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
ICP 是可证伪的理想客户画像——一个能够**明确排除**不符合条件的公司的定义,而非泛泛的目标市场总地址(TAM)。
|
||||
|
||||
> "如果你的 ICP 不能排除任何公司,它就不是 ICP,而是 TAM 幻灯片。"
|
||||
|
||||
## ICP 三层结构
|
||||
|
||||
### 1. Firmographic Filters(公司特征)
|
||||
```
|
||||
- 行业垂直(2-4 个具体行业,而非"企业")
|
||||
- 收入范围或员工规模区间
|
||||
- 地理区域(如与 go-to-market 相关)
|
||||
- 技术栈要求(他们必须已经使用什么?)
|
||||
```
|
||||
|
||||
### 2. Behavioral Qualifiers(行为限定)
|
||||
```
|
||||
- 什么业务事件使他们成为"现在的买家"?
|
||||
- 你的产品解决的痛点是什么,他们无法忽视?
|
||||
- 组织内部谁最强烈地感受这个痛点?
|
||||
- 他们当前的替代方案是什么?
|
||||
```
|
||||
|
||||
### 3. Disqualifiers(排除条件)——同等重要
|
||||
```
|
||||
- 什么样的账户看起来很好但永远不会成交?
|
||||
- 哪些行业或细分市场你的赢率低于 15%?
|
||||
- 哪些公司阶段你的产品还为时过早或过于复杂?
|
||||
```
|
||||
|
||||
## Why Disqualifiers Matter
|
||||
|
||||
大多数销售团队只定义"谁是我的目标",但:
|
||||
- 错误客户消耗最多资源
|
||||
- 错误客户有最低赢率和最高流失率
|
||||
- 明确的排除条件节省销售时间用于正确客户
|
||||
|
||||
## ICP vs TAM
|
||||
|
||||
| | ICP | TAM |
|
||||
|--|-----|-----|
|
||||
| 目的 | 指导销售执行和资源配置 | 投资者/管理层展示市场规模 |
|
||||
| 可证伪性 | ✅ 必须能排除公司 | ❌ 通常是"越大越好" |
|
||||
| 销售使用 | 日常决策(路由、优先排序) | 年度汇报 |
|
||||
|
||||
## Connections
|
||||
|
||||
- [[sales-outbound-strategist]] — ICP 框架来源
|
||||
- [[Signal-Based Selling Framework]] — ICP 定义触发信号路由
|
||||
- [[Account Tiering Model]] — ICP 匹配决定账户层级
|
||||
- [[Land-and-Expand]] — ICP 内现有客户的扩张策略
|
||||
48
wiki/concepts/Land-and-Expand.md
Normal file
48
wiki/concepts/Land-and-Expand.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: "Land-and-Expand"
|
||||
type: concept
|
||||
tags: []
|
||||
sources: [sales-account-strategist, sales-outbound-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Land-and-Expand 是一种 SaaS/企业软件公司的核心增长策略,指在赢得初始合同(land deal)后,通过系统性方法将单点解决方案逐步扩展为企业级平台关系,最大化每个客户账户的收入潜力。
|
||||
|
||||
## Core Principles
|
||||
|
||||
### The Land Phase
|
||||
- 以低风险切入点进入客户组织——通常是一个部门、一个用例或一个产品模块
|
||||
- 目标是建立可衡量的成功证据(ROI 数据、用户数、效率提升)
|
||||
- 目标是培养至少一个内部冠军(champion)来推动内部推广
|
||||
|
||||
### The Expand Phase
|
||||
- 基于已验证的成功,向相邻用例、额外用户、新产品模块扩展
|
||||
- 时机信号:容量使用率 >80%、特征采纳速度加快、部门级使用不对称
|
||||
- 永远在客户成功之后才推扩张——在尚未成功的账户上销售更多会加速流失
|
||||
|
||||
## Key Metrics
|
||||
|
||||
| Metric | Description | Target |
|
||||
|--------|-------------|--------|
|
||||
| NRR (Net Revenue Retention) | 扩张收入 - 流失收入 - 收缩收入 | >100%,优秀 >120% |
|
||||
| Expansion Ratio | 扩张收入 / 总 ARR | >1.2x |
|
||||
| Time to Expand | 首次成交到首次扩张的时间 | <12 个月 |
|
||||
| Land Deal Size | 初始合同规模 | 因细分市场而异 |
|
||||
|
||||
## Signals for Expansion
|
||||
|
||||
每个扩张信号必须同时具备三个维度:
|
||||
1. **信号(Signal)**:使用率上升、用户增长、特征采纳
|
||||
2. **情境(Context)**:为什么发生?业务背景是什么?
|
||||
3. **时机(Timing)**:为什么是现在?客户即将做出什么决策?
|
||||
4. **利益相关者对齐(Stakeholder Alignment)**:谁关心这个机会?
|
||||
|
||||
**没有同时满足四个维度的,只能算"观察",不是"机会"。**
|
||||
|
||||
## Connection
|
||||
- [[Net Revenue Retention (NRR)]] — Land-and-Expand 的终极目标是最大化 NRR
|
||||
- [[Account Strategist Agent]] — 执行 Land-and-Expand 的核心角色
|
||||
- [[sales-account-strategist]]
|
||||
- [[Churn Prevention Playbook]] — Land-and-Expand 的对立面是流失,两者都需要积极管理
|
||||
88
wiki/concepts/Multi-Channel-Sequence-Architecture.md
Normal file
88
wiki/concepts/Multi-Channel-Sequence-Architecture.md
Normal file
@@ -0,0 +1,88 @@
|
||||
---
|
||||
title: "Multi-Channel Sequence Architecture"
|
||||
type: concept
|
||||
tags: [sales, outbound, engagement]
|
||||
sources: [sales-outbound-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
多渠道触达序列架构——在 3-4 周内通过 8-12 次触点跨越多个渠道(Email/LinkedIn/Phone/Video)的出站序列,每次触达必须提供新的价值角度。
|
||||
|
||||
> "Each touch must add a new value angle. Repeating the same ask with different words is not a sequence — it is nagging."
|
||||
|
||||
## Core Architecture
|
||||
|
||||
**结构:8-12 次触点 / 3-4 周 / 多渠道变化**
|
||||
|
||||
每次触点必须:
|
||||
1. 使用不同渠道
|
||||
2. 提供新的信息角度
|
||||
3. 包含一个软性 CTA(永远不重复同样诉求)
|
||||
|
||||
## Channel Selection by Persona
|
||||
|
||||
| Persona | Primary | Secondary | Tertiary |
|
||||
|---------|---------|-----------|----------|
|
||||
| C-Suite | LinkedIn InMail | Warm intro/referral | Short direct email |
|
||||
| VP-level | Email | LinkedIn | Phone |
|
||||
| Director | Email | Phone | LinkedIn |
|
||||
| Manager/IC | Email | LinkedIn | Video (Loom) |
|
||||
| Technical buyers | Email (technical content) | Community/Slack | LinkedIn |
|
||||
|
||||
## Reference Sequence Template (10 Touches)
|
||||
|
||||
```
|
||||
Touch 1 (Day 1, Email): Signal-based opening + specific value prop + soft CTA
|
||||
Touch 2 (Day 3, LinkedIn): Connection request with personalized note (no pitch)
|
||||
Touch 3 (Day 5, Email): Share relevant insight/data point tied to their situation
|
||||
Touch 4 (Day 8, Phone): Call with voicemail drop referencing email thread
|
||||
Touch 5 (Day 10, LinkedIn): Engage with their content or share relevant content
|
||||
Touch 6 (Day 14, Email): Case study from similar company/situation + clear CTA
|
||||
Touch 7 (Day 17, Video): 60-second personalized Loom showing something specific to them
|
||||
Touch 8 (Day 21, Email): New angle — different pain point or stakeholder perspective
|
||||
Touch 9 (Day 24, Phone): Final call attempt
|
||||
Touch 10 (Day 28, Email): Breakup email — honest, brief, leave the door open
|
||||
```
|
||||
|
||||
## Cold Email Anatomy
|
||||
|
||||
### Subject Line
|
||||
- 3-5 words, lowercase, looks like internal email
|
||||
- Reference signal or specificity: "re: the new data team"
|
||||
- Never clickbait, never ALL CAPS, never emoji
|
||||
|
||||
### Opening Line (Signal-Based)
|
||||
```
|
||||
Bad: "I hope this email finds you well."
|
||||
Bad: "I'm reaching out because [company] helps companies like yours..."
|
||||
Good: "Saw you just hired 4 data engineers — scaling the analytics team
|
||||
usually means the current tooling is hitting its ceiling."
|
||||
```
|
||||
|
||||
### Value Proposition
|
||||
- One sentence connecting their situation to an outcome they care about
|
||||
- Use their vocabulary, not your marketing copy
|
||||
- Specificity beats cleverness: numbers, timeframes, concrete outcomes
|
||||
|
||||
### CTA (Single, Clear, Low Friction)
|
||||
```
|
||||
Bad: "Would love to set up a 30-minute call to walk you through a demo"
|
||||
Good: "Worth a 15-minute conversation to see if this applies to your team?"
|
||||
Good: "Open to hearing how [similar company] handled this?"
|
||||
```
|
||||
|
||||
## Rules of Sequence Design
|
||||
|
||||
1. **Never send without a reason the buyer should care right now**
|
||||
2. **If you cannot articulate why you are contacting this specific person at this specific company at this specific moment, you are not ready to send**
|
||||
3. **Do not automate what should be personal, and do not personalize what should be automated**
|
||||
4. **Test one variable at a time** — changing subject + opening + CTA simultaneously learns nothing
|
||||
5. **Document what works** — a playbook that lives in one rep's head is not a playbook
|
||||
|
||||
## Connections
|
||||
|
||||
- [[sales-outbound-strategist]] — 序列架构来源
|
||||
- [[Signal-Based Selling Framework]] — 序列触发信号来源
|
||||
- [[Account Tiering Model]] — 不同层级账户的序列定制程度不同
|
||||
49
wiki/concepts/Signal-Based-Selling-Framework.md
Normal file
49
wiki/concepts/Signal-Based-Selling-Framework.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: "Signal-Based Selling Framework"
|
||||
type: concept
|
||||
tags: [sales, outbound, intent-data]
|
||||
sources: [sales-outbound-strategist]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
信号驱动型销售框架——出站销售由买家行为信号触发,而非销售配额或时间表驱动。相比无触发的批量冷出站,信号驱动的出站转化率高出 **4-8 倍**。
|
||||
|
||||
## Core Principle
|
||||
|
||||
> "Outreach should be triggered by evidence, not quotas."
|
||||
|
||||
出站序列应在买家信号最强烈的时刻启动,而非按照固定日历或活动目标。
|
||||
|
||||
## Signal Tiers
|
||||
|
||||
| Tier | Type | Intent Strength | Examples |
|
||||
|------|------|----------------|----------|
|
||||
| **Tier 1** | Active Buying Signals | 最高 | G2/定价页访问、竞品对比搜索、RFP公告、招聘特定技术 |
|
||||
| **Tier 2** | Organizational Change | 高 | 领导层变动、融资事件(B轮+增长目标)、部门招聘激增、M&A活动 |
|
||||
| **Tier 3** | Technographic & Behavioral | 中 | 技术栈变化、会议出席/演讲、内容下载/网络研讨会参与、竞品合同续约时间 |
|
||||
|
||||
## Speed-to-Signal
|
||||
|
||||
信号半衰期极短:
|
||||
- **< 30 分钟**:信号新鲜,必须立即路由到正确销售
|
||||
- **24 小时后**:信号失效
|
||||
- **72 小时后**:竞争对手已成交
|
||||
|
||||
路由规则必须匹配信号类型 → 销售专业领域 → 区域,不允许信号在共享队列中等待。
|
||||
|
||||
## Reply Rate Benchmarks
|
||||
|
||||
| Outreach Type | Reply Rate |
|
||||
|---------------|-----------|
|
||||
| 泛化型(无定向) | 1-3% |
|
||||
| 角色/行业定制 | 5-8% |
|
||||
| **信号驱动 + 账户研究** | **12-25%** |
|
||||
| 推荐/引入型 | 30-50% |
|
||||
|
||||
## Connections
|
||||
|
||||
- [[sales-outbound-strategist]] — 框架来源
|
||||
- [[ICP (Ideal Customer Profile)]] — 信号触发的目标定义
|
||||
- [[Account Tiering Model]] — 信号的接收方账户分层处理
|
||||
@@ -4,6 +4,15 @@
|
||||
- [Overview](overview.md) — living synthesis
|
||||
|
||||
## Sources
|
||||
- [2026-04-25] [Outbound Strategist Agent](sources/sales-outbound-strategist.md)
|
||||
- [2026-04-24] [Deal Strategist Agent](sources/sales-deal-strategist.md)
|
||||
- [2026-04-24] [Account Strategist Agent](sources/sales-account-strategist.md)
|
||||
- [2026-04-24] [Sales Proposal Strategist](sources/sales-proposal-strategist.md)
|
||||
- [2026-04-24] [Sales Coach Agent](sources/sales-coach.md)
|
||||
- [2026-04-24] [Discovery Coach Agent](sources/sales-discovery-coach.md)
|
||||
- [2026-04-24] [Paid Media Tracking & Measurement Specialist Agent](sources/paid-media-tracking-specialist.md)
|
||||
- [2026-04-24] [Paid Media Ad Creative Strategist Agent](sources/paid-media-creative-strategist.md)
|
||||
- [2026-04-24] [Paid Social Strategist](sources/paid-media-paid-social-strategist.md)
|
||||
- [2026-04-24] [Paid Media Search Query Analyst Agent](sources/paid-media-search-query-analyst.md)
|
||||
- [2026-04-24] [Paid Media Auditor Agent](sources/paid-media-auditor.md)
|
||||
- [2026-04-24] [Paid Media PPC Campaign Strategist Agent](sources/paid-media-ppc-strategist.md)
|
||||
@@ -379,7 +388,6 @@
|
||||
- [2026-04-20] [corporate-training-designer](sources/corporate-training-designer.md) — (expected: wiki/sources/corporate-training-designer.md — source missing)
|
||||
- [2026-04-20] [specialized-civil-engineer](sources/specialized-civil-engineer.md) — (expected: wiki/sources/specialized-civil-engineer.md — source missing)
|
||||
- [2026-04-20] [project-management-experiment-tracker](sources/project-management-experiment-tracker.md) — (expected: wiki/sources/project-management-experiment-tracker.md — source missing)
|
||||
- [2026-04-20] [paid-media-paid-social-strategist](sources/paid-media-paid-social-strategist.md) — (expected: wiki/sources/paid-media-paid-social-strategist.md — source missing)
|
||||
- [2026-04-20] [automation-governance-architect](sources/automation-governance-architect.md) — (expected: wiki/sources/automation-governance-architect.md — source missing)
|
||||
- [2026-04-20] [project-manager-senior](sources/project-manager-senior.md) — (expected: wiki/sources/project-manager-senior.md — source missing)
|
||||
- [2026-04-20] [project-management-jira-workflow-steward](sources/project-management-jira-workflow-steward.md) — (expected: wiki/sources/project-management-jira-workflow-steward.md — source missing)
|
||||
@@ -395,20 +403,13 @@
|
||||
- [2026-04-20] [specialized-model-qa](sources/specialized-model-qa.md) — (expected: wiki/sources/specialized-model-qa.md — source missing)
|
||||
- [2026-04-20] [sales-pipeline-analyst](sources/sales-pipeline-analyst.md) — (expected: wiki/sources/sales-pipeline-analyst.md — source missing)
|
||||
- [2026-04-20] [sales-outbound-strategist](sources/sales-outbound-strategist.md) — (expected: wiki/sources/sales-outbound-strategist.md — source missing)
|
||||
- [2026-04-20] [sales-deal-strategist](sources/sales-deal-strategist.md) — (expected: wiki/sources/sales-deal-strategist.md — source missing)
|
||||
- [2026-04-20] [specialized-cultural-intelligence-strategist](sources/specialized-cultural-intelligence-strategist.md) — (expected: wiki/sources/specialized-cultural-intelligence-strategist.md — source missing)
|
||||
- [2026-04-20] [sales-account-strategist](sources/sales-account-strategist.md) — (expected: wiki/sources/sales-account-strategist.md — source missing)
|
||||
- [2026-04-20] [sales-proposal-strategist](sources/sales-proposal-strategist.md) — (expected: wiki/sources/sales-proposal-strategist.md — source missing)
|
||||
- [2026-04-20] [healthcare-marketing-compliance](sources/healthcare-marketing-compliance.md) — (expected: wiki/sources/healthcare-marketing-compliance.md — source missing)
|
||||
- [2026-04-20] [llm-wiki](sources/llm-wiki.md) — (expected: wiki/sources/llm-wiki.md — source missing)
|
||||
- [2026-04-20] [sales-coach](sources/sales-coach.md) — (expected: wiki/sources/sales-coach.md — source missing)
|
||||
- [2026-04-20] [specialized-workflow-architect](sources/specialized-workflow-architect.md) — (expected: wiki/sources/specialized-workflow-architect.md — source missing)
|
||||
- [2026-04-20] [sales-discovery-coach](sources/sales-discovery-coach.md) — (expected: wiki/sources/sales-discovery-coach.md — source missing)
|
||||
- [2026-04-20] [government-digital-presales-consultant](sources/government-digital-presales-consultant.md) — (expected: wiki/sources/government-digital-presales-consultant.md — source missing)
|
||||
- [2026-04-20] [paid-media-tracking-specialist](sources/paid-media-tracking-specialist.md) — (expected: wiki/sources/paid-media-tracking-specialist.md — source missing)
|
||||
- [2026-04-20] [agentic-identity-trust](sources/agentic-identity-trust.md) — (expected: wiki/sources/agentic-identity-trust.md — source missing)
|
||||
- [2026-04-20] [specialized-document-generator](sources/specialized-document-generator.md) — (expected: wiki/sources/specialized-document-generator.md — source missing)
|
||||
- [2026-04-20] [paid-media-creative-strategist](sources/paid-media-creative-strategist.md) — (expected: wiki/sources/paid-media-creative-strategist.md — source missing)
|
||||
- [2026-04-20] [identity-graph-operator](sources/identity-graph-operator.md) — (expected: wiki/sources/identity-graph-operator.md — source missing)
|
||||
- [2026-04-20] [accounts-payable-agent](sources/accounts-payable-agent.md) — (expected: wiki/sources/accounts-payable-agent.md — source missing)
|
||||
- [2026-04-20] [recruitment-specialist](sources/recruitment-specialist.md) — (expected: wiki/sources/recruitment-specialist.md — source missing)
|
||||
@@ -661,6 +662,7 @@
|
||||
- [LaunchDarkly](entities/LaunchDarkly.md)
|
||||
- [LeonardoDaVinci](entities/LeonardoDaVinci.md)
|
||||
- [Linear](entities/Linear.md)
|
||||
- [LinkedIn-Campaign-Manager](entities/LinkedIn-Campaign-Manager.md)
|
||||
- [LinuxServer.io](entities/LinuxServer.io.md)
|
||||
- [Mac-Mini-M4](entities/Mac-Mini-M4.md)
|
||||
- [Manus](entities/Manus.md)
|
||||
@@ -670,6 +672,7 @@
|
||||
- [Mem0](entities/Mem0.md)
|
||||
- [Memsearch](entities/Memsearch.md)
|
||||
- [MerlinClash插件](entities/MerlinClash插件.md)
|
||||
- [Meta-Ads-Manager](entities/Meta-Ads-Manager.md)
|
||||
- [Micro-Focus](entities/Micro-Focus.md)
|
||||
- [Micro-Focus-IGA](entities/Micro-Focus-IGA.md)
|
||||
- [Microsoft-Planner](entities/Microsoft-Planner.md)
|
||||
@@ -742,6 +745,7 @@
|
||||
- [Terraform](entities/Terraform.md)
|
||||
- [Terragrunt](entities/Terragrunt.md)
|
||||
- [Tiago-Forte](entities/Tiago-Forte.md)
|
||||
- [TikTok-Ads](entities/TikTok-Ads.md)
|
||||
- [tini](entities/tini.md)
|
||||
- [Todoist](entities/Todoist.md)
|
||||
- [Trae](entities/Trae.md)
|
||||
@@ -773,10 +777,16 @@
|
||||
## Concepts
|
||||
- [14种UML图](concepts/14种UML图.md)
|
||||
- [7种视觉风格系统](concepts/7种视觉风格系统.md)
|
||||
- [ABTesting](concepts/ABTesting.md)
|
||||
- [Account-Health-Score](concepts/Account-Health-Score.md)
|
||||
- [Account-Tiering-Model](concepts/Account-Tiering-Model.md)
|
||||
- [AccountArchitecture](concepts/AccountArchitecture.md)
|
||||
- [ActionItemTracking](concepts/ActionItemTracking.md)
|
||||
- [Active-Accountability](concepts/Active-Accountability.md)
|
||||
- [Adaptive-Tone](concepts/Adaptive-Tone.md)
|
||||
- [AdExtensions](concepts/AdExtensions.md)
|
||||
- [AdStrength](concepts/AdStrength.md)
|
||||
- [Advantage+-Campaigns](concepts/Advantage+-Campaigns.md)
|
||||
- [Adversarial-Debate-Pattern](concepts/Adversarial-Debate-Pattern.md)
|
||||
- [Agent-Build-Gate](concepts/Agent-Build-Gate.md)
|
||||
- [Agent-Design-Principles](concepts/Agent-Design-Principles.md)
|
||||
@@ -842,6 +852,7 @@
|
||||
- [Centralized-Logging](concepts/Centralized-Logging.md)
|
||||
- [CEOPattern](concepts/CEOPattern.md)
|
||||
- [Chained Agents](concepts/Chained Agents.md)
|
||||
- [Challenger-Sales-Model](concepts/Challenger-Sales-Model.md)
|
||||
- [Change-Failure-Rate](concepts/Change-Failure-Rate.md)
|
||||
- [Change-Management](concepts/Change-Management.md)
|
||||
- [Channel-Based-Monitoring](concepts/Channel-Based-Monitoring.md)
|
||||
@@ -885,15 +896,18 @@
|
||||
- [Continuous-Deployment](concepts/Continuous-Deployment.md)
|
||||
- [Continuous-Integration](concepts/Continuous-Integration.md)
|
||||
- [Conversational-Interface](concepts/Conversational-Interface.md)
|
||||
- [Conversions-API](concepts/Conversions-API.md)
|
||||
- [Cost-Optimization](concepts/Cost-Optimization.md)
|
||||
- [CoworkWorkspace](concepts/CoworkWorkspace.md)
|
||||
- [Coze-Workflow](concepts/Coze-Workflow.md)
|
||||
- [CreativeFatigue](concepts/CreativeFatigue.md)
|
||||
- [Credential-Isolation](concepts/Credential-Isolation.md)
|
||||
- [Credit-Efficient-Processing](concepts/Credit-Efficient-Processing.md)
|
||||
- [Cron定时任务](concepts/Cron定时任务.md)
|
||||
- [Cross-Account-Monitoring](concepts/Cross-Account-Monitoring.md)
|
||||
- [Cross-account-Terraform-Modules](concepts/Cross-account-Terraform-Modules.md)
|
||||
- [Cumulative-Memory](concepts/Cumulative-Memory.md)
|
||||
- [Custom-Audience-Engineering](concepts/Custom-Audience-Engineering.md)
|
||||
- [Custom-Instructions](concepts/Custom-Instructions.md)
|
||||
- [Daily-Digest](concepts/Daily-Digest.md)
|
||||
- [DAST](concepts/DAST.md)
|
||||
@@ -957,6 +971,7 @@
|
||||
- [Fixed-Point-Semantics](concepts/Fixed-Point-Semantics.md)
|
||||
- [Food-Sensitivity-Tracking](concepts/Food-Sensitivity-Tracking.md)
|
||||
- [Full-Draft-Generation](concepts/Full-Draft-Generation.md)
|
||||
- [Full-Funnel-Campaign-Architecture](concepts/Full-Funnel-Campaign-Architecture.md)
|
||||
- [Gatekeeper](concepts/Gatekeeper.md)
|
||||
- [GDM3](concepts/GDM3.md)
|
||||
- [Generalist](concepts/Generalist.md)
|
||||
@@ -975,6 +990,7 @@
|
||||
- [Hidden-Failure-Paths](concepts/Hidden-Failure-Paths.md)
|
||||
- [Hierarchy-Agent-Pattern](concepts/Hierarchy-Agent-Pattern.md)
|
||||
- [high-availability](concepts/high-availability.md)
|
||||
- [HookBodyCTA](concepts/HookBodyCTA.md)
|
||||
- [HouseholdInventoryTracking](concepts/HouseholdInventoryTracking.md)
|
||||
- [HTTPS自动化证书](concepts/HTTPS自动化证书.md)
|
||||
- [Human-Handoff](concepts/Human-Handoff.md)
|
||||
@@ -983,6 +999,7 @@
|
||||
- [HybridDnsResolution](concepts/HybridDnsResolution.md)
|
||||
- [Hyperautomation](concepts/Hyperautomation.md)
|
||||
- [IAST](concepts/IAST.md)
|
||||
- [ICP (Ideal Customer Profile)](concepts/ICP-Ideal-Customer-Profile.md)
|
||||
- [Idea-Density](concepts/Idea-Density.md)
|
||||
- [Idea-Museum](concepts/Idea-Museum.md)
|
||||
- [Identity-Governance](concepts/Identity-Governance.md)
|
||||
@@ -992,6 +1009,7 @@
|
||||
- [Immutable-Root-Filesystem](concepts/Immutable-Root-Filesystem.md)
|
||||
- [Incident-Management](concepts/Incident-Management.md)
|
||||
- [InclusiveVisuals](concepts/InclusiveVisuals.md)
|
||||
- [Incrementality-Testing](concepts/Incrementality-Testing.md)
|
||||
- [Indexing](concepts/Indexing.md)
|
||||
- [Infrastructure-as-Code](concepts/Infrastructure-as-Code.md)
|
||||
- [Intent-Classification](concepts/Intent-Classification.md)
|
||||
@@ -1008,6 +1026,7 @@
|
||||
- [Knock-out-Pattern](concepts/Knock-out-Pattern.md)
|
||||
- [Knowledge-Base-RAG](concepts/Knowledge-Base-RAG.md)
|
||||
- [Kubernetes](concepts/Kubernetes.md)
|
||||
- [Land-and-Expand](concepts/Land-and-Expand.md)
|
||||
- [Landing-Zone-Architecture](concepts/Landing-Zone-Architecture.md)
|
||||
- [LangChain](concepts/LangChain.md)
|
||||
- [Language-Detection](concepts/Language-Detection.md)
|
||||
@@ -1027,9 +1046,12 @@
|
||||
- [Log-Driven-Debugging](concepts/Log-Driven-Debugging.md)
|
||||
- [Management-Pack](concepts/Management-Pack.md)
|
||||
- [MCPOnceAllAgents](concepts/MCPOnceAllAgents.md)
|
||||
- [MEDDPICC](concepts/MEDDPICC.md)
|
||||
- [MeetingNotes](concepts/MeetingNotes.md)
|
||||
- [Memory-Backend](concepts/Memory-Backend.md)
|
||||
- [MEMORY.md](concepts/MEMORY.md.md)
|
||||
- [MessageMatch](concepts/MessageMatch.md)
|
||||
- [Multi-Channel-Sequence-Architecture](concepts/Multi-Channel-Sequence-Architecture.md)
|
||||
- [Micro-Recovery](concepts/Micro-Recovery.md)
|
||||
- [Model-Context-Protocol](concepts/Model-Context-Protocol.md)
|
||||
- [Model-Fallback](concepts/Model-Fallback.md)
|
||||
@@ -1048,6 +1070,7 @@
|
||||
- [Multi-Tenancy](concepts/Multi-Tenancy.md)
|
||||
- [nas套件管理](concepts/nas套件管理.md)
|
||||
- [NegativePromptingLibrary](concepts/NegativePromptingLibrary.md)
|
||||
- [Net-Revenue-Retention](concepts/Net-Revenue-Retention.md)
|
||||
- [NFS网络备份](concepts/NFS网络备份.md)
|
||||
- [Nitro-System](concepts/Nitro-System.md)
|
||||
- [Normal-Change](concepts/Normal-Change.md)
|
||||
@@ -1069,6 +1092,7 @@
|
||||
- [PerformanceMax](concepts/PerformanceMax.md)
|
||||
- [Personal-CRM](concepts/Personal-CRM.md)
|
||||
- [Personalization](concepts/Personalization.md)
|
||||
- [PersuasionArchitecture](concepts/PersuasionArchitecture.md)
|
||||
- [Pipeline](concepts/Pipeline.md)
|
||||
- [Pivot-Strategy](concepts/Pivot-Strategy.md)
|
||||
- [Plan-Mode](concepts/Plan-Mode.md)
|
||||
@@ -1108,6 +1132,7 @@
|
||||
- [RemoteDevelopment](concepts/RemoteDevelopment.md)
|
||||
- [RemoteRescuePattern](concepts/RemoteRescuePattern.md)
|
||||
- [Renovate-Bot](concepts/Renovate-Bot.md)
|
||||
- [ResponsiveSearchAds](concepts/ResponsiveSearchAds.md)
|
||||
- [Retrieval](concepts/Retrieval.md)
|
||||
- [Reviewer](concepts/Reviewer.md)
|
||||
- [Rightsizing](concepts/Rightsizing.md)
|
||||
@@ -1141,6 +1166,7 @@
|
||||
- [Self-Interest](concepts/Self-Interest.md)
|
||||
- [Self-Referential-Computation](concepts/Self-Referential-Computation.md)
|
||||
- [Self-Sufficiency](concepts/Self-Sufficiency.md)
|
||||
- [Signal-Based-Selling-Framework](concepts/Signal-Based-Selling-Framework.md)
|
||||
- [Semantic-Deduplication](concepts/Semantic-Deduplication.md)
|
||||
- [Semantic-Search](concepts/Semantic-Search.md)
|
||||
- [Semantic-Versioning](concepts/Semantic-Versioning.md)
|
||||
@@ -1154,6 +1180,7 @@
|
||||
- [Shift-Left-Security](concepts/Shift-Left-Security.md)
|
||||
- [Shift-Right-Security](concepts/Shift-Right-Security.md)
|
||||
- [Single-Control-Plane](concepts/Single-Control-Plane.md)
|
||||
- [SKAdNetwork](concepts/SKAdNetwork.md)
|
||||
- [SmartBidding](concepts/SmartBidding.md)
|
||||
- [SnapMirror](concepts/SnapMirror.md)
|
||||
- [Social-Media-Monitoring](concepts/Social-Media-Monitoring.md)
|
||||
@@ -1189,6 +1216,7 @@
|
||||
- [Test-Mode](concepts/Test-Mode.md)
|
||||
- [Text-and-Search](concepts/Text-and-Search.md)
|
||||
- [Threat-Modeling](concepts/Threat-Modeling.md)
|
||||
- [ThreeActProposalNarrative](concepts/ThreeActProposalNarrative.md)
|
||||
- [TieredCampaignArchitecture](concepts/TieredCampaignArchitecture.md)
|
||||
- [Time-to-Market](concepts/Time-to-Market.md)
|
||||
- [Todoist-API](concepts/Todoist-API.md)
|
||||
@@ -1227,6 +1255,7 @@
|
||||
- [WEBHOOK_URL](concepts/WEBHOOK_URL.md)
|
||||
- [Weekly-Pattern-Analysis](concepts/Weekly-Pattern-Analysis.md)
|
||||
- [What-If-Simulation](concepts/What-If-Simulation.md)
|
||||
- [WinThemes](concepts/WinThemes.md)
|
||||
- [Workflow-Engineering](concepts/Workflow-Engineering.md)
|
||||
- [Workspace](concepts/Workspace.md)
|
||||
- [X11](concepts/X11.md)
|
||||
|
||||
86
wiki/log.md
86
wiki/log.md
@@ -1,3 +1,75 @@
|
||||
## [2026-04-25] ingest | Outbound Strategist Agent
|
||||
- Source file: Agent/agency-agents/sales/sales-outbound-strategist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Outbound Strategist Agent——信号型出站销售策略师,将出站从"批量轰炸"转变为"精准触发"。核心理念:信号驱动出站转化率比无触发出站高 4-8 倍;信号半衰期 30 分钟,24 小时后失效,72 小时后竞争对手已成交。核心框架:三层信号分级体系(主动购买/组织变化/技术行为)+ 可证伪 ICP 定义 + 三层账户分级(Tier 1 深度多线程 / Tier 2 半个性化 / Tier 3 自动化轻定制)+ 8-12 触点 3-4 周多渠道序列。冷邮件回复率基准:泛化 1-3%、角色定制 5-8%、信号驱动 12-25%、推荐引入 30-50%。SDR 角色演变:从批量操作员 → 深度账户专家。
|
||||
- Concepts created: [[Signal-Based-Selling-Framework]], [[ICP (Ideal Customer Profile)]], [[Multi-Channel-Sequence-Architecture]], [[Account-Tiering-Model]]
|
||||
- Concepts updated: [[Challenger-Sales-Model]](sources 添加 sales-outbound-strategist)、[[Land-and-Expand]](sources 添加 sales-outbound-strategist)
|
||||
- Entities linked: Outbound Strategist Agent, SDR
|
||||
- Source page: wiki/sources/sales-outbound-strategist.md
|
||||
- Notes: overview.md 新增"### Sales Outbound Methodology"章节(位于 Sales Discovery Methodology 之前);index.md Concepts 节新增 4 个概念条目;Entity 页面未创建(Outbound Strategist Agent 和 SDR 均仅出现 1 次,不足独立建页阈值);与 [[sales-deal-strategist]] 的漏斗互补关系已记录(出站=漏斗顶部,Deal=漏斗中部)
|
||||
|
||||
## [2026-04-25] ingest | Deal Strategist Agent
|
||||
- Source file: Agent/agency-agents/sales/sales-deal-strategist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Deal Strategist Agent——高级deal策略师与管线架构师智能体,专注于MEDDPICC资质评分、竞争定位和复杂B2B销售周期的赢单规划。核心理念:每个deal都是战略问题而非关系练习;MEDDPICC全面推行的组织赢率提升18%、deal规模扩大24%;Commit deals预测准确率85%+;Qualified Pipeline(28/40+)赢率35%+;永远不做单线程账户。核心框架:MEDDPICC八维评分(每维度5分,满分40)+ Challenger商业教学六步序列 + 竞争三区定位(Winning/Battling/Losing)+ 地雷问题布局 + 交易检查方法论。
|
||||
- Concepts updated: [[MEDDPICC]](新增 Deal-Level Application 和 Deal Verdict Categories)、[[Challenger Sales Model]](新增 Commercial Teaching 六步序列)
|
||||
- Entities linked: [[Sales Coach Agent]], [[Discovery Coach Agent]], [[Sales Proposal Strategist]], Deal Strategist Agent(均出现1次,不足独立Entity建页阈值)
|
||||
- Source page: wiki/sources/sales-deal-strategist.md
|
||||
- Notes: index.md 已替换占位符条目(2026-04-20 → 2026-04-25);overview.md 已新增独立段落(Sales Coaching Methodology 章节末尾);MEDDPICC 和 Challenger Sales Model 两个 Concept 页面均已更新 sources 列表 + 新增 sales-deal-strategist 专属内容;未创建新 Entity/Concept 页面(Deal Scoring/Competitive Positioning/Win Planning 等概念在 sales-deal-strategist 源文档中均仅出现1次,不足独立建页阈值);与 [[sales-discovery-coach]] 的"发现→策略"协同关系已记录;与 [[sales-proposal-strategist]] 在"策略分析 vs 叙事构建"上的互补关系已记录于 Contradictions
|
||||
|
||||
## [2026-04-25] ingest | Account Strategist Agent
|
||||
- Source file: Agent/agency-agents/sales/sales-account-strategist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Account Strategist Agent——售后账户扩张策略师智能体,专门负责 Land-and-Expand 执行、QBR 设计、利益相关者映射和净收入留存(NRR)最大化。核心理念:最佳销售时机是客户成功时;永远不做单线程账户;NRR 是终极指标。核心框架:扩张信号四维度(信号+情境+时机+利益相关者对齐)、账户健康三色评分(绿扩张/黄稳定/红救流失)、多线程关系建设(每账户至少三条独立关系线)。
|
||||
- Concepts created: [[Land-and-Expand]], [[Net Revenue Retention (NRR)]], [[Account Health Score]]
|
||||
- Entities linked: Account Executive (AE), Customer Success (CS), Product Team, Executive Sponsor
|
||||
- Source page: wiki/sources/sales-account-strategist.md
|
||||
- Notes: 与 [[sales-proposal-strategist]] 的"赢单叙事"互补(前者构建叙事,后者交付超越叙事);与 [[sales-coach]] 协同(后者辅导卖方,前者辅导买方冠军);与 [[sales-discovery-coach]] 形成完整销售生命周期覆盖(发现→赢单→扩张);overview.md 新增"Sales Account Expansion Methodology"主题节;创建 3 个独立 Concept 页面(Land-and-Expand、NRR、Account Health Score)
|
||||
|
||||
## [2026-04-25] ingest | Sales Proposal Strategist
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Sales Proposal Strategist——将 RFP 响应转化为赢单叙事的系统化提案方法论。核心框架:三幕提案叙事结构(理解挑战→解决方案旅程→转变状态)+ 3-5 个赢标主题矩阵 + 执行摘要五步模板 + 说服架构(首因/近因效应、认知负荷管理、社会认同排序、损失厌恶框架)。核心理念:提案在开篇100词决定胜负;叙事是差异化核心;永远不直接批评竞争对手;定价在价值之后;内容库按赢标主题而非章节组织。
|
||||
- Concepts created: [[WinThemes]], [[ThreeActProposalNarrative]], [[PersuasionArchitecture]]
|
||||
- Entities linked: 无特定命名实体
|
||||
- Source page: wiki/sources/sales-proposal-strategist.md
|
||||
- Notes: 与 [[sales-coach]] 在"辅导行为 vs 撰写结构"上形成 Sales 体系互补关系;与 [[sales-discovery-coach]] 的发现阶段输入为提案策略提供买方情境;无冲突发现;overview.md 暂不需要更新
|
||||
|
||||
## [2026-04-25] ingest | Sales Coach Agent
|
||||
- Source file: Agent/agency-agents/sales/sales-coach.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Sales Coach Agent——AI 销售教练 Agent,通过苏格拉底式提问驱动销售代表成长。核心辅导框架:Richardson Sales Performance(四维能力)、Challenger 辅导模型、MEDDPICC 资质诊断。关键方法论:辅导行为而非结果;一次只做一件事;管道质量是管理工具;挑战"happy ears"要求可验证的承诺。数据支撑:正式辅导项目配额完成率91.2%,vs 非正式辅导84.7%;每周2小时辅导赢单率56%,vs 少于30分钟43%。
|
||||
- Concepts created: MEDDPICC, Challenger Sales Model
|
||||
- Entities linked: Discovery Coach Agent(已有)、Sales Pipeline Analyst Agent(已有)、Sales Deal Strategist Agent(已有)
|
||||
- Source page: wiki/sources/sales-coach.md
|
||||
- Notes: 与 Discovery Coach Agent 的辅导焦点层次差异已记录于 Contradictions;source页面内 Key Concepts 详细记录了 MEDDPICC、Challenger、Richardson Sales Performance 等框架;overview.md 新增"Sales Coaching Methodology"主题节,置于"Sales Discovery Methodology"之后,两者协同关系已明确
|
||||
|
||||
## [2026-04-25] ingest | Discovery Coach Agent
|
||||
- Source file: Agent/agency-agents/sales/sales-discovery-coach.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Discovery Coach Agent——销售发现访谈方法论教练智能体,坚信发现是交易成败的真正战场。整合三大发现框架(SPIN Selling / Gap Selling / Sandler Pain Funnel)+ 标准30分钟发现电话结构(开场2分钟 / 发现18分钟 / 定向pitch 6分钟 / 下一步4分钟)+ AECR异议处理框架(Acknowledg/Empathize/Clarify/Reframe)。核心原则:发现不是审讯,Implication问题通过激活损失厌恶推动成交,60/40规则(买家说话60%以上),最优秀销售多问一个问题。
|
||||
- Concepts created: SPIN Selling(作为wikilink保留于source页面内)、Gap Selling(同)、Sandler Pain Funnel(同)、AECR Framework(同)、Upfront Contract(同)、Discovery Call Structure(同)
|
||||
- Entities linked: Neil Rackham(同)、Keenan(同)、Sandler(同)
|
||||
- Source page: wiki/sources/sales-discovery-coach.md
|
||||
- Notes: Entity/Concept页面未单独创建(均首次出现且可抽象为独立概念,建议在后续摄入相关源文件时再评估);未发现与现有Wiki内容的冲突;overview.md新增"Sales Discovery Methodology"主题节;source页面内详细记录了各框架的定义和引用
|
||||
|
||||
## [2026-04-25] ingest | Paid Media Ad Creative Strategist Agent
|
||||
- Source file: Agent/agency-agents/paid-media/paid-media-creative-strategist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: 付费媒体广告创意策略 Agent——由 John Williams(@itallstartedwithaidea)设计,专注于 Google、Meta、Microsoft 及程序化平台的全渠道广告文案创作、响应式搜索广告(RSA)架构设计和系统性创意测试框架。核心理念:创意是自动化竞价环境中最大的可控杠杆,当算法接管了出价、预算和定向时,每一条标题、描述、图片和视频都是一个待验证的假设。
|
||||
- Concepts created: [[ResponsiveSearchAds]], [[AdStrength]], [[CreativeFatigue]], [[HookBodyCTA]], [[ABTesting]], [[MessageMatch]], [[AdExtensions]]
|
||||
- Entities linked: [[GoogleAds]], [[MetaAdsManager]], [[MicrosoftAdvertising]], [[PerformanceMax]], [[JohnWilliams]](已存在)
|
||||
- Source page: wiki/sources/paid-media-creative-strategist.md
|
||||
- Notes: 与 [[paid-media-ppc-strategist]] 在"自动化 vs 创意质量"权衡上的张力已记录于 Contradictions;与 [[paid-media-programmatic-buyer]] 在"创意新鲜度"上的潜在冲突已记录;与 [[paid-media-paid-social-strategist]] 协同关系已记录(受众洞察→平台原生创意执行);overview.md 中 paid-media-creative-strategist 条目已从简略描述更新为完整条目,Key Concepts 行已更新
|
||||
|
||||
## [2026-04-25] ingest | Paid Social Strategist
|
||||
- Source file: Agent/agency-agents/paid-media/paid-media-paid-social-strategist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: 跨平台付费社交广告专家 Agent,覆盖 Meta(Facebook/Instagram)、LinkedIn、TikTok、Pinterest、X 和 Snapchat,设计从引流到再营销的全漏斗社交广告项目。核心理念:社交广告本质是"打断"而非"回答",必须构建平台原生体验而非跨平台复用创意。
|
||||
- Concepts created: [[Full-Funnel-Campaign-Architecture]], [[Custom-Audience-Engineering]], [[Conversions-API]], [[Advantage+-Campaigns]], [[Incrementality-Testing]], [[SKAdNetwork]]
|
||||
- Entities created: [[Meta-Ads-Manager]], [[LinkedIn-Campaign-Manager]], [[TikTok-Ads]]; [[JohnWilliams]] 已更新
|
||||
- Source page: wiki/sources/paid-media-paid-social-strategist.md
|
||||
- Notes: 与 [[paid-media-programmatic-buyer]] 在"自动化 vs. 控制"权衡上存在张力已记录于 Contradictions;与 [[paid-media-ppc-strategist]] 在跨渠道预算分配验证原则上有协同关系;与 [[paid-media-creative-strategist]] 在受众策略→创意方向上有依赖关系已记录
|
||||
|
||||
## [2026-05-06] ingest | Paid Media Search Query Analyst Agent
|
||||
- Source file: Agent/agency-agents/paid-media/paid-media-search-query-analyst.md
|
||||
- Status: ✅ 成功摄入
|
||||
@@ -2753,9 +2825,11 @@
|
||||
- Concepts linked: [[Infrastructure-as-Code]], [[DRY Principle]], [[GitOps]], [[CloudWatch-Alarms]], [[KMS-Encryption]]
|
||||
- Entities linked: [[Gruntwork]], [[Atlantis]], [[Terraform]], [[Terragrunt]], [[DBRE]], [[CloudWatch]]
|
||||
- Source page: wiki/sources/learning-sessions-cloud-transformation-programme-deploying-rds-via-terraform.md
|
||||
- Notes:
|
||||
- index.md 已替换 expected placeholder 条目,补充中文摘要
|
||||
- overview.md 已新增独立段落(置于 CTP Topic 16 后),与 Terragrunt/Terraform/Gruntwork/Atlantis 等相关来源建立知识链路
|
||||
- DBRE/Greg 提及 1 次,不足 Entity 建页阈值,以 wikilink 形式记录于 Source page
|
||||
- CloudWatch/KMS 在 wiki 中已存在关联页面,以 wikilink 形式记录无需新建
|
||||
- 冲突检测:与 ctp-topic-48-terraform-vs-terragrunt 一致(推荐 Terragrunt);与 ctp-topic-9-ci-cd-with-gruntwork 互补(Gruntwork CI/CD 基础);与 ctp-topic-16-cross-account-terraform-modules 共享 Terraform 生态,CI/CD 载体不同无冲突
|
||||
## [2026-04-25] ingest | Paid Media Tracking & Measurement Specialist Agent
|
||||
- Source file: Agent/agency-agents/paid-media/paid-media-tracking-specialist.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: 付费媒体追踪与归因专家 Agent——由 John Williams(@itallstartedwithaidea)设计,负责构建跨平台(GTM、GA4、Google Ads、Meta CAPI、LinkedIn Insight Tag)的事件追踪架构,确保每一次转化都被正确计数,每一分广告投入都可衡量。核心理念:错误追踪比无追踪更糟糕,错误计数的转化会主动误导出价算法向错误方向优化。
|
||||
- Concepts linked: [[GoogleTagManager]], [[GoogleAnalytics4]], [[MetaConversionsAPI]], [[ServerSideTagging]], [[ConversionTracking]], [[AttributionModeling]], [[ConsentModeV2]], [[DataLayerArchitecture]]
|
||||
- Entities linked: [[JohnWilliams]], [[TheAgency]]
|
||||
- Source page: wiki/sources/paid-media-tracking-specialist.md
|
||||
- Notes: 该 Agent 为其他所有 Paid Media Agent 提供数据基础设施;与 paid-media-creative-strategist/paid-social-strategist/ppc-strategist/programmatic-buyer/search-query-analyst/auditor 均存在 depends_on 关系(协同关系已记录于 Connections);index.md 已插入于 paid-media-programmatic-buyer 之后;Concepts 均为工具/框架类概念,当前仅出现 1 次,不足独立建页阈值,以 wikilink 形式记录于 Source page
|
||||
|
||||
@@ -56,7 +56,7 @@ The Agency 的 Paid Media 部门专注于企业级付费媒体策略与运营,
|
||||
|
||||
**[[paid-media-programmatic-buyer]]**(Programmatic & Display Buyer):程序化购买与展示广告策略 Agent——专注于程序化广告购买和展示广告策略执行,覆盖 DSP 平台操作、受众定向、创意优化和效果分析。与 [[paid-media-ppc-strategist]] 协同:前者定义全渠道预算分配和策略框架,后者执行具体程序化购买操作。
|
||||
|
||||
**[[paid-media-creative-strategist]]**(Creative Strategist):付费媒体创意策略 Agent——专注于广告创意资产策略,为 Performance Max 和 Display 广告提供创意方向和优化建议。与 [[paid-media-ppc-strategist]] 协同:后者提供投放策略,前者提供创意资产支撑。
|
||||
**[[paid-media-creative-strategist]]**(Creative Strategist):付费媒体广告创意策略 Agent——由 John Williams(@itallstartedwithaidea)设计,专注于 Google、Meta、Microsoft 及程序化平台的全渠道广告文案创作、响应式搜索广告(RSA)架构设计和系统性创意测试框架。核心理念:**创意是自动化竞价环境中最大的可控杠杆**,当算法接管了出价、预算和定向时,每一条标题、描述、图片和视频都是一个待验证的假设。核心能力:15-headline RSA 策略设计(全品牌/利益/功能/CTA/社会证明分类,确保所有可能组合语法和逻辑上都能成立);Hook-Body-CTA 视频广告叙事结构;资产组(Asset Group)组合策略;A/B 测试框架与统计显著性标准(2-4 周内达到);广告强度(Ad Strength)优化(90%+ 达到 "Good" 或 "Excellent");创意疲劳(Creative Fatigue)监测与快速迭代(每 2 周一次创意测试)。成功指标:CTR 提升 15-25%、转化率提升 5-10%、测试后 2-4 周内达成统计显著性。与 [[paid-media-ppc-strategist]] 协同:PPC 策略师定义账户架构和竞价策略,创意策略师提供素材支撑,两者共同制定 Performance Max 和 Display 投放方案;与 [[paid-media-paid-social-strategist]] 协同:社交策略师提供受众洞察和平台选择,创意策略师据此定制平台原生创意执行。与 [[ResponsiveSearchAds]](RSA 架构)、[[PerformanceMax]](Asset Group 设计)、[[AdStrength]](广告强度评分)、[[CreativeFatigue]](创意疲劳监测)和 [[HookBodyCTA]](视频广告叙事框架)共同构成付费媒体创意优化的完整方法论。
|
||||
|
||||
**[[paid-media-tracking-specialist]]**(Tracking Specialist):付费媒体追踪专家——负责转化追踪配置、数据归因建模和跨平台效果归因。与 [[paid-media-ppc-strategist]] 协同:为竞价策略优化提供可靠的数据基础。
|
||||
|
||||
@@ -64,7 +64,9 @@ The Agency 的 Paid Media 部门专注于企业级付费媒体策略与运营,
|
||||
|
||||
**[[paid-media-auditor]]**(Auditor):付费媒体账户审计专家——系统化评估 Google Ads、Microsoft Ads 和 Meta Ads 账户,覆盖 200+ 检查点(账号结构/追踪配置/竞价策略/创意/受众/竞争定位),每项发现附严重程度和预估业务影响。与 [[paid-media-ppc-strategist]] 协同:基于后者定义的基准进行效果诊断。成功指标:审计通常识别 15-30% 效率提升机会,80%+ 高优先级建议 30 天内落地。
|
||||
|
||||
Key concepts: [[PerformanceMax]], [[SmartBidding]], [[AccountArchitecture]], [[TieredCampaignArchitecture]], [[IncrementalityTesting]], [[ConversionActionHierarchy]], [[CustomerMatch]], [[BudgetPacing]]
|
||||
**[[paid-media-paid-social-strategist]]**(Paid Social Strategist):跨平台付费社交广告专家——覆盖 Meta(Facebook/Instagram)、LinkedIn、TikTok、Pinterest、X 和 Snapchat,设计从引流到再营销的全漏斗社交广告项目。核心理念:社交广告本质是"打断"而非"回答",必须构建平台原生体验而非跨平台复用创意。核心能力:全漏斗架构(引流→互动→再营销→留存)、平台差异化创意策略、像素/CRM 受众工程、Conversions API 实施、SKAdNetwork 应对 iOS 隐私变化。与 [[paid-media-ppc-strategist]] 和 [[paid-media-programmatic-buyer]] 同属付费媒体体系,但专注社交渠道而非搜索或程序化展示。关键决策原则:跨渠道预算分配必须基于搜索+展示+社交综合数据验证,而非单一渠道数据。
|
||||
|
||||
Key concepts: [[PerformanceMax]], [[SmartBidding]], [[AccountArchitecture]], [[TieredCampaignArchitecture]], [[IncrementalityTesting]], [[ConversionActionHierarchy]], [[CustomerMatch]], [[BudgetPacing]], [[ResponsiveSearchAds]], [[AdStrength]], [[CreativeFatigue]], [[HookBodyCTA]], [[MessageMatch]], [[ABTesting]], [[AdExtensions]]
|
||||
|
||||
### Multi-Agent Monitoring & Automation
|
||||
**Dynamic Dashboard**:基于 [[OpenClaw]] 的多数据源实时监控仪表盘——通过子代理并行抓取 GitHub/Twitter/Polymarket/系统健康等多数据源,定时聚合结果推送 Discord,支持告警阈值和历史趋势存储。用对话式指令替代数周前端开发,立即获得实时洞察。[[polymarket-autopilot]] 是 Polymarket 市场监控的具体实现——AI Agent 24/7 自动监控预测市场、分析概率变化、自动执行交易策略。与 [[self-healing-home-server]] 的系统监控场景关联,[[earnings-tracker]] 的市场数据监控场景扩展,[[content-factory]] 共享子代理并行执行模式。
|
||||
@@ -619,6 +621,30 @@ Key concepts: [[Django ORM]], [[Django REST Framework]], [[Django Admin 定制]]
|
||||
- **[[UEFI Only]]** — HP ZBook 终极启动修复方案,切换后消除 Legacy BBS 项干扰
|
||||
- **[[NVMe硬盘分区]]** — Ubuntu 24.04 自动识别并优化 NVMe 分区对齐
|
||||
|
||||
### Sales Outbound Methodology
|
||||
**[[sales-outbound-strategist]]**(Outbound Strategist Agent):信号型出站销售策略师,将出站销售从"批量轰炸"转变为"精准触发"——核心信念:出站应由证据驱动,而非配额驱动。核心理念:**信号驱动出站转化率比无触发出站高 4-8 倍**;信号的半衰期极短(30 分钟内必须路由到正确销售),24 小时后信号失效,72 小时后竞争对手已成交。核心框架:三层信号分级体系(Tier 1 主动购买信号如 G2 访问/竞品对比 → Tier 2 组织变化信号如融资/招聘/领导层变动 → Tier 3 技术/行为信号如技术栈变化/内容互动)+ 可证伪 ICP 定义(含排除条件,否则是 TAM 幻灯片)+ 三层账户分级(Tier 1 深度多线程个性化 / Tier 2 半个性化序列 / Tier 3 自动化轻定制)+ 8-12 触点 3-4 周多渠道序列(每次触达必须提供新的价值角度)。冷邮件回复率基准:泛化型 1-3%、角色定制 5-8%、信号驱动 12-25%、推荐引入型 30-50%。SDR 角色演变:从每天 100 次活动的批量操作员 → 拥有 50-80 个深度账户的信号监控管线专家。与 [[sales-discovery-coach]] 协同——发现阶段收集的 ICP 信号直接驱动出站序列启动;与 [[sales-deal-strategist]] 形成漏斗互补——出站负责漏斗顶部(Signal → Contact),Deal Strategist 负责漏斗中部(Qualified → Commit);与 [[sales-account-strategist]] 形成客户生命周期互补——出站获取新客户,Account Strategist 负责 Land-and-Expand 扩张。
|
||||
|
||||
### Sales Discovery Methodology
|
||||
**[[sales-discovery-coach]]**(Discovery Coach Agent):销售发现访谈(Discovery)方法论与教练框架,帮助销售代表和SDR成为更优秀的买家访谈者——坚信发现阶段才是交易成败的真正战场,而非演示、提案或谈判阶段。
|
||||
|
||||
**三大发现框架:**
|
||||
- **[[SPIN Selling]]**(Neil Rackham):四步提问法(Situation → Problem → Implication → Need-Payoff),核心洞察是 Implication 问题通过激活损失厌恶心理推动成交,是 SPIN 框架中最有力量但最常被跳过的一步
|
||||
- **[[Gap Selling]]**(Keenan):以当前状态与期望未来状态之间的差距为中心的销售方法论;差距越大紧迫感越强;根因问题(而非表面症状)才真正驱动购买决策
|
||||
- **[[Sandler Pain Funnel]]**:从表面症状 → 商业影响 → 个人/情感层面的三层漏斗;第三层(情感层面)是大多数销售人员永远不会触及的区域,但购买决策本质上是情感决策
|
||||
|
||||
**标准发现电话结构(30分钟)**:开场2分钟(Upfront Contract,设定三种可能结果建立信任)→ 发现阶段18分钟(60-70%精力放在当前状态和痛点)→ 定向pitch 6分钟(仅展示直接对应买家痛点的能力)→ 下一步4分钟(明确谁做什么、什么时候做)
|
||||
|
||||
**[[AECR Framework]]**(异议处理四步框架):Acknowledge → Empathize → Clarify → Reframe,将异议视为诊断信息而非攻击。核心洞察:预算异议几乎从不是真正的预算问题,本质是买家对价值是否超过成本的判断。
|
||||
|
||||
核心教练原则:发现不是审讯,而是帮助买家更清晰地看清自身处境;60/40规则(买家说话60%以上);最优秀的销售比竞争对手多问一个问题;资格筛选要快(没有真正痛点、无法触达决策者、无紧迫时间线就不是交易而是预测谎言)。
|
||||
|
||||
### Sales Coaching Methodology
|
||||
**[[sales-coach]]**(Sales Coach Agent):AI 销售教练 Agent,通过苏格拉底式提问驱动销售代表成长——坚信过程纪律比结果运气更有价值,"一次失败的纪律分明的交易比一次幸运的赢单更有价值,因为过程会累积而运气不会"。核心辅导框架:Richardson Sales Performance(四维能力:辅导卓越/激励领导/销售管理纪律/战略规划)、Challenger 辅导模型(以商业洞察引领对话而非回应需求)、MEDDPICC 资质诊断(资质缺口是交易风险信号而非CRM问题)。每周2小时以上辅导的代理赢单率56%,vs 少于30分钟仅43%;正式辅导项目配额完成率91.2%,vs 非正式辅导84.7%。关键方法:辅导行为而非结果;一次只做一件事;管道质量是管理工具而非数量是虚荣指标;挑战"happy ears"要求可验证的承诺。[[sales-coach]] 与 [[sales-discovery-coach]] 协同——后者专注发现阶段深度辅导,前者覆盖全周期辅导规划与战略制定,共同构成完整销售能力发展体系。
|
||||
|
||||
**[[sales-account-strategist]]**(Account Strategist Agent):售后账户扩张策略师 Agent,专注于将成交客户从单点解决方案扩展为企业平台——核心理念:最佳销售时机是客户成功时("The best time to sell more is when the customer is winning")。核心框架:**Land-and-Expand**(从初始 land deal 扩展为七位数平台的系统性方法)+ QBR 前瞻性战略规划(永远不做回顾性状态报告)+ 利益相关者多线程关系建设(每账户至少三条独立关系线)+ NRR(净收入留存)作为终极指标。账户健康评分体系:绿色账户推扩张、黄色账户稳基础、红色账户救流失。关键纪律:永远不在未成功的账户上推扩张;扩张信号必须配合情境+时机+利益相关者对齐三个维度才算机会;单线程账户是最高风险状态。[[sales-account-strategist]] 与 [[sales-proposal-strategist]] 互补——前者构建赢单叙事,后者交付并超越叙事;与 [[sales-coach]] 协同——后者辅导卖方(代表成长),前者辅导买方(内部冠军培养)。
|
||||
|
||||
**[[sales-deal-strategist]]**(Deal Strategist Agent):高级deal策略师与管线架构师,将严谨的资质方法论应用于复杂B2B销售周期——坚信每个deal都是战略问题而非关系练习,"如果资质缺口没有尽早识别,失败就已经锁定了,只是你还没发现"。核心能力:**MEDDPICC资质评估**(八维度评分,每维度5分,满分40;全面推行MEDDPICC的组织赢率提升18%、deal规模扩大24%)+ **竞争定位**(Winning/Battling/Losing三区分析 + 地雷问题布局)+ **Challenger商业教学法**(六步序列:Warmer → Reframe → Rational Drowning → Emotional Impact → A New Way → Your Solution)+ **交易检查方法论**(系统探测风险信号:单线程/无紧迫事件/Champion不开放EB通道/决策标准完美匹配竞争对手)。核心原则:预测准确率Commit deals关闭率85%+;Qualified Pipeline(28/40+)赢率35%+;永远不做单线程账户;每条资质缺口必须附带具体下一步、责任人、和截止日期。与 [[sales-discovery-coach]] 协同——后者提供买方情境输入(发现阶段),前者构建交易策略(评估+定位+计划);与 [[sales-proposal-strategist]] 互补——Deal Strategist提供结构化deal分析和竞争定位,Proposal Strategist将其转化为说服性叙事,共同构成"发现→赢单策略→提案叙事"完整销售闭环。
|
||||
|
||||
## Conflict Areas
|
||||
|
||||
1. **Kanban vs Event Sourcing**: Kanban emphasizes visual team collaboration; Event Sourcing emphasizes auto-tracking and context preservation. **[[Project State Management]]**(事件驱动看板替代方案)vs 传统 PM 工具。核心差异:手动拖拽 vs 自然语言输入;静态快照 vs 全历史保留;无上下文 vs 完整决策链。**[[Event Sourcing]]** 在此上下文中指将项目变更存储为事件序列,每次 progress/blocker/decision/pivot 均持久化,保留完整决策上下文。
|
||||
|
||||
50
wiki/sources/sales-outbound-strategist.md
Normal file
50
wiki/sources/sales-outbound-strategist.md
Normal file
@@ -0,0 +1,50 @@
|
||||
---
|
||||
title: "Outbound Strategist Agent"
|
||||
type: source
|
||||
tags: []
|
||||
date: 2026-04-25
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[Agent/agency-agents/sales/sales-outbound-strategist.md]]
|
||||
|
||||
## Summary(用中文描述)
|
||||
- 核心主题:信号驱动型出站销售策略与多渠道序列设计
|
||||
- 问题域:B2B 出站销售如何从"批量轰炸"转向"精准触发",在买家信号最强烈的时刻介入
|
||||
- 方法/机制:三层信号分级体系(主动购买信号→组织变化信号→技术/行为信号)+ ICP 可证伪定义 + 三层账户分级模型 + 8-12 触点 3-4 周多渠道序列架构
|
||||
- 结论/价值:信号驱动出站转化率比无触发出站高 4-8 倍;SDR 角色从批量操作员进化为信号监控专家
|
||||
|
||||
## Key Claims(用中文描述)
|
||||
- 信号驱动出站转化率比无触发冷出站高 4-8 倍
|
||||
- 信号半衰期短:30 分钟内路由到正确销售,24 小时后信号失效,72 小时后竞争对手已成交
|
||||
- 可用 ICP 必须可证伪——不能排除任何公司的 ICP 不是 ICP,是 TAM 幻灯片
|
||||
- 序列中每次触达必须提供新的价值角度——重复同样诉求不是序列,是骚扰
|
||||
- 冷邮件回复率基准:泛化型 1-3%、角色定制 5-8%、信号驱动 12-25%、推荐引入型 30-50%
|
||||
- SDR 角色转变:从每天 100 次活动操作员 → 拥有 50-80 个深度账户的管线专家
|
||||
|
||||
## Key Quotes
|
||||
> "If you cannot articulate why you are contacting this specific person at this specific company at this specific moment, you are not ready to send." — Outbound Strategist Agent 核心原则
|
||||
> "Each touch must add a new value angle. Repeating the same ask with different words is not a sequence — it is nagging." — 序列设计原则
|
||||
|
||||
## Key Concepts
|
||||
- [[Signal-Based Selling Framework]]:基于买家行为信号触发精准出站的方法论,转化率比传统冷出站高 4-8 倍
|
||||
- [[ICP (Ideal Customer Profile)]]:可证伪的理想客户画像定义框架,包含公司特征、行为限定和排除条件三层结构
|
||||
- [[Multi-Channel Sequence Architecture]]:8-12 次触点跨越 3-4 周的多渠道触达序列,每触点必须增加新的价值角度
|
||||
- [[Account Tiering Model]]:三层账户分级模型(Tier 1 深度多线程 / Tier 2 半个性化序列 / Tier 3 自动化轻定制)
|
||||
|
||||
## Key Entities
|
||||
- Outbound Strategist Agent:信号型出站策略师与序列架构师智能体,核心职责:设计多渠道触达序列、定义 ICP、按账户分层执行
|
||||
- SDR (Sales Development Representative):角色演变对象,从批量操作员进化为信号监控专家
|
||||
|
||||
## Connections
|
||||
- [[sales-deal-strategist]] ← complements ← [[sales-outbound-strategist]]:出站负责发现和培育潜在机会,Deal Strategist 负责赢单策略
|
||||
- [[sales-discovery-coach]] ← feeds_into ← [[sales-outbound-strategist]]:发现阶段收集的 ICP 信号直接驱动出站序列的启动
|
||||
- [[sales-account-strategist]] ← extends ← [[sales-outbound-strategist]]:出站获取新客户后,Account Strategist 负责 Land-and-Expand 扩张
|
||||
- [[sales-proposal-strategist]] ← follows ← [[sales-outbound-strategist]]:出站触达后进入提案阶段,Proposal Strategist 构建赢单叙事
|
||||
|
||||
## Contradictions
|
||||
- 与 [[sales-deal-strategist]] 的区域:
|
||||
- 冲突点:出站策略以信号触发为唯一启动条件;Deal Strategist 以 MEDDPICC 资质评估为赢单框架,两者对"何时介入"的定义角度不同
|
||||
- 当前观点:出站必须在信号出现 30 分钟内行动,时机优先于资质评估
|
||||
- 对方观点:任何 deal 进入赢单阶段前必须通过 MEDDPICC 全面评估
|
||||
- 协调方式:两者处于销售漏斗的不同阶段——出站负责漏斗顶部(Signal → Contact),Deal Strategist 负责漏斗中部(Qualified → Commit)
|
||||
Reference in New Issue
Block a user