MEDDPICC: what it stands for, and how to run it with dated milestones

The definitions below follow MEDDICC, the training company that publishes the framework. The third column is the event that proves a letter, as opposed to a guess typed into a CRM field.

In our experience, six of the letters get said out loud somewhere: on a call, in an email thread, in a procurement form. Two don’t. MEDDICC notes that the economic buyer is “unlikely to raise their hand and tell you they’re the EB,” and nobody announces they’re your champion. Those two letters are the rep’s judgment, and they deserve the hardest look in every deal review.

MEDDIC is the original six letters: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. MEDDICC adds Competition. MEDDPICC adds Paper Process, for eight. The names blur in practice. Plenty of teams say MEDDICC and mean all eight, and MEDDICC, the company, recommends “the most complete version: MEDDPICC.” The I has two names too: Identify Pain in MEDDIC, and Implicate the Pain in MEDDICC’s own MEDDPICC definitions. This guide uses MEDDPICC and Identify Pain.

The framework came out of PTC, the design software company, in the 1990s. According to MEDDICC, Dick Dunkel formulated the six elements there. Jack Napoli is credited alongside him, and PTC sales leaders such as John McMahon shaped it. We didn’t find a record of who added Competition and Paper Process, or when.

Use all eight. The two later additions are the ones that surprise you in the last month of a deal: an option you never heard about, or a security review nobody mentioned.

The letters don’t arrive in acronym order. Buyers tell you about pain and metrics early, the people and the process later, and the paperwork last. So map each letter to the milestone where it should be proven, and give each milestone a date.

The targets count days from the first meeting. Two of them, “Pilot or priced proposal agreed” within 21 days and “Signer engaged and quote sent” within 30, come from one of our playbooks in Arrows. The rest are examples. Set yours from how long your won deals take.

The last column is the rule that turns a gate into a path. A missed target doesn’t freeze the deal or mark the rep down. It becomes the next step, with a date on it. The same playbook puts it plainly: a deal is “off the path when a milestone slips past its target,” or when it “goes 7 days without a real touch.”

Ebsta’s benchmarks put numbers on both ideas. Deals were 324% more likely to win if MEDDPICC was completed by the Solution Presented stage, and Ebsta reports that more than 7 days of activity with no future activity reduces win rates by 65%. Both are correlations. The 324% is about timing: the letters were proven by the time the seller presented a solution, around the fourth milestone here. It doesn’t say to hold a deal back until the fields are full.

Champion: proven by an introduction

MEDDICC defines a champion as “a person who has power, influence, and, subsequently, credibility within the customer’s organization.” A contact who likes you but lacks that power is a coach: useful for context, unable to carry the deal. A contact with power who “either doesn’t have a vested interest or isn’t selling internally for you” isn’t a champion yet either.

The cleanest test is an introduction. MEDDICC says a champion matters because “they will introduce you to key stakeholders,” and the stakeholder who matters most is the economic buyer. Until your contact puts you in front of the person who signs, treat them as a coach and forecast that way. Breadth is the other signal. Gong’s analysis of 1.8 million new business deals closed in 2024 found that won deals had twice as many buyer contacts as deals that didn’t close.

Paper process: ask before the yes

Paper process is every step between the buyer’s yes and a signed contract: procurement intake, a security questionnaire, legal redlines, the signature itself. Each step has its own owner and its own queue, and none of them move on your timeline. Reps leave this letter late because asking about contracts on day 10 feels pushy. It isn’t. “What has to happen after you decide?” is a fair question by day 14, and it puts a date on the paper before the deal depends on it.

A worked example (illustrative)

Day 31 of a deal. You sent a priced proposal on day 19, and your contact, a director of operations, says it’s “with leadership.” The COO, who signs, hasn’t been on a call. Nobody has mentioned security review. On the map, the deal missed its 30-day milestone yesterday, with two letters open: Champion, because the director hasn’t introduced you to the signer, and Paper Process, because nobody has told you the steps. Here are the three next steps the map gives you, as the rep would send them:

1. Today, to the director: “Could you introduce me to your COO this week? I’d like 20 minutes to confirm what she needs to see before signing. Thursday or Friday works on my side.” Due: the introduction by day 35.
2. Today, in the same email: “Who on your side runs vendor security reviews and contract review? If you send me their names, I’ll get our security documents to them now, so that runs in parallel.” Due: the names by day 33.
3. Day 35, if there’s no introduction: “Would it help if I wrote a short note you could forward to your COO? I’ll keep it to five lines.” If that stalls too, the director is a coach, and the close date in the forecast moves out.

Each step is an ask with a date. It either proves the letter or tells you the deal is further from signature than the forecast says. If you put asks like these in the recap after every call, our free sales follow-up email builder gives you a starting draft.

Most MEDDPICC rollouts stall in the CRM. The team adds eight required fields, reps fill them in before the forecast call, and the fields go stale. Prospeo’s MEDDIC implementation guide puts it bluntly: “The fastest way to kill MEDDIC is mandatory fields that reps treat like tax forms.” It adds that reps fill fields in “five minutes before pipeline review to keep managers happy.”

A field records what was true on the day someone typed it. A live deal changes every week. A dated milestone shows when it’s late. When a target passes and its letter is still open, everyone sees it without anyone updating a thing.

When MEDDPICC is overkill

The same Prospeo guide says “MEDDIC is overkill for transactional sales with a single decision-maker.” We agree. If one person decides, signs and pays inside a couple of weeks, use a lighter check like BANT and keep the eight letters for deals with a buying group.

When AI fills the fields

AI tools now fill MEDDPICC fields from call transcripts, and their vendors are candid about the limits. coffee.ai, which sells AI MEDDPICC tooling, says champion identification “remains the hardest MEDDPICC element to automate reliably” and that “a human review layer is required to reach acceptable accuracy.” Sybill, which auto-fills MEDDPICC fields, sends low-confidence entries to a review queue and says “the rep’s job shifts from documenting to reviewing.”

Summaries also drop things the buyer did say. In our test of 22 AI notetakers on one sales call, each on its default template, several summaries missed the timeline and who makes the decision: the raw material for Decision Process and Economic Buyer. So whatever fills in the letters, keep the source next to each answer.

A milestone map is easy to keep on five deals, and your best rep already keeps one in their head. The other fifteen get improvised, and those are the deals where the economic buyer hears about you last.

Arrows works every open deal against your team’s playbook. We build it with you at the agent kickoff, from how your reps already work their deals, and it’s written in plain language in the same shape as the map above: milestones with targets, when each agent action runs, and the rules. If your team qualifies with MEDDPICC, your milestones can carry the letters in your team’s own words.

On each deal, the agents do the work between calls:

• Overview keeps track of where the deal stands against its milestones, what happens next, who decides and what goes on the quote.
• Multi-thread runs when someone new appears on the deal, or when the next milestone needs a role nobody fills yet, such as the signer before the quote. Arrows shows who’s on the deal and who decides, so your rep can multi-thread early. Your rep does the relationship work.
• Post-call follow-up drafts the recap your rep sends that day, with the next milestone and a date for it.
• CRM update prepares changes from calls and emails, and writes them back to HubSpot, Salesforce, Attio, Close or Pipedrive once your rep approves them.

Today, every one of those waits for your rep’s approval before it sends.

One playbook for the whole team matters more than any single rep’s setup. When we tried running our sales team in Claude, two reps started from the same skills and ended up with two versions of the sales process, and nobody owned the plan for the deal.