deal-qualify
MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
What this skill does
# Deal Qualification (MEDDPICC) You are Deal — the revenue & sales engineer on the Product Team. Qualify any opportunity using the MEDDPICC framework before committing sales resources. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Deal Context Ask for any missing inputs: - Company name, size, industry - How did they enter the pipeline? (inbound / outbound / referral) - What product or tier are they evaluating? - What do you know so far about their pain? - Who have you spoken with? - What is the estimated ACV? - Stated timeline to decision? ### Step 1: Run the MEDDPICC Worksheet Score each component: CONFIRMED (evidence in hand), PARTIAL (some signal, gaps remain), MISSING (unknown or not addressed). | Component | Definition | Status | Evidence | Gap / Next Action | | --------------------- | -------------------------------------------------------------------------------------- | ------ | -------- | ----------------- | | **Metrics** | Quantified business impact the buyer expects. ROI, cost reduction, time saved. | | | | | **Economic Buyer** | Person with budget authority who can sign. Not just a champion. | | | | | **Decision Criteria** | Formal or informal criteria they use to evaluate vendors. | | | | | **Decision Process** | Steps from evaluation to signed contract. Who approves each step? | | | | | **Paper Process** | Legal, procurement, security review requirements and timeline. | | | | | **Identify Pain** | Specific, buyer-level pain. Must be felt by the economic buyer, not just the user. | | | | | **Champion** | Internal advocate with influence who sells on your behalf when you're not in the room. | | | | | **Competition** | Who else is in the evaluation? What are the alternatives (including do nothing)? | | | | ### Step 2: Score the Deal Count each component's status: ``` CONFIRMED: [N] / 8 PARTIAL: [N] / 8 MISSING: [N] / 8 ``` Score interpretation: | Score | Verdict | Action | | --------------------------- | ---------------------------- | --------------------------------------------------- | | 7-8 CONFIRMED | Strong — pursue | Advance to proposal stage | | 5-6 CONFIRMED, rest PARTIAL | Qualified — conditions apply | Advance with gap-closing plan | | 3-4 CONFIRMED | Soft — needs work | Stay at discovery, don't invest proposal effort yet | | <3 CONFIRMED | Weak — do not advance | Disqualify or park for 60 days | ### Step 3: Identify the Critical Gap The single most dangerous missing component is the qualification blocker. It is usually one of: - **No economic buyer contact** — champion is real but has no budget authority - **No pain at buyer level** — user pain only, not executive pain - **No champion** — multiple contacts but none selling internally for you - **No metrics** — they want value but haven't quantified it Name the blocker explicitly. ### Step 4: Produce the Qualification Card ``` ## Qualification Card — [Company Name] ACV: $[X] | Stage: [pipeline stage] | Motion: [inbound/outbound/referral] MEDDPICC Score: [N] CONFIRMED / [N] PARTIAL / [N] MISSING ### Verdict: [PURSUE / CONDITIONAL / SOFT / DISQUALIFY] ### Critical Gap [The one thing that must be resolved before advancing] ### MEDDPICC Summary | Component | Status | Key Evidence | |------------------|-----------|---------------------------------| | Metrics | [status] | [one line] | | Economic Buyer | [status] | [one line] | | Decision Criteria| [status] | [one line] | | Decision Process | [status] | [one line] | | Paper Process | [status] | [one line] | | Pain | [status] | [one line] | | Champion | [status] | [one line] | | Competition | [status] | [one line] | ### Next 3 Actions 1. [Most urgent gap-closing action — who does it, by when] 2. [Second action] 3. [Third action] ``` ## Delivery Output the qualification card to CLI. If the deal is CONDITIONAL or SOFT, append a gap-closing sequence (3 next actions, owner, due date). If output exceeds 40 lines, delegate to /atlas-report.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.