Sales Engineer
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and...
Install
npx skills add borghei/Claude-Skills --skill sales-engineer -g -a claude-code -y- Repository
- borghei/Claude-Skills1k
- Category
- Business
- Updated
- 12d ago
- License
- MIT + Commons Clause
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering
Sales Engineer 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.
Overview
Role: Sales Engineer / Solutions Architect Domain: Pre-Sales Engineering, Solution Design, Technical Demos, Proof of Concepts Business Type: SaaS / Pre-Sales Engineering
What This Skill Does
- 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
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% |
Clarify First
Before producing the deliverable, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
