Your Discovery Call Found the Problem. It Never Found the Cost of the Problem.

"Pain identified: churn." That is in the CRM. That is what the rep logged after forty-five minutes with a VP of Customer Success. The deal went to proposal, sat for six weeks, got a "we're revisiting priorities" email, and died. In the post-mortem, the manager said pipeline quality. The rep said timing. Nobody said: we never actually found out what the churn was costing them, so we couldn't build a business case, so the economic buyer had nothing to take to the CFO, so the deal had no legs.

That is the failure mode. It is endemic. And it is invisible in most sales organisations because the CRM treats "churn is too high" and "churn is costing us approximately £2.4m in ARR and adding 30% to CAC payback" as the same data point. They are not.

The Distinction That Actually Matters

Discovery training, even good discovery training, teaches reps to surface problems. Find the pain, confirm it's real, qualify that the prospect wants to fix it. That is necessary. It is not sufficient.

A vague problem and a quantified problem are not the same qualification signal. When a buyer says "our onboarding is too slow and we're losing accounts because of it," that is a symptom. It might be a symptom attached to £800k of annual revenue at risk, or it might be attached to four accounts and a mild awkwardness in QBRs. The rep who logs "pain identified: onboarding / churn" and moves to demo has no idea which universe they're in. They are hoping the buyer cares enough to self-propel the deal forward. Most of the time, the buyer doesn't, because the buyer hasn't quantified it either.

This is the gap where enterprise deals go to stall. Not at discovery. Not at proposal. In the space between them, when someone internal at the buying organisation tries to build a business case and realises they have nothing to build it with.

Why Reps Don't Go There

The most common reason is social discomfort. Asking "what is that actually costing you?" feels presumptuous, or aggressive, or like you're trying to inflate urgency. Reps who have been trained on rapport-based selling instinctively back off when the buyer gets vague.

The second reason is that buyers often don't know. And when buyers say "I'm not sure, it's hard to quantify," most reps accept that as a final answer. It isn't. It's an invitation to help them think through it.

The third reason is that managers don't inspect for it. If your deal review process asks "did they identify pain?" rather than "what did they get the buyer to quantify?", you're measuring the wrong thing. Your inspection process is producing the behaviour you're getting. Discovery Call Scorecard for Managers exists partly to fix that specific hole.

What Getting There Actually Looks Like

Here is the conversation most reps have:

Rep: "You mentioned churn is a problem. How significant is that for you?" Buyer: "It's been a real challenge. We're seeing it across several segments." Rep: "Understood, that's definitely something we help with."

Logged: pain identified.

Here is what the conversation looks like when the rep is actually doing the work:

Rep: "You mentioned churn is a problem. Do you have a rough sense of your current rate?" Buyer: "We're running around 18% annually." Rep: "And what's a typical ACV for the accounts you're losing?" Buyer: "Varies, but average is probably £40k." Rep: "Rough numbers, if you're carrying, say, 200 accounts, that's 36 churned accounts a year at £40k. That's £1.4m walking out the door. Does that feel roughly right to you, or am I off?" Buyer: "Actually that's probably conservative. Some of the accounts leaving are above average size." Rep: "So if you could reduce that rate to 12%, which is closer to what similar companies run on our platform, you're talking about recovering around £600k in the first year. Is that the kind of number that would get your CFO's attention?" Buyer: "Yes. Honestly that's the number I've been trying to put together."

That last line. That is what qualification sounds like. The buyer just told you they have been trying to build the business case themselves and couldn't get there. You just became useful in a way that the three other vendors they're talking to probably haven't.

The arithmetic doesn't have to be perfect. It has to be shared. You are constructing a number together, which means the buyer now owns it. That is the mechanism.

The Skill That Nobody Coaches

Pulling a number out of a reluctant buyer is a specific skill. It has component parts: knowing which metric to start with, how to do the back-of-envelope maths in the room, how to offer a number as a hypothesis rather than a claim, and how to hand the pen to the buyer at the right moment so they adjust it upward and own the result.

None of that is in most discovery frameworks. Most frameworks get you to "impact" as a category and leave you there. The Symptom, Impact, Root Cause discovery framework is one of the cleaner structures for moving from surface complaint to financial consequence, and even that requires the rep to do the number-building move rather than just ask about it abstractly.

The reps who are good at this are not aggressive. They are genuinely curious and slightly mathematical. They treat the buyer's business as a system and find the leak. The conversation feels collaborative because it is.

What to Look for in Call Review

If you manage AEs or run enablement, add these questions to your call review process:

The Discovery Call Review Rubric has a fuller version of this inspection lens if you want something you can drop into your team's existing call review process.

The CRM Problem

"Pain identified" as a checkbox creates a false sense of qualification. Your pipeline reviews feel grounded in real discovery. They're not. They're grounded in symptom collection, which is one layer above nothing.

If you want to fix this at a process level, add a mandatory field: "Quantified impact." Make it a text field, not a dropdown. Require a number, a metric, or an explicit note that the buyer couldn't quantify and that this is a risk. Make it visible in pipeline review. You will immediately see how many of your "qualified" opportunities have nothing in that field. That absence is your forecast risk. It just hasn't been named yet.

The deals that stall aren't usually complex. They're usually deals where the champion wanted to buy, went to their economic buyer, and had nothing concrete to show them. Not because the product wasn't right. Because the rep never helped them build the case.

Buyers are not always going to do that work themselves. The ones who do are already sold. The ones you need to win are the ones who needed a partner to get there, and found a vendor instead.