Back to Details

sales-engineer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sales Engineer

销售工程师

Expert-level technical sales support.
专业级技术销售支持。

Core Competencies

核心能力

  • Technical demonstrations
  • Solution architecture
  • RFP/RFI responses
  • POC management
  • Technical objection handling
  • Competitive positioning
  • Customer requirements analysis
  • Cross-functional collaboration
  • 技术演示
  • 解决方案架构
  • RFP/RFI响应
  • POC管理
  • 技术异议处理
  • 竞品定位
  • 客户需求分析
  • 跨职能协作

Discovery Process

需求探索流程

Technical Discovery Questions

技术需求探索问题

Environment:
  • What systems do you currently use?
  • How are they integrated?
  • What's your tech stack?
  • What security/compliance requirements?
Requirements:
  • What problem are you trying to solve?
  • What does success look like?
  • What are your must-haves vs nice-to-haves?
  • What's your timeline?
Decision Process:
  • Who else is involved in this decision?
  • What's your evaluation process?
  • What other solutions are you considering?
  • What would make this a no-brainer?
环境相关：
  • 你当前使用哪些系统？
  • 这些系统是如何集成的？
  • 你的技术栈是什么？
  • 有哪些安全/合规要求？
需求相关：
  • 你试图解决什么问题？
  • 成功的标准是什么？
  • 你的必备需求和可选需求分别是什么？
  • 你的时间规划是怎样的？
决策流程相关：
  • 还有哪些人参与这个决策？
  • 你的评估流程是什么？
  • 你还在考虑哪些其他解决方案？
  • 什么因素会让你毫不犹豫地选择我们？

Discovery Template

需求探索模板

markdown
undefined
markdown
undefined

Technical Discovery: [Company Name]

Technical Discovery: [Company Name]

Company Overview

Company Overview

  • Industry: [Industry]
  • Size: [Employees]
  • Tech maturity: [Low/Medium/High]
  • Industry: [Industry]
  • Size: [Employees]
  • Tech maturity: [Low/Medium/High]

Current State

Current State

  • Systems: [List]
  • Pain points: [List]
  • Workflows: [Description]
  • Systems: [List]
  • Pain points: [List]
  • Workflows: [Description]

Requirements

Requirements

Must Have

Must Have

  1. [Requirement]
  2. [Requirement]
  1. [Requirement]
  2. [Requirement]

Nice to Have

Nice to Have

  1. [Requirement]
  1. [Requirement]

Technical Environment

Technical Environment

  • Cloud: [AWS/GCP/Azure/On-prem]
  • Languages: [Languages]
  • Integrations needed: [Systems]
  • Cloud: [AWS/GCP/Azure/On-prem]
  • Languages: [Languages]
  • Integrations needed: [Systems]

Success Criteria

Success Criteria

Timeline

Timeline

  • Decision: [Date]
  • Implementation: [Date]
  • Go-live: [Date]
  • Decision: [Date]
  • Implementation: [Date]
  • Go-live: [Date]

Next Steps

Next Steps

  • [Action item]
undefined
  • [Action item]
undefined

Demo Excellence

卓越演示指南

Demo Preparation

演示准备

markdown
undefined
markdown
undefined

Demo Plan: [Company Name]

Demo Plan: [Company Name]

Attendees

Attendees

NameRolePriorities
[Name][Role][What they care about]
NameRolePriorities
[Name][Role][What they care about]

Agenda (60 min)

Agenda (60 min)

  1. Discovery recap (5 min)
  2. Solution overview (10 min)
  3. Use case demo (30 min)
  4. Q&A (10 min)
  5. Next steps (5 min)
  1. Discovery recap (5 min)
  2. Solution overview (10 min)
  3. Use case demo (30 min)
  4. Q&A (10 min)
  5. Next steps (5 min)

Use Cases to Demo

Use Cases to Demo

  1. [Use case]: [Pain point it addresses]
  2. [Use case]: [Pain point it addresses]
  3. [Use case]: [Pain point it addresses]
  1. [Use case]: [Pain point it addresses]
  2. [Use case]: [Pain point it addresses]
  3. [Use case]: [Pain point it addresses]

Competitive Differentiators

Competitive Differentiators

  • vs [Competitor]: [Our advantage]
  • vs [Competitor]: [Our advantage]

Potential Objections

Potential Objections

ObjectionResponse
[Objection][Response]
ObjectionResponse
[Objection][Response]

Demo Environment

Demo Environment

  • Instance: [URL]
  • Data: [Test data to use]
  • Features to show: [List]
  • Instance: [URL]
  • Data: [Test data to use]
  • Features to show: [List]

Success =

Success =

[What does a successful demo look like?]
undefined
[What does a successful demo look like?]
undefined

Demo Structure

演示结构

1. CONNECT (5 min)
   - Recap discovery
   - Confirm priorities
   - Set agenda

