How to make your buyer feel the problem before you pitch.
Your solution only exists to solve a problem — but not just any problem. The exact problem, for that exact buyer, in their exact situation. And here’s the secret most sellers miss: the secret to selling isn’t knowing your product inside and out, it’s knowing your buyer’s problem better than they do. This is the Problem beat of the StorySelling Formula, and it’s where belief is either earned or lost.
Problems aren’t flat — they live in layers. Peel them in the right order and two things happen: you earn trust (because you’re describing their world more clearly than they usually hear it), and you create motion (because the cost of staying the same becomes unbearable). Here’s how.
Peel the layers, in order
Start with their current way — the spreadsheets, the Slack threads, the once-a-week review. Honor it; don’t roll your eyes. That current way produces problems (the symptoms that bubble up — renewals slip, risk shows up too late). Underneath the symptoms are limitations (the real constraint: the data is stale, they only review monthly). And underneath that is impact — what it actually costs. Current way → problems → limitations → impact. Move through them cleanly and you’re not accusing anyone; you’re organizing their reality.
Turn a cracked windshield into a smashed one
A problem with no impact is a cracked windshield — annoying, but nobody pays to fix it. The only reason someone parts with a dollar is to solve a problem that actually hurts. So find the one thing that smashes the windshield: the cost, in time, money, risk, or energy. "Our CRM takes four seconds to load" earns a shrug. "Because our CRM takes four seconds to load, reps waste twenty minutes a day — five thousand lost selling hours a year" is a business problem worth solving. Ask yourself: is my buyer’s problem cracked or smashed? If it’s cracked, name the thing that smashes it.
Get specific — scenes stick
Vague problems get vague responses. "We struggle with forecasting" is noise. "We discover risk on Thursdays with three-day-old usage data" is a scene, and scenes stick, because the brain can picture them. Specificity is what makes the buyer feel understood — and understood is what earns belief. Trade every generic complaint for a concrete moment: a day of the week, a number, a felt frustration. The more it sounds like their actual life, the more they lean in.
Blame the system, not the people
How you phrase the problem decides whether you get a partner or a defender. "Deals slip because managers aren’t doing their job" earns a defender — now they argue with you. "Deals slip because managers are blind six days out of seven" earns a partner — now they want to fix the system. Blame invites debate; systems invite design. Frame every problem as a loop the situation produces, never a failing of the people in the room, and the buyer joins you on the same side of the table.
Say it in one breath — then stop
The whole problem should compress into a single sentence a skeptical person can nod at without a slide: "Because you [current way], you keep seeing [problem] driven by [limitation], which costs [impact] and leaves people [emotion]." If it can’t be said in one breath, it isn’t sharp enough yet. Then do the hardest thing in selling: stop. Let the silence work. Let the room sit in the cost — don’t rush to rescue. If you’ve named it right, someone will ask, "so what do we do?" That question is the door to your solution.
"Anyone can point out a flaw. The seller who wins names the whole problem — the current way, the limitation underneath, and the real cost of staying stuck — so clearly that the buyer feels ‘later’ is more expensive than ‘now.’ That’s the moment interest becomes urgency."
Frequently asked
How do I make a buyer feel their problem?
Peel it in layers — current way → symptoms → the limitation underneath → the real cost — then get specific enough that it sounds like their actual life ("we find risk on Thursdays with three-day-old data"). Add the impact that turns a cracked windshield into a smashed one, say it in one breath, and stop so the room sits in the cost.
Why isn’t naming the problem enough to close?
Because a problem with no impact is just a fun fact. "Our CRM is slow" changes nothing; "our slow CRM costs 5,000 selling hours a year" is a problem worth paying to solve. Buyers only spend money to fix a pain that hurts — so you have to attach the cost in time, money, or risk before the problem creates any urgency.
Should I talk about the problem or the solution first?
Problem first, always. You haven’t earned the right to talk about your solution until the buyer agrees the problem is worth solving. Spend zero time on your product until you’ve named their current way, the limitation, and the cost. Lead with the solution and you’re just another vendor talking about yourself.
How do I talk about a problem without sounding like I’m blaming the buyer?
Blame the system, not the people. "Managers aren’t doing their job" makes them defensive; "managers are blind six days out of seven" makes them a partner in fixing it. Frame every problem as a loop the situation produces, never a failing of the people in the room — blame invites debate, systems invite design.