MEDDPICC Call Review

The file

---
name: meddpicc-call-review-prompt
description: >-
  A MEDDPICC scorecard for any sales call transcript: each of the eight elements scored 0 to 4 with evidence from the call, plus an overall score out of 100, so managers see which deal gaps to coach.
  Task type: Analyze. Built for Enablement, Sales, Leadership.
  Use when the request sounds like "MEDDPICC Call Review".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Deal Strategy and Negotiation
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/meddpicc-call-review-prompt
---

# MEDDPICC Call Review

A MEDDPICC scorecard for any sales call transcript: each of the eight elements scored 0 to 4 with evidence from the call, plus an overall score out of 100, so managers see which deal gaps to coach.

One job only: a MEDDPICC scorecard for any sales call transcript: each of the eight elements scored 0 to 4 with evidence from the call, plus an overall score out of 100, so managers see which deal gaps to coach. Anything outside that job belongs in another file in the Deal Strategy and Negotiation suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- sales call transcript
- component score
- example

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
The MEDDPICC methodology is a framework used in sales to ensure a comprehensive and effective sales process. It stands for:

M - Metrics: Identifying the key financial or operational metrics the prospect is trying to improve
E - Economic Buyer: Understanding who the real decision maker is 
D - Decision Criteria: Determining what factors will drive the prospect's purchase decision
D - Decision Process: Learning the formal process the prospect follows to make a purchase
P - Paper Process: Mapping out the internal process/paperwork required to approve a purchase
I - Identify Pain: Uncovering the key problems/challenges the prospect is facing
C - Champion: Finding an internal advocate for your solution within the prospect's organization
C - Competition: Understanding who your competitors are and how you compare

You will be evaluating a sales call transcript against this MEDDPICC methodology. Here are the steps:

1. First thing you do is ask the user for the transcript and what sales stage it is along with any other questions you have about the call. After they give it to you, Read through the entire sales call transcript provided in {$SALES_CALL_TRANSCRIPT}.

2. For each component of MEDDPICC, evaluate how well the salesperson addressed that area during the call. Use the following scale:
 - 0: Not addressed at all
 - 1: Barely addressed 
 - 2: Somewhat addressed
 - 3: Well addressed
 - 4: Thoroughly addressed

3. Write down your evaluation for each MEDDPICC component inside <component_score> tags, along with a brief justification.

<example>
<component_score>
M (Metrics): 2
The salesperson asked about the prospect's website traffic metrics, but did not probe deeply into their goals for improving those metrics.
</component_score>
</example>

4. After evaluating each component, provide an overall MEDDPICC score for the sales call on a scale of 0-100. Justify this overall score by referring back to your evaluations of the individual components.

<example>
Overall MEDDPICC Score: 65/100

Justification: 
The salesperson did a good job identifying the economic buyer and decision criteria, but fell short in other areas like understanding the full decision process, identifying the key pain points, finding an internal champion, and addressing the competition. By neglecting some of these critical components, the call likely did not position the solution as compellingly as it could have.
</example>

5. Before providing your final evaluations, you may want to use an internal <scratchpad> to take notes and think through your reasoning.

Remember, your goal is to comprehensively evaluate how well the salesperson followed the MEDDPICC methodology based on the call transcript provided. Provide your evaluations in the format specified, referring back to the transcript details to justify your scores.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/meddpicc-call-review-prompt
- Suite: https://www.therevenueaireport.com/agent-skills/suites/deal-strategy-and-negotiation
- Publication: The Revenue AI Report, https://www.therevenueaireport.com