He Told Me Exactly What He Needed. He Was One Layer Off.
This is the weekly article where I dive into one of my own calls, pull a lesson in order to point you to a resource so that you can learn from these calls and/or avoid the thing. All names have been anonymized.
The Call
Ok, it's not just one call. I have this call constantly.
Someone books time having already worked out what they "need". They're not confused. They didn't book time to be educated. They've thought about it, they've arrived with a diagnosis, and they'd like to get on with buying the thing.
Except - I don't sell to need and neither should your team.
For this particular call, the sales leader was fairly new to this team. Not to leadership, but to this team specifically. They were having a hard time evaluating the team as half were new, he is new, and they have a brand new motion taking place. Some of you may nod your head at this. Inbound had dried up a bit, so BOOM, the team was not going to be asked to....HUNT for net new. So not only did they need to lift the win rate by an easy 5-10%, but they also needed more pipeline.
So what he needed, he'd decided, was one common standard to measure people against. That's a good diagnosis. Most sellers would have taken it and started scoping. Not me tho. Before we went anywhere near what he wanted to buy, I asked him something about what was happening to the deals inside the pipeline.
"When you look at the notes in your team's deals, what problems emerge that your team uncovers that they can solve - name three".
He gave me three answers.
- We're consultative.
- We simplify environments.
- We care.
I then asked, if I were to ask each team member on your team, what would their answers and notes look like? He said, you'd get a different answer from every person on his team (so I already know one root cause is everyone has a different definition of what they solve for, they get happy ears, hear a need and show the product, don't build a business case on why the buyer should change and poof - win rates are low - buyers ghost).
So his initial diagnosis wasn't wrong about needing a shared standard. He was just one layer too high..... You can't measure people against a standard until you've agreed what you're measuring them toward.
The Insight
Here's what most sellers do instead. They fill the prescription. They sell to need. Sometimes, they take an order.
A buyer says we need this thing. The seller hears a qualified opportunity, checks there's budget, books the next call. It feels like they are listening to the buyer and responding. It looks like a healthy pipeline. It's order-taking with a discovery call stapled to the front of it (YIKES).
A buyer can only diagnose what they can see from their chair. He could see he had no way to evaluate his team. He could not see that nobody in the building agreed on what the company fixes for people, because nobody had ever done that exercise. No one had stopped to figure out what good looks like and then replicated it.
No shade to buyers. That is literally our job as sellers, to bring another POV, to get a buyer to reflect on something they hadn't thought of, to have that lightbulb moment that what they thought was the fix, perhaps isn't. But when sales leadership is in it, it's hard to have the outside view. That's the part they're paying us for. They aren't paying us to take an order, they are paying us to ensure we have suss-ed (is this a word - spellcheck says no) out their entire problem environment so they have confidence in the solution.
This prospect did the hard thing. He answered questions he hadn't prepared for, he stayed with me on my digging and journey to figure out - should you even change? He stopped, he reflected, he went with me when I dove in deeper to create a through line and got him to agree to go on the journey to change. And then he said, "I think that our CEO should come to the next call".
The Read
We commissioned a survey of more than 1,200 B2B buyers across the US and Canada. C-level down to manager, every function from IT to procurement. It's here: How Buyers Want To Be Sold
73 percent of them start the buying process by identifying the size and scope of the business problem they're trying to solve. They do the work. They arrive with a diagnosis, the way he did.
48 percent of them have STILL bought the wrong product, because they didn't properly understand the problem they were trying to solve.
47 percent have bought the wrong product because the salesperson didn't understand it either.
Put those two next to each other. The buyer's homework didn't save them, and nobody on our side of the table caught it either.
There's a better number in the same survey. 61 percent have bought something they didn't know they needed, until after they talked to a salesperson. That only happens when somebody did the diagnosing.
Let's think..... pull the last three deals your team put in commit. Can your reps tell you:
- the business problem the buyer has, not the thing they asked for?
- what it's costing them, in their numbers if not fixed?
- what it stems from?
- and can they show you where the BUYER said it? (not a gut feeling, not an assumption - the buyer's actual words)
If you can't find those, but you can find the product they asked for, a budget and a timeline.....
Your team took an order. Your team didn't run discovery.
The Resource
We wrote up why discovery calls fail and what to do instead. It starts exactly where this call started, with knowing the three or four business problems you actually solve and how each one shows up in a buyer's environment before you ever get on the phone. In this instance, I was looking for quota attainment, win rate and average deal size - and bingo - I got those problems nailed and then dove into why they were happening. On the next call, I'll get what it's costing the org.
It's also blunt about the thing sitting underneath all of this. Buyers don't always know what's wrong, and they almost never know what's causing it.
So - go pull three deals. Can your team answer the questions?
For a quick read - check out one of our blog articles here on why your team's discovery calls are failing

