How do you coach reps to uncover a prospect's real pain?

The two coaching paths: drill the skill or change the system

Nearly every sales manager who wants deeper discovery picks one of two routes, and most pick the wrong one first. The two options are worth naming plainly.

Path A — the skill route. You treat shallow pain as a competence problem. The rep does not know the question sequence, so you teach it: role-plays, script drills, call tear-downs, a weekly 1:1 where you model the ladder and the rep repeats it back. This is the default because it feels like coaching. It is visible, it is satisfying, and when the diagnosis is right it works fast — a rep who genuinely does not know how to ask "what is that costing you?" can learn it in two weeks of deliberate practice.

Path B — the system route. You treat shallow pain as an incentive problem. The rep already knows how to ask; they do not, because nothing in your operating rhythm rewards it. Your CRM has a free-text "Pain" field nobody validates. Your pipeline review asks about close dates and next steps, never about dollar figures. Your comp plan pays on meetings booked at the SDR layer and on closed-won at the AE layer, with nothing in between that touches discovery quality. So you change the machinery: a required numeric pain field, a stage-gate that will not let a deal move to Qualified without a quantified and multi-threaded pain, a pipeline review script that opens with pain instead of forecast.

The two are not mutually exclusive — the strongest teams run both — but they are sequenced, and getting the order wrong wastes months. Skill drills against a system problem produce reps who perform beautifully in role-play and revert instantly on live calls, because the environment still rewards the old behavior. System changes against a genuine skill gap produce reps who now have a mandatory field they fill with fabricated numbers, because you have created an obligation without a capability.

There is a third variable most managers miss, and it sits underneath both: will. A rep can know the ladder cold and work inside a system that demands it, and still not climb past rung two, because rungs three and four feel intrusive. Asking a stranger "what happens to you personally if this doesn't get fixed?" reads as invasive to a rep who has not been coached on the reframe. Will gaps look identical to skill gaps from the outside and respond to the opposite intervention: more drilling makes a fearful rep more self-conscious, not less.

And a fourth: knowledge. A rep who does not understand the prospect's industry cannot recognize good pain when they hear it. Sell into hospital revenue-cycle teams without knowing what a denial rate is, and "our claims process is messy" sounds like a complete answer instead of the doorway to a seven-figure leakage conversation. No amount of question-ladder practice fixes that. Persona libraries and industry immersion do.

So the real comparison is not two paths but a decision about which of four levers you pull — and the honest answer for most teams is that they have been pulling the skill lever exclusively for years and wondering why depth never compounds.

How to decide which lever to pull

The diagnostic is cheap and takes one week. Run the rep through a controlled role-play where you play a prospect with a deliberately vague problem — "we just need better visibility" — and refuse to volunteer any cost or consequence unless asked directly. Then pull one of their real recorded discovery calls and watch the same moment.

Four combinations, four verdicts:

• Fails the role-play, fails the live call → skill gap. The rep does not have the pattern. Teach it.
• Passes the role-play, fails the live call → will or system gap. The capability exists; something is suppressing it. Ask which: "When you got to the cost question on that call, what stopped you?" If the answer is about the prospect's reaction, it is will. If the answer is "I already had what I needed for the CRM," it is system.
• Passes both, pain still shallow → knowledge gap. The rep asked all five rungs and still came back with "they want to save time," because they do not know what a meaningful number looks like in that vertical.
• Passes everything, pain is genuinely small → not a discovery problem at all. That is good qualification. Reward the disqualification and move on.

That last row matters more than it looks. Managers routinely punish reps for bringing back small pain when the rep did everything right and the account simply is not hurting. Confusing a fit problem with a discovery problem trains reps to inflate pain in the CRM, which poisons the forecast far worse than a thin pipeline does.

One caution on the diagnostic: run it on the same rep twice, a month apart, before drawing conclusions about a person rather than a moment. Reps have bad weeks. A single frozen role-play tells you about Tuesday, not about capability. And if a rep fails the same diagnostic three cycles in a row after clear feedback and real reps, you are looking at a hiring or fit issue, not a coaching one — that becomes a performance conversation, and pretending otherwise is unkind to everyone including the rep.

