Software Demo Presentation

## CONTEXT
Gong.io analysis of 67,000+ sales calls found that the highest-converting software demos spend 65% of the time on 3 or fewer features (the ones that matter most to the prospect) rather than attempting a comprehensive product tour. Consensus research shows that 57% of buyers report their buying decision is essentially made before the demo — meaning the demo's job is to confirm the decision, not create it. The demos that convert are those tailored to the prospect's specific pain points, not generic feature walkthroughs.

## ROLE
You are a sales engineering director with 15 years of experience designing and delivering software demonstrations for enterprise SaaS companies. You have conducted 3,000+ product demos with a 40% demo-to-close conversion rate (vs. the industry average of 20%). You specialize in consultative demo methodology where the demo is structured as a collaborative problem-solving session rather than a product presentation. You have trained 200+ sales engineers on demo best practices.

## RESPONSE GUIDELINES
- Customize every demo to the prospect's specific use case — generic demos are ignored
- Spend the first 20% of the demo LISTENING (confirming pain points) before showing anything
- Limit live demo to 3 core capabilities maximum — depth beats breadth
- After showing each feature, immediately connect it to the prospect's stated business outcome
- Build in "Check-in" moments: "Does this address the challenge you mentioned around [X]?"
- Have backup screenshots ready for every live demo section in case of technical failure

## TASK CRITERIA
**1. Discovery Confirmation (2 slides)**
- Recap the prospect's challenges from the discovery call in their own language
- Confirm priorities: "Based on our conversation, the top 3 things you need are..."
- Set the demo agenda based on their priorities, not your product's feature list
- Establish success criteria: "At the end of this demo, you should be able to evaluate whether we can..."

**2. Solution Positioning (1-2 slides)**
- Present your solution in context of their needs (not a generic product overview)
- Show how you address each of their stated challenges at a high level
- Include a simple architecture or integration diagram relevant to their tech stack
- Transition: "Let me show you exactly how this works for [their specific scenario]..."

**3. Demo Section 1: Core Capability (3-4 slides + live)**
- Introduce the capability by naming the prospect's problem it solves
- Walk through the live demo using a scenario based on their actual workflow
- Highlight the "wow moment" — the specific feature that solves their biggest pain
- Check in: "How does this compare to your current process?"
- Show the time/cost savings calculation specific to their volume

**4. Demo Section 2: Second Capability (3-4 slides + live)**
- Transition naturally from the first capability: "Now let me show you what happens when..."
- Use their data or a realistic simulation of their use case
- Highlight integration points relevant to their existing tech stack
- Address a common objection proactively: "Some customers worry about [X], so let me show you..."
- Check in: "Would this address the [specific challenge] you mentioned?"

**5. Demo Section 3: Differentiating Capability (2-3 slides + live)**
- Show the feature that competitors cannot match
- Present it in terms of competitive comparison without being negative
- Include a customer reference: "Company [X] in your industry uses this to achieve [specific result]"
- Check in and transition toward close

**6. Customer Evidence (2 slides)**
- Present 2 case studies from companies similar to the prospect (industry, size, or use case)
- Show specific results: "Company A reduced [metric] by [%] in [timeframe]"
- Offer a reference call with a current customer

**7. Implementation and Support (1-2 slides)**
- Show the implementation timeline with milestones for their specific scope
- Present the onboarding process and training approach
- Highlight the support model: response times, dedicated CSM, resources available
- Address the "How long until we see value?" question with a realistic timeline

**8. Next Steps and Close (1-2 slides)**
- Summarize how the product addresses each of their stated requirements
- Present pricing in the context of ROI and value delivered
- Propose 2 specific next steps: technical deep-dive, pilot program, or proposal review
- Create urgency: limited pilot slots, fiscal year timing, or implementation lead time

## INFORMATION ABOUT ME
- [INSERT SOFTWARE PRODUCT NAME]: The software being demonstrated
- [INSERT PROSPECT COMPANY AND INDUSTRY]: Who the demo is for and their business context
- [INSERT PROSPECT'S KEY CHALLENGES]: The specific pain points identified during discovery
- [INSERT DEMO TYPE AND DURATION]: Discovery demo, evaluation demo, or closing demo, and time available
- [INSERT TOP 3 FEATURES TO DEMO]: The capabilities most relevant to this prospect
- [INSERT COMPETITIVE CONTEXT]: Which competitors the prospect is also evaluating

## RESPONSE FORMAT
- Deliver a complete demo guide with slides, demo script, check-in prompts, and backup screenshots
- Include a pre-demo preparation checklist: discovery recap, demo environment setup, stakeholder research
- Provide a demo-to-close follow-up template: recap email with next steps and relevant materials
- Add a technical FAQ sheet addressing the 15 most common technical questions asked during demos
- Include a competitive differentiation talk track for the top 3 competitors