Pain Discovery

A prospect who has described a symptom is aware of a problem. That’s different from being motivated to solve it.

Awareness doesn’t close deals. Urgency does. And urgency only comes from understanding what the problem actually costs: in revenue, in time, in organizational risk, or in personal consequence for the person sitting across from you on the call.

When a rep accepts a symptom and moves on, they’re building a deal on a foundation that hasn’t been tested. The prospect said something was wrong. The rep filed it as “qualified” and moved to the demo. Three months later, the deal stalls because the prospect never felt the weight of the problem clearly enough to prioritize fixing it.

The number a CFO approves, the urgency a champion carries into an internal meeting, the business case that gets the economic buyer to act: all of it depends on pain that has been fully surfaced, quantified, and owned. None of it comes from a symptom the rep didn’t dig past.

Pain in a B2B sale exists at three distinct levels. Most reps stop at the first one.

Layer 1: Organizational pain

This is the symptom layer. Something in the business isn’t working. Reps aren’t ramping fast enough. Deals are stalling after the first meeting. The team is missing quota. The pipeline looks full but forecasts keep coming in low.

Organizational pain is real, but it’s diffuse. It belongs to everyone and no one. It creates awareness in the room but rarely creates the personal urgency that drives a buying decision forward.

Layer 2: Financial pain

This is where the symptom gets a number attached to it. Slow ramp time isn’t just a problem: it means each new hire produces zero revenue for six months, at a fully-loaded cost that the business is carrying. Deals stalling after the first meeting isn’t just a problem: it means the average deal cycle is stretching from 60 days to 90, which means Q3 pipeline isn’t closing in Q3.

Financial pain is what a CFO needs before they approve a budget. It’s what a champion needs before they can make a compelling internal case. Without it, the business case is “this seems like a good idea.” With it, the business case is “we are losing $X every month this goes unsolved.”

Layer 3: Personal pain

This is the layer most reps never reach, and it’s the one that actually moves deals.

Organizational problems are felt by teams. Financial problems are felt by the business. Personal pain is felt by the specific person on the call: the VP of Sales who has to be on every new hire’s calls for their first two months. The Head of Enablement whose playbook isn’t working and who’s getting pressure from above. The CRO who can’t forecast accurately because pipeline is full of deals that were never properly qualified.

When a prospect describes a problem they feel personally, the conversation changes. They stop describing and start advocating. They have a stake in solving it that’s beyond professional obligation. That’s the person who becomes a champion. That’s the person who will push for budget, pull in the economic buyer, and keep the deal moving when it hits internal friction.

Finding personal pain is the goal of pain discovery. Everything else is a step toward it.

The technique is simple. The execution is hard because it requires the rep to resist the strongest instinct in sales: the urge to solve.

When a prospect describes a symptom, the natural sales response is to connect it to a solution. The prospect says “our reps take too long to ramp” and the rep’s brain immediately finds the feature that addresses it. The temptation to pivot to the pitch is immediate and almost physical.

Pain discovery requires the opposite move. When a symptom surfaces, go deeper into it, not forward toward the solution. Three questions do most of the work:

The process question

Maps current reality. “Walk me through how that works today.” Or: “What does your current approach look like when a new rep joins?” This gives the rep specific context to build on, and often surfaces additional symptoms the prospect hadn’t mentioned because they’d forgotten they were problems.

The impact question

Attaches consequences to the symptom. “What happens when that breaks down?” Or: “What does that mean for the business when a rep isn’t productive for six months?” This is where the symptom starts becoming financial pain. The prospect is now calculating a cost, often out loud, for the first time.

The personal question

Surfaces individual stakes. “How does that affect you specifically?” Or: “What does that mean for your quarter when deals slip?” Or simply: “What does that look like from where you sit?” This is the question most reps skip because it feels presumptuous or too personal. It’s the most important one.

The sequence matters. A rep who jumps to the personal question before establishing the symptom and the financial impact will get a polite, surface answer. The personal question only produces a real answer when the prospect has already walked through the organizational and financial layers and is ready to connect the problem to their own experience.

