本文へ移動
cccskills
無料GitHub で公開

deal-qualification

Qualify a sales opportunity using the MEDDIC framework. Use when the user says "qualify this deal", "is this deal real", "MEDDIC qualification", "MEDDICC framework", "should I pursue this opportunity", "deal review", "how qualified is this prospect", "pipeline review prep", "forecast this deal", "sanity check on this opportunity", or wants to assess whether a sales opportunity is worth pursuing and at what pipeline stage.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Overview

Based on "MEDDICC" by Andy Whyte (and the original MEDDIC methodology from PTC). MEDDICC is the qualification framework used by the highest-performing enterprise sales teams globally. It maps every deal across seven dimensions: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, and Competition. Gaps in any dimension are gaps in your deal - not unknowns, risks.

Workflow

Step 1: Score each MEDDICC dimension

Run through every letter. For each one, write what you know and what you don't know. A blank answer is a red flag, not a neutral state.

DimensionKey question
M - MetricsWhat is the quantified business impact of solving this problem?
E - Economic BuyerWho has final budget authority? Have you spoken to them directly?
D - Decision CriteriaWhat does the prospect use to evaluate solutions? Do you know all criteria?
D - Decision ProcessWhat are the steps from now to signed contract? Who is involved at each step?
I - Identify PainWhat is the explicit, documented pain? Who feels it most acutely?
C - ChampionWho inside the account is actively selling for you when you're not in the room?
C - CompetitionWho else is being evaluated? What is your position vs. each competitor?

Step 2: Flag red zones

For each dimension scored blank or weak, mark it RED. A deal with 3+ red zones should not be in your forecast at any stage above "pipeline."

Common red zone patterns:

  • "I haven't met the Economic Buyer" = you are not in a real deal yet
  • "I don't know their evaluation criteria" = you are flying blind in a competitive situation
  • "I have a contact but no Champion" = your contact cannot close this internally without you

Step 3: Build the gap-closing plan

For every red zone, write one action to close the gap this week.

Format:

  • Gap: [dimension + what's missing]
  • Action: [specific outreach or meeting to close it]
  • Owner: [who on your team does this]
  • Deadline: [specific date]

Example:

  • Gap: Economic Buyer - never spoken to VP of Finance who owns budget
  • Action: Ask Champion to facilitate 20-min intro call with VP Finance
  • Owner: [AE name]
  • Deadline: This Friday

Step 4: Assign a deal stage based on MEDDICC completeness

StageMEDDICC requirement
PipelinePain confirmed, one internal contact
QualifiedM + E + I confirmed, Champion identified
CommitAll 7 dimensions known, Decision Process has a close date
ClosedContract signed

Do not let deals sit in Commit without all 7 dimensions covered.

Step 5: Prep the deal review narrative

Write a 5-sentence deal summary using this structure:

  1. What is the pain and who feels it? (I)
  2. What is the quantified impact of solving it? (M)
  3. Who is the Champion and what have they done to demonstrate that? (C)
  4. Who is the Economic Buyer and what is their posture? (E)
  5. What is the next step and when does it happen? (D - process)

This narrative is what you bring to pipeline review. If you can't write it, the deal is not qualified.

Anti-Patterns

1. Confusing a contact with a Champion Bad: "My Champion is [name] - she was really engaged on our last call." Good: A Champion has organizational credibility, access to the Economic Buyer, and has taken a personal risk for you (e.g., introduced you upward, shared internal budget info, advocated in a meeting you weren't in).

2. Accepting verbal budget confirmation as Economic Buyer access Bad: "They said budget isn't an issue." Good: "I have met the Economic Buyer, confirmed the budget line, and know who needs to sign the PO."

3. Leaving competition as "unknown" Bad: "We don't know who else they're evaluating." Good: Ask directly - "Are you evaluating other solutions alongside us?" Then position against each competitor.

4. Moving a deal to Commit on gut feel Bad: "They seem really interested, I'm 90% confident." Good: Every MEDDICC dimension is documented. The Decision Process has a signed-off timeline with specific dates.

Quality Checklist

  • All 7 MEDDICC dimensions answered - no blanks
  • Red zones identified and a gap-closing action written for each
  • Champion has demonstrated internal advocacy, not just enthusiasm
  • Economic Buyer has been spoken to directly, not just named
  • Metrics are quantified in the prospect's own terms (time, money, or risk)
  • Decision Process has a specific close date agreed upon with the prospect
  • Deal stage matches MEDDICC completeness, not the sales rep's optimism

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する