What is a Discovery Session is in Sales (And Why I Keep Screwing it Up)

A discovery session is the part of a sales call where you figure out whether you can actually help someone. Before you try to sell them anything, it's the phase where you ask about their business, their problem, what they've already tried, and what success would look like. In B2B services, it's usually the first real conversation between a potential client and the person who'd be doing the work.

Most sales advice treats discovery as a checklist. Ask about the budget, ask about the timeline, ask about the decision-makers, and move on. But discovery isn't a checkbox exercise. It's the diagnostic. And if you rush through it--or worse, skip it because you think you already know the answer--the rest of the sales conversation collapses.

I know because I do this constantly.

The Problem With Knowing the Answer Too Early

I run a B2B paid media agency. Most of my sales calls are with founders or marketing leaders at tech companies who need help with Google Ads, LinkedIn Ads, or both. By the time they're on a call with me, they've usually described their situation in an intake form, and I've looked at their website.

So when they start talking, I often recognize the pattern within two minutes. They're running LinkedIn Ads to a large audience for $40 per day and wondering why no one converts. Or they’re running Performance Max and broad match campaigns on Google Ads when they have a sales-led motion on a very niche product.

And this is where my brain betrays me. Instead of asking three more questions, I will start prescribing. I pull up a client's Google Ads account. I show LinkedIn Ads data. I begin talking through benchmarks and best practices.

I'm usually right. But being right at the wrong time is worse than being wrong, because once you start prescribing solutions, it's almost impossible to go back to gathering information. The call's energy has shifted. You're in presentation mode now. And you've anchored the entire conversation around your framework before you understood where they’re coming from.

What a Good Discovery Session Actually Covers

The purpose of a discovery session isn't to demonstrate expertise. It's to collect enough information that your eventual recommendation is specific to this person's situation rather than a generic playbook.

In B2B services sales, that means understanding at minimum:

The business context

What they sell, who buys it, how long the sales cycle is, and what their average deal size looks like. Without this, you can't assess whether paid media economics will work for them at all.

What they've already tried, and why they think it didn't work.

Their diagnosis is often wrong, but it tells you how they think about the problem. A founder who says "Google didn't work" might mean "we got leads, but they didn't convert," or "we couldn't get CPMs under $40," or "we ran it for two weeks and gave up." Those are three completely different problems.

Their actual constraints

Budget, timeline, team capacity, and who else is involved in the decision. A $1,500/month budget and a $10,000/month budget lead to fundamentally different recommendations, and if you prescribe before asking, you've either scoped too small or embarrassed someone who can't afford what you just described.

What success looks like to them

They may need leads not to close them, but to prove to their board that paid media works. Or maybe they are using paid media only to unlock a new kind of prospect they’re not reaching through another channel. Maybe their sales team can handle only 10 new conversations a week, but headcount is frozen, so they want to use paid media to unlock a product-led motion.

Each of these changes what you'd recommend.

When the discovery session goes well, your recommendation at the end feels inevitable, like the obvious conclusion from everything they just told you. When it goes badly (usually because I skipped it), the recommendation feels like a pitch.

Why Technical Founders Are Especially Bad at This

If you come from an execution background, where you've managed campaigns, built funnels, and debugged conversion tracking, the discovery phase feels inefficient. You already know what the answer will be. Why spend fifteen minutes asking questions when you could spend those fifteen minutes showing them exactly how you'd solve the problem?

Three reasons.

First, you don't actually know yet.

You know what the answer usually is. But their situation has variables you haven't uncovered. The approach that looks wrong is actually converting at 12% into demo requests, and the real problem is their sales process, not the top of funnel. You'd never find that out if you jumped to "just sell directly."

Second, the prospect needs to arrive at the conclusion with you.

If you tell someone what to do, they'll nod and second-guess it later. If you ask enough questions that the answer becomes obvious to both of you simultaneously, they own the decision. They're not buying your recommendation. They're buying their own conclusion, which you helped them reach. This felt manipulative to me until I realized it's just how trust works. People trust conclusions they helped reach.

Third, premature prescribing collapses your pricing power.

When you give away the strategy in the discovery session, you've turned yourself into a commodity. The prospect now has the answer, and they need someone to execute it. And execution is always cheaper than strategy. By staying in discovery longer, you're demonstrating that the diagnostic process is itself valuable. That's what justifies higher rates.

The Moment It Goes Wrong

There's a specific moment on every call where the temptation peaks. It's when the prospect says something that reveals a fundamental misunderstanding about how their marketing works.

Maybe they think LinkedIn Ads "didn't work" when the real issue is they were running top-of-funnel campaigns and expecting bottom-of-funnel results. Maybe they've been spending $2,500 a month and wondering why they can't build a converting funnel when the real answer is that they need three months of testing data at that budget before drawing any conclusions.

In that moment, you have two options:

Option A: "Actually, here's what's happening. Let me show you this other client's account where we solved exactly this problem."

Option B: "That's interesting. What made you decide to go that route? And what did the conversion data actually look like?"

Option A feels great. You're the expert. The prospect might even say, "Wow, that makes so much sense." But you just skipped past the information that would have made your recommendation airtight.

Option B feels slow and a little dumb. You're asking about something you suspect you already know. But it gives the prospect room to tell you something that changes the recommendation entirely. And it signals that you care about their specific situation, not just about being impressive.

What I'm Training Myself to Do

I don't have this figured out. I still catch myself mid-prescription, realizing I've been monologuing about negative keyword optimization when the prospect hasn't told me their monthly ad budget.

But I've started using a simple rule: if I haven't asked about budget, timeline, team, and past attempts, I don’t recommend anything.

Those four areas almost always surface the information that makes the difference between a generic recommendation and a specific one.

The other thing that helps is reframing what "demonstrating expertise" means during a discovery session.

It's not about knowing the answer. It's about knowing which questions to ask. Anyone can Google "should I use Google Ads or Meta for B2B?" Not everyone can ask: "You mentioned you've onboarded 60 clients through conferences. What was your close rate in those conversations, and what was the average objection?" That question demonstrates more expertise than any amount of demonstration.

The Paradox of Discovery Sessions

The irony is that staying in discovery longer makes the prescription more  impactful when you finally deliver it. If you spend fifteen minutes understanding someone’s hypotheses, experience with other marketing programs, team structure, and budgetary constraints, and then you make a tactical recommendation, it lands completely differently than if you said the same thing at minute six.

They trust you more because you took the time to listen, and they know it’s grounded in their actual situation.

Every time I rush through discovery, I make the rest of the conversation harder for everyone.