skills/louisblythe/salesskills/sales-playbook-scaling

sales-playbook-scaling

Installation
SKILL.md

Sales Playbook Development & Scaling

You are an expert in building and scaling sales playbooks. Your goal is to help create systematic, repeatable sales processes that drive consistent results across teams and deal types.

Initial Assessment

Before building playbooks, understand:

  1. Sales Context

    • What are you selling? (Product, price point, complexity)
    • Who buys? (Persona, industry, company size)
    • What's the typical sales cycle?
    • What's your sales model? (Inbound, outbound, PLG, enterprise)
  2. Current State

    • What process exists today?
    • What's documented vs. tribal knowledge?
    • Where does the team struggle?
    • What do top performers do differently?
  3. Scaling Goals

    • How fast is the team growing?
    • What new segments or products?
    • What consistency problems exist?
    • What metrics need improvement?

Core Principles

1. Document What Works

Playbooks capture success patterns:

  • What top performers do consistently
  • What's been validated by results
  • What's repeatable by others
  • What addresses real buyer needs

2. Prescriptive, Not Rigid

Provide clear guidance with room for judgment:

  • Specific enough to follow
  • Flexible enough for situations
  • Principles behind the tactics
  • When to deviate and why

3. Continuously Improve

Playbooks are living documents:

  • Update based on results
  • Incorporate new learnings
  • Remove what doesn't work
  • Version and communicate changes

4. Enable, Don't Constrain

Playbooks help reps succeed, not restrict them:

  • Reduce cognitive load
  • Accelerate ramp time
  • Improve consistency
  • Preserve creativity where it matters

Sales Process Foundation

Defining Your Sales Stages

Standard B2B Sales Stages:

Stage Definition Exit Criteria
Prospecting Identifying and reaching target accounts Conversation scheduled
Discovery Understanding needs and qualification Qualified opportunity created
Solution Presenting solution and building case Technical validation complete
Proposal Formal proposal and negotiation Verbal commitment received
Closing Contract execution Deal signed

Stage Design Principles:

  • Each stage has clear entry/exit criteria
  • Stages reflect buyer's journey, not yours
  • 5-7 stages maximum
  • Measurable criteria, not subjective

Exit Criteria Examples

Discovery → Solution:

  • Pain/problem confirmed and quantified
  • Budget existence validated
  • Decision process understood
  • Key stakeholders identified
  • Timeline established
  • Competition known

Solution → Proposal:

  • Solution requirements confirmed
  • Technical/security validation complete
  • Business case built
  • Champion confirmed and engaged
  • Economic buyer identified
  • Proposal parameters discussed

Qualification Framework

BANT (Basic):

  • Budget: Can they pay?
  • Authority: Can they decide?
  • Need: Do they have the problem?
  • Timeline: Will they act?

MEDDIC (Enterprise):

  • Metrics: How they measure success
  • Economic Buyer: Who has authority
  • Decision Criteria: How they'll evaluate
  • Decision Process: How they'll decide
  • Identify Pain: What problem exists
  • Champion: Who will sell internally

SPICED (Modern):

  • Situation: Current state
  • Pain: Problem impact
  • Impact: Business consequence
  • Critical Event: Timeline driver
  • Decision: Process and criteria

Playbook Components

1. Prospecting Playbook

Target Definition:

IDEAL CUSTOMER PROFILE
Industry: [Specific industries]
Company Size: [Employee count / Revenue]
Technology: [Tech stack indicators]
Triggers: [Buying signals]
Titles: [Target personas]

Outreach Cadence:

DAY 1: Email 1 (Problem-focused)
DAY 3: LinkedIn connection + note
DAY 5: Phone call #1
DAY 7: Email 2 (Value-add content)
DAY 10: Phone call #2 + voicemail
DAY 12: LinkedIn engagement
DAY 14: Email 3 (Case study)
DAY 17: Phone call #3
DAY 21: Breakup email

Messaging by Persona:

Persona Primary Pain Value Message Proof Points
[Title 1] [Pain] [Message] [Proof]
[Title 2] [Pain] [Message] [Proof]

2. Discovery Playbook

Call Structure:

OPENING (2 min)
- Thank them for time
- Confirm agenda and time available
- Set expectations for the call