2. CONTEXT (5 min)
   - "Based on what you shared..."
   - Frame the solution

3. SHOW (30 min)
   - Start with the "wow"
   - Tell a story, don't feature dump
   - Match to their use cases
   - Involve the audience

4. SUMMARIZE (5 min)
   - Recap value
   - Address concerns
   - Trial/POC discussion

5. CLOSE (5 min)
   - Clear next steps
   - Timeline alignment
   - Owner assignment
1. 建立关联（5分钟）
   - 回顾需求探索内容
   - 确认优先级
   - 设定议程

2. 构建场景（5分钟）
   - "基于你分享的内容..."
   - 阐述解决方案

3. 演示展示（30分钟）
   - 从"惊艳点"开始
   - 讲好故事而非堆砌功能
   - 匹配他们的用例
   - 引导观众参与

4. 总结（5分钟）
   - 回顾价值
   - 解决顾虑
   - 讨论试用/POC

5. 收尾（5分钟）
   - 明确后续步骤
   - 对齐时间规划
   - 分配负责人

Demo Best Practices

演示最佳实践

Do:
  • Start with their problem
  • Use their terminology
  • Show the "aha" moment early
  • Involve the audience
  • Handle questions gracefully
Don't:
  • Feature dump
  • Rush through
  • Ignore questions
  • Over-promise
  • Bad-mouth competitors
建议做法：
  • 从他们的问题切入
  • 使用他们的术语
  • 尽早展示"恍然大悟"的时刻
  • 引导观众参与
  • 从容处理问题
避免做法：
  • 堆砌功能
  • 仓促推进
  • 忽略问题
  • 过度承诺
  • 贬低竞品

POC Management

POC管理

POC Framework

POC框架

markdown
undefined
markdown
undefined

POC Plan: [Company Name]

POC Plan: [Company Name]

Objectives

Objectives

  • Primary: [Objective]
  • Secondary: [Objective]
  • Primary: [Objective]
  • Secondary: [Objective]

Success Criteria

Success Criteria

CriteriaTargetMeasurement
[Criteria][Target][How to measure]
CriteriaTargetMeasurement
[Criteria][Target][How to measure]

Scope

Scope

In Scope

In Scope

  • [Item]
  • [Item]
  • [Item]
  • [Item]

Out of Scope

Out of Scope

  • [Item]
  • [Item]

Timeline

Timeline

PhaseDurationDates
Setup1 week[Dates]
Testing2 weeks[Dates]
Evaluation1 week[Dates]
PhaseDurationDates
Setup1 week[Dates]
Testing2 weeks[Dates]
Evaluation1 week[Dates]

Resources

Resources

  • Customer: [Names/roles]
  • Our team: [Names/roles]
  • Customer: [Names/roles]
  • Our team: [Names/roles]

Technical Setup

Technical Setup

  • Environment: [Details]
  • Data: [What data to use]
  • Integrations: [What to connect]
  • Environment: [Details]
  • Data: [What data to use]
  • Integrations: [What to connect]

Check-in Schedule

Check-in Schedule

  • Kickoff: [Date]
  • Weekly sync: [Day/Time]
  • Final review: [Date]
  • Kickoff: [Date]
  • Weekly sync: [Day/Time]
  • Final review: [Date]

Risks

Risks

RiskMitigation
[Risk][Plan]
undefined
RiskMitigation
[Risk][Plan]
undefined

POC Success Metrics

POC成功指标

TECHNICAL SUCCESS
- Feature requirements met: X/Y
- Performance benchmarks: Pass/Fail
- Integration completed: Yes/No

BUSINESS SUCCESS
- Time savings demonstrated: X%
- Ease of use rating: X/5
- Stakeholder approval: Yes/No

RELATIONSHIP SUCCESS
- Engagement level: High/Medium/Low
- Champion identified: Yes/No
- Decision maker engaged: Yes/No
技术成功
- 功能需求达成率：X/Y
- 性能基准：通过/未通过
- 集成完成：是/否

业务成功
- 已证明的时间节省率：X%
- 易用性评分：X/5
- 相关方批准：是/否

关系成功
- 参与度：高/中/低
- 已找到内部支持者：是/否
- 已对接决策人：是/否

RFP Response

RFP响应

RFP Response Template

RFP响应模板

markdown
undefined
markdown
undefined

RFP Response: [Company Name]

RFP Response: [Company Name]

Executive Summary

Executive Summary

[2-3 paragraphs summarizing fit]
[2-3 paragraphs summarizing fit]

Company Overview

Company Overview

[About your company]
[About your company]

Solution Overview

Solution Overview

[How you address their needs]
[How you address their needs]

Requirements Response

Requirements Response

IDRequirementResponseNotes
R1[Req]Full/Partial/Roadmap[Details]
R2[Req]Full/Partial/Roadmap[Details]
IDRequirementResponseNotes
R1[Req]Full/Partial/Roadmap[Details]
R2[Req]Full/Partial/Roadmap[Details]