There’s a specific moment in a discovery conversation when a rep has found the real pain. The prospect stops describing their situation in general terms and starts talking specifically about what it costs them, personally, if the problem doesn’t get solved.

“We’ve had three reps leave in the past year because they felt unsupported. I’ve had to explain that to the board twice.”

“Our SE is on every deal right now because AEs can’t handle technical questions alone. He’s exhausted and I’m worried we’re going to lose him.”

“I’m personally reviewing every forecast call because I don’t trust what’s in the CRM. That’s four hours a week I don’t have.”

These are not symptoms. They are pains with names, costs, and consequences attached. A deal built on statements like these has a different foundation than a deal built on “we want to improve sales productivity.”

The difference shows in how deals develop. A prospect who has fully articulated their pain at all three layers has, in a sense, made the case for the purchase themselves. The rep isn’t persuading. They’re confirming what the prospect already knows to be true.

In a technical B2B sale, there’s an extra layer of complexity. The prospect often describes their problem in technical terms: an integration that doesn’t work, a workflow that breaks under scale, a process that requires too much manual effort. The rep hears technical language and either nods along without fully understanding, or pivots to a technical answer before they’ve connected the technical problem to the business and personal consequences underneath it.

A technical symptom isn’t a business pain. “Our current tool doesn’t integrate with Salesforce” is a technical observation. “Because our current tool doesn’t integrate with Salesforce, our reps are spending 45 minutes a day on manual data entry, our CRM is perpetually out of date, and I can’t trust any pipeline report I pull” is a business pain with financial and personal consequences attached.

The rep’s job in a technical sale is to bridge the gap between the technical description and the business cost. Not to become a technical expert, but to ask the question that translates the technical problem into organizational and personal terms: “When that happens, what does that mean for the business?”

These two things are often confused, and the confusion produces weak discovery.

A need is something a prospect wants. Better reporting. Faster onboarding. A more accurate forecast. Needs are forward-looking and product-adjacent. They often emerge in the first few minutes of a call when a prospect describes why they took the meeting.

Pain is what’s driving the need. The reason they want better reporting is that they’re flying blind on forecast and got surprised at the end of last quarter. The reason they want faster onboarding is that they’ve lost two deals this month to a competitor because their newest rep didn’t know how to handle a competitive objection.

Starting with needs is fine. Staying there is the problem. A prospect who has articulated a need is describing where they want to go. A prospect who has fully articulated their pain is describing what it costs to stay where they are. The second framing is the one that builds urgency.

Beyond the right questions, pain discovery requires two behaviors that are genuinely difficult under the pressure of a live call.

Patience

Staying in the problem long enough to get to the third layer takes longer than it feels like it should. The rep has to hold the urge to solve, ask another question, and then another, before the real pain surfaces. In a 45-minute call where time feels scarce, that patience is hard to maintain.

Recall

The rep needs to know which question to ask next, at the moment it matters, based on what the prospect just said. Pain discovery isn’t a script. It’s a dynamic process that responds to what’s being surfaced in real-time. Under the cognitive load of managing a live conversation, recalling the right follow-up question, the implication question that quantifies the symptom, is the first thing to disappear.

This is the core problem with training reps on pain discovery frameworks. The knowledge transfers in the classroom. On a live call, under pressure, the trained behavior collapses and the default behavior takes over. The rep hears a symptom, connects it to a feature, and pivots to the pitch before the real pain has surfaced.

Commit reads the live call transcript and pushes the right follow-up question the moment a prospect describes a symptom. When the prospect says “our reps struggle with technical questions,” Commit surfaces the impact and personal questions the rep should be asking next, before the instinct to pitch takes over.

The rep doesn’t have to hold the entire pain discovery framework in their head while managing the conversation. The sequence is there, in real-time, based on what’s being said, so the rep stays in the problem long enough to find the pain that actually drives the deal forward.

That’s real-time sales enablement applied to discovery: the right question at the right moment, surfaced automatically, so the rep never leaves a symptom on the table when the real pain is one question deeper.