Sales Engineer Skill
Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/sales-engineer-3, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/business-growth/skills/sales-engineer#main ~/.claude/skills/sales-engineer-3For one project only, change the path to .claude/skills/sales-engineer-3. This skill also uses rfp_response_analyzer.py, phase1_rfp_results.json, competitive_matrix_builder.py, competitive_data.json, phase2_competitive.json, poc_planner.py — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Sales Engineer Skill
Show the full text226 lines
| name | description |
|---|---|
| sales-engineer | Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'. |
Sales Engineer Skill
5-Phase Workflow
Phase 1: Discovery & Research
Objective: Understand customer requirements, technical environment, and business drivers.
Checklist:
- 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: Run rfp_response_analyzer.py to score initial requirement alignment.
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json > phase1_rfp_results.json
Output: Technical discovery document, requirement map, initial coverage assessment.
Validation checkpoint: Coverage score must be >50% and must-have gaps ≤3 before proceeding to Phase 2. Check with:
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json | python -c "import sys,json; r=json.load(sys.stdin); print('PROCEED' if r['coverage_score']>50 and r['must_have_gaps']<=3 else 'REVIEW')"
Phase 2: Solution Design
Objective: Design a solution architecture that addresses customer requirements.
Checklist:
- Map product capabilities to customer requirements
- Design integration architecture
- Identify customization needs and development effort
- Build competitive differentiation strategy
- Create solution architecture diagrams
Tools: Run competitive_matrix_builder.py using Phase 1 data to identify differentiators and vulnerabilities.
python scripts/competitive_matrix_builder.py competitive_data.json --format json > phase2_competitive.json
python -c "import json; d=json.load(open('phase2_competitive.json')); print('Differentiators:', d['differentiators']); print('Vulnerabilities:', d['vulnerabilities'])"
Output: Solution architecture, competitive positioning, technical differentiation strategy.
Validation checkpoint: Confirm at least one strong differentiator exists per customer priority before proceeding to Phase 3. If no differentiators found, escalate to Product Team (see Integration Points).
Phase 3: Demo Preparation & Delivery
Objective: Deliver compelling technical demonstrations tailored to stakeholder priorities.
Checklist:
- 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 assets/demo_script_template.md for structured demo preparation.
Output: Customized demo, stakeholder-specific talking points, feedback capture.
Validation checkpoint: Demo script must cover every must-have requirement flagged in phase1_rfp_results.json before delivery. Cross-reference with:
python -c "import json; rfp=json.load(open('phase1_rfp_results.json')); [print('UNCOVERED:', r) for r in rfp['must_have_requirements'] if r['coverage']=='Gap']"
Phase 4: POC & Evaluation
Objective: Execute a structured proof-of-concept that validates the solution.
Checklist:
- 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: Run poc_planner.py to generate the complete POC plan.
python scripts/poc_planner.py poc_data.json --format json > phase4_poc_plan.json
python -c "import json; p=json.load(open('phase4_poc_plan.json')); print('Go/No-Go:', p['recommendation'])"
Templates: Use assets/poc_scorecard_template.md for evaluation tracking.
Output: POC plan, evaluation scorecard, go/no-go recommendation.
Validation checkpoint: POC conversion requires scorecard score >60% across all evaluation dimensions (functionality, performance, integration, usability, support). If score <60%, document gaps and loop back to Phase 2 for solution redesign.
Phase 5: Proposal & Closing
Objective: Deliver a technical proposal that supports the commercial close.
Checklist:
- 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 assets/technical_proposal_template.md for the proposal document.
Output: Technical proposal, implementation timeline, risk mitigation plan.
Python Automation Tools
1. RFP Response Analyzer
Script: scripts/rfp_response_analyzer.py
Purpose: Parse RFP/RFI requirements, score coverage, identify gaps, and generate bid/no-bid recommendations.
Coverage Categories: Full (100%), Partial (50%), Planned (25%), Gap (0%).
Priority Weighting: Must-Have 3×, Should-Have 2×, Nice-to-Have 1×.
Bid/No-Bid Logic:
- Bid: Coverage >70% AND must-have gaps ≤3
- Conditional Bid: Coverage 50–70% OR must-have gaps 2–3
- No-Bid: Coverage <50% OR must-have gaps >3
Usage:
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json # human-readable
python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json # JSON output
python scripts/rfp_response_analyzer.py --help
Input Format: See assets/sample_rfp_data.json for the complete schema.
2. Competitive Matrix Builder
Script: scripts/competitive_matrix_builder.py
Purpose: Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities.
Feature Scoring: Full (3), Partial (2), Limited (1), None (0).
Usage:
python scripts/competitive_matrix_builder.py competitive_data.json # human-readable
python scripts/competitive_matrix_builder.py competitive_data.json --format json # JSON output
Output Includes: Feature comparison matrix, weighted competitive scores, differentiators, vulnerabilities, and win themes.
3. POC Planner
Script: scripts/poc_planner.py
Purpose: 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:
python scripts/poc_planner.py poc_data.json # human-readable
python scripts/poc_planner.py poc_data.json --format json # JSON output
Output Includes: Phased POC plan, resource allocation, success criteria, evaluation scorecard, risk register, and go/no-go recommendation framework.
Reference Knowledge Bases
| Reference | Description |
|---|---|
references/rfp-response-guide.md |
RFP/RFI response best practices, compliance matrix, bid/no-bid framework |
references/competitive-positioning-framework.md |
Competitive analysis methodology, battlecard creation, objection handling |
references/poc-best-practices.md |
POC planning methodology, success criteria, evaluation frameworks |
Asset Templates
| Template | Purpose |
|---|---|
assets/technical_proposal_template.md |
Technical proposal with executive summary, solution architecture, implementation plan |
assets/demo_script_template.md |
Demo script with agenda, talking points, objection handling |
assets/poc_scorecard_template.md |
POC evaluation scorecard with weighted scoring |
assets/sample_rfp_data.json |
Sample RFP data for testing the analyzer |
assets/expected_output.json |
Expected output from rfp_response_analyzer.py |
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
| 1 | |
| 2 | name "sales-engineer" |
| 3 | description Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'. |
| 4 | |
| 5 | |
| 6 | # Sales Engineer Skill |
| 7 | |
| 8 | ## 5-Phase Workflow |
| 9 | |
| 10 | ### Phase 1: Discovery & Research |
| 11 | |
| 12 | **Objective:** Understand customer requirements, technical environment, and business drivers. |
| 13 | |
| 14 | **Checklist:** |
| 15 | [ ] Conduct technical discovery calls with stakeholders |
| 16 | [ ] Map customer's current architecture and pain points |
| 17 | [ ] Identify integration requirements and constraints |
| 18 | [ ] Document security and compliance requirements |
| 19 | [ ] Assess competitive landscape for this opportunity |
| 20 | |
| 21 | **Tools:** Run `rfp_response_analyzer.py` to score initial requirement alignment. |
| 22 | |
| 23 | |
| 24 | python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json > phase1_rfp_results.json |
| 25 | |
| 26 | |
| 27 | **Output:** Technical discovery document, requirement map, initial coverage assessment. |
| 28 | |
| 29 | **Validation checkpoint:** Coverage score must be >50% and must-have gaps ≤3 before proceeding to Phase 2. Check with: |
| 30 | |
| 31 | python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json | python -c "import sys,json; r=json.load(sys.stdin); print('PROCEED' if r['coverage_score']>50 and r['must_have_gaps']<=3 else 'REVIEW')" |
| 32 | |
| 33 | |
| 34 | |
| 35 | |
| 36 | ### Phase 2: Solution Design |
| 37 | |
| 38 | **Objective:** Design a solution architecture that addresses customer requirements. |
| 39 | |
| 40 | **Checklist:** |
| 41 | [ ] Map product capabilities to customer requirements |
| 42 | [ ] Design integration architecture |
| 43 | [ ] Identify customization needs and development effort |
| 44 | [ ] Build competitive differentiation strategy |
| 45 | [ ] Create solution architecture diagrams |
| 46 | |
| 47 | **Tools:** Run `competitive_matrix_builder.py` using Phase 1 data to identify differentiators and vulnerabilities. |
| 48 | |
| 49 | |
| 50 | python scripts/competitive_matrix_builder.py competitive_data.json --format json > phase2_competitive.json |
| 51 | |
| 52 | python -c "import json; d=json.load(open('phase2_competitive.json')); print('Differentiators:', d['differentiators']); print('Vulnerabilities:', d['vulnerabilities'])" |
| 53 | |
| 54 | |
| 55 | **Output:** Solution architecture, competitive positioning, technical differentiation strategy. |
| 56 | |
| 57 | **Validation checkpoint:** Confirm at least one strong differentiator exists per customer priority before proceeding to Phase 3. If no differentiators found, escalate to Product Team (see Integration Points). |
| 58 | |
| 59 | |
| 60 | |
| 61 | ### Phase 3: Demo Preparation & Delivery |
| 62 | |
| 63 | **Objective:** Deliver compelling technical demonstrations tailored to stakeholder priorities. |
| 64 | |
| 65 | **Checklist:** |
| 66 | [ ] Build demo environment matching customer's use case |
| 67 | [ ] Create demo script with talking points per stakeholder role |
| 68 | [ ] Prepare objection handling responses |
| 69 | [ ] Rehearse failure scenarios and recovery paths |
| 70 | [ ] Collect feedback and adjust approach |
| 71 | |
| 72 | **Templates:** Use `assets/demo_script_template.md` for structured demo preparation. |
| 73 | |
| 74 | **Output:** Customized demo, stakeholder-specific talking points, feedback capture. |
| 75 | |
| 76 | **Validation checkpoint:** Demo script must cover every must-have requirement flagged in `phase1_rfp_results.json` before delivery. Cross-reference with: |
| 77 | |
| 78 | python -c "import json; rfp=json.load(open('phase1_rfp_results.json')); [print('UNCOVERED:', r) for r in rfp['must_have_requirements'] if r['coverage']=='Gap']" |
| 79 | |
| 80 | |
| 81 | |
| 82 | |
| 83 | ### Phase 4: POC & Evaluation |
| 84 | |
| 85 | **Objective:** Execute a structured proof-of-concept that validates the solution. |
| 86 | |
| 87 | **Checklist:** |
| 88 | [ ] Define POC scope, success criteria, and timeline |
| 89 | [ ] Allocate resources and set up environment |
| 90 | [ ] Execute phased testing (core, advanced, edge cases) |
| 91 | [ ] Track progress against success criteria |
| 92 | [ ] Generate evaluation scorecard |
| 93 | |
| 94 | **Tools:** Run `poc_planner.py` to generate the complete POC plan. |
| 95 | |
| 96 | |
| 97 | python scripts/poc_planner.py poc_data.json --format json > phase4_poc_plan.json |
| 98 | |
| 99 | python -c "import json; p=json.load(open('phase4_poc_plan.json')); print('Go/No-Go:', p['recommendation'])" |
| 100 | |
| 101 | |
| 102 | **Templates:** Use `assets/poc_scorecard_template.md` for evaluation tracking. |
| 103 | |
| 104 | **Output:** POC plan, evaluation scorecard, go/no-go recommendation. |
| 105 | |
| 106 | **Validation checkpoint:** POC conversion requires scorecard score >60% across all evaluation dimensions (functionality, performance, integration, usability, support). If score <60%, document gaps and loop back to Phase 2 for solution redesign. |
| 107 | |
| 108 | |
| 109 | |
| 110 | ### Phase 5: Proposal & Closing |
| 111 | |
| 112 | **Objective:** Deliver a technical proposal that supports the commercial close. |
| 113 | |
| 114 | **Checklist:** |
| 115 | [ ] Compile POC results and success metrics |
| 116 | [ ] Create technical proposal with implementation plan |
| 117 | [ ] Address outstanding objections with evidence |
| 118 | [ ] Support pricing and packaging discussions |
| 119 | [ ] Conduct win/loss analysis post-decision |
| 120 | |
| 121 | **Templates:** Use `assets/technical_proposal_template.md` for the proposal document. |
| 122 | |
| 123 | **Output:** Technical proposal, implementation timeline, risk mitigation plan. |
| 124 | |
| 125 | |
| 126 | |
| 127 | ## Python Automation Tools |
| 128 | |
| 129 | ### 1. RFP Response Analyzer |
| 130 | |
| 131 | **Script:** `scripts/rfp_response_analyzer.py` |
| 132 | |
| 133 | **Purpose:** Parse RFP/RFI requirements, score coverage, identify gaps, and generate bid/no-bid recommendations. |
| 134 | |
| 135 | **Coverage Categories:** Full (100%), Partial (50%), Planned (25%), Gap (0%). |
| 136 | **Priority Weighting:** Must-Have 3×, Should-Have 2×, Nice-to-Have 1×. |
| 137 | |
| 138 | **Bid/No-Bid Logic:** |
| 139 | **Bid:** Coverage >70% AND must-have gaps ≤3 |
| 140 | **Conditional Bid:** Coverage 50–70% OR must-have gaps 2–3 |
| 141 | **No-Bid:** Coverage <50% OR must-have gaps >3 |
| 142 | |
| 143 | **Usage:** |
| 144 | |
| 145 | python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json # human-readable |
| 146 | python scripts/rfp_response_analyzer.py assets/sample_rfp_data.json --format json # JSON output |
| 147 | python scripts/rfp_response_analyzer.py --help |
| 148 | |
| 149 | |
| 150 | **Input Format:** See `assets/sample_rfp_data.json` for the complete schema. |
| 151 | |
| 152 | |
| 153 | |
| 154 | ### 2. Competitive Matrix Builder |
| 155 | |
| 156 | **Script:** `scripts/competitive_matrix_builder.py` |
| 157 | |
| 158 | **Purpose:** Generate feature comparison matrices, calculate competitive scores, identify differentiators and vulnerabilities. |
| 159 | |
| 160 | **Feature Scoring:** Full (3), Partial (2), Limited (1), None (0). |
| 161 | |
| 162 | **Usage:** |
| 163 | |
| 164 | python scripts/competitive_matrix_builder.py competitive_data.json # human-readable |
| 165 | python scripts/competitive_matrix_builder.py competitive_data.json --format json # JSON output |
| 166 | |
| 167 | |
| 168 | **Output Includes:** Feature comparison matrix, weighted competitive scores, differentiators, vulnerabilities, and win themes. |
| 169 | |
| 170 | |
| 171 | |
| 172 | ### 3. POC Planner |
| 173 | |
| 174 | **Script:** `scripts/poc_planner.py` |
| 175 | |
| 176 | **Purpose:** Generate structured POC plans with timeline, resource allocation, success criteria, and evaluation scorecards. |
| 177 | |
| 178 | **Default Phase Breakdown:** |
| 179 | **Week 1:** Setup — environment provisioning, data migration, configuration |
| 180 | **Weeks 2–3:** Core Testing — primary use cases, integration testing |
| 181 | **Week 4:** Advanced Testing — edge cases, performance, security |
| 182 | **Week 5:** Evaluation — scorecard completion, stakeholder review, go/no-go |
| 183 | |
| 184 | **Usage:** |
| 185 | |
| 186 | python scripts/poc_planner.py poc_data.json # human-readable |
| 187 | python scripts/poc_planner.py poc_data.json --format json # JSON output |
| 188 | |
| 189 | |
| 190 | **Output Includes:** Phased POC plan, resource allocation, success criteria, evaluation scorecard, risk register, and go/no-go recommendation framework. |
| 191 | |
| 192 | |
| 193 | |
| 194 | ## Reference Knowledge Bases |
| 195 | |
| 196 | | Reference | Description | |
| 197 | |-----------|-------------| |
| 198 | | `references/rfp-response-guide.md` | RFP/RFI response best practices, compliance matrix, bid/no-bid framework | |
| 199 | | `references/competitive-positioning-framework.md` | Competitive analysis methodology, battlecard creation, objection handling | |
| 200 | | `references/poc-best-practices.md` | POC planning methodology, success criteria, evaluation frameworks | |
| 201 | |
| 202 | ## Asset Templates |
| 203 | |
| 204 | | Template | Purpose | |
| 205 | |----------|---------| |
| 206 | | `assets/technical_proposal_template.md` | Technical proposal with executive summary, solution architecture, implementation plan | |
| 207 | | `assets/demo_script_template.md` | Demo script with agenda, talking points, objection handling | |
| 208 | | `assets/poc_scorecard_template.md` | POC evaluation scorecard with weighted scoring | |
| 209 | | `assets/sample_rfp_data.json` | Sample RFP data for testing the analyzer | |
| 210 | | `assets/expected_output.json` | Expected output from rfp_response_analyzer.py | |
| 211 | |
| 212 | ## Integration Points |
| 213 | |
| 214 | **Marketing Skills** - Leverage competitive intelligence and messaging frameworks from `marketing-skill/` |
| 215 | **Product Team** - Coordinate on roadmap items flagged as "Planned" in RFP analysis from `product-team/` |
| 216 | **C-Level Advisory** - Escalate strategic deals requiring executive engagement from `c-level-advisor/` |
| 217 | **Customer Success** - Hand off POC results and success criteria to CSM from `../customer-success-manager/` |
| 218 | |
| 219 | |
| 220 | |
| 221 | **Last Updated:** February 2026 |
| 222 | **Status:** Production-ready |
| 223 | **Tools:** 3 Python automation scripts |
| 224 | **References:** 3 knowledge base documents |
| 225 | **Templates:** 5 asset files |
| 226 |
Discussion
Client Proposal Generator for Marketing ServicesPaste your rough notes about the client and what you'd do for them, and get back a polished, ready-to-send proposal with pricing tiers and next steps.Sales materials that help you close dealsTell us what you sell and who buys it; get back a pitch outline, a one-page leave-behind, and ready answers to the objections you hear most.Business & Growth Skills — RouterRouter/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').Quote postTwo-step workflow for creating quote posts on LinkedIn. The assistant drafts original short quotes to accompany a caption, then produces a Gemini prompt that recreates a reference image with the chosen quote baked in. Use this skill whenever the user says "quote post", "quote graphic", "motivational post", "build me a quote", or wants a low-effort high-engagement LinkedIn graphic. Optimised for LinkedIn's employee and early-career audience, which skews toward motivational content.
Browse more free Claude skills or everything in Sales.