sales-engineer

Manage pre-sales engineering processes from discovery to technical handoff.

2|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill sales-engineer-canhada-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sales-engineer
Source: https://github.com/Canhada-Labs/ceo-orchestration/tree/main/.claude/skills/domains/sales/skills/sales-engineer
Command: npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill sales-engineer-canhada-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps sales engineers streamline pre-sales engineering processes, ensuring a structured approach to technical discovery, demo design, and competitive analysis, leading to more effective technical sales handoffs.

Core Features & Use Cases

  • Structured Discovery: Facilitates a comprehensive architectural, integration, security, and regulatory discovery process.
  • Demo Engineering Discipline: Guides the creation of audience-specific, outcome-driven demo narratives.
  • POC Scoping: Defines and manages proof-of-concept acceptance criteria, timelines, and data protocols.
  • Battlecard Structure: Develops competitive battlecards with factual differentiators and proof artifacts.
  • Technical Win Discipline: Ensures technical wins are documented with reference customers and success criteria.
  • Cross-team Handoff: Facilitates a structured technical handoff to delivery teams, including all necessary artifacts.
  • Anti-patterns and Best Practices: Offers guidance on avoiding common pitfalls in technical sales engagements.

Quick Start

Initiate the sales-engineering process by loading the skill and providing the necessary technical context and discovery notes.

Frequently Asked Questions about sales-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure technical discovery for B2B pre-sales engineering?

Pre-sales engineering discovery is structured by evaluating architectural, integration, security, and regulatory requirements. This ensures comprehensive technical context gathering before progressing to demo design and proof-of-concept scoping.

What is the best way to scope a proof of concept for technical sales?

Scoping a technical sales proof of concept requires defining explicit acceptance criteria, timelines, and data protocols. This structured approach ensures POC evaluations remain bounded and directly validate the targeted technical win.

How do I design audience-specific demo narratives for technical sales?

Audience-specific demo narratives are designed using an outcome-driven discipline that tailors technical presentations to the specific stakeholders. This ensures the demonstration directly addresses the architectural needs of the evaluation.

Can I use this for B2B technical sales scenarios involving complex product evaluations?

Yes, this framework is specifically designed for B2B technical sales scenarios involving complex product evaluations. It manages the full pre-sales lifecycle from initial discovery through to the final cross-team technical handoff.

How do you create competitive battlecards with factual differentiators?

Competitive battlecards are created by documenting factual product differentiators alongside concrete proof artifacts. This structure provides technical sales teams with verifiable evidence to counter competitors during complex evaluations.

What are common pre-sales anti-patterns in technical sales engagements?

Common technical sales engagement anti-patterns include unstructured discovery and poorly defined POC acceptance criteria. This framework provides explicit best practices to avoid these pitfalls and ensure a clean technical handoff to delivery teams.