
sales-presentations
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
- Installs
- 580
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/louisblythe/sales-skills --skill sales-presentations- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sales-presentations automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
-
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)
-
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?
-
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:
- Headline (the point of the slide)
- Supporting visual or content
- 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:
- What type of presentation is this?
- Who will be in the audience?
- Where are they in the buying process?
- What's your desired outcome from this meeting?
- What objections or concerns do you anticipate?
- 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
FAQ
What does the sales-presentations skill do?
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
How do I install sales-presentations?
Run npx skills add https://github.com/louisblythe/sales-skills --skill sales-presentations in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sales-presentations/ (personal) or .claude/skills/sales-presentations/ (project).
Which AI agents can use sales-presentations?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sales-presentations safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sales-presentations?
It is published by louisblythe in louisblythe/sales-skills. It has 580 recorded installs.
More from louisblythe/sales-skills
appointment-booking
louisblythe/sales-skills
When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."
objection-handling
louisblythe/sales-skills
When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."
outbound-prospecting
louisblythe/sales-skills
When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.
closing
louisblythe/sales-skills
When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."
sales-psychology
louisblythe/sales-skills
When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.
follow-up-discipline
louisblythe/sales-skills
When the user wants to improve their persistent but respectful outreach that keeps deals moving. Also use when the user mentions "following up," "staying on top of deals," "persistent outreach," "keeping deals alive," "not letting deals fall through," or "consistent follow-up."
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.