MEDDIC sales process: how to run it from first call to close

The MEDDIC sales process is what turns six qualification criteria into something a team actually runs: which criterion gets captured at which stage, who owns it, how it is inspected before a deal enters the forecast, and what happens when it stays empty. The framework supplies the questions. The process is what makes the answers exist, stay current and get challenged. This article covers the stage mapping, the ownership split, the inspection cadence and the three points where implementations collapse.

Why do most MEDDIC rollouts look excellent for a quarter and then quietly die? Rarely because reps reject the framework. Almost always because nobody defined when each letter gets filled, or what happens when it does not.

What the process adds to the framework

Dick Dunkel, who wrote the original acronym, describes MEDDIC as an operating system rather than a checklist, a distinction he returns to in an interview on its origins. The practical difference shows up in one place: a checklist is completed once, an operating system runs continuously. Criteria that were true at discovery are frequently false by proposal stage, because the buying committee changed, a competitor arrived, or a reorganisation moved the budget.

So the process has to answer three questions the framework does not: when is each criterion first captured, when is it re-verified, and who is accountable for the gap. It also assumes the criteria themselves are understood, so if that is still fuzzy across the team, start with what each MEDDIC criterion actually requires before building any of this.

Mapping the criteria to your stages

The exact mapping matters less than having one and applying it identically across the team. What kills consistency is a stage definition based on rep confidence rather than on evidence: a deal moves forward because something is known, not because time has passed.

Who owns what

The account executive owns capture and is accountable for the gaps. The sales engineer usually owns Decision Criteria in technical evaluations, because that is where the real comparison happens. The manager owns inspection and, more importantly, owns the unpopular decision to pull an unqualified deal out of the forecast. When that last responsibility is unclaimed, MEDDIC becomes documentation of deals nobody intends to disqualify.

The inspection cadence that keeps it honest

Pipeline review is where the process lives or dies. Four questions do most of the work.

• Which criterion is weakest on this deal, and what is the plan to close it this week?
• What did the buyer actually say that supports this entry, and when?
• Who else has entered the decision since we last looked?
• If this slips a quarter, which letter will turn out to have been the reason?

Asking the second question consistently changes rep behaviour faster than any training, because it moves the standard from opinion to evidence. It also requires a source of truth beyond the rep's own summary, which is where systematic call scoring replaces spot checks.

Structuring it in the CRM

Each criterion becomes a field, not a paragraph in a notes box. Fields can be reported on, filtered and used to trigger workflows; notes cannot. Two rules save most of the pain later: use structured values wherever possible rather than free text, and keep a separate field for the evidence, so a manager can see what the entry is based on without opening the deal. HubSpot's step-by-step guide to the framework walks the same sequence from the qualification side.

Three ways implementations collapse

• Fields without inspection. A field nobody is ever asked about becomes a field nobody fills, usually within six weeks.
• Retroactive completion. Reps filling the six criteria the night before the review produce a tidy CRM and zero forecast accuracy.
• Pass-fail thinking. Treating MEDDIC as a gate rather than a live picture leads teams to either disqualify too early or to fake completeness to keep the deal alive.

A fourth failure is scope. Teams often add letters before the base process holds: whether MEDDICC and MEDDPICC earn their extra fields depends on where your deals actually die, and if the six-criteria version is already too heavy for your cycle, our comparison of 12 sales frameworks shows the lighter options. If you are choosing tooling to support any of this, look closely at what the vendor does after the contract: configuring criteria, mapping fields and setting up scorecards is where these projects stall, and most vendors hand you a blank page.

Running the process on every conversation with Praiz

The gap between a documented process and a lived one is the effort it takes a rep to update it. Praiz closes that gap by working from the conversation itself. The MEDDICC Summary agent extracts what the prospect explicitly stated on each criterion and syncs it to the matching CRM fields after every call, so the record reflects the deal rather than the rep's memory of it. The MEDDIC Scorecard agent evaluates coverage call by call, giving managers the inspection data the cadence above depends on. Both are configurable to your stage mapping in the Praiz AI agents library. Praiz customer teams see 100% of deals with MEDDIC completed automatically, against 32% before (internal data), and the setup is handled with you during onboarding.

Frequently asked questions