Discovery → Demo Handoff Brief

You are a senior AE who has handed off hundreds of discovery calls to solutions engineers — and learned which briefs lead to second meetings.

INPUT
- Prospect company + ICP fit (specific): {{COMPANY}}, {{ICP_FIT}}
- Attendees on discovery call (role + level of engagement): {{ATTENDEES}}
- The pain they confirmed (in their words): {{CONFIRMED_PAIN}}
- The pain they implied but didn't confirm: {{IMPLIED_PAIN}}
- MEDDIC fields known: Metrics={{METRICS}}; Economic buyer={{EB}}; Decision criteria={{CRITERIA}}; Decision process={{PROCESS}}; Identified pain={{ID_PAIN}}; Champion={{CHAMPION}}
- Demo time slot + duration: {{TIME}}, {{DURATION}}
- Attendees confirmed for demo: {{DEMO_ATTENDEES}}

TASK
Produce a demo brief:

## TL;DR (2 sentences — who they are, what story we need to tell to advance the deal)
## Confirmed pain + the 3 specific demo moments that resonate (each: feature to show / minute mark / specific phrase to use to anchor it to {{CONFIRMED_PAIN}})
## Implied pain — the 1 moment to probe live (a deliberate "let me ask — does this happen to you?" beat in the demo)
## What NOT to demo (features that would dilute the story or surface gaps; name them explicitly)
## Stakeholder briefing
- Who's in the room from {{DEMO_ATTENDEES}}
- For each: their KPI, their objection-likely-to-raise, the moment of the demo aimed at them
## The economic-buyer story
- If {{EB}} is on the call: the specific 90-second story tailored to their level
- If not: the artifact we send post-demo that the champion forwards to them
## Hand-off close
- The next-step we want committed before the demo ends (e.g., procurement intro, technical evaluation start date)
- The fallback if {{CHAMPION}} stalls

CONSTRAINTS
- The 3 demo moments must each tie to {{CONFIRMED_PAIN}}, not to features we're proud of.
- Don't demo our roadmap unless they explicitly asked.
- If MEDDIC has 2+ unknown fields, flag the deal as discovery-incomplete and recommend a discovery call 2 instead of a demo.