63 lines
3.1 KiB
Markdown
63 lines
3.1 KiB
Markdown
---
|
||
title: "Sales Engineer"
|
||
type: source
|
||
tags: [agent, the-agency, sales, pre-sales]
|
||
date: 2026-04-20
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Agent/agency-agents/sales/sales-engineer.md]]
|
||
|
||
## Summary
|
||
- 核心主题：Sales Engineer（售前工程师）智能体角色定义与核心能力
|
||
- 问题域：B2B 销售中的技术决策环节，售前工程师如何桥接产品能力与业务价值
|
||
- 方法/机制：技术发现、演示工程、POC 设计与执行、竞争定位、解决方案架构、异议处理
|
||
- 结论/价值：售前工程师是赢得技术决策的关键角色，技术是工具而非叙事，必须连接回业务成果
|
||
|
||
## Key Claims
|
||
- 售前工程师是连接产品功能与买家业务需求的桥梁，必须将每个技术对话连接回业务成果
|
||
- 演示不是产品 tour，而是叙事，买家在演示中看到问题被实时解决
|
||
- POC 不是免费试用，而是有明确成功标准的结构化评估，范围蔓延是最大风险
|
||
- 竞争定位应基于事实（FIA 框架），而非 FUD（恐惧、不确定、怀疑）
|
||
- 技术异议通常不是表面问题，需解码真实顾虑
|
||
|
||
## Key Quotes
|
||
> "You can't get the sales win without the technical win — but the technology is your toolbox, not your storyline." — 核心定位
|
||
|
||
> "Every technical conversation must connect back to a business outcome or it's just a feature dump." — 沟通原则
|
||
|
||
> "A demo is not a product tour. A demo is a narrative where the buyer sees their problem solved in real time." — 演示理念
|
||
|
||
> "Technical objections are rarely about the stated concern... 'does it support SSO?' usually means 'will this pass our security review?'" — 异议解码
|
||
|
||
## Key Concepts
|
||
- [[Technical Discovery]]：结构化需求分析，揭示架构、集成需求、安全约束和真正的技术决策标准
|
||
- [[Demo Engineering]]：以影响为导向的演示设计，在展示产品前先量化问题
|
||
- [[POC-Scoping]]：概念验证的范围设计，聚焦单一关键验证点，避免范围蔓延
|
||
- [[FIA Framework]]：竞争定位框架（Fact, Impact, Act），保持定位基于事实
|
||
- [[Solution Architecture]]：将产品能力映射到买方基础设施（已有概念）
|
||
- [[Technical Objection Handling]]：解码真实顾虑而非表面问题
|
||
- [[Evaluation Management]]：技术评估过程端到端管理
|
||
|
||
## Key Entities
|
||
- [[Sales Discovery Coach]]：发现方法论指导智能体，发现真正购买动机
|
||
- [[Deal Strategist]]：交易策略智能体，专注 MEDDPICC 资格认证
|
||
- [[Proposal Strategist]]：提案策略智能体，将 RFP 响应转化为制胜叙事
|
||
- [[Sales Account Strategist]]：售后账户策略智能体
|
||
- [[Pipeline Analyst]]：管道健康诊断智能体
|
||
|
||
## Connections
|
||
- [[Sales Discovery Coach]] ← prepares ← [[Sales Engineer]]
|
||
- [[Sales Engineer]] ← delivers → [[Proof-of-Concept-POC]]
|
||
- [[Deal Strategist]] ← collaborates_with ← [[Sales Engineer]]
|
||
- [[Proposal Strategist]] ← collaborates_with ← [[Sales Engineer]]
|
||
|
||
## Contradictions
|
||
- 无明显冲突
|
||
|
||
## Success Metrics
|
||
- Technical Win Rate: 70%+
|
||
- POC Conversion: 80%+
|
||
- Demo-to-Next-Step Rate: 90%+
|
||
- Time to Technical Decision: 中位数 18 天
|
||
- Competitive Technical Win Rate: 65%+ |