"So, what keeps you up at night?"

If you are still asking this question on a discovery call, stop. Immediately. You sound like every other lazy salesperson from 1995. You are asking your prospect to perform for you. You are asking them to neatly package up their deepest business anxieties and hand them to a stranger on a platter.

It does not work.

You get one of two answers. A polite, canned response about "scaling the team" or "improving efficiency". Or you get silence followed by a vague, "You know, the usual stuff". Either way, you learn nothing. You build zero rapport. You are back at square one, but now you look like an amateur.

The goal of discovery is not to ask a magic question that unlocks the buyer's soul. The goal is to facilitate a conversation that helps the buyer diagnose their own problem with your guidance. You are not a talk show host. You are a doctor. You do not ask "So, what hurts?". You ask specific questions to isolate the source of the pain.

Your job is to move from the abstract to the concrete. From "We want to be more data-driven" to "My reps spend 6 hours a week manually copy-pasting data into Salesforce, and I still don't trust the forecast". That second statement is something you can sell against.

The Three-Layer Questioning Framework

Great discovery is not about having a list of 20 questions to read off. It is about a logical progression. Think of it in three layers: Process, Problem, and Payoff. You cannot skip a layer.

Layer 1: Process Questions (The "How")

Before you can find the pain, you need to understand the workflow. Process questions are safe, objective, and easy for the prospect to answer. They lower their guard because you are just asking for facts, not feelings.

You are mapping their reality.

"Walk me through how your team handles [specific task] today, from start to finish."
"Who is involved at each step of that process?"
"What tools or systems are you using to manage that?"
"How do you measure success for that workflow right now?"

Let's say you sell a contract management solution. A bad question is "Are your contracts a mess?". A good process question is "Can you walk me through what happens after a deal is verbally agreed to, all the way until the contract is signed and filed?".

The prospect can easily describe this. As they do, you listen for keywords: "manually", "email it around", "version control", "chase legal", "scan it". These are the cracks where the problems hide.

Layer 2: Problem Questions (The "So What?")

Once you understand the process, you can start poking at those cracks. Problem questions connect the steps in their process to negative consequences. This is where you move from reporter to consultant. You are helping them articulate the friction they feel every day.

This is the crucial step to Find the Pain Behind the Pain in Discovery.

"You mentioned you email drafts back and forth. What happens when someone works off the wrong version?"
"How long does it typically take to get a signature from legal? What is the impact of that delay on a deal closing?"
"What is the consequence of a key term being missed in that manual review process?"
"How much of your top AE's time is spent on this administrative work instead of selling?"

Notice the pattern. You take their words ("we email it") and attach a "so what" to it. You are not inventing problems. You are shining a spotlight on the inherent consequences of their current process.

A great problem question makes the prospect pause and think, "Huh. I never actually quantified that before". That is the moment they realize the status quo is more painful than they thought. This is where you separate yourself from the reps who just pitch features.

Layer 3: Payoff Questions (The "What If?")

Now you have a process map and a list of problems tied to it. The final layer is to connect those problems to business value. Payoff questions help the prospect articulate the positive business outcomes of fixing the problem. You are helping them build their own business case.

"If you could cut that contract cycle from 10 days to 2 days, how many more deals could you close this quarter?"
"If your AEs got back those 5 hours per week, what would they do with that time? How much more pipeline would that generate?"
"What would it mean for your forecast accuracy if you had a single source of truth for all contract data?"
"You're a VP of Sales. How does solving this problem help you hit your board-level commitments?"

This is how you get to ROI. You are not telling them the payoff. You are asking questions that lead them to state the payoff in their own words. When a prospect says "If we could do that, it would mean an extra $500k in pipeline this quarter", they have just sold themselves on the value of a solution. Your job just got a lot easier.

This is the opposite of a feature dump. You are not talking about your product. You are talking about their business. The best discovery calls feel less like a sales pitch and more like a strategy session. By the end, the prospect should feel like you understand their business better than any other vendor they have spoken to.

So throw out your list of canned questions. Stop asking what keeps them up at night. Start with the process, dig for the problem, and guide them to the payoff. That is how you turn a conversation into a qualified opportunity.

TL;DR

Stop asking lazy, generic questions like "What are your pains?". They invite vague answers and make you sound like every other salesperson.
Use the 3-Layer Framework: Ask about Process (How it works today), then Problem (Why it is broken), then Payoff (What it is worth to fix it).
Guide the prospect to build their own business case. By asking smart payoff questions, you get them to state the value of solving the problem in their own words.

Your AI sidekick reads this and acts.

Subscribe to The GTM & SDR Diary