Sales Engineer

Guides technical discovery, demo engineering, POC scoping, and competitive positioning for B2B sales evaluations.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill sales-engineer-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Sales Engineer
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/sales/sales-engineer
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill sales-engineer-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pre-sales teams often lose winnable deals because demos become feature dumps, POCs suffer scope creep, and competitive positioning relies on FUD instead of facts. This Skill provides a structured methodology for running technical evaluations that connect product capabilities to business outcomes and drive deals to a decision. ## Core Features & Use Cases - Technical Discovery & Demo Engineering: Run structured needs analysis and design impact-first demos tailored to the audience, with a planned "aha moment" for each buyer. - POC Scoping & Execution: Define written success criteria, tight scope, hard timelines, and decision gates using a ready-to-use POC template. - Competitive Positioning: Build FIA-framework (Fact, Impact, Act) battlecards, deploy landmine discovery questions, and map winning/battling/losing zones per competitor. - Use Case: A solutions engineer preparing for a head-to-head evaluation against a competitor uses this Skill to structure discovery notes, script a tailored demo narrative, scope a two-week POC with explicit pass/fail criteria, and prepare objection-handling responses for security and scale concerns. ## Quick Start Act as a Sales Engineer and help me scope a proof of concept for a prospect evaluating our product against a competitor, including success criteria, timeline, and decision gates.

Frequently Asked Questions about Sales Engineer

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

FAQPage Schema
How do I scope a proof of concept for a B2B software deal?▼

Start with a one-sentence problem statement defining what the POC will prove, then write explicit pass/fail success criteria agreed with the buyer before starting. Scope aggressively to one core use case, set a two-to-three-week timeline, and include a midpoint review plus a final decision gate.

How to structure a sales demo that wins technical evaluations?▼

Lead with the quantified problem from discovery, show the end-state outcome first, then reverse into how it works, and close with a relevant customer proof point. Tailor the narrative to the audience and plan a specific "aha moment" where the buyer sees their exact problem solved.

What is the FIA framework for competitive battlecards?▼

FIA stands for Fact, Impact, Act: state an objectively true fact about the competitor, explain its business impact on the buyer, then define the specific talk track or demo action. This keeps positioning fact-based and credible instead of relying on FUD.

How do I handle technical objections like SSO or scalability concerns?▼

Decode the real concern behind the surface question: "does it support SSO" usually means "will this pass security review." Respond to the root issue with full architecture walkthroughs or benchmark data from comparable customers rather than checkbox answers.

When should I avoid attacking a competitor in a technical evaluation?▼

Never trash competitors directly; acknowledge their genuine strengths, then articulate differentiation tied to the buyer's specific requirements. For criteria where the competitor is stronger, acknowledge it and reframe around the buyer's primary long-term priorities.