A Better Sales Discovery Conversation Starts With the Buyer's Problem

A potential buyer agrees to a meeting. You've prepared your presentation, know the product's strongest features, and have a reasonable idea of what you want to recommend.

Then the conversation begins, and you're already thinking about how to close the deal.

There's a problem with that approach: You may be preparing to sell something before you understand what the buyer actually needs.

A buyer can express interest in a product without having a clear reason to purchase it. They may be exploring options, comparing prices, or trying to solve a problem they haven't fully defined.

A useful discovery conversation helps both sides understand the situation before deciding whether an offer makes sense.

Sometimes that leads to a sale. Sometimes it reveals that the proposed solution isn't right for the buyer.

Both outcomes can be useful.

The First Problem a Buyer Mentions May Not Be the Real Issue

Consider a hypothetical business owner looking for customer relationship management (CRM) software.

They open the conversation with a straightforward request:

"We need a better CRM. Our sales team keeps missing follow-ups."

A salesperson could immediately demonstrate automated reminders, pipeline dashboards, and contact-management features.

Those features might help. But they might also address the wrong problem.

What if the sales team already has a CRM but rarely updates it? What if follow-ups are missed because responsibilities aren't clearly assigned? What if the existing software works, but nobody has agreed on a consistent process?

Buying another system won't automatically resolve those issues.

The initial request tells you what the buyer thinks might help. It doesn't necessarily explain what's causing the difficulty.

Before recommending a solution, investigate what is happening.

Ask:

• "Can you walk me through what happens when a new lead comes in?"

• "Where do follow-ups usually get missed?"

• "When did this last happen?"

• "What have you already tried to improve the process?"

These questions move the conversation away from product preferences and toward the buyer's actual experience.

The goal isn't to challenge the buyer for the sake of it. It's to understand whether the proposed purchase would address the problem.

Ask Questions That Reveal Consequences

Understanding what happens is only part of discovery.

You also need to understand why it matters.

Suppose the hypothetical business owner explains that salespeople sometimes forget to contact prospects after an initial conversation.

That sounds like a problem, but how significant is it?

Does it happen once a month or several times a week? Does it affect promising opportunities or mostly low-priority inquiries? Has the business lost deals because of it?

A useful follow-up might be:

"What happened the last time an important follow-up was missed?"

That question invites the buyer to describe a specific consequence rather than make a general statement.

Another useful question is:

"What would improve for your team if this stopped happening?"

The answer may reveal the outcome the buyer actually wants.

Perhaps they want more reliable communication, better accountability, or less time spent checking whether work has been completed.

Those outcomes matter more than a feature list because they provide a basis for evaluating possible solutions.

But don't assume every inconvenience has a measurable financial cost.

If the buyer can't identify a meaningful consequence, that uncertainty is worth acknowledging rather than turning it into an exaggerated business case.

Understand What the Buyer Is Already Doing

A buyer's current process tells you something about the problem and the alternatives they have available.

In the hypothetical CRM conversation, the business might already use shared spreadsheets, calendar reminders, or an existing sales platform.

Ask how those tools fit into the team's daily work.

What works reasonably well? Where does the process break down? What would be difficult about changing it?

These questions can uncover practical constraints that aren't obvious from the initial request.

For example, the buyer might need software that integrates with an existing system. Or the team may be unwilling to maintain another platform.

A product can have useful features and still be a poor choice if adopting it creates more work than the buyer can reasonably manage.

Understanding current behavior also prevents you from treating every workaround as a failure.

Sometimes the existing approach is good enough. Sometimes the buyer needs a process change rather than a new purchase.

A good discovery conversation leaves room for either conclusion.

Find Out What Success Would Actually Look Like

Sales conversations can become vague when both sides agree that something needs to improve but never define the desired result.

"Better efficiency" sounds positive.

So does "improved productivity."

Neither tells you much about what the buyer expects.

Instead, ask:

"If we were having this conversation three months after making a change, what would need to be different for you to consider it worthwhile?"

The answer might involve fewer missed follow-ups, clearer ownership of leads, or less manual checking by the sales manager.

Those are more useful outcomes to discuss.

They also make it easier to recognize when an offer doesn't match expectations.

If the buyer's main concern is assigning responsibility, a system focused primarily on reporting features may not be the best answer.

