Problem confirmation
Get the buyer to say the problem back to you in their own words, on record, before you show anything about your product. A problem the rep states is forgettable; a problem the buyer states out loud is the thing they'll defend internally later.
Winning by Design's SPICED framework treats 'Pain' as a two-way confirmation step, not a slide the rep reads; Gong call data shows top performers spend 2-3 minutes here letting the buyer talk more than the rep does.
- Restate the pain you heard in discovery as a question, not a statement
- Let the buyer correct, sharpen, or add detail, and write down what they say
- Ask who else feels this pain (finance, ops, the contractors themselves)
- Ask how they cope with it today, in their own words
- Pause and let silence do the work instead of filling it
- A bullet list of 'common pains in your industry'
- Moving to the solution before the buyer confirms the pain themselves
- Assuming the pain from the intro call still ranks first for this buyer
- Talking over the buyer's answer to add your own framing
- Buyer answers with a shrug ('yeah I guess, it's fine')
- Buyer describes a different, unrelated problem than the one you prepped for
- Buyer defers to someone else in the room to answer ('ask Dana')
- The rep states the problem as a fact instead of asking the buyer to confirm it.
- The rep moves on after a lukewarm 'sure' instead of probing for a number.
- The pain confirmed doesn't map to a budget line anyone owns.
- · In your last three calls, did the buyer say the problem back in their own words, or did you say it for them?
- · Do you have a note of who specifically owns this pain, by name and title?
You mentioned [pain] costs your team [time/money]. Is that still the biggest blocker, or has something changed since we last talked?
"A lot of companies struggle with international payroll compliance."
"Last time we talked, your ops lead said onboarding a new contractor in Brazil takes 11 days and touches four systems. Is that still the case, or has it gotten worse since you hired in two new countries?"
Cites a specific prior statement, a number, and a named role, then invites the buyer to update or confirm it live.
Quick quiz
1. Why confirm the problem in the buyer's own words instead of stating it yourself?
- ○ It saves the rep time.
- ✓ A problem the buyer voices out loud is one they'll later defend internally to their own team.
Winning by Design frames pain confirmation as building the buyer's internal case, not the rep's pitch.
2. A lukewarm 'yeah I guess, it's fine' response means the rep should…
- ○ Move to the demo to re-engage them.
- ✓ Probe further for a specific cost or owner before continuing.
A vague confirmation usually means the pain isn't prioritized yet, and pushing forward wastes the rest of the call.