Implementation Approach

Implementation Approach

[How you'll implement]
[How you'll implement]

Support & Services

Support & Services

[What support you provide]
[What support you provide]

Pricing

Pricing

[Pricing summary]
[Pricing summary]

References

References

[Customer references]
[Customer references]

Appendix

Appendix

[Additional materials]
undefined
[Additional materials]
undefined

Response Categories

响应分类

FULL: We fully meet this requirement today
PARTIAL: We partially meet this, with [explanation]
ROADMAP: This is on our roadmap for [timeframe]
PARTNER: We address this via [partner]
N/A: Not applicable to our solution
完全满足：我们当前完全符合该需求
部分满足：我们部分符合该需求，[说明]
路线规划中：该需求已纳入我们的[时间规划]路线图
合作伙伴支持：我们通过[合作伙伴]满足该需求
不适用：与我们的解决方案无关

Objection Handling

异议处理

Common Objections

常见异议

ObjectionResponse Framework
"Too expensive"Value justification + ROI
"Missing feature X"Workaround + roadmap
"We use competitor Y"Differentiation + migration ease
"Security concerns"Certifications + architecture
"Implementation risk"Success stories + support
异议回应框架
"价格太高"价值论证+投资回报率
"缺少功能X"替代方案+路线图
"我们使用竞品Y"差异化优势+迁移便捷性
"安全顾虑"认证资质+架构说明
"实施风险"成功案例+支持服务

LAER Framework

LAER回应框架

L - Listen
  - Let them finish
  - Take notes
  - Show empathy

A - Acknowledge
  - "I understand your concern"
  - Validate the point

E - Explore
  - "Can you tell me more?"
  - Understand root cause

R - Respond
  - Address specifically
  - Provide evidence
  - Offer alternatives
L - 倾听
  - 让对方说完
  - 做好记录
  - 表达共情

A - 认可
  - "我理解你的顾虑"
  - 认同对方的观点

E - 探索
  - "你能详细说说吗？"
  - 了解根本原因

R - 回应
  - 针对性解决
  - 提供证据
  - 给出替代方案

Technical Content

技术内容

Competitive Battle Card

竞品对战卡片

markdown
undefined
markdown
undefined

Competitive Battle Card: [Competitor]

Competitive Battle Card: [Competitor]

Quick Facts

Quick Facts

  • Founded: [Year]
  • Employees: [Number]
  • Funding: [Amount]
  • Customers: [Number]
  • Founded: [Year]
  • Employees: [Number]
  • Funding: [Amount]
  • Customers: [Number]

Their Strengths

Their Strengths

  • [Strength 1]
  • [Strength 2]
  • [Strength 1]
  • [Strength 2]

Their Weaknesses

Their Weaknesses

  • [Weakness 1]
  • [Weakness 2]
  • [Weakness 1]
  • [Weakness 2]

Our Differentiators

Our Differentiators

AreaUsThem
[Area][Our approach][Their approach]
AreaUsThem
[Area][Our approach][Their approach]

Common Objections

Common Objections

ObjectionResponse
"[Objection]""[Response]"
ObjectionResponse
"[Objection]""[Response]"

Landmines to Set

Landmines to Set

  • "[Question to ask prospect]"
  • "[Question to ask prospect]"

Reference Customers

Reference Customers

  • [Customer] who switched from [Competitor]
undefined
  • [Customer] who switched from [Competitor]
undefined

Reference Materials

参考资料

  • references/demo_playbook.md
    - Demo best practices
  • references/objections.md
    - Objection handling guide
  • references/competitive.md
    - Competitive intelligence
  • references/rfp_templates.md
    - RFP response templates
  • references/demo_playbook.md
    - 演示最佳实践指南
  • references/objections.md
    - 异议处理指南
  • references/competitive.md
    - 竞品情报
  • references/rfp_templates.md
    - RFP响应模板

Scripts

脚本工具

bash
undefined
bash
undefined

Demo environment setup

演示环境设置

python scripts/demo_setup.py --customer "Customer Name" --use-cases uc1,uc2
python scripts/demo_setup.py --customer "Customer Name" --use-cases uc1,uc2

RFP analyzer

RFP分析工具

python scripts/rfp_analyzer.py --rfp rfp.pdf --output requirements.csv
python scripts/rfp_analyzer.py --rfp rfp.pdf --output requirements.csv

POC tracker

POC跟踪工具

python scripts/poc_tracker.py --customer "Customer Name" --status update
python scripts/poc_tracker.py --customer "Customer Name" --status update

Competitive comparison

竞品对比工具

python scripts/competitive_compare.py --competitor "Competitor Name"
undefined
python scripts/competitive_compare.py --competitor "Competitor Name"
undefined