louisblythe/sales-skills1 file

Sales Playbook Scaling

When the user wants to build, document, or scale sales playbooks and processes. Also use when the user mentions "sales playbook," "sales process," "repeatable sales," "scaling sales," "sales methodology," "deal stages," "sales SOP," or "sales best practices." This skill covers creating systematic, scalable sales approaches that drive consistent results.

Specification
Skill ID
louisblythe/sales-skills/sales-playbook-scaling
Publisher
louisblythe
Repository
sales-skills
Installs
0
Files
1
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

louisblythe/sales-skills/sales-playbook-scalingInstalls these files
  • SKILL.md

What this skill tells the agent

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)
  1. Current State
  • What process exists today?
  • What's documented vs. tribal knowledge?
  • Where does the team struggle?
  • What do top performers do differently?
  1. 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:

StageDefinitionExit Criteria
ProspectingIdentifying and reaching target accountsConversation scheduled
DiscoveryUnderstanding needs and qualificationQualified opportunity created
SolutionPresenting solution and building caseTechnical validation complete
ProposalFormal proposal and negotiationVerbal commitment received
ClosingContract executionDeal 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:

PersonaPrimary PainValue MessageProof 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 SayResponse 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:

Use this skill in a project

Open any RiverX project, search the Skills panel for louisblythe/sales-skills/sales-playbook-scaling, and install it in one click.

Use this skill