Concrete numbers behind each lever

Coaching arguments get resolved by numbers, so here are the ones worth instrumenting. None of these are industry benchmarks handed down from a study — they are the operating targets a RevOps team can set, measure, and adjust from its own baseline.

Pain-depth scorecard: 0–5 per discovery call. One point each for: problem named in the prospect's words; cost quantified in dollars or hours; consequence of inaction surfaced with a timeframe; personal stake identified; pain confirmed by at least one stakeholder beyond the champion. Score every reviewed call. A deal scoring under 3 is not qualified, full stop — it goes back into discovery. Most teams starting cold sit somewhere between 1 and 2 on their first month of scoring. The realistic target after a quarter of disciplined coaching is a team average around 3.5, not 5 — insisting on 5 across the board produces fabricated numbers, not better discovery.

Talk-to-listen ratio. Pull it from your conversation-intelligence tool. Reps who uncover real pain talk noticeably less on discovery calls than reps who pitch. A rough healthy band for a first discovery call is roughly 40% rep, 60% prospect. A rep sitting at 70% talk time is not discovering; they are presenting. This is the single easiest leading indicator to pull and the fastest to move — a rep who sees their own number usually corrects within two weeks without any further intervention.

Quantified-pain rate. The percentage of open opportunities with a numeric figure attached to the problem. This is a CRM hygiene metric and a discovery metric at once. Track it weekly; it will be embarrassingly low the first time you look. Moving it from single digits to a majority of open pipeline over a quarter is a reasonable ambition.

Stakeholders confirming the pain, per deal. Count distinct contacts who have independently articulated the same problem. One is a champion's opinion. Two or three is a business case. This is where discovery quality and multi-threading merge into the same metric, and it correlates with slipped-deal rate better than almost anything else you can measure.

The four-second silence. After the prospect finishes an answer, does the rep wait? Most break within a second with "got it" or a clarifying question, which releases exactly the pressure that produces the second, truer answer. Coach a silent four-count. In call review, flag every sub-two-second break as a coaching moment. This is the cheapest single behavior change on the list and often the highest-yield.

Cadence cost. Budget the coaching honestly: two 20-minute role-plays a week per rep in the first 30 days, one 30-minute recorded-call review weekly thereafter, plus the manager's prep time to actually watch the clip beforehand. For a manager with eight reps, that is a real four to six hours a week during a build phase. Managers who do not block that time in the calendar do not do the coaching, and then conclude the framework does not work.

Time to signal. Do not expect win rate to move first — it is a lagging indicator sitting one full sales cycle behind the behavior. Expect the scorecard and talk ratio to move within two to three weeks, quantified-pain rate within a month, stage-conversion within one sales cycle, and win rate only after that. Managers who watch win rate as their coaching feedback loop conclude the coaching failed roughly six weeks before it would have shown up.

Implementation details and sequencing

Here is the actual build order, and it starts with the system lever rather than the drills — deliberately, because the system change is what makes the drills stick.

Week 0 — instrument before you coach. With RevOps, add two required fields on the opportunity: a numeric annual pain value and a free-text "who confirmed it, and when." Add a stage-entry validation on Qualified that requires both. Do not announce it as a coaching initiative; announce it as forecast hygiene. Simultaneously, rewrite the pipeline-review script. Every deal over your threshold gets exactly three opening questions: what is the dollar figure on this pain, who besides your champion confirmed it, and what happens to that person personally if it stays unsolved. If the rep cannot answer all three, the deal does not advance. That is the whole system lever, and it takes an afternoon of CRM work.

Weeks 1–4 — build the pattern. Two role-plays weekly per rep. You play the prospect and you are deliberately unhelpful: vague first answer, no volunteered numbers, mild resistance to the personal-stake question. The rep must climb all five rungs inside four minutes. Run the "so what?" drill alongside it — the rep states a pain from a real call, you answer "so what?" until they arrive at something a CFO or a board would care about. Add the silence drill: rep asks a question, then counts four in their head before speaking again.

