account-executive
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAccount Executive Expert
企业销售客户经理（Account Executive）专家
Comprehensive expertise in full-cycle B2B sales execution.
全面掌握全周期B2B销售执行专业技能。
Core Competencies
核心能力
Discovery
需求挖掘
- Deep qualification methodology
- Pain point extraction
- Business case building
- Stakeholder mapping
- Competitive positioning
- 深度资质审核方法论
- 痛点挖掘
- 商业案例构建
- 利益相关人映射
- 竞品定位
Demonstration
方案演示
- Needs-based demo structure
- Storytelling with product
- Feature-benefit translation
- Handling objections mid-demo
- Multi-stakeholder presentations
- 基于需求的演示结构
- 结合产品的故事化讲解
- 功能-价值转化
- 演示中异议处理
- 多利益相关人演示
Proposal & Negotiation
方案提案与谈判
- Proposal construction
- ROI justification
- Pricing strategy
- Contract negotiation
- Procurement navigation
- 提案撰写
- ROI合理性论证
- 定价策略
- 合同谈判
- 采购流程对接
Closing
成交环节
- Commitment progression
- Timeline management
- Champion coaching
- Executive alignment
- Risk mitigation
- 承诺推进
- 时间线管理
- 内部支持者辅导
- 高管对齐
- 风险缓解
Sales Methodologies
销售方法论
MEDDPICC
MEDDPICC
- Metrics: Quantifiable goals
- Economic buyer: Final decision maker
- Decision criteria: Evaluation factors
- Decision process: Steps to purchase
- Paper process: Legal/procurement
- Implications of pain: Cost of inaction
- Champion: Internal advocate
- Competition: Alternative options
- Metrics: 可量化目标
- Economic buyer: 最终决策者
- Decision criteria: 评估因素
- Decision process: 采购步骤
- Paper process: 法务/采购流程
- Implications of pain: 不作为的成本
- Champion: 内部支持者
- Competition: 替代方案
Challenger Sale
Challenger Sale
- Teach something new
- Tailor to stakeholder
- Take control of sale
- 传递新知
- 贴合利益相关人需求
- 掌控销售节奏
Solution Selling
Solution Selling
- Diagnose before prescribing
- Create value, not just communicate it
- Align to business outcomes
- 先诊断再开方
- 创造价值，而非仅传递价值
- 对齐业务成果
Deal Management
成交管理
Pipeline Hygiene
销售管道健康度
- Weekly deal reviews
- Accurate forecasting
- Risk identification
- Next step clarity
- Close date discipline
- 每周成交复盘
- 精准预测
- 风险识别
- 下一步动作明确
- 成交日期管控
Stakeholder Management
利益相关人管理
- Champion development
- Executive sponsor access
- Technical validation
- Procurement relationship
- Legal coordination
- 内部支持者培养
- 高管赞助人对接
- 技术验证
- 采购关系维护
- 法务协调
Discovery Framework
需求挖掘框架
SPIN Questions
SPIN Questions
Situation: "How are you currently handling X?"
Problem: "What challenges do you face with that approach?"
Implication: "What happens if this isn't solved?"
Need-payoff: "How would solving this impact your business?"Situation: "你们目前是如何处理X的？"
Problem: "这种方式下你们面临哪些挑战？"
Implication: "如果这个问题不解决会有什么后果？"
Need-payoff: "解决这个问题会对你们的业务产生怎样的影响？"Pain Stack
痛点层级
- Technical pain: Feature gaps, integration issues
- Business pain: Revenue impact, efficiency loss
- Personal pain: Career risk, time waste
- 技术痛点: 功能缺口、集成问题
- 业务痛点: 营收影响、效率损失
- 个人痛点: 职业风险、时间浪费
Objection Handling
异议处理
Price Objection
价格异议
1. Acknowledge: "I understand budget is a concern"
2. Clarify: "What were you expecting to invest?"
3. Value: "Let me show you the ROI breakdown"
4. Options: "We have flexible payment terms"1. 认可: "我理解预算是个关注点"
2. 澄清: "你们预期的投入是多少？"
3. 价值呈现: "让我为你展示ROI明细"
4. 方案选项: "我们有灵活的付款条款"Timing Objection
时间异议
1. Understand: "What's driving that timeline?"
2. Cost of delay: "Each month costs you $X"
3. Quick wins: "We can start with phase 1"
4. Create urgency: "Q4 pricing ends Friday"1. 了解原因: "是什么因素决定了这个时间线？"
2. 延迟成本: "每延迟一个月会给你们带来X美元的损失"
3. 快速启动: "我们可以先从第一阶段开始"
4. 制造紧迫感: "第四季度定价将于周五截止"Competition Objection
竞品异议
1. Don't disparage: Focus on your strengths
2. Differentiate: "Where we uniquely excel is..."
3. References: "Companies like you chose us because..."
4. Proof: "Here's a comparison based on your needs"1. 不贬低竞品: 聚焦自身优势
2. 差异化: "我们的独特优势是..."
3. 客户案例: "像你们这样的企业选择我们是因为..."
4. 实证: "这是基于你们需求的对比分析"Key Metrics
关键指标
| Metric | Description |
|---|---|
| Win rate | Deals won / total deals |
| Average deal size | Revenue per closed deal |
| Sales cycle | Time from SQL to close |
| Quota attainment | % of quota achieved |
| Forecast accuracy | Predicted vs. actual |
| Pipeline coverage | Pipe / quota ratio |
| Activity metrics | Calls, demos, proposals |
| 指标 | 描述 |
|---|---|
| 赢单率 | 成交数/总跟进数 |
| 平均成交规模 | 每笔成交的营收 |
| 销售周期 | 从合格销售线索（SQL）到成交的时间 |
| 配额完成率 | 完成配额的百分比 |
| 预测准确率 | 预测值vs实际值 |
| 销售管道覆盖率 | 销售管道金额/配额比例 |
| 活动指标 | 通话数、演示数、提案数 |
Negotiation Tactics
谈判技巧
BATNA Framework
BATNA Framework
- Know your Best Alternative To Negotiated Agreement
- Understand their BATNA
- Never negotiate against yourself
- Walk away power = leverage
- 了解你的最佳替代谈判协议方案（BATNA）
- 知晓对方的BATNA
- 绝不单方面让步
- 离场能力=谈判筹码
Concession Strategy
让步策略
- Never give without getting
- Start with low-cost/high-value items
- Save meaningful concessions for close
- Document all agreements
- 无回报绝不让步
- 从低成本高价值的事项开始
- 重要让步留到成交阶段
- 记录所有协议内容
Email Templates
邮件模板
Follow-up after demo
演示后跟进
Subject: Next steps for [Company] + [Your Company]
Hi [Name],
Great conversation today. As discussed:
1. [Key pain point you'll solve]
2. [Value proposition aligned to their goals]
3. [Next step with date]
I'll send over [promised materials] by EOD.
Looking forward to [next meeting].
[Your name]主题: [客户公司] + [你的公司] 后续行动
嗨 [姓名],
今天的交流非常愉快。正如我们讨论的:
1. [你将解决的核心痛点]
2. [与他们目标对齐的价值主张]
3. [带日期的下一步行动]
我会在今日下班前发送[承诺的材料]。
期待[下次会议]。
[你的姓名]Re-engagement
重新激活客户
Subject: Quick question about [their initiative]
Hi [Name],
Saw [trigger event/news] - congrats!
Given [relevant change], wanted to reconnect about
[original discussion topic].
Would [specific date/time] work for a brief call?
[Your name]主题: 关于[他们的项目]的小问题
嗨 [姓名],
看到[触发事件/新闻]了——恭喜!
鉴于[相关变化], 想和你重新聊聊
[最初的讨论话题]。
[具体日期/时间]方便进行简短通话吗?
[你的姓名]Demo Best Practices
演示最佳实践
Structure
结构
- Recap (2 min): Confirm pain points
- Agenda (1 min): Set expectations
- Value demo (15-20 min): Show, don't tell
- Objections (5-10 min): Address concerns
- Next steps (2 min): Confirm action items
- 回顾 (2分钟): 确认痛点
- 议程 (1分钟): 设定预期
- 价值演示 (15-20分钟): 展示而非讲述
- 异议处理 (5-10分钟): 解决顾虑
- 下一步行动 (2分钟): 确认行动项
Tips
小贴士
- Demo to their use case, not features
- Pause for questions frequently
- Use their data/examples when possible
- Have backup demos ready for technical issues
- Record for stakeholders who can't attend
- 针对他们的使用场景演示，而非单纯展示功能
- 频繁暂停以接收提问
- 尽可能使用他们的数据/案例
- 准备备用演示以应对技术问题
- 录制演示供无法参会的利益相关人观看