Define the context, goals, and constraints for this specific demo
💡
Research from Gartner: 73% of enterprise AEs give the same demo to every prospect. The 27% who tailor to specific pain and persona win at 2× the rate.
🏢 Deal Context
🎯 Demo Objectives
Audience Mapping
Identify who will be in the room and tailor your approach accordingly
💡
The same demo to a CFO and a CTO should look completely different. Map who's attending before you build the flow.
👥 Who's in the Room?
🎭 Select the Primary Audience Type
Pain → Demo → Outcome Map
Map each pain point to a specific demo element and business outcome. This is what makes a demo feel tailored instead of generic.
💡
The rule: every demo element should answer "So what?" for the audience in the room. If you can't connect a feature to a pain and an outcome, cut it.
🗺 Pain → Demo Capability → Business Outcome
Customer Pain
Demo Capability to Show
Business Outcome / "So What"
🚫 What to Cut from the Demo
Demo Flow Builder
Build your minute-by-minute demo agenda — with connection points, "so what" moments, and planned transitions
📋 Standard Demo Architecture
Best practice structure for a 60-minute business demo. Adjust time allocations based on your allotted time.
💬 Key Transitions & Connection Phrases
Use these phrases to connect each demo section back to the specific pain they mentioned:
${['"You mentioned earlier that [pain]. Let me show you exactly how we solve that..."','"This is the part that addresses [use case] — based on what you shared, this should look familiar..."','"The reason this matters for [Company] specifically is [connection to their situation]..."','"Before I move on — does this address the [specific concern] you raised earlier?"','"The \'so what\' for your team is: instead of [current state], this gives you [outcome]."','"Your [persona in room] will care most about this next section because [reason]."'].map(p => `
"${p}"
`).join('')}
🛡 Objection Prep — During-Demo Objections
${[
{obj:'We already have something that does this',resp:'Great context — can I ask what specifically it does well? [pause] Here\'s where we typically see the gap with similar solutions: [specific comparison]. Does that show up for you?'},
{obj:'Can you show us [feature you don\'t have]',resp:'That\'s a fair question. That specific feature [is on our roadmap / isn\'t something we\'ve built yet]. What I\'d want to understand is why that\'s important to you — because there may be another way we solve the underlying need.'},
{obj:'This looks complicated',resp:'Fair reaction — let me show you what the day-to-day experience looks like for the person actually using it. [simplify]. Does that feel more manageable?'},
{obj:'We need to see it with our data',resp:'Absolutely — and that\'s exactly what a POV is designed for. Let\'s use today to validate the use case is right, and then we can talk about scoping a 2-week pilot with your actual data.'},
].map(o => `
"${o.obj}"
"${o.resp}"
`).join('')}
Demo Plan
Your complete tailored demo plan — print or share with your SE before the meeting
🎬
Complete the planner and click "Generate Demo Plan"