Sales AI Skill
Sales Engineering Partnership
Optimize the partnership between Account Executives and Solutions Engineers to improve deal quality, technical credibility, and win rates. Use when aligning AE-SE workflows, defining pre-sales responsibilities, improving demo effectiveness, managing SE capacity, or measuring technical sales effectiveness. Triggers on phrases like "sales engineering", "SE partnership", "AE-SE alignment", "pre-sales workflow", "demo effectiveness", "SE capacity", "technical sales", "solution engineering", "pre-sales process", "AE SE collaboration".
Sales Engineering Partnership & Alignment
Optimize the partnership between Account Executives (AEs) and Solutions Engineers (SEs) — ensuring technical credibility, efficient resource utilization, and higher win rates across the sales cycle.
Workflow
- Define AE and SE roles and responsibilities at each deal stage.
- Establish engagement model: When SE joins, what they do, decision criteria.
- Create joint discovery and demo preparation process.
- Implement SE capacity management and deal prioritization.
- Build feedback loop: SE insights → product, deal learnings → enablement.
- Measure SE effectiveness: win rate impact, time allocation, revenue influence.
- Conduct regular alignment meetings and process reviews.
- Train AEs on technical selling; train SEs on business acumen.
Role Definition and Engagement Model
AE vs SE RESPONSIBILITIES BY DEAL STAGE
==========================================
Stage 1 — Prospecting (AE-only):
════════════════════════════════════════════════════════════════════════
AE Responsibilities:
→ Identify and qualify target accounts
→ Initial outreach and interest generation
→ BANT qualification (budget, authority, need, timeline)
→ Schedule discovery call
SE Involvement: None at this stage
Stage 2 — Discovery (Joint):
════════════════════════════════════════════════════════════════════════
AE Responsibilities:
→ Lead business conversation (goals, challenges, success metrics)
→ Understand decision process and stakeholders
→ Manage meeting flow and next steps
SE Responsibilities:
→ Technical discovery (current stack, integrations, requirements)
→ Identify technical risks and concerns
→ Document technical requirements
→ Assess technical fit and feasibility
Stage 3 — Demo / Solution Presentation (Joint):
════════════════════════════════════════════════════════════════════════
AE Responsibilities:
→ Open meeting: Set agenda, introduce SE
→ Connect solution to business outcomes
→ Handle commercial and procurement discussions
→ Manage objections (commercial, timeline, competitive)
SE Responsibilities:
→ Lead product demonstration (tailored to customer use case)
→ Address technical questions in depth
→ Show integration capabilities and architecture
→ Provide technical proof points and evidence
Stage 4 — POC / Proof of Concept (SE-led, AE-supported):
════════════════════════════════════════════════════════════════════════
SE Responsibilities:
→ Design POC scope and success criteria
→ Execute POC setup and configuration
→ Train customer on POC environment
→ Monitor POC progress and address issues
AE Responsibilities:
→ Manage customer expectations and timeline
→ Ensure executive stakeholders engaged
→ Track POC to business value alignment
→ Prepare for POC review and next steps
Stage 5 — Proposal and Negotiation (AE-led, SE-supported):
════════════════════════════════════════════════════════════════════════
AE Responsibilities:
→ Lead commercial negotiation
→ Manage procurement and legal processes
→ Handle pricing, terms, and discounts
SE Responsibilities:
→ Provide technical documentation (architecture, integration plans)
→ Answer technical RFP questions
→ Support technical risk mitigation discussions
→ Attend final technical review meetings
STAGE-BY-STAGE OWNERSHIP MATRIX:
════════════════════════════════════════════════════════════════════════
Stage | AE Lead | SE Lead | Joint
════════════════════════════════════════════════════════════════════════
Prospecting | ✓ | |
Discovery | | | ✓
Demo | | ✓ | ✓ (presentation)
POC | | ✓ | ✓ (management)
Proposal | ✓ | |
Negotiation | ✓ | | ✓ (technical)
Close | ✓ | |
════════════════════════════════════════════════════════════════════════
SE Capacity Management
SE CAPACITY PLANNING
======================
SE Time Allocation (Ideal):
════════════════════════════════════════════════════════════════════════
Activity | % of Time | Hours/Week (40hr week)
════════════════════════════════════════════════════════════════════════
Active deals (demo, discovery)| 40% | 16 hours
POC execution | 15% | 6 hours
Deal preparation | 15% | 6 hours
Proposals and RFPs | 10% | 4 hours
Enablement and content | 10% | 4 hours
Admin and internal meetings | 10% | 4 hours
════════════════════════════════════════════════════════════════════════
SE-to-AE Ratio:
→ Industry standard: 1 SE per 3–5 AEs
→ Enterprise sales: 1 SE per 2–3 AEs (more complex deals)
→ SMB/PLG sales: 1 SE per 8–12 AEs (simpler, self-serve demos)
→ Our target: 1 SE per 4 AEs (balanced for mid-market focus)
Deal Prioritization Framework:
════════════════════════════════════════════════════════════════════════
Priority | Criteria | SE Commitment
════════════════════════════════════════════════════════════════════════
P1 | Enterprise, > $100K, champion | Full engagement
P2 | Mid-market, $50K–$100K | Standard engagement
P3 | SMB, < $50K | Limited (recorded demo)
P4 | Unqualified, exploratory | No SE involvement
════════════════════════════════════════════════════════════════════════
SE UTILIZATION TRACKING:
→ Target utilization: 70–80% (leaves capacity for enablement and prep)
→ Over-utilized (> 90%): Risk of burnout, quality degradation
→ Under-utilized (< 60%): Opportunity for more deal support or content creation
→ Monthly review: SE deal count, time allocation, revenue influenced
Demo Effectiveness
DEMO BEST PRACTICES
=====================
Demo Preparation Checklist:
→ Discovery completed: Understand customer use case, pain points, goals
→ Tailored demo: Show ONLY features relevant to THIS customer (not full product tour)
→ Story structure: Problem → Agitation → Solution (our product) → Result
→ Environment: Clean demo environment, realistic data, customer industry
→ Tech check: Internet, screen sharing, audio working 10 minutes before
→ Roles clear: AE introduces, SE demos, AE closes with next steps
→ Backup plan: Recorded demo available if technical issues occur
Demo Structure (45 minutes):
════════════════════════════════════════════════════════════════════════
Time | Section | Owner | Content
════════════════════════════════════════════════════════════════════════
0–5 min | Introduction | AE | Agenda, customer context, goals
5–10 min| Current challenges | AE | Recap discovery, confirm pain points
10–25 min| Demo (part 1) | SE | Core features addressing primary pain
25–35 min| Demo (part 2) | SE | Advanced features, integrations
35–40 min| Q&A | Both | Address questions and concerns
40–45 min| Next steps | AE | Summary, POC proposal, timeline
════════════════════════════════════════════════════════════════════════
Demo Effectiveness Metrics:
════════════════════════════════════════════════════════════════════════
Metric | Target | Current
════════════════════════════════════════════════════════════════════════
Demo-to-proposal conversion | > 60% | 55%
Demo-to-close win rate | > 35% | 30%
Customer engagement (Q&A) | > 5 questions| 4 questions
Stakeholder attendance | > 3 stakeholders| 2.5
Post-demo satisfaction | > 4.0/5.0 | 3.8/5.0
════════════════════════════════════════════════════════════════════════
Integration Points
- CRM (Salesforce, HubSpot): Deal tracking, SE assignment, activity logging
- Demo Platform (Gong, DemoPad, Reveals): Demo recording, playback, analysis
- Communication (Zoom, Google Meet): Virtual demos, discovery calls, POC sessions
- Sandbox/POC Environment: Isolated product instances for customer testing
- Documentation (Confluence, Notion): Technical documentation, architecture templates
- Enablement (Gong, Highspot, Seismic): Demo training, best practices, coaching
- Analytics (Tableau, Power BI): SE utilization, deal influence, win rate analysis
- Product Team: SE feedback loop, feature requests, technical roadmap alignment
Edge Cases
- SE bottleneck: Too many deals, SE can't cover all requests
- Prioritization: Enforce deal priority framework; decline P3/P4 SE requests
- Self-serve: Recorded demos and interactive sandbox for lower-priority deals
- AE empowerment: Train AEs to handle basic demos without SE
- Hiring: Scale SE team proportional to AE growth
- Temporary: Contract SEs during peak periods
- AE doesn't prepare SE for discovery: SE arrives unprepared
- Process: AE must share discovery briefing 24 hours before SE involvement
- Template: Standard discovery brief (company, contacts, pain points, goals)
- Quality check: SE can decline meeting if briefing insufficient
- Accountability: Manager enforces preparation standard
- Culture: "No briefing, no SE" — mutual respect for time
- SE says "yes" to impossible technical requirements: Over-promising to save deal
- Training: SE trained on product boundaries and realistic timelines
- Escalation: SE can escalate to product team before committing
- Documentation: All commitments documented in proposal (not verbal)
- Post-sale: SE briefs implementation team on all commitments
- Accountability: SE performance measured on delivery, not just deal win
- AE and SE conflict on deal strategy: Different approaches to same deal
- Resolution: Manager mediates; data-driven decision
- Alignment meeting: Pre-deal strategy session (AE + SE + manager)
- Clear roles: AE owns commercial; SE owns technical — respect boundaries
- Joint accountability: Both responsible for deal outcome (shared metrics)
- Feedback: Post-deal retrospective to improve future alignment
Disclaimer: All rights reserved by Circulos AI. These skills are specifically designed for Claude Code, Claude Cowork, Codex, and OpenClaw. When using or referencing any skill, please provide proper attribution to Circulos AI.