sales-engineer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSales Engineer Skill
销售工程师Skill
A production-ready skill package for pre-sales engineering that bridges technical expertise and sales execution. Provides automated analysis for RFP/RFI responses, competitive positioning, and proof-of-concept planning.
一套面向售前工程师的生产级Skill包,衔接技术专长与销售执行。提供RFP/RFI响应、竞品定位和概念验证(POC)规划的自动化分析。
Overview
概述
Role: Sales Engineer / Solutions Architect
Domain: Pre-Sales Engineering, Solution Design, Technical Demos, Proof of Concepts
Business Type: SaaS / Pre-Sales Engineering
角色: 销售工程师 / 解决方案架构师
领域: 售前工程、解决方案设计、技术演示、概念验证(POC)
业务类型: SaaS / 售前工程
What This Skill Does
本Skill的功能
- RFP/RFI Response Analysis - Score requirement coverage, identify gaps, generate bid/no-bid recommendations
- Competitive Technical Positioning - Build feature comparison matrices, identify differentiators and vulnerabilities
- POC Planning - Generate timelines, resource plans, success criteria, and evaluation scorecards
- Demo Preparation - Structure demo scripts with talking points and objection handling
- Technical Proposal Creation - Framework for solution architecture and implementation planning
- Win/Loss Analysis - Data-driven competitive assessment for deal strategy
- RFP/RFI响应分析 - 对需求覆盖情况打分、识别缺口、生成投标/不投标建议
- 竞品技术定位 - 构建功能对比矩阵、识别差异化优势与薄弱点
- POC规划 - 生成时间线、资源计划、成功标准和评估评分卡
- 演示准备 - 结构化演示脚本,包含沟通要点与异议处理内容
- 技术方案创建 - 提供解决方案架构与实施规划框架
- 赢单/丢单分析 - 基于数据的竞品评估,用于交易策略制定
Key Metrics
关键指标
| Metric | Description | Target |
|---|---|---|
| Win Rate | Deals won / total opportunities | >30% |
| Sales Cycle Length | Average days from discovery to close | <90 days |
| POC Conversion Rate | POCs resulting in closed deals | >60% |
| Customer Engagement Score | Stakeholder participation in evaluation | >75% |
| RFP Coverage Score | Requirements fully addressed | >80% |
| 指标 | 描述 | 目标 |
|---|---|---|
| 赢单率 | 赢单数量 / 总机会数 | >30% |
| 销售周期长度 | 从需求发现到成交的平均天数 | <90天 |
| POC转化率 | 转化为成交订单的POC数量 | >60% |
| 客户参与度评分 | 利益相关者在评估中的参与度 | >75% |
| RFP覆盖评分 | 需求完全满足的比例 | >80% |
5-Phase Workflow
五阶段工作流
Phase 1: Discovery & Research
阶段1:需求发现与调研
Objective: Understand customer requirements, technical environment, and business drivers.
Activities:
- Conduct technical discovery calls with stakeholders
- Map customer's current architecture and pain points
- Identify integration requirements and constraints
- Document security and compliance requirements
- Assess competitive landscape for this opportunity
Tools: Use to score initial requirement alignment.
rfp_response_analyzer.pyOutput: Technical discovery document, requirement map, initial coverage assessment.
目标: 了解客户需求、技术环境和业务驱动因素。
活动:
- 与利益相关者开展技术需求发现沟通
- 梳理客户当前架构与痛点
- 识别集成需求与约束条件
- 记录安全与合规要求
- 评估该业务机会下的竞争格局
工具: 使用 对初始需求匹配度进行打分。
rfp_response_analyzer.py输出: 技术需求发现文档、需求映射表、初始覆盖评估报告。
Phase 2: Solution Design
阶段2:解决方案设计
Objective: Design a solution architecture that addresses customer requirements.
Activities:
- Map product capabilities to customer requirements
- Design integration architecture
- Identify customization needs and development effort
- Build competitive differentiation strategy
- Create solution architecture diagrams
Tools: Use to identify differentiators and vulnerabilities.
competitive_matrix_builder.pyOutput: Solution architecture, competitive positioning, technical differentiation strategy.
目标: 设计满足客户需求的解决方案架构。
活动:
- 将产品能力与客户需求进行匹配
- 设计集成架构
- 识别定制需求与开发工作量
- 构建竞品差异化策略
- 创建解决方案架构图
工具: 使用 识别差异化优势与薄弱点。
competitive_matrix_builder.py输出: 解决方案架构、竞品定位、技术差异化策略。
Phase 3: Demo Preparation & Delivery
阶段3:演示准备与交付
Objective: Deliver compelling technical demonstrations tailored to stakeholder priorities.
Activities:
- Build demo environment matching customer's use case
- Create demo script with talking points per stakeholder role
- Prepare objection handling responses
- Rehearse failure scenarios and recovery paths
- Collect feedback and adjust approach
Templates: Use for structured demo preparation.
demo_script_template.mdOutput: Customized demo, stakeholder-specific talking points, feedback capture.
目标: 交付契合利益相关者优先级的有吸引力的技术演示。
活动:
- 搭建匹配客户使用场景的演示环境
- 创建分角色的演示脚本与沟通要点
- 准备异议处理方案
- 演练故障场景与恢复流程
- 收集反馈并调整方案
模板: 使用 进行结构化演示准备。
demo_script_template.md输出: 定制化演示、分角色沟通要点、反馈记录。
Phase 4: POC & Evaluation
阶段4:POC与评估
Objective: Execute a structured proof-of-concept that validates the solution.
Activities:
- Define POC scope, success criteria, and timeline
- Allocate resources and set up environment
- Execute phased testing (core, advanced, edge cases)
- Track progress against success criteria
- Generate evaluation scorecard
Tools: Use to generate the complete POC plan.
poc_planner.pyTemplates: Use for evaluation tracking.
poc_scorecard_template.mdOutput: POC plan, evaluation scorecard, go/no-go recommendation.
目标: 执行结构化的概念验证,验证解决方案的有效性。
活动:
- 定义POC范围、成功标准与时间线
- 分配资源并搭建环境
- 分阶段执行测试(核心功能、高级功能、边缘场景)
- 跟踪进度与成功标准的匹配情况
- 生成评估评分卡
工具: 使用 生成完整的POC计划。
poc_planner.py模板: 使用 进行评估跟踪。
poc_scorecard_template.md输出: POC计划、评估评分卡、执行/终止建议。
Phase 5: Proposal & Closing
阶段5:方案提交与成交
Objective: Deliver a technical proposal that supports the commercial close.
Activities:
- Compile POC results and success metrics
- Create technical proposal with implementation plan
- Address outstanding objections with evidence
- Support pricing and packaging discussions
- Conduct win/loss analysis post-decision
Templates: Use for the proposal document.
technical_proposal_template.mdOutput: Technical proposal, implementation timeline, risk mitigation plan.
目标: 提交支持商业成交的技术方案。
活动:
- 整理POC结果与成功指标
- 创建包含实施计划的技术方案
- 用证据回应未解决的异议
- 支持定价与包装讨论
- 决策后进行赢单/丢单分析
模板: 使用 编写方案文档。
technical_proposal_template.md输出: 技术方案、实施时间线、风险缓解计划。
Python Automation Tools
Python自动化工具
1. RFP Response Analyzer
1. RFP响应分析器
Script:
scripts/rfp_response_analyzer.pyPurpose: Parse RFP/RFI requirements, score coverage, identify gaps, and generate bid/no-bid recommendations.
Coverage Categories:
- Full (100%) - Requirement fully met by current product
- Partial (50%) - Requirement partially met, workaround or configuration needed
- Planned (25%) - On product roadmap, not yet available
- Gap (0%) - Not supported, no current plan
Priority Weighting:
- Must-Have: 3x weight
- Should-Have: 2x weight
- Nice-to-Have: 1x weight
Bid/No-Bid Logic:
- Bid: Coverage score >70% AND must-have gaps <=3
- Conditional Bid: Coverage score 50-70% OR must-have gaps 2-3
- No-Bid: Coverage score <50% OR must-have gaps >3
Usage:
bash
undefined脚本:
scripts/rfp_response_analyzer.py用途: 解析RFP/RFI需求、对覆盖情况打分、识别缺口,并生成投标/不投标建议。
覆盖类别:
- 完全满足(100%) - 需求完全由现有产品满足
- 部分满足(50%) - 需求部分满足,需要变通方案或配置
- 规划中(25%) - 已在产品路线图中,尚未可用
- 缺口(0%) - 不支持,暂无计划
优先级权重:
- 必需项: 3倍权重
- 应该项: 2倍权重
- 可选项: 1倍权重
投标/不投标逻辑:
- 投标: 覆盖评分>70% 且 必需项缺口≤3
- 有条件投标: 覆盖评分50-70% 或 必需项缺口2-3
- 不投标: 覆盖评分<50% 或 必需项缺口>3
使用方法:
bash
undefinedHuman-readable output
人类可读格式输出
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json
JSON output
JSON格式输出
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json
Help
帮助信息
python scripts/rfp_response_analyzer.py --help
**Input Format:** See `assets/sample_rfp_data.json` for the complete schema.python scripts/rfp_response_analyzer.py --help
**输入格式:** 完整 schema 请参考 `assets/sample_rfp_data.json`。2. Competitive Matrix Builder
2. 竞品矩阵构建器
Script:
scripts/competitive_matrix_builder.pyPurpose: Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.
Feature Scoring:
- Full (3) - Complete feature support
- Partial (2) - Partial or limited feature support
- Limited (1) - Minimal or basic feature support
- None (0) - Feature not available
Usage:
bash
undefined脚本:
scripts/competitive_matrix_builder.py用途: 生成功能对比矩阵、计算竞品评分、识别差异化优势与薄弱点。
功能评分:
- 完全支持(3) - 完整的功能支持
- 部分支持(2) - 部分或有限的功能支持
- 有限支持(1) - 最小或基础的功能支持
- 无支持(0) - 功能不可用
使用方法:
bash
undefinedHuman-readable output
人类可读格式输出
python scripts/competitive_matrix_builder.py competitive_data.json
python scripts/competitive_matrix_builder.py competitive_data.json
JSON output
JSON格式输出
python scripts/competitive_matrix_builder.py competitive_data.json --format json
**Output Includes:**
- Feature comparison matrix with scores
- Weighted competitive scores per product
- Differentiators (features where our product leads)
- Vulnerabilities (features where competitors lead)
- Win themes based on differentiatorspython scripts/competitive_matrix_builder.py competitive_data.json --format json
**输出内容包括:**
- 带评分的功能对比矩阵
- 各产品的加权竞品评分
- 差异化优势(我方产品领先的功能)
- 薄弱点(竞品领先的功能)
- 基于差异化优势的赢单主题3. POC Planner
3. POC规划器
Script:
scripts/poc_planner.pyPurpose: Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards.
Default Phase Breakdown:
- Week 1: Setup - Environment provisioning, data migration, configuration
- Weeks 2-3: Core Testing - Primary use cases, integration testing
- Week 4: Advanced Testing - Edge cases, performance, security
- Week 5: Evaluation - Scorecard completion, stakeholder review, go/no-go
Usage:
bash
undefined脚本:
scripts/poc_planner.py用途: 生成结构化的POC计划,包含时间线、资源分配、成功标准和评估评分卡。
默认阶段划分:
- 第1周: 搭建 - 环境部署、数据迁移、配置
- 第2-3周: 核心测试 - 主要使用场景、集成测试
- 第4周: 高级测试 - 边缘场景、性能、安全
- 第5周: 评估 - 完成评分卡、利益相关者评审、执行/终止决策
使用方法:
bash
undefinedHuman-readable output
人类可读格式输出
python scripts/poc_planner.py poc_data.json
python scripts/poc_planner.py poc_data.json
JSON output
JSON格式输出
python scripts/poc_planner.py poc_data.json --format json
**Output Includes:**
- POC plan with phased timeline
- Resource allocation (SE, engineering, customer)
- Success criteria with measurable metrics
- Evaluation scorecard (functionality, performance, integration, usability, support)
- Risk register with mitigation strategies
- Go/No-Go recommendation frameworkpython scripts/poc_planner.py poc_data.json --format json
**输出内容包括:**
- 分阶段时间线的POC计划
- 资源分配(销售工程师、研发、客户)
- 可量化的成功标准
- 评估评分卡(功能、性能、集成、易用性、支持)
- 风险登记册与缓解策略
- 执行/终止建议框架Reference Knowledge Bases
参考知识库
| Reference | Description |
|---|---|
| RFP/RFI response best practices, compliance matrix, bid/no-bid framework |
| Competitive analysis methodology, battlecard creation, objection handling |
| POC planning methodology, success criteria, evaluation frameworks |
| 参考文档 | 描述 |
|---|---|
| RFP/RFI响应最佳实践、合规矩阵、投标/不投标框架 |
| 竞品分析方法论、作战卡片创建、异议处理 |
| POC规划方法论、成功标准、评估框架 |
Asset Templates
资产模板
| Template | Purpose |
|---|---|
| Technical proposal with executive summary, solution architecture, implementation plan |
| Demo script with agenda, talking points, objection handling |
| POC evaluation scorecard with weighted scoring |
| Sample RFP data for testing the analyzer |
| Expected output from rfp_response_analyzer.py |
| 模板 | 用途 |
|---|---|
| 技术方案模板,包含执行摘要、解决方案架构、实施计划 |
| 演示脚本模板,包含议程、沟通要点、异议处理 |
| POC评估评分卡模板,带加权评分 |
| 用于测试分析器的示例RFP数据 |
| |
Communication Style
沟通风格
- Technical yet accessible - Translate complex concepts for business stakeholders
- Confident and consultative - Position as trusted advisor, not vendor
- Evidence-based - Back every claim with data, demos, or case studies
- Stakeholder-aware - Tailor depth and focus to audience (CTO vs. end user vs. procurement)
- 专业且易懂 - 为业务利益相关者翻译复杂概念
- 自信且顾问式 - 定位为可信顾问,而非供应商
- 基于证据 - 所有主张均有数据、演示或案例研究支持
- 关注利益相关者 - 根据受众调整内容深度与重点(CTO vs 终端用户 vs 采购)
Integration Points
集成点
- Marketing Skills - Leverage competitive intelligence and messaging frameworks from
../../marketing-skill/ - Product Team - Coordinate on roadmap items flagged as "Planned" in RFP analysis from
../../product-team/ - C-Level Advisory - Escalate strategic deals requiring executive engagement from
../../c-level-advisor/ - Customer Success - Hand off POC results and success criteria to CSM from
../customer-success-manager/
Last Updated: February 2026
Status: Production-ready
Tools: 3 Python automation scripts
References: 3 knowledge base documents
Templates: 5 asset files
- 营销Skill - 利用 中的竞品情报和消息框架
../../marketing-skill/ - 产品团队 - 与 协调RFP分析中标记为“规划中”的路线图项
../../product-team/ - 高管咨询 - 将需要高管参与的战略交易升级至
../../c-level-advisor/ - 客户成功 - 将POC结果与成功标准移交至 的客户成功经理
../customer-success-manager/
最后更新: 2026年2月
状态: 生产就绪
工具: 3个Python自动化脚本
参考文档: 3份知识库文档
模板: 5个资产文件