A promising call can go quiet for a predictable reason: the SDR notices a problem, labels it, and immediately starts describing a solution. The buyer has not yet felt the cost of leaving that problem alone. In SPIN Selling, the Problem stage is not a bridge to rush across; it is where a vague inconvenience becomes a priority worth changing.
The premature pitch pattern
Reps often hear a small signal—manual reporting, slow follow-up, inconsistent forecasting—and respond with a feature. That response may be accurate, but accuracy is not urgency. The prospect can agree that the feature sounds useful while continuing with the current process because the personal and commercial consequences remain unexplored.
A rushed pitch also turns discovery into a quiz. The SDR asks whether a problem exists, receives a yes, and moves on. Buyers then give short answers because the conversation has taught them that every answer is merely a cue for a demo. Curiosity disappears before the real diagnosis begins.
The alternative is to treat the first problem as an opening, not proof. Ask what happens when it occurs, who has to compensate, how often it affects decisions, and what has already been tried. Each question should help the buyer connect a workflow issue to time, risk, revenue, or customer experience.
How to stay in Problem longer
Use a sequence that narrows gently. Start broad: “Where does that process become difficult?” Then make the impact concrete: “When that happens at month end, what does it delay?” Finally, ask for ownership: “Who feels that delay most?” The goal is not to manufacture pain. It is to understand the cost of a problem the buyer has already named.
Listen for contrast words such as “usually,” “except,” “but,” and “sometimes.” They often reveal the gap between the official process and the lived process. If a prospect says follow-up is automated but admits exceptions are handled in spreadsheets, do not return to your pitch. Explore the exceptions, volume, and consequences.
Good problem questions are neutral. Avoid stacking your conclusion into the question, such as “That must be hurting conversion, right?” Instead ask, “What does that do to conversion?” Neutral questions produce better evidence and make the buyer an active participant in the diagnosis.
The problem stage succeeds when the buyer explains why change matters in their own language, not when the rep names the most features.
Turn symptoms into implications
Symptoms are easy to acknowledge; implications create momentum. “We lose track of a few leads” is a symptom. “Which leads tend to be missed, and what is one recovered opportunity worth?” invites the buyer to calculate the implication. The SDR does not need to supply a dramatic number when the buyer can describe the real trade-off.
Keep the thread visible. If the buyer mentions manager time, return to it after discussing the process: “You said managers spend Friday repairing the report. What else is not happening while they do that?” This shows that you heard them and links separate details into a business case.
Do not confuse a long discovery with a deep one. Two thoughtful follow-ups on one material issue are more valuable than ten unrelated questions. Depth gives a later recommendation a clear reason to exist.
- Listen for the buyer's exact language before choosing a response.
- Ask one clear follow-up question rather than delivering a longer pitch.
- Capture the moment in your call notes so the next conversation starts with context.
A practical call plan
Before a call, choose two likely problem areas from the account context and prepare open questions for each. During the call, write down the buyer's words verbatim. After the call, score whether you learned the frequency, impact, owner, and attempted workaround for at least one issue.
If those four elements are missing, the next step should be more discovery rather than a generic demonstration. A useful recap sounds like this: “You are spending three days reconciling data, sales leaders cannot trust the weekly forecast, and the current workaround depends on one analyst. Did I get that right?” The buyer's confirmation creates a shared diagnosis.
Put the lesson into the next call
Choose one behavior from this article and practise it deliberately on your next five conversations. Review the recording immediately afterwards: identify the cue, the response you used, and the buyer's reaction. Small, observable adjustments compound faster than a wholesale rewrite of a working sales process.
Consistency matters more than a perfect script. When a team uses a shared framework, managers can coach a precise moment and reps can repeat a precise habit. That creates a more useful feedback loop for the buyer and a more dependable pipeline for the business.