agency-sales-engineer

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

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sammysparks000/skillshare --skill agency-sales-engineer-sammysparks000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-sales-engineer
Source: https://github.com/sammysparks000/skillshare/tree/main/skills/sales-engineer
Command: npx skills add https://github.com/sammysparks000/skillshare --skill agency-sales-engineer-sammysparks000

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: Structured needs analysis plus impact-first demo narratives that quantify the buyer's problem before showing the product, with an explicit "aha moment" target. - POC Scoping & Execution: A ready-to-use POC template with written success criteria, in/out scope boundaries, hard timelines, checkpoints, and a binary GO/NO-GO decision gate. - Competitive Positioning & Objection Handling: FIA-framework (Fact, Impact, Act) battlecards, landmine discovery questions, winning/battling/losing zone analysis, and a decoder for common technical objections. - Use Case: A solutions engineer preparing for a head-to-head evaluation against a competitor uses this Skill to build evaluation notes, design a tailored two-week POC with agreed success criteria, and prepare landmine questions that surface their product's architectural strengths. ## Quick Start Help me scope a two-week proof of concept for a prospect evaluating our product against a competitor, including success criteria and a decision gate.

Frequently Asked Questions about agency-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 get written success criteria agreed with the buyer before starting. Scope aggressively to one critical use case, set a two-to-three-week timeline, and build in a midpoint review checkpoint.

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

Lead with impact, not features: quantify the buyer's problem using discovery specifics, show the end-state outcome first, then reverse into how it works. Tailor the demo to the audience and plan the narrative arc to peak at one clear "aha moment."

What is the FIA framework for competitive battlecards?▼

FIA stands for Fact, Impact, Act. State an objectively true fact about the competitor, explain why it matters to the buyer's business, then define the specific talk track or demo moment to make the point land without attacking the competitor.

How do I handle technical objections in a sales evaluation?▼

Decode the real concern behind the stated question first. "Does it support SSO?" usually means "will this pass security review," so respond to the root concern with architecture detail or benchmark proof rather than a surface-level yes.

When should a POC be considered out of scope or too long?▼

A POC is misscoped when you cannot write its problem statement in one sentence or when success criteria are ambiguous. POCs longer than two to three weeks produce evaluation fatigue rather than better decisions, so defer extra requests to a phase two.