About sales-enablement
A sales enablement skill for designing onboarding, training, playbooks, coaching, and measurement programs. It focuses on ongoing systems that develop seller effectiveness rather than one-off training events.
Key features
- 01Training and onboarding program design
- 02Sales playbook and content planning
- 03Coaching and skill development
- 04Certification and tool adoption guidance
- 05Metrics and performance measurement
Use cases
- 01Planning a new-hire sales ramp
- 02Building or maintaining a sales playbook
- 03Creating ongoing coaching programs
- 04Measuring enablement outcomes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ ncklrs/ startup-os-skills --skill sales-enablementAfter installing, type/sales-enablementin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
rules/_sections.mdcertification-programs.mdcoaching-feedback.mdcompetitive-intelligence.mdcontent-strategy.mdcontinuous-learning.mdonboarding-ramp.mdperformance-measurement.mdplaybook-creation.mdtool-adoption.mdtraining-program-design.mdDetails
From the project READMESales Enablement
Strategic sales enablement expertise for building world-class sales organizations — from onboarding to continuous development.
Philosophy
Great sales enablement isn't about training events. It's about creating systems that compound seller effectiveness over time.
The best enablement programs:
- Reduce time-to-productivity — Every day of ramp time costs revenue
- Enable, don't dictate — Provide tools and frameworks, not scripts
- Measure outcomes, not activities — Training hours mean nothing without behavior change
- Meet sellers where they are — Just-in-time beats just-in-case
How This Skill Works
When invoked, apply the guidelines in rules/ organized by:
training-*— Training program design, delivery, retentiononboarding-*— New hire ramp, bootcamps, 30-60-90 plansplaybook-*— Sales playbook creation, maintenance, adoptioncontent-*— Enablement content strategy and managementcoaching-*— Coaching programs, feedback systems, skill developmentcertification-*— Certification design, assessment, compliancetools-*— Tool adoption, training, stack optimizationmeasurement-*— Metrics, ROI, performance tracking
Core Frameworks
The Enablement Maturity Model
| Stage | Characteristics | Focus |
|---|---|---|
| Ad Hoc | Reactive, tribal knowledge | Document what exists |
| Foundational | Basic onboarding, scattered content | Build core programs |
| Managed | Consistent programs, basic metrics | Measure and iterate |
| Optimized | Data-driven, personalized paths | Predictive enablement |
| Strategic | Revenue attribution, business partner | Enablement as competitive advantage |
The 70-20-10 Learning Model
┌─────────────────┐
│ Experiential │ ← 70% — Learning by doing
│ (On the job) │ Deals, calls, shadowing
├─────────────────┤
│ Social │ ← 20% — Learning from others
│ (Coaching) │ Mentors, peers, feedback
├─────────────────┤
│ Formal │ ← 10% — Structured training
│ (Training) │ Courses, certifications
└─────────────────┘
Enablement Content Types
| Content Type | Purpose | When to Use | Shelf Life |
|---|---|---|---|
| Playbooks | Process guidance | Complex deals, new motions | 6-12 months |
| Battle Cards | Competitive positioning | Head-to-head deals | 3-6 months |
| Talk Tracks | Conversation starters | Discovery, objections | 6-12 months |
| Case Studies | Proof points | Late-stage deals | 12-24 months |
| Quick Reference | Just-in-time help | Daily selling | Ongoing updates |
| Micro-learning | Skill reinforcement | Continuous development | 6-12 months |
The Ramp Timeline
Week 1-2: FOUNDATIONS
├── Company, product, market
├── Tools and systems
└── Shadow experienced reps
Week 3-4: SKILLS BUILDING
├── Methodology training
├── Product deep-dives
└── Role-play practice
Week 5-8: GUIDED PRACTICE
├── Assisted customer calls
├── Deal coaching
└── First solo activities
Week 9-12: INDEPENDENT PERFORMANCE
├── Full territory ownership
├── Performance to quota
└── Certification completion
Seller Competency Framework
┌─────────────────────────────────────────────────────────────┐
│ BUSINESS ACUMEN │
│ (Industry, market, financial understanding) │
├─────────────────────────────────────────────────────────────┤
│ PRODUCT KNOWLEDGE SALES SKILLS │
│ (Features, use cases, (Discovery, demo, │
│ competition) negotiation) │
├─────────────────────────────────────────────────────────────┤
│ TOOL PROFICIENCY │
│ (CRM, enablement platform, sales tools) │
└─────────────────────────────────────────────────────────────┘
Program Overview
| Program | Audience | Cadence | Owner |
|---|---|---|---|
| New Hire Bootcamp | All new sales hires | Continuous | Enablement |
| Product Release Training | All sellers | Per release | Product + Enablement |
| Methodology Reinforcement | All sellers | Quarterly | Enablement |
| Competitive Updates | All sellers | Monthly | Competitive Intel |
| SKO (Sales Kickoff) | All revenue team | Annual | Enablement + Leadership |
| Manager Coaching | Frontline managers | Monthly | Enablement |
| Role Certifications | By role | Annual | Enablement |
Anti-Patterns
- Training events as strategy — One-time training doesn't change behavior
- Content graveyards — Building content no one uses or can find
- Product feature focus — Teaching features instead of customer outcomes
- Enablement as admin — Scheduling training instead of driving performance
- One-size-fits-all — Same training for enterprise AE and SMB SDR
- No measurement — Can't prove impact, can't get resources
- Tribal knowledge — Top performers hoard instead of share
- Tool overload — Adding tools without removing friction
Comments
Markdown supported