atl-btl-messaging
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseATL vs BTL Messaging Framework
ATL vs BTL 沟通框架
Above-the-Line (ATL) - VPs, C-Level, Directors
ATL - 副总裁、高管层、总监
Mindset:
- Think past and future (strategic)
- Want validation, not problems solved
- Care about big picture, not daily operations
What They Care About:
- Revenue impact
- Risk reduction
- Strategic initiatives
- Competitive positioning
- Board/investor optics
Message Length: 2-3 sentences only
Language to Use:
- "Strategic initiative"
- "Revenue impact"
- "Competitive advantage"
- "Board-level priority"
- "Risk mitigation"
Example ATL Email:
Subject: Q1 revenue efficiency
{{firstName}},
If you could identify revenue leakage 3 months faster, what would that mean for next year's targets?
We helped {{similar_company}}'s CEO do exactly that.
15 minutes to explore?Fatal ATL Mistake: Talking about operational problems = immediate delegation to subordinate
思维模式:
- 着眼过去与未来(战略性)
- 希望获得认可,而非解决具体问题
- 关注全局,而非日常运营
他们关心的内容:
- 营收影响
- 风险降低
- 战略举措
- 竞争定位
- 董事会/投资者视角
沟通内容长度: 仅2-3句话
推荐使用的表述:
- "战略举措"
- "营收影响"
- "竞争优势"
- "董事会级优先事项"
- "风险缓解"
ATL邮件示例:
Subject: Q1 revenue efficiency
{{firstName}},
If you could identify revenue leakage 3 months faster, what would that mean for next year's targets?
We helped {{similar_company}}'s CEO do exactly that.
15 minutes to explore?ATL沟通致命错误: 谈论运营层面的问题 = 会被立即转交给下属处理
Below-the-Line (BTL) - Managers, ICs, End-Users
BTL - 经理、普通员工(IC)、终端用户
Mindset:
- Think present (tactical)
- Want problems solved immediately
- Care about daily workflow
What They Care About:
- Daily pain points
- Time savings
- Workflow improvements
- Making their job easier
- Looking good to their boss
Message Length: 3-4 sentences acceptable
Language to Use:
- "Stop spending 3 hours every week on..."
- "Eliminate the manual work of..."
- "Never deal with {{pain}} again"
- "Save {{X}} hours per week"
Example BTL Email:
Subject: 3 hours back
Hey {{firstName}},
Stop spending 3 hours every week fighting with Excel.
We helped {{similar_company}}'s ops team cut their reporting time by 70%.
Want to see how?Fatal BTL Mistake: Talking about ROI and strategic impact = doesn't resonate, too abstract
思维模式:
- 着眼当下(战术性)
- 希望立即解决问题
- 关注日常工作流程
他们关心的内容:
- 日常痛点
- 时间节省
- 工作流程优化
- 简化工作内容
- 在上司面前表现出色
沟通内容长度: 3-4句话均可
推荐使用的表述:
- "无需再每周花费3小时处理..."
- "消除...的手动工作"
- "再也不用应对{{pain}}这类问题"
- "每周节省{{X}}小时"
BTL邮件示例:
Subject: 3 hours back
Hey {{firstName}},
Stop spending 3 hours every week fighting with Excel.
We helped {{similar_company}}'s ops team cut their reporting time by 70%.
Want to see how?BTL沟通致命错误: 谈论投资回报率(ROI)和战略影响 = 无法引起共鸣,过于抽象
Decision Framework: Who to Target
决策框架:该触达谁
Target ATL (Executives) When:
- Deal size > $50K ACV
- Strategic/transformation purchase
- Requires budget approval from top
- Long sales cycle acceptable
Target BTL (End-Users) When:
- Product-led growth motion
- User adoption drives expansion
- Bottom-up sale
- Need internal champion first
Multi-Thread (Both) When:
- Complex enterprise sale
- Multiple stakeholders
- Both budget holder and user buy-in needed
选择触达ATL(高管)的场景:
- 交易规模 > 5万美元年度合同价值(ACV)
- 战略性/转型性采购
- 需要高层批准预算
- 可接受较长销售周期
选择触达BTL(终端用户)的场景:
- 产品驱动增长模式
- 用户采用率推动业务扩张
- 自下而上的销售
- 首先需要内部支持者
同时触达两者的场景:
- 复杂的企业级销售
- 存在多个利益相关方
- 同时需要预算负责人与用户的认可
Combines with
可结合使用的技能
| Skill | Why |
|---|---|
| Adjust sequence length for ATL vs BTL |
| Apply word count rules by seniority |
| CXO Passdown for ATL targeting |
| Choose bucket by seniority level |
| 技能 | 原因 |
|---|---|
| 针对ATL与BTL调整沟通序列长度 |
| 根据职级应用字数规则 |
| 针对ATL触达使用CXO向下传递策略 |
| 根据职级选择个性化分类 |
Example prompts
示例提示词
Rewrite this email for a CFO (ATL) instead of a Finance Manager (BTL).Create an ATL email about cost reduction for a VP Operations at a logistics company.I have a BTL champion - write a BTL email I can ask them to forward to their VP.Rewrite this email for a CFO (ATL) instead of a Finance Manager (BTL).Create an ATL email about cost reduction for a VP Operations at a logistics company.I have a BTL champion - write a BTL email I can ask them to forward to their VP.