Identify Pain: the problem, in their words, with a number on it
No anchored pain — nothing pulls the deal forward.
Updated
What is the I in MEDDPICC?
The I is Identify Pain: the problem pulling the deal forward, in the buyer’s own words rather than a vendor’s paraphrase. Some teams call it Implicate the Pain, and meddicc.com uses both names. A pain that has only been stated is a topic; a pain that has been quantified is a business case. The gap between the two is why deals with enthusiastic champions still lose to no-decision.
How do I get the prospect to put a number on the problem?
Don’t bring the number. Build it with them from the workaround: who does it, how often, and for how long. Then ask what a year of it costs, so the arithmetic is theirs.
How it actually gets missed
Reps hear a pain on the discovery call, write it down, and never take it further, because it already sounds like enough. It is not: nobody has said how often it happens, who it happens to, or what it costs — so when the deal reaches a budget conversation there is nothing to weigh the price against.
How deep, not how many
Identify Pain questions, from stated to quantified
Identify Pain has three rungs, and where a deal sits on them is the difference between a dimension you have answered and one you have qualified. These are the rungs SalesWolf marks on the deal, by the same names and in the same order. What is written under each is the standard to hold a deal to. The product can only mark what is on record, so check its rung against this bar before you rely on it.
stated
Somebody has said the problem out loud. This is where a discovery call usually ends, and it is one rung of three.
“What made you take this call now, rather than six months ago?”
Gets the problem in their words, with a hint of what changed.
“If you could fix one thing about how this works today, what would it be?”
Asks for the pain without steering them towards yours.
contextualized
You know who it affects, how often, and what they currently do instead. The workaround is usually where the real cost hides.
“Who feels that day to day, and what do they do instead right now?”
Moves a stated problem into context by finding the workaround, which is where the cost lives.
“How often does that actually happen — weekly, monthly, every close?”
Gets frequency, without which no figure can be built.
quantified
There is a number on it — hours, headcount, revenue, error rate. Quantified pain is what a business case is built out of.
“How many hours a week does the workaround take, and whose hours are they?”
Builds the number from the workaround you already found, in units they can check.
“If nothing changed for another year, what does that cost you?”
Asks the customer to do the arithmetic, so the number is theirs rather than yours.
Done when · You can say, in their words, what is actually pulling this deal forward.
The questions for every letter, on one page.
This page in plain text, with nothing to sign in to. Open it on a phone on the way into the call.
Sample deal · Halden Freight · Identify Pain
On a deal, it has a position. On this one, it is confirmed at quantified.
Qualification
Gaps aren't failures. They're the next things worth learning.
14 days free, no card, no call.