CommunityCoding & Developmentgithub.com

Hyde-and-Larkin/sales-enablement

Turn positioning and launch context into sales-ready assets: product playbook, one-pagers, talk tracks, FAQs, objection handling, demo scripts, and training plans, scaled to the launch tier. Use when packaging enablement for sales, CS, or partners, or when a founder needs to arm their first sellers.

What is sales-enablement?

sales-enablement is a Claude Code agent skill that turn positioning and launch context into sales-ready assets: product playbook, one-pagers, talk tracks, FAQs, objection handling, demo scripts, and training plans, scaled to the launch tier. Use when packaging enablement for sales, CS, or partners, or when a founder needs to arm their first sellers.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Hyde-and-Larkin/product-marketing-toolkit/tree/main/skills/sales-enablement

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Sales Enablement Packager

Part of the Product Marketing Toolkit. Before you start, read whatever exists in context/ (positioning, objections, proof library, and the launch tier). If those files are empty or missing, ask for the essentials instead of guessing. Label anything you infer as an assumption, and never invent statistics, customer names, or quotes: use a bracketed placeholder like [sourced metric, n, date] instead.

A systematic framework for creating, packaging, and delivering sales enablement assets that equip teams to sell effectively.

Overview

This skill helps product marketers:

  • Determine which assets to create by release tier
  • Build effective enablement materials
  • Organize assets for easy discoverability
  • Deliver training that drives adoption
  • Measure enablement effectiveness
  • Maintain and update assets over time

Core Principles

Seller-Centric Design Build for how sellers actually work, not how we want them to work.

Findability Over Completeness Better to have 5 assets sellers can find than 20 they can't.

Actionable Over Comprehensive Sellers need quick answers, not encyclopedias.

Continuous Iteration Enablement is never "done" - iterate based on usage and feedback.

Cross-Functional Alignment Partner with sales leaders, training teams, and ops to ensure adoption.

Enablement Asset Library

Internal Assets (For Sales/CS Teams)

1. Product Playbook Purpose: Central hub for all product/feature enablement

Contents:

  • Product overview (1-2 pages max)
  • Example use cases and "how-to" scenarios
  • Demo video (3-5 minutes)
  • Customer-facing slides or one-pager
  • FAQ (anticipated questions)
  • Knowledge base article links
  • Competitive positioning
  • Discovery questions
  • Objection handling

Format: One hub in whatever the field uses (enablement platform, wiki, CRM) Audience: Sales, CS, Onboarding, Partners Update Cadence: As needed when product changes

2. Pitch Deck Purpose: Visual aid for customer conversations

Contents:

  • Value proposition slides
  • Problem/solution narrative
  • Product capabilities with UI/UX screenshots
  • Use case examples with visuals
  • Proof points and customer stories
  • Pricing (if appropriate)
  • Next steps/CTAs

Format: PowerPoint/Google Slides Audience: AEs, CSMs for customer presentations Update Cadence: Quarterly or with major releases

3. One-Pagers (Multiple Types)

Product/Feature One-Pager

  • What it is (1-2 sentences)
  • Key benefits (3-5 bullets)
  • How it works (visual diagram)
  • Who it's for (target customer)
  • Proof point or customer quote

Competitive One-Pager

  • vs. [Competitor] positioning
  • Key differentiators
  • When we win
  • Trap-setting questions
  • Proof points

Vertical/Industry One-Pager

  • Industry-specific use cases
  • Relevant pain points
  • Tailored value props
  • Industry proof points
  • Vertical-specific messaging

Format: PDF, 1 page, visually designed Audience: All customer-facing teams Update Cadence: As needed, review quarterly

4. Battlecards Purpose: Competitive positioning at-a-glance

Contents:

  • Quick comparison (us vs. them)
  • When you'll encounter them
  • Why we win (3-5 points)
  • Trap-setting questions
  • Landmines (their weaknesses)
  • Objection handling
  • Proof points

Format: 1-2 pages, scannable format Audience: Sales teams in competitive deals Update Cadence: Quarterly or when competitor changes

5. Discovery Question Guide Purpose: Uncover pain and qualify opportunities

Contents:

  • Situation questions (understand current state)
  • Problem questions (surface pain)
  • Implication questions (amplify impact)
  • Need-payoff questions (build desire)
  • Organized by customer segment or use case

Format: Quick reference sheet or embedded in playbook Audience: AEs, CSMs in discovery conversations Update Cadence: Based on what's working in field

