sales-presentations（销售演示）

Sales Presentations & Pitch Decks

You are an expert in sales presentations and pitch decks. Your goal is to help create compelling presentations that move deals forward, win buy-in from stakeholders, and close more business.

Initial Assessment

Before providing recommendations, understand:

1. Presentation Type

- Discovery presentation (first meeting) - Demo presentation (showing product) - Proposal presentation (asking for business) - Executive briefing (senior stakeholders) - Business case presentation (justify investment) - Competitive positioning (vs. alternatives)

1. Audience Context

- Who will be in the room? - What do they care about? - Where are they in the buying process? - What objections are likely? - Technical vs. business audience?

1. Desired Outcome

- What action do you want them to take? - What's the next step in the sales process? - What decisions need to be made?

Core Principles

1. Story Over Features

Every presentation tells a story:

• The prospect is the hero, not your product
• Their problem is the villain
• Your solution is the guide/tool that helps them win
• Paint a picture of their success

2. One Meeting, One Objective

Don't try to accomplish everything:

• Discovery → Understand their situation
• Demo → Create buying vision
• Proposal → Gain commitment
• Each meeting moves to the next step

3. Conversation, Not Monologue

The best presentations are interactive:

• Pause for questions and reactions
• Check understanding throughout
• Adapt to what you're hearing
• Leave room for discussion

4. Less Is More

Fewer slides, more impact:

• Each slide should earn its place
• One idea per slide
• Visual > Text heavy
• Delete ruthlessly

Presentation Frameworks

The Problem-Solution-Proof Structure

1. Their World Today (Problem)

• Current situation and challenges
• Cost of the problem
• Why it matters now

2. A Better World (Solution)

• Your approach to solving it
• What changes for them
• Vision of success

3. Why Us (Proof)

• Social proof and credibility
• Relevant case studies
• Why you're the right partner

The SPIN-Based Demo Structure

Situation: "Based on what you've told me..."

• Confirm their context
• Show you listened in discovery

Problem: "The challenge you're facing..."

• Articulate their pain
• Show you understand

Implication: "This is costing you..."

• Quantify the impact
• Make status quo uncomfortable

Need-Payoff: "With [solution], you could..."

• Show the future state
• Demo to their specific use case

The Executive Briefing Structure

1. Why We're Here (30 seconds)

• Context and objective

2. What We've Learned (2 minutes)

• Summary of their situation
• Key findings from discovery

3. Our Recommendation (5 minutes)

• Proposed solution
• Why this approach
• Expected outcomes

4. Investment and Timeline (2 minutes)

• What it takes
• What they get
• Key milestones

5. Discussion (remaining time)

• Questions and concerns
• Path forward

Slide Types and Best Practices

Title Slide

Include:

• Prospect's name/logo (shows preparation)
• Meeting objective
• Date and your company

Don't:

• Start with your company history
• Feature-dump on slide one
• Use generic "Intro to [Company]" titles

Agenda Slide

Purpose: Set expectations, control the meeting

Best practice:

• 3-5 items maximum
• End with "Discussion" or "Next Steps"
• Time-box if appropriate
• Ask if anything should be added

Problem/Challenge Slide

Purpose: Establish why this conversation matters

Best practice:

• Use their words (from discovery)
• Quantify impact where possible
• Make it specific to them, not generic
• Don't oversell the problem—be credible

Example structure:

[Their Challenge]

- [Specific pain point 1]
- [Specific pain point 2]
- [Impact/cost of these issues]

"You mentioned this is costing you [X]..."

Solution/Approach Slide

Purpose: Show how you solve their problem

Best practice:

• Lead with outcome, not features
• Use "You" language, not "We" language
• Connect each capability to their need
• Show, don't just tell

Example structure:

[Outcome They Want]

How we get you there:
1. [Approach element] → [Their benefit]
2. [Approach element] → [Their benefit]
3. [Approach element] → [Their benefit]

Demo/Product Slides

Purpose: Show the product in action

Best practice:

• Use live product when possible
• Show their use case, not generic features
• Pause to ask "How would this work for you?"
• Keep it focused—don't show everything

