The problem
SE bandwidth is the constraint at every Series B+ B2B SaaS. The AE-to-SE bring-in is the cheapest place to lose deals.
Common failure mode: 1. AE has run 2-3 calls. Buyer has technical concerns. 2. AE Slacks SE: "Hey, can you join Tuesday's call? It's about XYZ." 3. SE blocks the time, doesn't review prior calls, walks in cold. 4. Buyer technical reviewer asks a sharp question. SE answers generically. 5. Buyer concludes vendor doesn't have technical maturity.
The deal doesn't die in that one call. It goes from "leaning yes" to "let's evaluate two more vendors" — which kills it three weeks later.
The fix: a pre-SE briefing artifact
Before any SE joins a deal, the AE needs to have generated (or AI-generated) a 1-pager that gives the SE technical context, not just deal context.
The brief structure
#### 1. The technical question that triggered the bring-in
Specific. "Can our product handle multi-region failover?" Not "they have technical concerns."
#### 2. The buyer's actual stack
Inferred from emails, LinkedIn (engineer titles), public Github org, prior call transcripts. SE needs to know: what's the cloud? what's the data warehouse? what's the orchestrator?
#### 3. Where the AE has already committed
"AE told them on call 2 that we have a Snowflake connector. We do, but it's the V1 connector that doesn't support push-down compute. SE must clarify or risk overpromise."
#### 4. Competing solutions in flight
If buyer mentioned evaluating vendors, list them. SE needs to know whether to position against Snowflake-native, BigQuery-native, or general-purpose competitors.
#### 5. Technical evaluator's profile
Name, title, LinkedIn-derived background. Are they a hands-on engineer or an architect? Determines depth of detail SE should go into.
The AI workflow
name: se-prep-brief
trigger: AE adds SE as participant to opportunity OR explicitly tags @se-prep in Slack
Inputs: - All Gong transcripts for the deal - Emails (filtered to technical content) - Salesforce technical-fit custom fields - Public artifacts: buyer's LinkedIn, company engineering blog, Github
Claude pulls these, generates the 5-section brief, posts in a deal Slack channel 24 hours before SE joins.
The system prompt (compressed)
You are a sales engineering prep specialist. Given the artifacts, write a 1-pager SE bring-in brief with exactly these sections:
1. The technical question driving the bring-in (cite source call/email)
2. Buyer's stack — inferred or stated, with confidence level on each item
3. AE commitments at risk (look for AE hedge phrases: "should be fine", "let me confirm", "I think we can")
4. Competing solutions mentioned by buyer (with vendor names + how positioned)
5. Technical evaluator profile (name, title, LinkedIn-derived background, likely depth preference)Constraints: - If you don't know something, write "unknown — SE to confirm." - Never invent technical capabilities the company has. - Max 400 words. ```
What changes
The SE walks in with the same context as the AE. First question doesn't catch them flat. They confirm or clarify the AE's commitments before the buyer can use them against the vendor.
In our experience: SE-attended calls move opportunities one stage faster (about 7 days) when this brief is in play.
Pitfalls
- **AE forgets to trigger it**: bake the trigger into Salesforce — when SE is added to opportunity record, fire the workflow automatically.
- **Stack inference is wrong**: model can hallucinate based on company size + industry. Add a "confidence" indicator to each stack item; SE asks buyer to confirm low-confidence items.
- **AE feels exposed about hedges**: same framing as AE→CS handoff. This is for the team's deal hygiene, not gotcha.
Tools
- **Vivun**: if you have it, ingest its opportunity scoring + technical signal data
- **Gong / Chorus**: transcripts
- **Salesforce**: trigger + custom fields
- **Anthropic Claude**: long-context handling
- **Slack**: SE notification + thread for ongoing dialogue
A note on SE utilization
Beyond the immediate deal, this brief reduces SE wasted time. SEs spend ~20-30% of their week on calls they shouldn't be on or were under-prepared for. Tightening the AE-SE bring-in handoff lifts effective SE capacity without hiring.