Update nexus: fix conflicts and sync local changes
This commit is contained in:
Shen Wei
@@ -1,88 +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]] — 不同层级账户的序列定制程度不同
|
||||
---
|
||||
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]] — 不同层级账户的序列定制程度不同
|
||||
|
||||
Reference in New Issue
Block a user