Sales Engineer Discovery Brief Builder
Convert account notes into a structured sales engineer brief for technical discovery, demos, integrations, and proof-of-concept planning.
Prompt Template
You are a solutions engineering lead. Create a technical discovery brief for a sales engineer joining an active opportunity. Account: [company name, size, industry] Primary business pain: [what the buyer wants to solve] Stakeholders and roles: [economic buyer, champion, admin, security, IT, end users] Current stack: [tools, systems, data sources, integrations] Use cases to validate: [top 3-5 workflows] Known technical requirements: [SSO, API, data residency, permissions, uptime, compliance] Known objections or risks: [security, migration effort, performance, budget, timeline] Demo or workshop goal: [what must be proven] Open questions: [unknowns from AE discovery] Next meeting format: [technical discovery / custom demo / POC scoping] Return: 1. One-page opportunity context 2. Technical discovery agenda 3. Must-ask questions by stakeholder 4. Recommended demo flow or artifacts 5. Integration and security watch-outs 6. Success criteria for the next step 7. Internal prep checklist for AE + SE
Example Output
# Sales Engineer Brief — Acme Logistics
Opportunity Context
Acme wants to reduce manual shipment exception handling across 14 warehouses. The VP Ops is the economic buyer; the champion is the Director of Fulfillment. Their current stack is NetSuite, Zendesk, Snowflake, and a custom warehouse app.
Technical Discovery Agenda
1. Confirm exception workflows and current manual steps
2. Map required data sources and sync frequency
3. Validate permission model for warehouse managers
4. Identify reporting requirements for VP Ops
5. Agree on POC success criteria
Must-Ask Questions
- **IT:** Is SSO mandatory for pilot users? Any data residency restrictions?
- **Ops:** Which exception types cost the most time today?
- **Data:** Where is shipment status considered the source of truth?
Demo Flow
Start with exception dashboard → drill into delayed shipment → show automated customer notification → show manager approval workflow → finish with Snowflake export.
Watch-Outs
Security review may block if API scopes are unclear. Prepare least-privilege permission diagram.
Next-Step Success Criteria
Technical stakeholders agree the pilot can use NetSuite + Zendesk data without custom engineering.
Tips for Best Results
- 💡Write the brief from the SE’s point of view: what must be learned, proven, and de-risked next.
- 💡Separate business pain from technical requirements so the demo does not become a feature tour.
- 💡List unknowns explicitly; a good brief prevents the AE from pretending discovery is more complete than it is.
Related Prompts
Cold Email Sequence Writer
Write a 4-email cold outreach sequence that gets replies without being pushy, spammy, or forgettable.
Sales Discovery Call Questions
Generate a structured discovery call question framework that uncovers genuine pain, budget, and buying process.
Sales Proposal Writer
Write a compelling, customer-specific sales proposal that clearly communicates value, ROI, and next steps.