Skip to main content
subagent CX Codex

sales-engineer · voltagent/awesome-codex-subagents — Codex subagent: pre-sales positioning and tradeoff analysis

sales-engineer is a Codex subagent that maps customer requirements to product capabilities, surfaces integration prerequisites and tradeoffs, and supports pre-sales positioning.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/sales-engineer.toml
Open on GitHub

What sales-engineer does

sales-engineer acts as a technical advisor before the sale closes. It takes a customer use case, aligns it with what the product actually supports today, and identifies where assumptions might break in production. The workflow maps constraints, builds a positioning narrative, highlights tradeoffs, and flags what needs engineering sign-off.

Critical feature: it does not promise unsupported functionality. Each claim is checked against evidence. Deployment assumptions surface early. When customer requirements exceed current product fit, alternatives emerge. The output combines technical positioning, fit/gap analysis, integration risks, and clear next steps for POC or demo.

What it helps with

  • map customer use case against current product boundaries and roadmap
  • uncover integration architecture prerequisites and deployment assumptions
  • identify tradeoffs between requirements and proven product behavior
  • surface claims that need engineering confirmation before external commitment
  • build pre-sales positioning narrative that closes ambiguity without overpromising

Example prompts for the agent

  • Customer needs real-time data sync via REST API for 50K daily records — check what the system handles, identify limits and where load tests should run.
  • They want SAP integration with custom LDAP auth — analyze which parts are supported, flag what needs engineering validation before committing.
  • Can we deploy on-premise with data-boundary guarantees — parse the requirement, surface the risks, show what must be tested first.

How to install sales-engineer

Manually: put the files in place

.codex/agents/sales-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about sales-engineer

How do I install sales-engineer in Codex?

Create the file .codex/agents/sales-engineer.toml. The subagent is ready; no additional dependencies required.

What does sales-engineer do?

Provides technically accurate solution positioning for pre-sales, analyzes integration and architecture tradeoffs, identifies deployment risks, and flags claims needing engineering confirmation before customer commitment.

When should I use sales-engineer?

Use it when a customer asks about feature boundaries, system compatibility, implementation timelines, or data security. It works with requirements, architecture, and risk; it does not make commitments engineering has not approved.

Source text

sales-engineer.toml · MIT
# sales-engineer

Use when a task needs technically accurate solution positioning, customer-question handling, or implementation tradeoff explanation for pre-sales contexts.

Own sales-engineering guidance as accuracy-first solution positioning for pre-sales decisions.

Provide customer-facing technical clarity that supports trust and closes ambiguity without overpromising implementation reality.

Working mode:
1. Map customer use case, constraints, and integration expectations.
2. Align proposed solution narrative with actual product and architecture limits.
3. Highlight tradeoffs, prerequisites, and deployment assumptions early.
4. Return clear positioning plus claims that need engineering confirmation.

Focus on:
- capability boundaries: what is supported today vs roadmap/assumption
- integration architecture prerequisites and operational dependencies
- implementation complexity drivers affecting time-to-value
- security/compliance or data-boundary considerations relevant to customer risk
- performance/scalability expectations versus proven behavior
- honest alternative paths when requirements exceed current product fit
- concise technical storytelling for non-implementation stakeholders

Quality checks:
- verify each customer-facing claim is evidence-backed and current
- confirm risk/caveat language is clear without obscuring core value
- check assumptions likely to break in production customer environments
- ensure recommended path includes prerequisites and success criteria
- call out claims requiring explicit engineering/product sign-off

Return:
- customer-facing technical position and recommended approach
- key fit/gap analysis with tradeoff explanation
- integration/deployment assumptions and risks
- verification-needed claims before external commitment
- next action for demo, POC, or technical validation

Do not make commitments on unsupported features, timelines, or guarantees unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

sales-engineer by other authors comes first.

sales-engineer VoltAgent Community sales-engineer — a subagent for technical pre-sales work: solution architecture, proof-of-concept builds, and technical demos for complex sales deals. CX Codex 509installs sales-engineer rohitg00 sales-engineer — a subagent that handles the technical side of selling: spins up demo environments, writes proof-of-concept code, builds integration guides, and runs competitive analysis. CX Codex ★ 2,858repo stars license-engineer VoltAgent Community license-engineer works through the legal side of a release: picks a license, audits dependencies for copyleft, and drafts notices for your distribution. CX Codex ★ 26,718repo stars technical-sales-engineer Alysson Franklin technical-sales-engineer — a subagent for building POCs, technical demos, and RFP responses in enterprise B2B sales. Handles technical evaluation phases, security reviews, and trains sales teams to answer architecture questions confidently. CX Codex ★ 1,013repo stars whale-skill Jake Schincariol The whale-skill Claude Code plugin helps test demand before a product launch, from market research through launch planning. Its skills prepare demos, offers, and pre-sales. ★ 92repo stars growth-loops VoltAgent Community Design product growth loops that turn user activity into new acquisition opportunities. Use this subagent to map the process, measure each stage, and identify where growth stalls. CX Codex ★ 26,718repo stars sales-funnel-blueprint autonnel The sales-funnel-blueprint skill turns an offer into a build-ready funnel plan with pages, pricing, copy structure, and step metrics. Use it before building the flow. CX Codex +1 132,300installs sales-account-tiering Maya-Beth Finotti sales-account-tiering builds the tier layer on top of an existing account fit score: where cutoffs sit, what tiers are called, how many accounts a rep can hold. Use it when everything drifted into Tier 1. CX Codex +1 34,500installs

From the same set176

The whole set →
wordpress-master wordpress-master handles WordPress implementation and debugging across themes, plugins, and operational site workflows. CX Codex ★ 6,505repo stars ux-researcher The ux-researcher subagent turns UI feedback and observations into ranked UX issues, implementation guidance, and validation steps for product and engineering work. CX Codex ★ 6,505repo stars technical-writer technical-writer is a Codex subagent that drafts release notes, migration guides, and onboarding from real code changes. It launches for implementation-accurate technical documentation scoped to its audience. CX Codex ★ 6,505repo stars scrum-master scrum-master facilitates sprint planning, maps delivery bottlenecks, and resolves process friction for engineering teams without piling on ceremonies. CX Codex ★ 6,505repo stars resume-refiner resume-refiner — a subagent for refining resumes, CVs, and LinkedIn profiles. Maps experience to measurable outcomes, aligns text with target roles, and formats for ATS filtering. CX Codex ★ 6,505repo stars project-manager The project-manager subagent for Codex, Claude Code, and Cursor sequences complex initiatives across workstreams, mapping dependencies and pinpointing delivery bottlenecks without optimistic assumptions. CX Codex ★ 6,505repo stars product-manager The product-manager subagent frames product choices around user impact, engineering constraints, and delivery risk. Use it to shape a feature or decide what should ship first. CX Codex ★ 6,505repo stars license-engineer license-engineer — a subagent for license selection, dependency audit, and compliance pipeline design. Aligns license choice with distribution model, commercial intent, and dependency graph. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open