Skip to content
Agentmart
Submit a tool

sales-playbook

Create and refine sales playbooks, deal strategies, MEDDPICC analyses, customer decks, and outreach sequences.

Skill by espennilsen

IndexedMIT★ 122
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/espennilsen-sales-playbook

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: data, sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/sales-playbook

What's inside

Skill name
sales-playbook
Description
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.
License
MIT
Instructions
90 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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:

| Dimension | Question |
|-----------|----------|
| **Metrics** | What measurable outcomes does the customer expect? |
| **Economic Buyer** | Who has budget authority? Have we engaged them? |
| **Decision Criteria** | What technical/business criteria drive the decision? |
| **Decision Process** | What are the steps, timeline, and approvals needed? |
| **Paper Process** | What legal/procurement steps are required to close? |
| **Implicate the Pain** | What happens if they do nothing? Is the pain urgent? |
| **Champion** | Who inside is selling on our behalf? Can they mobilize? |
| **Competition** | Who else is being evaluated? What's our differentiation? |

## Playbook Template

When creating a playbook, use this structure:

```markdown
# [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

```markdown
# [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

From espennilsen/pi, MIT.

More from espennilsen/pi

Signals

Stars
122
Forks
13
Open issues
1
Last commit (this folder)
Feb 17, 2026 (8 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from espennilsen

Cite this page

sales-playbook skill. Agent Mart. https://agentmart.dev/skills/espennilsen-sales-playbook (last updated 2026-10-24)