SITUATION (5 min)
- Current state questions
- What they use today
- Team structure and process

PROBLEM (10 min)
- What's not working
- Impact of the problem
- Previous attempts to solve

IMPLICATION (5 min)
- Business impact
- Cost of inaction
- Timeline pressure

NEXT STEPS (3 min)
- Summarize what you heard
- Confirm interest in continuing
- Schedule next meeting

Required Information:

  • Business problem articulated
  • Impact quantified (or estimated)
  • Current solution understood
  • Decision process mapped
  • Budget discussed
  • Timeline established
  • Competition identified

3. Demo Playbook

Pre-Demo Prep:

  • Review discovery notes
  • Customize demo for their use cases
  • Prepare relevant case studies
  • Anticipate objections
  • Know who's attending

Demo Structure:

RECAP (3 min)
- "Last time we discussed [pain points]..."
- Confirm priorities haven't changed
- Set agenda for demo

VISION (2 min)
- Paint picture of future state
- What success looks like

SOLUTION (15-20 min)
- Map features to stated needs
- Show, don't tell
- Get reactions throughout
- Handle questions in real-time

PROOF (5 min)
- Relevant customer examples
- Results they achieved
- Similar situation/company

NEXT STEPS (5 min)
- Summarize value
- Confirm fit
- Propose next steps
- Schedule follow-up

Post-Demo Actions:

  • Send recap email within 2 hours
  • Share relevant resources
  • Connect on LinkedIn (if not already)
  • Update CRM with notes
  • Schedule next meeting

4. Proposal/Negotiation Playbook

Proposal Components:

EXECUTIVE SUMMARY
- Their situation and needs
- Proposed solution
- Expected outcomes
- Investment summary

SOLUTION DETAILS
- What's included
- Implementation approach
- Timeline
- Support/success

INVESTMENT
- Pricing breakdown
- Payment terms
- What's not included

NEXT STEPS
- Decision timeline
- Implementation kickoff
- Key dates

Negotiation Guidelines:

If They Say Response Approach
"Too expensive" Revisit value, explore scope options
"Competitor is cheaper" Differentiate on value, TCO comparison
"Need to think about it" Uncover real concern, offer support
"Need discount" Trade for commitment, adjust scope

5. Closing Playbook

Closing Triggers:

  • All stakeholders aligned
  • Technical validation complete
  • Budget confirmed
  • Timeline agreed
  • Contract terms acceptable

Closing Process:

STEP 1: Verbal Commitment
- Confirm decision
- Review terms
- Identify any final concerns

STEP 2: Contract Delivery
- Send contract for review
- Offer to walk through
- Set signature deadline

STEP 3: Signature Follow-Up
- Day 1: Confirm receipt
- Day 3: Check for questions
- Day 5: Escalate if stalled

STEP 4: Handoff Prep
- Document deal context
- Introduce success team
- Schedule kickoff

Scaling Your Playbooks

By Customer Segment

Enterprise Playbook Differences:

  • Longer discovery process
  • Multiple demo variations
  • Executive engagement required
  • Procurement navigation
  • Legal review process

Mid-Market Playbook Differences:

  • Faster qualification
  • Standardized demos
  • Less procurement complexity
  • Quicker decision cycles

SMB Playbook Differences:

  • High velocity, low touch
  • Demo in first call
  • Quick proposal turnaround
  • Self-serve elements

By Deal Type

New Business Playbook:

  • Full qualification required
  • Complete discovery
  • Proof of value
  • Multiple stakeholders

Expansion Playbook:

  • Leverage existing relationship
  • Focus on new use case
  • Faster technical validation
  • Champion already exists

Renewal Playbook:

  • Value review
  • Risk assessment
  • Growth opportunities
  • Competitive defense

By Product/Solution

Create playbook variations for:

  • Different product lines
  • Solution bundles
  • Use case packages
  • Industry verticals

Playbook Enablement

Training Program

Week 1: Foundation

  • Sales methodology overview
  • Product knowledge basics
  • CRM and tools training
  • Process walkthrough

Week 2: Prospecting

  • ICP deep dive
  • Messaging practice
  • Cadence setup
  • Call simulations

Week 3: Discovery

  • Qualification framework
  • Question practice
  • Active listening
  • Note-taking

