**TL;DR** — Sales Engineer automates the technical sales back-office: demos, battlecards, proposal fragments, and competitive intel — generated fresh per prospect, not copy-pasted from last quarter's deck.
1. Define your positioning corpus — Drop your competitive battlecards, product architecture docs, and use-case libraries into the ARCHITECT context window. The richer the input, the sharper the output.
2. Wire it to your CRM triggers — Route new Opportunity creation events (or stage changes) to trigger fresh content generation. Sales Engineer doesn't need a human to tell it when to act.
3. Set output guardrails — Configure which content types the skill can produce autonomously and which require human review. Calibrate against your last three closed-won deals.
Example Prompt:
```
A Fortune 500 enterprise prospect just told us their main concern is integration complexity with their existing SAP stack. They have a 12-week procurement cycle and two technical evaluators. Generate: (1) a technical objection response framed for a non-technical buyer, (2) a proof-of-concept architecture diagram description for the evaluators, and (3) a competitive comparison table against the incumbent vendor on five integration touchpoints.
```
| Pros | Cons |
| --- | --- |
| Eliminates repetitive pre-sales content work | Output quality depends entirely on input corpus quality |
| Generates prospect-specific content at pipeline speed | Requires clean, current positioning docs to be effective |
| Frees senior SEs for complex technical conversations | May require legal review before customer-facing use |
| Scales pre-sales capacity without adding headcount | Not a replacement for deep technical discovery calls |
Sales Engineer is a force multiplier, not a replacement for your best technical sellers. Feed it good inputs, and it will keep your pipeline from starving at the technical evaluation stage. The moments it shines brightest: late-stage competitive deals where your team is outnumbered but out-prepared.