MEDDPICC scorecard
Generates a MEDDPICC deal qualification scorecard per account, scoring 0–3 for each element with evidence citations
One of 51 free, open-source prompts from Sonora — copy-paste-ready AI prompts for customer success and account management, organized by customer lifecycle stage. Copy this into any AI assistant, or run it on autopilot inside Sonora.
Generate a MEDDPICC deal qualification scorecard for [Customer]. Be dense, not verbose — fit everything into a single-page brief.
Step 1: Gather account context
Retrieve contract details (ARR, renewal date, term), account tier, and AM/CSM ownership. If multiple opportunities exist, focus on the most recent or highest-ARR one.
Step 2: Review stakeholder intelligence
Identify the economic buyer, champion(s), and key decision-makers. Note engagement recency and sentiment for each.
Step 3: Pull meeting notes and touchpoints
Retrieve recent meeting notes and touchpoints from the last 90 days. Flag any conversations referencing evaluation criteria, procurement timelines, competitive alternatives, or quantified business outcomes. Weight the past 90 days most heavily — older data can support a score but must not be the sole basis for a 2 or 3.
Step 4: Pull issues and feature requests
Surface open pain points and unresolved blockers from support tickets and feature requests.
Step 5: Check health and sentiment signals
Retrieve health score signals and sentiment trends for evidence of deal momentum or stall.
Step 6: Score each MEDDPICC element
Use this scale for all eight elements:
- 0 — Unknown: No data available. This element has not been explored.
- 1 — Identified: The element has been mentioned but lacks specifics or validation.
- 2 — Validated: Confirmed through direct conversation or documented evidence.
- 3 — Locked: Fully substantiated with multiple data points; low risk of change.
Every evidence citation must reference a specific date, data point, or interaction. Never infer or speculate. If no supporting data exists for an element, score it 0 and write “No data available” as the evidence summary.
Output
Write the output as a single-page brief with the following sections in order:
- H1 heading: “[Customer] MEDDPICC Scorecard”
- Line 1: Overall Score: [X/24] | Deal Stage: [stage] | Weakest Element: [element name]
- Line 2: ARR: $X | Renewal: [date] ([N] days out) | Tier: [tier] | AM/CSM: [name] | Economic Buyer: [name] | Champion: [name]
- Edge cases: If no opportunity or deal context exists, note this after the header and clarify that scores reflect relationship depth rather than an active deal. If no economic buyer or champion is identified, score those elements 0 and flag them prominently in Critical Gaps.
- Scorecard table with columns Element, Score, Evidence Summary, Gap — one row per element in this order: Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition. Score is 0–3. Evidence Summary is one sentence citing a specific data point or interaction. Gap states what’s missing for scores of 0 or 1, or “—” for scores of 2 or 3.
- Key Evidence — top 3 data points supporting the strongest-scored elements, each formatted as: [Date]: [What was confirmed — one sentence]. (Source)
- Critical Gaps — top 3 elements scoring 0 or 1, ranked by deal impact. For each: bold the element name and gap title, explain what’s unknown and why it matters, and suggest one specific discovery question or action.
- Next Steps — a table of three actions to advance the weakest MEDDPICC elements, with columns: Action, Owner, By when, Expected outcome.
- Data gap note: If no meeting notes exist within the past 90 days, note this and base scores only on documented touchpoints.
Data sources required
The catch
A prompt is only as good as the data you feed it.
Run this well and you'll be stitching together 4 disconnected systems by hand, for one account at a time — and the answer is only ever as fresh as your last copy-paste. Sonora already has the context, live:
- CRM / customer data — connected and continuously synced
- Meeting transcripts — connected and continuously synced
- Support tickets — connected and continuously synced
- Feature request tracker — connected and continuously synced
Inside Sonora this prompt runs grounded in your real customer data, on a schedule, across every account at once — and flags what needs you, before you have to ask.