mcpbeat Sign in

Deal Closer Playbook Skill for Claude

Analyzes a deal in progress and generates a comprehensive closing strategy. Researches the target company, maps the buying committee, builds objection responses, creates competitive positioning, and outputs a tactical deal-playbook.md with next-best-actions and a mutual close plan.

5k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill deal-closer-playbook

The instruction itself

5 sections, as written by the author

Deal Closer Playbook

Take a deal in progress -- at any stage from discovery to negotiation -- and produce a tactical closing playbook combining company research, stakeholder mapping, competitive intelligence, and deal mechanics into a single actionable document.

Contents

  • references/intelligence-gathering.md -- context intake, company research, buying-committee map, MEDDIC and velocity risk scoring
  • references/playbook-strategy.md -- objection matrix, competitive positioning, stage-specific closing strategy, mutual close plan, proposal talking points
  • references/output-template.md -- full deal-playbook.md structure to write

Workflow

Operate in two phases: gather intelligence, then generate the playbook. Be thorough but fast. Tie every section to a specific action.

  • Collect deal context. Gather the required, valuable, and nice-to-have inputs. Ask for anything missing; mark unavailable items [UNKNOWN] and work around them. See references/intelligence-gathering.md.
  • Research the company. Use WebSearch for current intelligence: overview, last-90-days news, financial signals, leadership/hiring, tech-stack signals, industry context. See references/intelligence-gathering.md.
  • Map the buying committee. Identify and profile each role (champion, economic buyer, technical evaluator, user buyer, coach, blocker, procurement/legal, executive sponsor). Flag unknown stakeholders as discovery gaps. See references/intelligence-gathering.md.
  • Assess deal risk. Score MEDDIC qualification and the velocity risk checklist. See references/intelligence-gathering.md.
  • Build the objection response matrix. Address every raised objection plus likely unraised ones for the stage and context. See references/playbook-strategy.md.
  • Build competitive positioning. For each competitor (or the status quo), document their pitch, where they win, where you win, landmine questions, and traps to avoid. See references/playbook-strategy.md.
  • Design the stage-appropriate closing strategy. Match tactics to discovery/demo, evaluation/proposal, or negotiation/close. See references/playbook-strategy.md.
  • Build the mutual close plan. Create the shared buyer-seller timeline to signed contract. See references/playbook-strategy.md.
  • Generate proposal talking points. Draft the opening, value prop, proof, differentiation, and the ask. See references/playbook-strategy.md.

10. Write the deal playbook. Output the complete document to deal-playbook.md using references/output-template.md.

Behavioral Rules

  • Be honest about deal risk. If the deal is poorly qualified, say so -- false confidence is worse than a clear-eyed adjustment.
  • Research before advising. Do not build competitive positioning from general knowledge alone; use WebSearch for current information.
  • Make it actionable. Every section answers "What do I do next?" If a section leads to no action, cut it.
  • Write for the rep, not the VP. Use direct, tactical language. This is a field guide, not a board deck.
  • Be specific about timing. "Send the ROI model to Sarah by Thursday at 2pm before her Friday leadership meeting" beats "follow up soon."
  • Do not manufacture information. Mark anything not found as a gap and recommend how the rep can get it.
  • Respect the competitive landscape. Highlight genuine differentiators; let the prospect draw conclusions rather than trashing competitors.
  • Think like the buyer. Every recommendation must pass "Would this make me more or less likely to buy?" Pushy tactics and artificial urgency destroy trust.

Edge Cases

  • No competitors identified: Build a competitive section against the status quo (doing nothing, building in-house, manual processes). Every deal competes against inaction.
  • Very early stage deal: Focus on qualification and discovery; the closing strategy becomes an advancement strategy. Do not write negotiation tactics for a pre-demo deal.
  • Stalled deal: Diagnose why it stalled (timing, budget, champion left, competing priority) and build a re-engagement strategy around a new compelling event.
  • Renewal/expansion deal: Shift from acquisition to retention framing. Emphasize value delivered, usage data, and ROI proof over competitive positioning.
  • Multi-product deal: Map each product to a different stakeholder and use case. Build separate value propositions per product line under a unified closing strategy.

Other skills for the same job

different authors, same section of the catalogue
Content Research Writer
by frostant
×10

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

4k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Notebooklm
by ZhanlinCui
×6

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

26k tokens scripts
Biorxiv Database
by christophacham
×4

Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.

9k tokens scripts
Openalex Database
by christophacham
×4

Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.

13k tokens scripts
Uspto Database
by christophacham
×4

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

21k tokens scripts
Denario
by christophacham
×3

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

11k tokens
Hypogenic
by christophacham
×3

Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.

7k tokens

How to use it

Copy the folder

Take onewave-ai/deal-closer-playbook from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.