agency-sales-engineer

Structure technical discovery into POC scopes, demo narratives, and competitive battlecards.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-sales-engineer-omeraltn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-sales-engineer
Source: https://github.com/omeraltn/ice_cream_website_testing/tree/main/.antigravity/agency-sales-engineer
Command: npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-sales-engineer-omeraltn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Sales Engineer Agent solves the disconnect between product capabilities and buyer outcomes during complex B2B evaluations by converting technical discovery into decision-focused demos, scoped POCs, and defensible competitive positioning.

Core Features & Use Cases

  • Technical Discovery & Notes: Structured prompts and templates to capture architecture, integration points, security requirements, and decision criteria from stakeholders.
  • Demo Engineering & Narrative: Guidance to craft impact-first demos that create an "aha" moment and map directly to buyer priorities.
  • POC Scoping & Execution Plans: Ready-made POC templates with explicit problem statements, success criteria, timelines, checkpoints, and decision gates.
  • Competitive Technical Positioning: FIA-style battlecards, landmine discovery questions, and reframing talk tracks to win head-to-head evaluations.
  • Objection Handling & Evaluation Management: Tactics for decoding surface objections, producing benchmark evidence, and managing the technical evaluation through to close.
  • Use Case: Run a pre-sales engagement for an enterprise prospect to produce a one-page POC scope, a two-path demo narrative, and a battlecard against the top competitor.

Quick Start

Ask the agent to run a technical discovery for [Account Name], map the top three pain points to product capabilities, and draft a two-week POC with explicit success criteria and decision gates.

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 POC for enterprise B2B pre-sales evaluations?

Scoping a POC for enterprise B2B pre-sales evaluations requires defining explicit problem statements, success criteria, timelines, and decision gates. This process converts technical discovery into a structured proof of concept that aligns directly with buyer priorities.

What is the best way to build a demo narrative for technical buyers?

The best way to build a demo narrative for technical buyers is to craft impact-first demos that create an aha moment mapped directly to buyer outcomes. This approach bridges product capabilities to specific stakeholder decision criteria.

How do I handle technical objections during a software evaluation?

Handling technical objections during a software evaluation involves decoding surface objections, producing benchmark evidence, and managing technical constraints like security and integration. This approach provides defensible talking points to guide evaluations through to close.

Can I generate competitive battlecards for head-to-head technical positioning?

Yes, you can generate competitive battlecards for head-to-head technical positioning using FIA-style frameworks. This includes landmine discovery questions and reframing talk tracks to defensibly differentiate your product against competitors during pre-sales evaluations.

What should be captured during technical discovery for complex software purchases?

Technical discovery for complex software purchases should capture architecture, integration points, security requirements, and decision criteria from stakeholders. This structured information forms the foundation for targeted demos, scoped POCs, and competitive positioning.