Use Call Openings to Diagnose a Discovery Problem
Help sales leaders examine opening behavior before selecting a discovery workshop.
A leader who says sellers need discovery training often describes several different behaviors. One seller begins with a long company story. Another asks a question without explaining why an answer matters. A third names an agenda, then leaves each answer behind for prepared points. A consultant makes an issue visible by reviewing real opening moments before recommending an exercise.
Treat an opening as a sequence of choices, not a personality test. An opening has a job. A seller needs to establish why a conversation exists, ask permission for a direction, and create room for a customer response. A polished voice does not prove those choices happened. A quiet seller often sets a useful agenda. An energetic seller sometimes rushes past a customer’s first clue. Managers need language for noticing behavior without reducing feedback to style.
In a fictional meeting, Lena sits with Devon, a sales director who says every seller pitches too soon. Lena asks for three recent openings from ordinary work rather than showcase calls. Devon shares recordings from a first conversation, a follow up with a known contact, and a call arranged after a webinar. Lena says, “Let’s listen through each customer’s first response. We are looking for choices we hear, not judging confidence.” Devon agrees and puts his notebook aside.
The first recording starts with a seller describing a company for forty seconds. The customer says, “We have a few options under review.” Lena pauses. “What did your seller learn before describing an offering?” Devon says, “Nothing.” She asks, “What opening move would create a different exchange?” He replies, “Name why our conversation was scheduled, then ask what prompted a review.” Their note reads: purpose missing before explanation. Devon now has a behavior for a manager discussion instead of a broad label such as weak discovery.
On a second recording, a seller says, “What are your priorities for this quarter?” The customer gives a short answer, then asks why a seller wants to know. Lena pauses again. Devon says, “At least she asked a question.” Lena agrees, then asks what a customer lacked. Devon hears no reason for a question. This issue differs from a first recording. Here, a seller did not need fewer questions. She needed a clear reason for her first question. Their note reads: question asked without context.
The third recording starts with a simple agenda. A seller says he wants to understand a recent process change and then discuss whether a later working session would be useful. The customer mentions a deadline. The seller acknowledges a deadline, then launches into prepared material about reporting. Devon notices his original diagnosis misses a choice. “He started well,” he says, “then he left a customer’s answer unexplored.” Lena writes: agenda set, answer not explored. A workshop built around one generic opening script would treat all three moments as identical. They are different.
Use an observation page. One space names an opening move. Another records customer words. A third captures a seller’s next response. Avoid labels such as good, bad, engaging, or weak. Specific observation creates a coaching path. “Seller named an agenda and asked permission” shows a manager what to reinforce. “Customer described a deadline, seller changed topics” shows a manager where to pause.
An opening often includes five choices. A seller names a relevant reason for contact. A seller offers a simple agenda. A seller asks for agreement or correction. A seller asks a question connected to an earlier reason. A seller responds to an answer before moving forward. Calls do not need identical wording. A conversation after a webinar deserves language different from a renewal conversation. This sequence gives managers a shared lens while leaving room for context.
Ask managers for examples matching calls their sellers make. A customer with five minutes between meetings creates pressure different from a scheduled forty five minute discovery call. A seller speaking with an operations lead often needs opening language different from language used with a senior executive. Keep examples free of customer names and sensitive details. The goal is not a library of clever lines. The goal is to notice whether a seller establishes purpose and responds to information available during a conversation.
Time pressure deserves direct practice. In a fictional roleplay, Jordan plays a prospect who says, “I have six minutes. We already use another approach.” A seller starts, “Thanks for making time. I saw your team recently changed how requests move between groups. I would like to understand whether handoffs are creating extra work, then decide whether a later conversation is worthwhile. Does your reason for taking this call fit our agenda?” Jordan replies, “The handoffs are messy, yet I did not agree to a product pitch.” The seller asks, “Which handoff creates most of your extra work?” This exchange includes purpose, permission, and a question tied to an observation.
Run a contrasting rehearsal where a seller leads with a company story. A manager interrupts after thirty seconds and asks one diagnostic question: “What information did a seller seek before explaining an offering?” Do not ask participants for a perfect statement on a first attempt. Ask for one altered choice. A seller who omitted an agenda adds one sentence. A seller who asked an unexplained question adds a reason. A seller who ignored an answer asks one follow up. Small, audible revisions give managers sharper feedback.
Managers also need a way to give feedback without taking over a call. After a roleplay, start with evidence. Say, “You named why you reached out and asked whether our agenda fit. When Jordan mentioned handoffs, you moved to reporting. What did you hear in his answer?” A seller has room to reflect before receiving advice. If a seller says, “I wanted to stay on my plan,” ask, “What question would help you understand a handoff issue?” Attention stays on a choice made during an opening.
Avoid one all purpose score. A seller receiving two out of five knows little about tomorrow’s adjustment. Separate observations make patterns clearer across a team. One manager might notice several sellers skip an agenda. Another might find sellers set an agenda yet fail to ask a question connected to customer context. Such patterns inform workshop design. They also stop leaders from calling every opening issue a confidence problem.
Before selecting a workshop exercise, agree on an exact behavior for practice. Write one sentence in plain language: “Sellers explain why they asked for time and ask one question linked to a stated customer situation.” Choose one call type where managers expect to hear this behavior. Decide how a manager will record evidence after a future call. A brief note with an opening move, customer response, and next move is enough. No elaborate scorecard belongs in an initial coaching cycle.
For a fictional practice situation, use a blank context. A team changed its approval process, and a seller has eight minutes for an introductory call. Record an opening aloud. Listen once without notes. Listen again and mark where you named purpose, asked permission, asked a connected question, and followed an answer. Revise your first missing choice only. Send your manager a recording and ask for feedback on a customer response you intend to explore next.
Practice these next
Design practice for sellers who answer their own questions before buyers respond.
Use a recent loss to identify a sales conversation worth rehearsing without assigning blame.
Guide manager feedback for demonstrations tied to buyer priorities.
Set shared coaching expectations after a merger without erasing useful local habits.
Build manager coaching confidence around observed call behavior and private, specific feedback.
Help sales leaders define what a new seller must demonstrate before managing accounts.