Week 4: Demo/Proposal

  • Demo certification
  • Objection handling
  • Proposal creation
  • Negotiation basics

Ongoing: Coaching

  • Call reviews
  • Deal coaching
  • Skill development
  • Best practice sharing

Certification Requirements

Skill Certification Method Pass Criteria
Product Knowledge Quiz 80%+ score
Discovery Recorded call review Checklist complete
Demo Live demo to manager All elements hit
Negotiation Role play Handle 3 scenarios

Playbook Accessibility

Where Playbooks Live:

  • Sales enablement platform
  • CRM embedded guidance
  • Shared drive/wiki
  • Printed quick reference cards

How to Maintain:

  • Quarterly reviews
  • Update for product changes
  • Incorporate win/loss learnings
  • Version control

Measuring Playbook Effectiveness

Leading Indicators

Activity Metrics:

  • Calls/emails per rep
  • Meetings booked
  • Discovery calls completed
  • Demos delivered

Quality Metrics:

  • Connect rates
  • Meeting show rates
  • Discovery → Demo conversion
  • Demo → Proposal conversion

Lagging Indicators

Outcome Metrics:

  • Win rate by stage
  • Average deal size
  • Sales cycle length
  • Quota attainment

Efficiency Metrics:

  • Revenue per rep
  • Ramp time for new hires
  • Forecast accuracy
  • Pipeline coverage

Continuous Improvement Loop

  1. Measure: Track playbook usage and outcomes
  2. Analyze: Identify what's working, what's not
  3. Update: Revise playbook based on data
  4. Train: Enable team on changes
  5. Repeat: Ongoing optimization

Building Your First Playbook

Quick-Start Template

[COMPANY] SALES PLAYBOOK
Version: 1.0
Last Updated: [Date]

1. OVERVIEW
- What we sell
- Who we sell to
- How we sell

2. SALES STAGES
[Stage definitions and exit criteria]

3. QUALIFICATION
[Framework and criteria]

4. PROSPECTING
[Cadence and messaging]

5. DISCOVERY
[Call structure and questions]

6. DEMO
[Structure and customization guide]

7. PROPOSAL
[Template and guidelines]

8. CLOSING
[Process and timeline]

9. OBJECTION HANDLING
[Common objections and responses]

10. TOOLS & RESOURCES
[What to use when]

Development Process

Step 1: Research (Week 1)

  • Interview top performers
  • Review winning deals
  • Analyze lost deals
  • Document current state

Step 2: Draft (Week 2)

  • Write first version
  • Get manager input
  • Pilot with 2-3 reps
  • Collect feedback

Step 3: Refine (Week 3)

  • Incorporate feedback
  • Add examples and templates
  • Create training materials
  • Finalize v1.0

Step 4: Launch (Week 4)

  • Team training session
  • Playbook distribution
  • Set expectations
  • Begin coaching

Step 5: Iterate (Ongoing)

  • Collect feedback
  • Track effectiveness
  • Update regularly
  • Celebrate wins

Common Playbook Mistakes

Content Mistakes

Too Generic:

  • Not specific enough to act on
  • Lacks examples
  • No context for decisions

Too Rigid:

  • No room for judgment
  • Doesn't account for variations
  • Feels like a script

Too Complex:

  • Too long to read
  • Too many steps
  • Overwhelming detail

Process Mistakes

Build and Forget:

  • No updates
  • Becomes outdated
  • Loses relevance

No Buy-In:

  • Imposed from above
  • No rep input
  • Ignored in practice

No Enablement:

  • Published but not trained
  • No coaching support
  • No accountability

Questions to Ask

If you need more context:

  1. What's your current sales process look like?
  2. What do your top performers do that others don't?
  3. Where do deals typically get stuck?
  4. What's your ramp time for new reps?
  5. How is your team structured?
  6. What tools do you use for sales enablement?

Related Skills

  • discovery-calls: For qualification frameworks and questions
  • sales-presentations: For demo structure and delivery
  • objection-handling: For objection response libraries
  • cold-outreach-writing: For prospecting messaging
  • sales-analytics: For measuring playbook effectiveness
Weekly Installs
6
GitHub Stars
11
First Seen
Mar 18, 2026