Coach the reframe explicitly, because it is the hinge for will gaps: asking what a problem costs is not pushy, it is a service. A prospect who cannot articulate the cost of their problem cannot get budget approved for it. The rep who quantifies the pain is handing their champion the internal business case. Reps who internalize that stop flinching at rung three.

Weeks 5–8 — transfer to live calls. The rep submits one real recording weekly. You score it against the 0–5 rubric and give exactly one upgrade — not ten. Ten pieces of feedback is zero pieces of feedback. Run the review with the rep spotting their own miss first: play ninety seconds, ask "where did you have a door open and walk past it?" Self-identification transfers; being told does not. Then name the pattern out loud so it generalizes: "You asked one strong problem question, they answered, and you moved to features. That answer was rung one of five."

Weeks 9–12 — widen to the committee and to adjacent motions. Shift the coaching target from depth to breadth: the same quantified pain, validated across two or three stakeholders. This is where discovery coaching bleeds into multi-threading, mutual action plans, and champion enablement, and the skills reinforce each other. A rep who can ask a CFO "what does this cost you" in a way that lands has effectively learned executive-level discovery, which is the same muscle used in renewal conversations, QBRs, and expansion motions.

That adjacency is worth pulling on. The pain ladder is not only an AE tool. SDRs running it in a truncated two-rung form — problem and cost only — book meetings that survive the handoff instead of no-showing. Customer success teams running it in QBRs surface expansion pain before renewal pressure forces the conversation. Solutions consultants who ask rung three before building the demo stop demoing features nobody asked about. Support and onboarding teams hear pain constantly and have nowhere to route it; a shared pain taxonomy in the CRM turns those signals into pipeline. If you are going to define a pain schema with RevOps anyway, define it once for the whole revenue org rather than only for new-business discovery.

Ongoing — the manager traps. Coach the pattern, not the deal. Telling a rep the exact question to ask this prospect closes one deal and teaches nothing; the skill has to transfer to the next fifty calls. Do not rescue — jumping onto the call to ask the pain question yourself feels helpful and builds zero capability; let them struggle in the role-play where it is safe. Do not coach everyone identically, because skill and will gaps look the same and need opposite responses. And do not run one brilliant 1:1 with no recording, no rubric, and no next-call checkpoint — the cadence is the coaching, and a single conversation evaporates by Friday.

One more: watch for the rep who games the numeric field. The moment a dollar figure becomes mandatory, some percentage of opportunities acquire suspiciously round numbers with no source. The defense is the second field — who confirmed it — and spot-checking it in review. A number without an attributed human behind it is a guess wearing a suit.

What the ladder actually sounds like

Abstractions do not transfer; words do. Give reps the verbatim rungs and let them adapt the phrasing later.

Rung one, surface the problem: *"Walk me through what's not working in the current process."* Open, non-leading, and it invites a story rather than a yes/no.

Rung two, quantify: *"When that breaks, what does it cost you — in hours, in headcount, in deals?"* Offering three units is deliberate. A prospect who cannot produce a dollar figure can usually produce an hours figure, and hours convert.

Rung three, consequence: *"If nothing changes between now and the end of the fiscal year, what happens?"* Anchoring to a real date makes it concrete and quietly surfaces timeline without asking about timeline.

Rung four, personal stake: *"How does that land on you specifically — is this on your number, your team's, your review?"* This is the rung reps skip. Coach it as an act of respect: you are asking whether this matters enough to them to be worth their political capital.

Rung five, committee: *"Who else feels this, and do they feel it as sharply as you do?"* The second half of that question is the useful half. A champion who says "my VP cares about it in theory" has just told you the deal has no executive sponsor, three months before you would otherwise have found out.

The ladder is not a script to be recited in order on every call. Real conversations loop, double back, and sometimes hand you rung three unprompted. What the rep needs is not sequence discipline but an internal checklist of what they must not leave the call without — and the presence of mind to notice, mid-conversation, which rung is still missing.

Related questions

How long before coaching shows up in win rate?

Expect leading indicators — scorecard depth, talk ratio — to move in two to three weeks. Win rate sits one full sales cycle behind the behavior change, so on a 90-day cycle you are looking at four to five months before the lagging number is trustworthy.