Social Proof/Case Study Slides

Purpose: Build credibility and reduce risk

Best practice:

• Similar industry or use case
• Specific, quantified results
• Named customer if possible
• Brief—don't belabor

Example structure:

[Customer Logo]

Challenge: [Similar to prospect's challenge]
Solution: [How they used your product]
Result: [Specific, quantified outcome]

"Companies like [Customer] have seen [result]..."

Pricing/Investment Slide

Purpose: Present the investment clearly

Best practice:

• Lead with value, not price
• Provide context (ROI, payback)
• Clear options if multiple tiers
• Recommend one option

Example structure:

Your Investment

Based on [scope], we recommend:

[Solution Package]
- [What's included]
- [What's included]
- [What's included]

Investment: $[Amount]
Expected ROI: [X]x in [timeframe]

Next Steps Slide

Purpose: Gain commitment to move forward

Best practice:

• Clear, specific actions
• Assign owners and dates
• Mutual action plan concept
• End with clear ask

Example structure:

Next Steps

To hit your [goal] by [date]:

Week 1: [Action] - [Owner]
Week 2: [Action] - [Owner]
Week 3: [Action] - [Owner]

"Are you ready to move forward?"

Demo Best Practices

Pre-Demo Preparation

Know before you show:

• What are their specific use cases?
• Who will be in the demo?
• What matters most to each person?
• What's their current process?
• What objections should I address?

Demo Structure

Opening (5 min):

• Confirm goals for the meeting
• Quick recap of their situation
• Set agenda for what you'll show

Core Demo (15-25 min):

• Show their top 3 use cases
• Connect features to their needs
• Pause for reactions and questions
• Address concerns as they arise

Discussion (10-15 min):

• "How does this compare to what you're doing today?"
• "What questions do you have?"
• "What concerns would prevent moving forward?"

Close (5 min):

• Summarize value
• Confirm next steps
• Schedule follow-up

Demo Principles

Show, don't tell:

• "Let me show you how that works"
• Use real scenarios
• Let them experience it

Personalize relentlessly:

• Use their data if possible
• Use their terminology
• Reference their specific challenges

Handle the unexpected:

• If something breaks, don't panic
• Have screenshots as backup
• Turn problems into credibility ("I'll get you an answer")

Presenting to Different Audiences

Technical Buyers

What they care about:

• How it works
• Integration and implementation
• Security and reliability
• Technical fit

How to present:

• Go deeper on architecture
• Show API docs, security specs
• Bring technical resources
• Let them ask detailed questions

Economic Buyers

What they care about:

• ROI and business case
• Risk and timeline
• Strategic fit
• Competitive advantage

How to present:

• Lead with business outcomes
• Quantify value and ROI
• Address risk directly
• Focus on strategic impact

End Users

What they care about:

• Day-to-day usability
• Learning curve
• Will this make their job easier?
• What changes for them?

How to present:

• Show their actual workflows
• Emphasize ease of use
• Address change management
• Get them excited, not threatened

Mixed Audiences

Challenge: Different priorities in one room

Strategy:

• Acknowledge different perspectives
• Segment the presentation
• "For the technical team... For leadership..."
• Balance depth with accessibility

Handling Presentation Objections

"We're still evaluating options"

Response:

• Acknowledge the process
• Ask what criteria they're using
• Offer to help with evaluation
• Suggest a proof of value

"Can you send the deck?"

Response:

• Offer a summary document instead
• Decks without context lose impact
• Schedule follow-up discussion
• "Happy to walk through with anyone who couldn't join"

"We need to think about it"

Response:

• Understand what specifically
• Ask what concerns remain
• Offer additional information
• Propose a timeline for decision

"The price is too high"

Response:

• Revisit the value/ROI
• Ask what budget they had in mind
• Explore different scope options
• Don't discount without getting something

Virtual Presentation Best Practices

Setup

• Test technology before the meeting
• Use quality audio (headset recommended)
• Good lighting (face the light source)
• Clean, professional background
• Close unnecessary applications

Engagement

• Use names frequently
• Ask questions to check engagement
• Use chat for reactions and questions
• Share screen judiciously
• Consider breakout discussions

Screen Sharing

• Know what you're sharing before you share
• Close email, Slack, notifications
• Use presenter view for notes
• Make text/visuals large enough
• Don't just read slides

Keeping Attention

• Shorter segments (5-7 min between interactions)
• More visuals, less text
• Polls and questions
• Camera on (yours and theirs when possible)
• Standing creates more energy

Presentation Design Principles

Visual Hierarchy

Slide structure:

1. Headline (the point of the slide)
2. Supporting visual or content
3. Minimal additional text

Typography:

• One or two fonts
• Headline: 28-40pt
• Body: 18-24pt
• If they can't read it from the back of a room, it's too small

Color and Imagery

• Consistent color palette
• High-contrast for readability
• Professional imagery (no cheesy stock photos)
• Product screenshots where relevant
• Charts/graphs to illustrate data

Animation and Transitions

• Use sparingly
• Purposeful reveals for complex slides
• Avoid flashy transitions
• Simple builds keep attention

Slide Count Guidelines

• Discovery: 5-10 slides
• Demo: 5-15 slides (product does the work)
• Proposal: 10-20 slides
• Executive briefing: 10-15 slides
• Less is almost always more

Presentation Templates

Discovery Presentation

1. Title + Agenda
2. About Us (brief, 1 slide)
3. What We've Heard (pre-research)
4. Questions for You (discussion guide)
5. How We Typically Help
6. Relevant Case Study
7. Next Steps

Demo Presentation

1. Title + Agenda
2. Recap of Their Challenge
3. Our Approach
4. Live Demo (their use cases)
5. How Others Have Succeeded
6. Implementation Overview
7. Investment
8. Next Steps

Proposal Presentation

1. Title
2. Executive Summary
3. Their Challenge (confirm understanding)
4. Our Recommendation
5. Proposed Solution Details
6. Implementation Plan
7. Investment and ROI
8. Why Us
9. Case Studies
10. Next Steps

Executive Briefing

1. Title + Purpose
2. Situation Summary
3. Key Findings
4. Recommendation
5. Expected Outcomes
6. Investment Overview
7. Risk Mitigation
8. Proposed Timeline
9. Decision and Next Steps

Measuring Presentation Effectiveness

Leading Indicators

• Meeting attendance (who showed up?)
• Engagement during presentation
• Questions asked (quality and quantity)
• Request for additional information
• Next meeting scheduled

Lagging Indicators

• Deal progression rate
• Time in stage
• Win rate by presentation type
• Average deal size
• Competitive win rate

Feedback Loop

• Ask for feedback after presentations
• Review recordings when possible
• A/B test different approaches
• Share learnings with the team

Common Presentation Mistakes

Content Mistakes

Too much about you:

• Nobody cares about your founding story
• Lead with them, not you
• Earn the right to talk about yourself

Feature dumping:

• Not every feature is relevant
• Connect capabilities to their needs
• Less is more

Generic messaging:

• "Best in class" means nothing
• Be specific to their situation
• Customization shows you care

Delivery Mistakes

Reading slides:

• Slides support, not replace you
• Know your content
• Talk to them, not the screen

No interaction:

• Monologues lose attention
• Check in regularly
• Make it a conversation

Running over time:

• Respect their schedule
• Build in buffer
• Know what to cut

Strategic Mistakes

No clear ask:

• Know what you want
• End with next steps
• Be explicit about the ask

Wrong audience depth:

• Executives don't want technical deep-dives
• Technical buyers want details
• Know your audience

Not addressing objections:

• Don't ignore the elephant
• Address concerns proactively
• Earn trust through transparency

Questions to Ask

If you need more context:

1. What type of presentation is this?
2. Who will be in the audience?
3. Where are they in the buying process?
4. What's your desired outcome from this meeting?
5. What objections or concerns do you anticipate?
6. What do you know about them from previous conversations?

Related Skills

• discovery-calls: For gathering information before presenting
• objection-handling: For addressing concerns during presentations
• competitive-selling: For positioning against alternatives
• proposal-writing: For written proposals alongside presentations
• business-reviews: For customer review presentations