6. Objection Handling Guide Purpose: Counter common pushbacks

Contents:

  • Common objection (exact words)
  • Response framework
  • Redirect strategy
  • Proof points to use
  • When to bring in specialists

Format: Table or Q&A format Audience: All customer-facing teams Update Cadence: Based on emerging objections

7. FAQ Document Purpose: Quick answers to common questions

Contents:

  • Product functionality questions
  • Pricing and packaging questions
  • Technical requirements
  • Implementation timeline
  • Support and services
  • Competitive questions

Format: Searchable document or knowledge base Audience: All customer-facing teams, Partners Update Cadence: Continuous updates as questions arise

8. Demo Videos

Marketing Demo (External)

  • 2-3 minutes max
  • Problem → solution → outcome
  • Professional production
  • Customer-facing, shareable

Product Demo (Internal)

  • 5-10 minutes
  • Feature walkthroughs
  • How to demonstrate key capabilities
  • Common demo flows
  • Tips and tricks

Format: Video (MP4) hosted in enablement platform Audience: Marketing demos for prospects; Product demos for internal teams Update Cadence: When UI changes or new features launch

9. Talk Tracks / Scripts Purpose: Language sellers can use verbatim

Contents:

  • Opening statements
  • Transition phrases
  • Value prop articulation
  • Closing statements
  • Email templates
  • Voicemail scripts

Format: Text document with copy-paste friendly formatting Audience: All customer-facing teams Update Cadence: Based on what's converting

10. Success Stories / Case Studies Purpose: Proof that solution works

Contents:

  • Customer background
  • Challenge they faced
  • Solution implemented
  • Results achieved (with metrics)
  • Quote from customer
  • When to use this story

Format: 1-page PDF or slide Audience: All customer-facing teams Update Cadence: Add new stories quarterly

External Assets (For Customers/Prospects)

1. Customer-Facing Slides Purpose: Slides AEs can share with prospects

Contents:

  • Product overview
  • Value proposition
  • Key capabilities
  • Use case examples
  • Proof points
  • Clean, professional design

Format: PowerPoint/PDF Audience: Prospects and customers Update Cadence: Quarterly

2. Solution Briefs Purpose: Standalone documents to share

Contents:

  • Executive summary
  • Business challenge
  • Solution approach
  • Key benefits
  • Customer examples
  • Next steps

Format: Professionally designed PDF Audience: Decision-makers and influencers Update Cadence: Annually or major releases

3. ROI Calculator / Assessment Purpose: Quantify value for prospects

Contents:

  • Input fields for customer data
  • Calculation methodology
  • Output: projected value
  • Assumptions documented
  • Shareable results

Format: Excel, Google Sheets, or web tool Audience: Economic buyers Update Cadence: Annually, validate assumptions quarterly

Asset Requirements by Release Tier

Tier 1 (Major Releases)

Required Internal Assets:

  • Full product playbook
  • Updated pitch deck
  • Product one-pager
  • Competitive battlecards (updated)
  • Discovery question guide
  • Objection handling guide
  • Comprehensive FAQ
  • Marketing demo video
  • Product demo video
  • Talk tracks
  • Success stories (if available)

Required External Assets:

  • Customer-facing slides
  • Solution brief
  • ROI calculator (if applicable)

Training Required:

  • Live training session
  • Recorded training for on-demand
  • Office hours for Q&A
  • Hands-on practice/roleplay

Timeline: Assets available T-30 days before launch

Tier 2 (Mid-Sized Releases)

Required Internal Assets:

  • Product playbook (lighter version)
  • Feature one-pager
  • Updated pitch deck (slides added)
  • FAQ
  • Product demo video
  • Talk tracks

Optional Internal Assets:

  • Discovery questions (if new use case)
  • Objection handling (if anticipated)
  • Battlecard updates (if competitive angle)

Required External Assets:

  • Customer-facing slides (feature overview)

Training Required:

  • Async training (video + doc)
  • Office hours for Q&A
  • Written enablement summary

Timeline: Assets available T-14 days before launch

Tier 3 (Minor Releases)

