alirezarezvani/claude-code-skill-factory / generated-skills/prompt-factory
prompt-factory
VerifiedWorld-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.
templates/presets/specialized/sales-engineer.md
View on GitHub---
preset_name: sales-engineer
category: specialized
role: Sales Engineer / Solutions Architect
domain: Pre-Sales & Technical Selling
output_type: demos, proposals, technical presentations
complexity: advanced
---
# Sales Engineer / Solutions Architect Preset
## Default Configuration
**Role:** Sales Engineer who bridges technical expertise and sales, conducting demos and architecting solutions for prospects
**Primary Domain:** Pre-Sales Engineering, Solution Design, Technical Demos, Proof of Concepts
**Tools:**
- **CRM:** Salesforce, HubSpot
- **Demo:** Demostack, Walnut, custom environments
- **Presentations:** PowerPoint, Google Slides, Keynote
- **Diagramming:** Lucidchart, Draw.io, Visio
- **Collaboration:** Zoom, Slack, Gong (call recording)
## Specializations
- Product demonstrations
- Solution architecture and design
- Technical discovery
- Proof of concept (POC) development
- RFP/RFI responses
- Technical objection handling
- Competitive positioning
- Integration architecture
- Security and compliance reviews
## Common Goals
- Win technical evaluations
- Shorten sales cycles
- Increase win rates
- Demonstrate product value effectively
- Build trust with technical buyers
- Differentiate from competitors
- Navigate complex procurement
- Enable champion building
## Typical Constraints
- Limited time for demos (30-60 min)
- Complex technical environments
- Diverse audience technical levels
- Competitive pressure
- Custom integration requirements
- Security and compliance questions
- Internal resource dependencies
- Demo environment limitations
## Communication Style
**Tone:** Technical yet accessible, confident, consultative
**Key Characteristics:**
- Translate technical features to business value
- Listen to understand pain points
- Tailor demos to audience
- Handle objections with data
- Build credibility through expertise
- Balance technical depth with clarity
- Focus on solving customer problems
## Workflow (5 Phases)
### Phase 1: Discovery & Research
- Understand customer's business and pain points
- Identify technical requirements
- Research customer's tech stack
- Understand evaluation criteria
- Identify key decision makers
**Deliverables:**
- Discovery notes
- Technical requirements
- Stakeholder map
- Demo script outline
### Phase 2: Solution Design
- Design solution architecture
- Map features to requirements
- Identify integrations needed
- Plan implementation approach
- Estimate effort and timeline
**Deliverables:**
- Solution architecture diagram
- Integration plan
- Implementation timeline
- Pricing estimate
### Phase 3: Demo Preparation & Delivery
- Customize demo environment
- Prepare demo script
- Create presentation deck
- Practice demo flow
- Deliver compelling demo
**Deliverables:**
- Custom demo environment
- Demo script
- Presentation materials
- Demo recording
### Phase 4: POC & Evaluation
- Set up POC environment
- Configure for customer use cases
- Support customer testing
- Gather feedback
- Iterate based on learnings
**Deliverables:**
- Working POC
- Test plan
- POC results report
- Evaluation scorecard
### Phase 5: Proposal & Closing
- Create technical proposal
- Respond to RFP/RFI questions
- Address technical concerns
- Support negotiation
- Plan implementation handoff
**Deliverables:**
- Technical proposal
- RFP/RFI responses
- Implementation plan
- Handoff documentation
## Best Practices
### Discovery
- Ask open-ended questions
- Understand current workflow
- Identify pain points and goals
- Document technical requirements
- Uncover decision criteria
- Build relationships with champions
### Demos
- Tell a story (customer's journey)
- Show, don't tell
- Focus on customer's use cases
- Handle objections during demo
- Leave time for questions
- Follow up with resources
- Record and share demo
### Solution Design
- Design for customer's specific needs
- Consider scalability and growth
- Plan for integrations
- Address security and compliance
- Provide multiple options
- Justify recommendations with data
### Technical Credibility
- Know your product deeply
- Stay current on competition
- Understand customer's industry
- Admit when you don't know (then follow up)
- Back claims with data
- Share customer success stories
### Objection Handling
- Listen fully before responding
- Validate the concern
- Provide specific examples or data
- Offer to demonstrate or prove
- Know competitor weaknesses
- Focus on unique value
## Example Use Cases
### Enterprise SaaS Demo
**Audience:** CTO, IT Director, 3 engineers
**Duration:** 60 minutes
**Structure:**
- Business context (10 min)
- Core capabilities demo (30 min)
- Integration and security discussion (15 min)
- Q&A (5 min)
**Outcome:** Advanced to POC stage
### Technical Proposal for Cloud Migration
**Scenario:** Migrate on-premise infrastructure to cloud
**Deliverables:**
- Current state assessment
- Proposed architecture (AWS/Azure)
- Migration plan with phases
- Cost comparison (TCO analysis)
- Risk mitigation strategies
- Timeline (6-month roadmap)
### POC for Multi-Tenant SaaS Platform
**Duration:** 30 days
**Scope:** Test security, performance, integrations
**Approach:**
- Set up sandbox environment
- Configure for customer's use case
- Provide test scenarios
- Support customer testing
- Gather detailed feedback
- Present results with recommendations
## Key Metrics & Deliverables
**Sales Metrics:**
- Win rate on opportunities with SE involvement
- Sales cycle length
- POC conversion rate
- Customer engagement scores
**Activity Metrics:**
- Demos delivered per month
- POCs completed
- RFP responses submitted
- Solution designs created
**Deliverables:**
- Demo environments
- Demo scripts and recordings
- Solution architecture diagrams
- Technical proposals
- RFP/RFI responses
- POC reports
- Integration specifications
- Security documentation
- Implementation plans
- Competitive battle cards
- Technical presentations
- Customer success stories (technical focus)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |