Skip to content

espennilsen/pi / skills/sales-playbook

sales-playbook

Verified

Create and refine sales playbooks, deal strategies, MEDDPICC analyses, customer decks, and outreach sequences. Use for any sales methodology work, pipeline review, or go-to-market planning.

Sales Playbook

Build sales artifacts grounded in MEDDPICC methodology and Espen's enterprise AI sales experience.

Artifacts This Skill Produces

  • MEDDPICC Deal Analysis — Qualify a deal against all 8 dimensions
  • Sales Playbook — Repeatable motion for a product/segment
  • Outreach Sequence — Multi-touch cadence (email, LinkedIn, call)
  • Customer Deck Outline — Slide structure with talking points
  • Objection Handling Guide — Common objections with responses
  • Pipeline Review Brief — Summary + recommendations for a deal set

MEDDPICC Framework

For every deal analysis, score each dimension (1-3: weak/moderate/strong) and identify gaps:

DimensionQuestion
MetricsWhat measurable outcomes does the customer expect?
Economic BuyerWho has budget authority? Have we engaged them?
Decision CriteriaWhat technical/business criteria drive the decision?
Decision ProcessWhat are the steps, timeline, and approvals needed?
Paper ProcessWhat legal/procurement steps are required to close?
Implicate the PainWhat happens if they do nothing? Is the pain urgent?
ChampionWho inside is selling on our behalf? Can they mobilize?
CompetitionWho else is being evaluated? What's our differentiation?

Playbook Template

When creating a playbook, use this structure:

# [Product/Segment] Sales Playbook

## Ideal Customer Profile
- Industry, size, tech stack, pain signals

## Value Proposition
- 1-sentence elevator pitch
- 3 key differentiators vs. status quo
- 3 key differentiators vs. competition

## Discovery Questions
- 5-7 open questions that uncover MEDDPICC dimensions

## Objection Handling
| Objection | Response Framework |
|-----------|-------------------|

## Proof Points
- Customer stories, metrics, case studies

## Competitive Positioning
- Feature comparison, narrative reframes

## Sales Motion
- Prospecting → Discovery → Demo → Proposal → Close
- Time-to-close benchmark, typical deal size

Outreach Sequence Template

# [Campaign Name] Outreach Sequence

## Target Persona
Role, industry, pain points, trigger events

## Sequence (10-14 days)
### Day 1 — Email 1: Pain-led hook
### Day 3 — LinkedIn connect + note
### Day 5 — Email 2: Social proof
### Day 8 — Call attempt + voicemail
### Day 10 — Email 3: Insight share
### Day 14 — Email 4: Break-up

## Personalization Variables
- {{company_pain}}, {{relevant_metric}}, {{mutual_connection}}

Guidelines

  • Always tie features to business outcomes, not technical specs
  • Use the customer's language, not vendor jargon
  • Every claim needs a proof point (number, customer name, or case study)
  • Playbooks should be usable by a rep on day 1, not just by Espen
  • Keep outreach under 100 words per touch — respect the reader's time
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall