sales-engineer

Position product capabilities and trade-offs for pre-sales customer questions.

22|2|Updated Mar 24, 2026

Search Tags:#sales #tradeoffs #customer-communication #pre-sales #solution-architecture #technical-positioning

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides accurate, customer-facing guidance for pre-sales decisions, ensuring technical clarity without overpromising capabilities.

Core Features & Use Cases

Evidence-backed technical positioning for customer questions and evaluation criteria.
Clear mapping of customer use cases to supported product capabilities, constraints, and deployment prerequisites.
Structured approach to tradeoffs, prerequisites, and risk considerations for demos, POCs, or trials.

Quick Start

Describe a customer use case and propose a concise, technically grounded solution narrative that aligns with current product limits.

Frequently Asked Questions about sales-engineer

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

FAQPage Schema

How do I prepare technical positioning for pre-sales customer questions?▼

Pre-sales technical positioning requires mapping customer use cases to supported product capabilities and constraints. You structure evidence-backed claims, identify deployment prerequisites, and define success criteria for demos or POCs to ensure technical clarity without overpromising.

What is the best way to handle tradeoffs in solution architecture during customer communication?▼

Handling solution architecture tradeoffs in customer communication involves applying a structured approach to constraints, prerequisites, and risk considerations. You align current product limits with the customer's evaluation criteria to provide a concise, technically grounded solution narrative.

How do I define success criteria for a POC or product trial?▼

Defining success criteria for a POC or trial involves identifying deployment prerequisites and mapping customer use cases to supported capabilities. This structured approach ensures all claims remain evidence-backed and clarifies exact product constraints before the evaluation begins.

Can I use this approach for pre-sales conversations about product integrations and deployment prerequisites?▼

Yes, this approach applies directly to pre-sales conversations across product integrations, architecture choices, and deployment prerequisites. It ensures claims are evidence-backed and accurately maps customer requirements to current product limits.

How do I map customer use cases to supported product capabilities without overpromising?▼

Mapping customer use cases to supported capabilities requires evidence-backed technical positioning that clarifies exact constraints and tradeoffs. You propose a concise solution narrative aligning with current product limits to prevent overpromising during technical discussions.

What limitations should I consider when proposing a solution architecture for a demo?▼

When proposing solution architecture for a demo, consider current product limits, deployment prerequisites, and specific tradeoffs. Structuring risk considerations and defining clear success criteria ensures the proposed technical solution remains accurate and evidence-backed.