A demo built from their deal, not your deck

Create an agenda for a demo with [COMPANY]:

Attendees: [LIST NAMES/TITLES]
Time: [MINUTES]
Their priorities: [WHAT THEY CARE ABOUT]
Features to show: [LIST]

Structure:
1. Re-confirm goals
2. Demo flow (feature by feature with transitions)
3. Q&A
4. Next steps

Include questions to ask during the demo.

ROLE
You are a sales engineer who designs demos around what was learned in discovery — not a generic feature tour.

INPUTS
From discovery: main pain [MAIN PAIN] / secondary concerns [SECONDARY CONCERNS] / success criteria [WHAT GOOD LOOKS LIKE] / decision process [WHO/HOW] / timeline [TIMELINE]
Who's attending: [NAME, ROLE] - cares about: [CARES ABOUT]
Meeting length: [TIME]

INPUT HANDLING
- If the main pain and attendees aren't provided, ask for those and stop.

TASK
1. Demo flow — what to show, in what order, time per section, transition points
2. Talking points per feature — tied to their stated pain, in their words
3. Landmines to avoid — features that confuse, areas where competitors win
4. Questions to ask during the demo — to confirm resonance and surface new info
5. Close strategy — how to end with clear next steps (trial/pilot if appropriate)

OUTPUT FORMAT
A timed demo agenda (Phase | Time | Focus) summing to the meeting length, then the talking points, landmines, questions, and close.

CONSTRAINTS
Show value, not features. Use the prospect's own language from discovery. Skip the basics. Map every section back to a stated pain or success criterion.

I am a [YOUR ROLE] preparing for a live product demo with [PROSPECT COMPANY NAME] in the [INDUSTRY] industry.

Demo logistics:
- Date: [DEMO DATE AND DURATION]
- Deal stage: [DEAL STAGE AND DEAL SIZE]

Attendees and their priorities: [ATTENDEES - NAMES, TITLES, KNOWN PRIORITIES]

Discovery insights (pains, current state, desired outcomes): [DISCOVERY INSIGHTS]

Competitive alternatives being evaluated: [COMPETITIVE ALTERNATIVES]

Key product capabilities I plan to show: [PRODUCT CAPABILITIES TO SHOWCASE]

Generate a comprehensive Demo Preparation Checklist covering these sections:

1. Pre-Demo Research & Intel: Specific research tasks to complete before the demo - company news, earnings, org changes, LinkedIn research on each attendee, and industry trends I should reference to demonstrate credibility.

2. Stakeholder-Specific Game Plan: For each attendee, provide their likely top question or concern, the one or two product moments in the demo that will resonate most with them, and a tailored "so what" statement connecting our capability to their specific priority.

3. Demo Storyline & Flow: A narrative arc structured as: Opening Hook (2 min) referencing their specific pain and setting the agenda around outcomes; Current State to Pain (3 min) reflecting back discovery to build buy-in before showing anything; Product Walkthrough ordered by impact, leading with the capability that solves their #1 pain (not a feature tour); a Competitive Differentiation moment where I organically highlight what we do that the competition cannot; an ROI / Value Anchor where I pause and quantify value using their own numbers; and a Close & Next Steps (3 min) sequence to drive commitment to a next step.

4. Objection & Risk Preparation: The top 3-5 objections or tough questions likely to come up during or after the demo (based on attendees, competitive landscape, and deal stage), each with a prepared response framework.

5. Technical & Environment Checklist: Demo environment setup and data requirements; a backup plan if the live demo fails (screenshots, recorded walkthrough); screen-sharing and AV check reminders; and any custom configuration or sample data to load that mirrors the prospect's world.

6. Post-Demo Playbook: A plan for the 24 hours after the demo, including a follow-up email template personalized to the conversation, stakeholder-specific follow-ups (e.g., security whitepaper to IT, ROI model to the CFO), and internal debrief questions for my team (what landed, what didn't, what's the next blocker).

Format the output with clear headers, bullet points, and checkboxes (using - [ ]) so I can use it as a working checklist.