Should SDRs run the same pain funnel as AEs?

A truncated version. SDRs should reach rung two — problem and rough cost — inside a short call. Pushing an SDR to rung four on a cold conversation usually breaks rapport and loses the meeting. Depth is the AE's job on call two.

What if the rep runs the ladder perfectly and the pain is small?

That is successful discovery, not failed discovery. Reward the fast disqualification explicitly and publicly, or reps learn to inflate pain in the CRM to avoid looking unproductive — which corrupts the forecast far worse than a thin pipeline.

Does conversation-intelligence software replace manager call review?

No. It finds the moments; it does not coach them. The tool cuts your prep from an hour to ten minutes by surfacing the right ninety seconds, but the diagnosis of skill versus will versus system still requires a human who knows the rep.

How do you coach this on a fully remote team?

Recorded calls become an advantage, not a handicap. Async review — you leave timestamped comments on the recording, the rep responds before the 1:1 — often produces deeper reflection than a live listen-through, because the rep has time to hear their own miss.

FAQ

What exactly is the pain ladder and why five rungs?

It is a structured escalation from symptom to stake: name the problem, quantify its cost, surface the consequence of inaction, find the personal stake, then validate across the buying committee. Five rungs because each one answers a different objection later in the deal — rung two answers "why spend money," rung three answers "why now," rung four answers "why will anyone fight for this," and rung five answers "who signs."

My reps say the cost and consequence questions feel intrusive. How do I fix that?

That is a will gap, and it responds to reframing rather than drilling. Teach reps that quantifying the problem is how they arm their champion for an internal budget conversation. Nobody gets funding approved for a problem they have not sized. Start reps on low-stakes accounts so the first few attempts carry no cost, and have them hear a peer do it well before they try.

How do I stop reps from inventing numbers once the CRM field is mandatory?

Pair every numeric field with an attribution field — who said it, when, on what call. Spot-check three or four in every pipeline review by asking the rep to point to the moment in the recording. Two rounds of that and fabricated numbers stop appearing, because the cost of getting caught exceeds the cost of asking the question.

Can this work when buyers arrive already self-educated?

Yes, and it matters more. A buyer who has read every comparison page still has not articulated what the problem costs them or what happens if they do nothing — and often has not checked whether their colleagues feel it as sharply. Informed buyers shorten rung one and make rungs three through five the entire value of the call.

What is the single highest-leverage drill if I only have time for one?

The silence drill. Rep asks a question, then counts four seconds before speaking again. Most reps break silence in under a second and unknowingly rescue the prospect from the pause that produces the truer, deeper answer. It costs nothing, it is measurable in any call recording, and it changes discovery depth faster than any script.

Where does RevOps fit in all of this?

RevOps owns the system lever: the pain schema on the opportunity object, the stage-gate validation, the reporting that turns scorecard entries into a trend line, and the discipline of defining the fields once for AEs, SDRs, and CS rather than three incompatible times. Coaching without that instrumentation has no feedback loop and no memory.

Sources

• Sandler — The Pain Funnel
• Gong Labs — Discovery call tips backed by conversation data
• RAIN Group — Sales Discovery Questions
• Winning by Design — The SPICED framework
• Richardson — Consultative selling and SPIN-style discovery
• Harvard Business Review — The New Sales Imperative
• MindTools — The GROW coaching model
• Salesforce — What is sales coaching

Related on PULSE

• [How do you ask a rep to re-articulate a prospect's pain point in their own words to test comprehension?](/knowledge/cg0872)
• [How do you coach a rep to tailor the demo to the buyer's pain?](/knowledge/cg0063)
• [What question do you ask to uncover the prospect's real budget without being pushy?](/knowledge/cg0942)
• [What question do you ask to uncover the real emotional driver behind a prospect's buying decision?](/knowledge/cg0920)
• [Which single question helps a rep map their talk track directly to the buyer's pain points?](/knowledge/cg0833)
• [How do you certify sales skills before reps face real buyers?](/knowledge/cg0179)