Agent skill
deal-qualification
Filed under Calls, demos and discovery.
From VijayMatt/go-to-market-agent-skills · 12 skills · 1 · pushed 2026-03-29
What it does when it runs
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/VijayMatt/go-to-market-agent-skills.git /tmp/go-to-market-agent-skills git -C /tmp/go-to-market-agent-skills sparse-checkout set "deal-qualification" mkdir -p ~/.claude/skills/deal-qualification cp -R "/tmp/go-to-market-agent-skills/deal-qualification/." ~/.claude/skills/deal-qualification/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from VijayMatt/go-to-market-agent-skills/blob/c948db28e7a0147976cc91ad91479900a75f7904/deal-qualification/SKILL.md, which is licensed MIT (repository). 3,880 words, 22 headings.
Deal Qualification: MEDDPICC — Full Methodology
What MEDDPICC Is (and What It Isn't)
MEDDPICC is a deal qualification framework with 8 elements. Each element represents something you must understand about a deal to accurately predict whether it will close. It is not a one-time checklist — it's a living map that gets updated with every interaction.
The 8 elements:
- M — Metrics
- E — Economic Buyer
- D — Decision Criteria
- D — Decision Process
- P — Paper Process
- I — Identify Pain
- C — Champion
- C — Competition
A common mistake: treating MEDDPICC as a CRM data-entry exercise. If your reps are filling in fields to satisfy their manager but not using the framework to actually run deals, you have a compliance problem, not a qualification program.
Element-by-Element Deep Dive
M — Metrics
Definition: The quantifiable business outcomes the buyer expects from this purchase. Not "what our product does" but "what measurable result the buyer needs to achieve."
Why it matters: Metrics are the foundation of your business case. Without them, you're selling a product. With them, you're solving a problem that has a dollar value. Deals with quantified metrics close at 2-3x the rate of deals without them.
How to uncover:
- "What does success look like 12 months after implementation?"
- "How are you measuring this problem today? What are the numbers?"
- "If this project delivers everything you want, what KPIs would move?"
- "What's the cost of the status quo — in dollars, hours, headcount, risk?"
Green flags:
- Buyer can articulate specific, quantified outcomes ("reduce audit cycle time from 6 weeks to 2 weeks")
- Metrics are tied to a strategic initiative the CEO cares about
- Buyer has already calculated the cost of the status quo
Red flags:
- Buyer speaks in vague terms ("improve efficiency," "modernize our processes")
- Metrics change every conversation (they haven't crystallized what they actually need)
- The buyer says "we haven't really quantified it" and isn't interested in doing so
- Metrics are aspirational but not connected to anyone's performance goals
Scoring:
- 0 = No metrics identified
- 1 = Vague/qualitative goals
- 2 = Some metrics identified but not quantified
- 3 = Clear, quantified metrics tied to business outcomes
E — Economic Buyer
Definition: The person with the authority to approve the budget and make the final purchasing decision. Not your champion. Not the person who runs the evaluation. The person who signs (or authorizes signing) the contract.
Why it matters: You can win every evaluation criterion and still lose the deal if the economic buyer doesn't see the value, didn't know about the purchase, or has different priorities. 68% of stalled deals have an unidentified or inaccessible economic buyer.
How to uncover:
- "Who has final approval authority for a purchase of this size?"
- "Has budget been allocated, or does this need to be approved through a separate process?"
- "Walk me through the last time your organization made a purchase similar to this one — who was involved in the final decision?"
- Ask your champion: "If you and I build the perfect business case, who do you present it to?"
Green flags:
- You've met the economic buyer (ideally, had a direct conversation)
- Economic buyer has expressed support or interest in the initiative
- Your champion has a strong relationship with the economic buyer and can articulate their priorities
- Budget is confirmed as allocated (not "we'll find it if we like the solution")
Red flags:
- "My boss will make the final call, but don't worry, they'll approve whatever I recommend" (this is almost never true for significant purchases)
- The economic buyer keeps getting pushed off ("they're too busy to meet with vendors")
- Your champion IS the economic buyer on paper but doesn't actually control budget
- The deal requires net-new budget allocation with no executive sponsor
Scoring:
- 0 = Economic buyer unknown
- 1 = Economic buyer identified but not met
- 2 = Economic buyer met, but support unclear
- 3 = Economic buyer met, engaged, and supportive
D — Decision Criteria
Definition: The specific, weighted criteria the buying committee uses to evaluate and compare solutions. Technical requirements, business requirements, vendor requirements, and any "must haves" vs. "nice to haves."
Why it matters: If you don't know the decision criteria, you can't position your strengths or address your weaknesses. If you didn't help shape the criteria, they were likely shaped by a competitor.
How to uncover:
- "What are the top 3-5 things that matter most in your evaluation?"
- "If two solutions were tied on everything else, what would be the tiebreaker?"
- "Are there any requirements that are absolute deal-breakers — things that would immediately disqualify a vendor?"
- "How are you weighting these criteria against each other?"
Shaping criteria (the advanced play): The best reps don't just discover criteria — they influence them. If your product is strong on security and weak on integrations, you educate the buyer on why security should be weighted more heavily. This is not manipulation — it's consultative selling. You genuinely believe security matters more, and you're helping the buyer see that.
Tactics:
- Share "lessons learned" from similar buyers: "Companies like yours who prioritized X over Y saw better outcomes because..."
- Offer a criteria template or evaluation framework (that naturally weights your strengths)
- Bring in a reference customer who can speak to why criterion X mattered in their evaluation
Green flags:
- You have the written decision criteria (ideally, an RFP or evaluation scorecard)
- You helped shape the criteria
- Your solution is strong on the criteria weighted most heavily
- You know which criteria your competitor is strong on
Red flags:
- The criteria sound like they were written by your competitor ("must have native integration with [competitor's ecosystem]")
- Criteria keep changing (signals internal misalignment or a new competitor entering)
- The buyer won't share their criteria ("we're evaluating based on overall fit" — this means someone else is driving the process)
Scoring:
- 0 = Decision criteria unknown
- 1 = General criteria known but not specific or weighted
- 2 = Specific criteria known
- 3 = Criteria known, weighted, and you influenced them
D — Decision Process
Definition: The step-by-step process the organization will follow to go from "evaluating" to "signed contract." Every step, every approver, every committee, every timeline.
Why it matters: If you don't know the process, you can't forecast accurately. Every unknown step is a potential deal-killer hiding in the shadows. The decision process includes people, steps, and timing — all three must be mapped.
How to uncover:
- "Can you walk me through every step from here to a signed agreement?"
- "Are there any review boards, steering committees, or approval layers we should know about?"
- "What's your target date for having a solution in place, and working backward from that, what needs to happen by when?"
- "Has this type of purchase been made before? What did the process look like last time?"
Green flags:
- The buyer has given you a clear, multi-step process with named approvers and dates
- You've validated the process with someone other than your primary contact
- The buyer has gone through a similar purchase process before (they know the ropes)
- Legal, procurement, and IT security reviews are identified and scheduled
Red flags:
- "We'll figure out the next steps after we finish evaluating" (they haven't thought about it, which means they're early stage)
- The process changes every time you ask (organizational dysfunction or your champion doesn't actually know)
- No timeline pressure — no event or deadline driving the decision ("we'd like to do this sometime this year")
- The buyer says they're the only decision-maker but the deal size suggests otherwise
Scoring:
- 0 = Decision process unknown
- 1 = High-level process known ("they'll evaluate, then decide")
- 2 = Step-by-step process mapped with approvers
- 3 = Process mapped, validated with multiple contacts, and aligned to a timeline
P — Paper Process
Definition: The administrative and legal process required to get from "verbal yes" to "signed contract." This includes legal review, procurement, security questionnaires, vendor onboarding, MSA negotiations, and payment terms.
Why it matters: More deals die in the paper process than most teams realize. A "verbal commit" is not a closed deal. The paper process can add 2-8 weeks to your cycle, and procurement teams have zero incentive to move quickly. Understanding this upfront prevents end-of-quarter surprises.
How to uncover:
- "Once we agree to move forward, what does the contracting process look like?"
- "Does your legal team need to review our agreement? How long does that typically take?"
- "Are there security or compliance questionnaires we should start on now?"
- "Will this go through procurement? Do they have preferred vendor requirements or standard terms they'll require?"
- "What payment terms does your organization typically use? (Net 30, quarterly, annual prepay?)"
Green flags:
- You've identified every step in the paper process and have timeline estimates
- You've started security questionnaires or legal review in parallel with the evaluation (not sequentially)
- Your champion is helping navigate internal bureaucracy
- You've dealt with this company's procurement team before and know their patterns
Red flags:
- The buyer says "just send us the contract and we'll sign" (either they're very small or they're underestimating their own process)
- Legal review is expected to take "a few weeks" with no specific timeline
- No one on the buyer's side has been through a procurement process like this before
- The buyer's organization recently changed procurement policies (new requirements you don't know about)
Scoring:
- 0 = Paper process unknown
- 1 = Basic awareness ("they have legal and procurement")
- 2 = Steps identified with rough timelines
- 3 = Full process mapped, parallel tracks started, champion actively facilitating
I — Identify Pain
Definition: The specific, urgent business pain that is driving this purchase. Not a "nice to have" improvement — a problem that is costing the organization money, time, risk, or competitive position, and that someone with power cares about fixing.
Why it matters: Pain is the fuel that drives deals forward. Without genuine, urgent pain, deals stall. With it, deals close themselves. The strength of the pain determines the speed of the deal and the size of the budget.
Three levels of pain:
| Level | Description | Buying Behavior |
|---|---|---|
| Latent pain | The buyer knows the problem exists but isn't actively trying to fix it | Will take meetings but won't commit to an evaluation timeline |
| Active pain | The buyer is actively looking for a solution | Running evaluations, has a timeline, has budget (or is requesting it) |
| Critical pain | The problem is causing measurable damage and someone powerful wants it fixed NOW | Short sales cycles, executive engagement, budget is not a question |
How to uncover:
- "What prompted you to start looking at solutions for this now, rather than 6 months ago?"
- "What happens if you don't solve this problem? What's the impact?"
- "Who else in the organization is feeling this pain? How does it affect their work?"
- "Have you tried to solve this before? What happened?"
- "On a scale of 1-10, how urgent is solving this problem relative to other initiatives on your plate?"
The "3 Whys" technique: When a buyer states a pain, ask "why does that matter?" three times. Each layer gets you closer to the real business impact.
- "We spend too much time on manual reconciliation." → Why does that matter?
- "It delays our month-end close by 5 days." → Why does that matter?
- "Our CFO is presenting late numbers to the board and it's becoming a career-limiting issue for our controller." → Now you have the real pain.
Green flags:
- Pain is specific, quantified, and connected to someone's performance goals
- Multiple stakeholders feel the same pain (it's not just one person's pet project)
- The buyer has tried to solve this before (proven willingness to invest)
- There's a triggering event creating urgency (regulatory deadline, audit finding, board mandate)
Red flags:
- The buyer can articulate the problem but can't quantify the impact
- Pain is acknowledged but no one is assigned to fix it
- The "pain" is actually curiosity — they want to explore options, not solve a problem
- The pain is felt by your contact but not by anyone with budget authority
Scoring:
- 0 = No pain identified
- 1 = Latent pain acknowledged
- 2 = Active pain with some urgency
- 3 = Critical pain with executive sponsorship and quantified business impact
C — Champion
Definition: An internal advocate within the buyer's organization who has power, influence, and a personal stake in your success. They actively sell on your behalf when you're not in the room.
Why it matters: You cannot close a deal you're not in the room for. And you're not in the room for 90% of the buying process. Your champion is your surrogate salesperson. Without one, you're hoping, not selling.
A true champion has ALL THREE of these qualities:
- Power/Influence: They have organizational standing. People listen to them. They can get a meeting with the economic buyer.
- Access to information: They can tell you what's happening behind the scenes — who's skeptical, what the real criteria are, where you stand vs. competition.
- Personal win: They personally benefit from your success — a promotion, solving a problem they own, looking innovative to their leadership.
If any one of these is missing, you have a coach or a supporter, not a champion. See references/champion-tests.md for the 3 validation tests.
How to build a champion:
- Help them look good internally (arm them with business cases, slides, ROI calculators)
- Give them information they can't get elsewhere (industry benchmarks, peer comparisons)
- Make it about their career, not your deal ("this could be the project that gets you promoted")
- Be honest about your weaknesses (builds trust and helps them defend against internal skeptics)
Green flags:
- They proactively share internal intelligence with you
- They've set up meetings with other stakeholders without being asked
- They've used your materials in internal presentations
- They tell you when things are going wrong (not just when things are going well)
- They push back on your proposals to make them better (they're invested in winning)
Red flags:
- They agree with everything you say (too eager = no influence)
- They can't get you a meeting with the economic buyer
- They don't know the decision process or criteria (no access to information)
- They say "I love your product" but can't articulate why it matters to their organization
- They're junior or new to the organization (limited influence)
Scoring:
- 0 = No champion identified
- 1 = Friendly contact, but no power, access, or personal stake
- 2 = Has 2 of 3 champion qualities
- 3 = True champion with power, access, and personal stake, actively selling internally
C — Competition
Definition: Who else is being evaluated, what their strengths and weaknesses are, and how the buyer perceives the competitive landscape. This includes direct competitors, indirect alternatives (consulting firms, manual processes), internal builds, and the status quo.
Why it matters: If you don't know who you're competing against, you can't position yourself effectively. And the most dangerous competitor is the one you don't know about.
The 4 types of competition:
- Direct competitors: Other vendors in your category
- Indirect competitors: Different approaches to the same problem (consulting firms, outsourcing, adjacent tools)
- Internal build: "We'll build it ourselves" — more common in engineering-led organizations
- Status quo: "We'll keep doing what we're doing" — wins more deals than any competitor
How to uncover:
- "Who else are you evaluating?" (direct ask — works more often than you'd think)
- "If you don't choose us, what would you do instead?" (captures the full competitive set including status quo)
- "What would you need to see from us to feel confident we're the right choice over the alternatives?"
- Ask your champion: "What are the internal conversations about the other options?"
Competitive positioning rules:
- Never trash the competition. It's unprofessional and it backfires. Instead, acknowledge their strengths and differentiate on what matters to THIS buyer.
- Set traps, don't react. If you know the competitor is weak on security, raise security as a topic before the buyer mentions it. Ask questions that expose the competitor's weakness without naming them.
- Compete on your strengths, not their weaknesses. "Here's why we're great at X" is more persuasive than "here's why they're bad at X."
- Understand their playbook. Know what your competitor will say about you, and pre-empt it.
Green flags:
- You know every competitor in the deal and their perceived strengths
- Your champion is sharing competitive intel
- The buyer's decision criteria favor your strengths (especially if you helped shape them)
- You're positioned as the "safe" choice (for risk-averse buyers) or the "innovative" choice (for forward-leaning buyers) — whichever matches their culture
Red flags:
- "We're only looking at you" (almost never true; they're either lying or this is a check-the-box evaluation)
- A competitor you didn't know about suddenly appears late in the process
- The buyer's questions shift to areas that are your competitor's talking points
- The buyer is asking for features you don't have that sound like a competitor's feature list
Scoring:
- 0 = Competitive landscape unknown
- 1 = Know some competitors are involved, no details
- 2 = Know competitors and their general positioning
- 3 = Full competitive map with positioning, buyer perceptions, and counter-strategy
Deal Scoring: Putting It All Together
Scoring Scale
Each element is scored 0-3. Total possible: 24.
| Score Range | Qualification Level | Action |
|---|---|---|
| 20-24 | Strong — High probability of closing | Invest maximum resources; accelerate timeline |
| 15-19 | Qualified — Real deal with gaps to close | Identify gaps; create plan to fill them in next 2 interactions |
| 10-14 | Developing — Potential, but significant unknowns | Must fill gaps before advancing to next stage; set a deadline |
| 5-9 | Weak — Major qualification gaps | Honest conversation with manager; consider deprioritizing |
| 0-4 | Unqualified — Not a real deal | Kill it or move to nurture. Do not invest selling time. |
Stage Gates
Deals should not advance past certain pipeline stages without minimum MEDDPICC scores. See references/stage-gates.md for the full framework. Summary:
| Pipeline Stage | Minimum Total Score | Required Elements |
|---|---|---|
| Discovery | 4 | Pain identified (1+), some contact engagement |
| Qualification | 10 | Pain (2+), Metrics (1+), Champion (1+), Economic Buyer (1+) |
| Solution / Demo | 14 | Above + Decision Criteria (2+), Competition (1+) |
| Proposal / Negotiation | 18 | Above + Decision Process (2+), Paper Process (1+) |
| Commit / Forecast | 21 | All elements at 2+, Champion at 3 |
When to Kill a Deal
Disqualification saves your most valuable resource: time. Kill a deal when:
- No identifiable pain. If after 2-3 conversations you can't find a quantified, urgent pain, this is not a deal. It's an exploration.
- No access to the economic buyer. If you can't even get a meeting with the person who controls budget after multiple attempts, your champion either doesn't have the influence they claim or the economic buyer isn't interested.
- Decision timeline is "someday." No triggering event, no deadline, no urgency. "Sometime next year" means never.
- Your champion leaves. If your only champion departs the organization, the deal resets to zero. Reassess from scratch.
- Criteria are stacked against you. If the decision criteria were clearly written by a competitor and the buyer won't reconsider them, you're the column B vendor there to validate a decision already made.
- The buyer won't share information. If they won't tell you the budget range, the competition, the decision process, or the criteria, they don't trust you enough to buy from you.
- The math doesn't work. If the potential deal value doesn't justify the sales effort required (small deal + long cycle + low probability = negative ROI), walk away.
How to kill gracefully:
- Be honest: "Based on what I'm seeing, I'm not sure we're the right fit for you right now. Here's why."
- Leave the door open: "If [conditions] change, I'd love to reconnect."
- Don't burn bridges: Today's dead deal is next year's opportunity.
Common Traps: Deals That Look Good But Will Never Close
The "Happy Ears" Deal
Everything the buyer says sounds positive. They love the demo. They love the pricing. They love you personally. But there's no pain, no timeline, and no budget. You're being used as a benchmark, a placeholder, or entertainment.
Test: Ask for something that costs them effort. "Can you introduce me to your CFO?" If they deflect, it's happy ears.
The "Free Consulting" Deal
The buyer keeps asking for POCs, custom analyses, architectural reviews, and workshops. They're getting enormous value from your sales process without any intention to buy. Each ask feels like "progress" but it's actually a treadmill.
Test: Gate your effort. "We're happy to do a deep-dive POC. To make sure we're both investing appropriately, can we align on the decision criteria and timeline before we scope it?"
The "Column B" Deal
You were invited to validate a decision that's already been made. The buyer needs three quotes for procurement compliance. You are the third quote.
Test: Ask about the evaluation timeline and process. If the process started months ago and you're late to the party, you're Column B. Ask directly: "Are you currently leaning toward any of the other solutions?"
The "Champion Without Clothes" Deal
Your "champion" is enthusiastic but has no organizational influence. They're a power user, an individual contributor, or someone new to the company. They want your product but can't get it bought.
Test: Run the champion tests in references/champion-tests.md. If they fail all three, you need to find a real champion or accept this deal will stall.
The "Moving Goalpost" Deal
Decision criteria change. Timelines shift. New stakeholders appear. Each time you think you're close, the finish line moves. This usually means there's internal disagreement about whether to do this project at all.
Test: Ask your champion: "Is there internal debate about whether this project should happen?" Get to the meta-conversation.
Reference Files
| File | Purpose |
|---|---|
references/meddpicc-scorecard.md | Fillable scorecard for each deal |
references/champion-tests.md | The 3 champion validation tests with worked examples |
references/stage-gates.md | What must be true at each pipeline stage |
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- deal-qualification-gates by NEON-Rutger · 45
- deal-qualification by jbalbu01 · 14
- budget-extraction-qualification by louisblythe · 136
- deal-documentation by louisblythe · 136
- deal-review-win-loss by louisblythe · 136
- deal-upselling by louisblythe · 136
- lead-qualification by louisblythe · 136
- lead-qualification-logic by louisblythe · 136
Need help setting it up?
This page tells you what deal-qualification does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.