The point isn't to promise a specific result. It's to establish what the buyer would consider valuable and whether the proposed solution could reasonably contribute to it.

Understand the Decision, Not Just the Problem

A buyer can have a genuine need and still be unable or unwilling to make a purchase.

Perhaps the budget hasn't been approved. Another team may need to evaluate the software. The organization might be committed to an existing contract.

These aren't necessarily objections to overcome. They're part of understanding the decision.

Useful questions include:

• "Who else would need to be involved in evaluating a change?"

• "What constraints would affect the decision?"

• "Is there a particular reason you're considering this now?"

• "What happens if you continue with the current approach?"

Ask these questions conversationally, not as an interrogation.

The answers help establish whether there is a realistic path forward.

They may also reveal that the timing isn't right.

A buyer who needs a solution eventually isn't necessarily ready to purchase one today. Treating those situations as identical can waste time for both sides.

Recognize When Your Offer Isn't a Good Fit

Not every discovery conversation should end with a proposal.

That can be uncomfortable when you've invested time preparing for the meeting. But recommending an unsuitable product doesn't become helpful simply because the buyer is interested.

Return to the hypothetical CRM example.

Suppose the conversation reveals that the company already has software capable of handling follow-up reminders.

The real issue is that nobody consistently assigns responsibility for new leads.

A new CRM might introduce additional costs without addressing that underlying problem.

In that situation, the salesperson could acknowledge the gap:

"Based on what you've described, it sounds like assigning follow-up responsibility may be the first issue to resolve. I'm not sure replacing your current system would solve that on its own."

That statement is hypothetical dialogue, not a quotation from Jay or an actual sales conversation.

It doesn't require the salesperson to solve the buyer's entire operational problem.

It simply avoids pretending that the offer is a better fit than the evidence suggests.

There are several reasonable outcomes when an offer isn't appropriate.

You might recommend addressing an internal process first, suggest a different type of solution, or agree to revisit the conversation when circumstances change.

Sometimes the right decision is to end the opportunity.

A useful sales conversation should make the decision clearer, even when the decision is not to buy.

Don't Confuse a Good Conversation With a Qualified Opportunity

A buyer can be engaged, ask thoughtful questions, and respond positively to a presentation without being ready to move forward.

Friendly conversation isn't the same as purchase intent.

Before treating an opportunity as qualified, consider whether you've established:

• A specific problem the buyer wants to address.

• Meaningful consequences or reasons the problem matters.

• A desired outcome that your offer could reasonably support.

• A workable decision process, including relevant constraints.

• A logical next step that both sides understand.

These aren't boxes to check mechanically. They're questions that help distinguish genuine progress from an enjoyable meeting.

If important information is missing, the next step may be another conversation rather than a proposal.

And if the evidence points toward a poor fit, that deserves attention before anyone invests more time.

When Discovery Needs a Different Approach

Not every sale requires a long discovery meeting.

For a simple, low-cost purchase, extensive questioning may create unnecessary friction. A buyer who knows exactly what they need may prefer a direct answer about availability, compatibility, or price.

Complex purchases usually involve more considerations, especially when several people are affected or implementation requires significant effort.

Discovery should match the decision's complexity.

There's also a difference between understanding a buyer's needs and trying to manufacture urgency.

Questions about consequences should help clarify the situation, not pressure someone into exaggerating a problem.

If a buyer has already provided enough information to make a sensible recommendation, continuing to ask questions simply to follow a sales script adds little value.

Good judgment includes knowing when to stop asking and start answering.

The Best Next Step Isn't Always a Proposal

A strong discovery conversation doesn't need to end with a dramatic closing statement.

It needs to produce a clearer understanding of the buyer's problem and what should happen next.

That might mean demonstrating a relevant capability, involving another decision-maker, clarifying a requirement, or agreeing that the offer isn't suitable.

Before recommending anything, make sure you can explain what the buyer is trying to accomplish, why it matters, and how your proposed solution would help.

If you can't make that connection, you may need more information—or a different recommendation.

The purpose of discovery isn't to find a way to sell something to everyone.

It's to determine whether there's a problem you can genuinely help solve.

For more practical perspectives on business, leadership, and sales, explore Jay Scott Kirk Lee's Blog or visit his About page.

About the author: Jay Scott Kirk Lee is a Canadian entrepreneur with a background in sales, marketing and business development.