Verified:GitHub

Sales Engineer

Align product capabilities with buyer needs during technical evaluations.

Updated Apr 16, 2026

Search Tags:#discovery #sales-engineering #pre-sales #demo-engineering #solution-architecture #poc-scoping #competitive-battlecards

Ready to run

npx skills add https://github.com/jc180105/.opencode --skill sales-engineer-jc180105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Sales Engineer
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/sales-engineer
Command: npx skills add https://github.com/jc180105/.opencode --skill sales-engineer-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior pre-sales engineers bridge product capabilities to buyer needs, ensuring that technical wins translate into business outcomes and help deals close.

Core Features & Use Cases

Technical Discovery: Structured needs analysis uncovering architecture, integration constraints, and decision criteria.
Demo Engineering: Impact-first demos tailored to specific audiences, highlighting outcomes.
POC Scoping & Execution: Tightly scoped proofs with explicit success criteria and timelines.
Competitive Positioning: FIA-based battlecards and defensible differentiation.
Solution Architecture: Mapping capabilities to buyer infrastructure and deployment patterns.
Evaluation Management: End-to-end ownership from discovery to technical close.

Quick Start

Provide a buyer-specific discovery summary and prepare two demo paths for the upcoming evaluation.

Frequently Asked Questions about Sales Engineer

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

FAQPage Schema

What is technical discovery in pre-sales engineering?▼

Technical discovery in pre-sales engineering is a structured needs analysis that uncovers a buyer's architecture, integration constraints, and decision criteria to align product capabilities with specific business outcomes.

How do I scope a POC for a complex B2B technical evaluation?▼

To scope a POC for a complex B2B technical evaluation, define tightly scoped proofs with explicit success criteria, clear timelines, and mapped solution architecture to ensure technical wins translate into closed deals.

What's the best way to design a product demo for technical buyers?▼

The best way to design a product demo for technical buyers is using impact-first demo engineering tailored to specific audiences, highlighting outcomes rather than features to bridge capabilities to buyer needs.

How do competitive battlecards help in solution architecture positioning?▼

Competitive battlecards help in solution architecture positioning by providing FIA-based defensible differentiation, enabling pre-sales engineers to map capabilities to buyer infrastructure while countering competitors during technical evaluations.

Can I manage the entire technical evaluation process from discovery to close?▼

Yes, you can manage the entire technical evaluation process from discovery to technical close using end-to-end evaluation management, unblocking technical evaluations by aligning product capabilities with buyer infrastructure and deployment patterns.

When do I need pre-sales engineering for a B2B deal?▼

You need pre-sales engineering for a B2B deal when complex technical evaluations require structured discovery, tailored demo design, POC scoping, and solution architecture to ensure technical wins translate into business outcomes.