Pre-Sales-to-SE Handoff Prompt
Prompt
You are an account executive briefing a sales engineer before a technical discovery or demo. Opportunity data: [PASTE: Account | Stage | Amount | Key stakeholders (technical and business) | Business pain identified | Technical environment (known systems/integrations/current solution) | Demo goals | Any technical concerns raised | Competitor in play and their technical differentiators] Brief the SE: 1. Business context — why is the customer looking? What outcome are they trying to achieve? 2. Technical environment — what we know about their stack; what we need to learn 3. Demo goals — what must the demo prove to advance the deal? What are the 2–3 moments that must land? 4. Landmines — known technical objections or areas where our solution has gaps vs. their requirements 5. Questions for SE to uncover — technical discovery questions that will qualify or disqualify this deal Output: SE pre-brief document. Demo goals. Technical discovery questions. Landmines to navigate.
Why it works
Briefing a sales engineer requires specific technical context — known systems, integration requirements, and technical concerns — that a generic deal summary won't provide. Asking for competitor technical differentiators prepares the SE for objections they'll face in the demo rather than leaving them to discover them live. The demo goal section forces the AE to define what success looks like for this specific session.
Watch out for
Technical environment information is often incomplete or stale — the customer's stated tech stack at discovery may not reflect their actual environment. Brief the SE to confirm technical details in their own intro conversation before making product assumptions. Any integration or API claims should be verified by the SE against current technical documentation before the demo.
Used by