Required Internal Assets:

  • FAQ (focused on what's new)
  • Updated existing playbook
  • Talk tracks (brief messaging)

Optional Internal Assets:

  • Short demo video (if visual change)
  • One-pager (if needed for clarity)

Training Required:

  • Written summary in team channel
  • FAQ in knowledge base
  • Optional drop-in Q&A session

Timeline: Assets available T-7 days before launch

Asset Creation Process

Step 1: Align on Requirements

With Sales Leadership:

  • What are biggest gaps in current enablement?
  • What assets would most help close deals?
  • What objections are teams facing?
  • What questions keep coming up?

With Product:

  • What's changing?
  • What new capabilities are available?
  • What are key use cases?
  • What's the competitive angle?

With Marketing:

  • What's the messaging?
  • What proof points exist?
  • What content is already created?
  • What's the campaign strategy?

Step 2: Prioritize Asset Development

Must-Have (Core Enablement):

  • Playbook with overview, use cases, FAQ
  • One-pager for quick reference
  • Demo video showing how it works

Should-Have (Enhanced Enablement):

  • Pitch deck for formal presentations
  • Battlecards if competitive
  • Discovery questions for qualification
  • Objection handling if anticipated

Nice-to-Have (Supplemental):

  • Multiple one-pagers (vertical-specific)
  • ROI calculators
  • Leave-behinds
  • Additional demo variations

Step 3: Build Assets

Content Development:

  • Start with messaging foundation
  • Work with design for visuals
  • Get product for screenshots/demos
  • Source proof points from customers
  • Write in conversational language
  • Keep it scannable and brief

Review & Validate:

  • Sales leadership review
  • Top performer feedback
  • Product accuracy check
  • Legal/compliance review (if needed)
  • Pilot with small group

Step 4: Organize for Findability

Enablement Platform Structure:

Product/Feature Name
├── Overview & Training
│   ├── Playbook (main hub)
│   ├── Training recording
│   └── Quick start guide
├── Sales Assets
│   ├── Pitch deck
│   ├── One-pagers
│   └── Demo videos
├── Competitive
│   ├── Battlecards
│   └── Competitive one-pagers
├── Discovery & Qualification
│   ├── Discovery questions
│   ├── Objection handling
│   └── Talk tracks
└── Customer Resources
    ├── Customer-facing slides
    ├── Solution briefs
    └── Case studies

Naming Conventions:

  • Include product/feature name
  • Include asset type
  • Include date (for versioning)
  • Example: "Reporting_Playbook_2026-Q2.pdf"

Tagging Strategy:

  • Tag by product
  • Tag by customer segment
  • Tag by sales motion (prospecting, upsell, renewal)
  • Tag by content type

Step 5: Deliver Training

Live Training Session:

  • What's launching and why it matters
  • Key messaging and value props
  • Demo walkthrough
  • How to use enablement assets
  • Q&A
  • Record for those who can't attend

Async Training:

  • Recorded video (15-20 min max)
  • Written summary (1-2 pages)
  • Links to all assets
  • FAQ document
  • Quiz or knowledge check (optional)

Reinforcement:

  • Follow-up email with key points
  • Office hours for questions
  • Manager toolkit for coaching
  • Sales plays/examples
  • Ongoing support channel

Step 6: Measure & Iterate

Track Usage:

  • Asset downloads/views
  • Training completion rates
  • Time spent on each asset
  • Search queries (what are they looking for?)

Gather Feedback:

  • Seller surveys
  • Manager feedback
  • Win/loss analysis
  • Sales call reviews (Gong, etc.)

Update Continuously:

  • Fix errors or outdated info immediately
  • Update proof points quarterly
  • Refresh competitive intel as needed
  • Archive outdated content

Delivery Channels

Enablement Platform

  • Primary repository
  • Searchable, organized
  • Version controlled
  • Access controlled

CRM Integration

  • Embed relevant assets in opportunity stages
  • Suggest content based on deal type
  • Make it contextual to where sellers work

Slack/Teams Channels

  • Announce new assets
  • Quick reference links
  • Q&A and support
  • Share wins using assets

Learning Management System (LMS)

  • Formal training courses
  • Onboarding curricula
  • Certification programs
  • Progress tracking

Manager Toolkits

  • Assets organized by use case
  • Coaching guides
  • Role-play scenarios
  • Performance metrics

Training Delivery Frameworks

Live Training Structure (1 hour)

00:00-00:10 - Context & Why It Matters

  • What's launching
  • Market opportunity
  • Why this matters to sellers

00:10-00:25 - Product & Positioning

  • What it is and how it works
  • Key messaging and value props
  • Demo walkthrough
  • Use cases

00:25-00:40 - How to Sell

  • Discovery questions to ask
  • Objections you'll hear
  • Competitive positioning
  • Sales plays

00:40-00:50 - Enablement Assets

  • Where to find everything
  • What each asset is for
  • Quick tour of playbook

00:50-01:00 - Q&A

  • Open questions
  • Next steps
  • Support channels

Async Training Structure

Video Module (15-20 min):

  • Section 1: Overview (3-5 min)
  • Section 2: How to position (5-7 min)
  • Section 3: How to demo (3-5 min)
  • Section 4: Resources available (2-3 min)

Written Companion:

  • TL;DR summary (bullets)
  • Key messages
  • Discovery questions
  • Objection handling
  • Links to all assets

Knowledge Check:

  • 5-10 questions
  • Scenario-based
  • Correct answers explained

Seller Toolkit by Sales Motion

Prospecting + New Business (AEs)

Primary Assets Needed:

  • Pitch deck (prospect version)
  • Industry one-pagers
  • Discovery questions
  • Competitive battlecards
  • Demo video (marketing version)
  • ROI calculator
  • Case studies

Training Focus:

  • How to open conversations
  • Discovery frameworks
  • Demo flow
  • Competitive differentiation

Upsell + Expansion (CSMs)

Primary Assets Needed:

  • Feature one-pagers
  • Use case examples
  • Demo videos (product walkthrough)
  • Success stories (expansion scenarios)
  • Talk tracks (value realization)

Training Focus:

  • Identifying expansion opportunities
  • Connecting features to business outcomes
  • Cross-sell plays
  • Adoption metrics to track

Re-Engage Lost Deals (AEs)

Primary Assets Needed:

  • "What's new" slides
  • Competitive positioning (updated)
  • Recent wins/case studies
  • Pricing/packaging changes
  • Product roadmap (if appropriate)

Training Focus:

  • Why now is different
  • What's changed since last conversation
  • How to re-open dormant opportunities
  • Objection handling (why they said no before)

Manager Enablement

Manager Toolkit Contents:

  • Overview of launch and assets
  • Coaching guide (how to reinforce)
  • Roleplay scenarios
  • Scorecards for skill assessment
  • Team meeting discussion guide
  • Metrics to track

Manager Responsibilities:

  • Reinforce training in team meetings
  • Observe and coach on usage
  • Share wins and best practices
  • Identify gaps and provide feedback
  • Hold team accountable for adoption

Common Mistakes to Avoid

Too Many Assets ❌ 50 different documents for one feature ✅ Core playbook + 3-5 supporting assets

Not Seller-Tested ❌ Launching assets without seller input ✅ Pilot with top performers, iterate based on feedback

Buried in Folders ❌ "It's in the drive somewhere" ✅ Clear structure, easy search, promoted regularly

Training Without Reinforcement ❌ One-and-done training session ✅ Ongoing support, manager coaching, best practice sharing

Outdated Content ❌ Assets from 2 years ago still in system ✅ Regular reviews, archive old content, version control

No Measurement ❌ Can't tell if anyone's using it ✅ Track usage, gather feedback, iterate

Best Practices

Start With Messaging Foundation Don't create assets before messaging is locked. Rework is expensive.

Less is More Fewer high-quality assets beat many mediocre ones. Focus on core essentials.

Design Matters Professional design signals quality and importance. Invest in good design.

Make It Findable If sellers can't find it in 30 seconds, it doesn't exist to them.

Use Seller Language Write how sellers talk, not how product teams write specs.

Show, Don't Just Tell Screenshots, videos, and examples are more effective than paragraphs.

Enable the Enablers Train managers and specialists first. They multiply your impact.

Celebrate Wins Share success stories of sellers using assets to close deals.

Integration with Launch Plan

Pre-Launch (T-30 to T-0):

  • Develop all required assets
  • Conduct live training
  • Distribute async training
  • Set up manager toolkits
  • Prepare support channels

Launch (T-0):

  • Send launch communication
  • Make assets available
  • Activate support channels
  • Monitor questions/issues

Post-Launch (T+7 to T+30):

  • Office hours for Q&A
  • Gather initial feedback
  • Share early wins
  • Update FAQs based on questions
  • Refine assets based on usage

Ongoing:

  • Monthly asset reviews
  • Quarterly deep-dive with sales leadership
  • Continuous iteration based on feedback
  • Archive outdated content
  • Add new success stories

This framework provides structure for creating, organizing, and delivering sales enablement that drives adoption and effectiveness. The goal is to arm sales teams with the right assets, in the right format, at the right time, so they can confidently sell your product.

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Related Skills