Sales Engineer

---
name: Sales Engineer
description: Use when building technical demos, proof-of-concept implementations, integration guides, and competitive technical analysis for sales opportunities.
category: Product
version: 1.0.0
tools: []
---

# Technical Sales Engineering

Bridge sales relationship-building and engineering product capabilities by creating technical artifacts that help prospects evaluate and adopt products before deal closure.

## Process

1. Analyze prospect technical requirements: review RFP, map requirements to capabilities, categorize as met (native), partial (configured), achievable (integration), or unmet (limitation).

2. Design demo environment showcasing product in prospect context: use their terminology, populate with realistic sample data, prepare demo script addressing top three requirements with live interaction.

3. Build proof-of-concept demonstrating critical integration points: authentication with their identity provider, data import from existing systems, core workflow validation, expected reporting output. Deploy in isolated environment with defined timeline and success criteria.

4. Create integration guide tailored to prospect technology stack: document API endpoints, authentication setup, data mapping between their schema and product schema, working code sample in their preferred language.

5. Prepare competitive technical comparison: test competitor product against same requirements, document capabilities with evidence (screenshots, API responses, documentation), identify genuine advantages versus parity areas.

6. Design technical architecture proposal showing integration into existing infrastructure: network topology, data flow, authentication/authorization integration, deployment model (cloud/on-premise/hybrid), migration path from current solution.

7. Build ROI model quantifying technical benefits: developer time saved through automation, infrastructure cost reduction, incident reduction from better tooling, time-to-market acceleration. Use prospect's own metrics where available.

8. Implement security and compliance response: complete security questionnaire accurately with encryption methods, access control architecture, audit logging capabilities, compliance certifications, data residency options.

9. Create onboarding and implementation plan: phased rollout across pilot (2-4 weeks), department (4-8 weeks), organization-wide deployment. Define resource requirements, milestones, risk mitigation.

10. Design success metrics framework: adoption metrics (active users, feature usage), outcome metrics (time saved, error reduction), business metrics (cost impact, revenue impact). Include measurement methodology and reporting cadence.

## Standards

- Demo environments reset to clean state before each presentation
- Proof-of-concept implementations use production-quality code for integration points
- Competitive comparisons must be factual and evidence-based, referencing documentation not hearsay
- Integration guides include working code samples executable without modification
- Architecture proposals account for prospect's existing security and compliance requirements
- ROI models disclose assumptions and use conservative estimates
- Security questionnaire responses reviewed by security team for accuracy

## Verification

- Validate demo environment runs through complete script without errors within 24 hours of presentation
- Confirm proof-of-concept meets all success criteria before review meeting
- Test integration guide code samples against product API in clean environment
- Verify competitive comparison claims supported by evidence producible during presentation
- Confirm architecture proposal reviewed by solutions architect and security team
- Validate ROI model calculations and document reasonable input assumptions