Target the Symptom, Not the Problem

Something subtle is happening in modern selling: teams keep pitching the problem, while buyers feel the symptom.

And when we take our own example, it becomes obvious: an executive, a Head of Sales, and a CMO do not feel the same symptoms. Same company, same product. Completely different pains, priorities, language, and KPIs.

That's why generic outreach fails, and why we sometimes lose prospects even as we're carefully explaining how our solution solves the problem. They just don't feel the problem we're talking about. They feel the symptom:

• their top pains
• their daily symptoms
• the KPIs they personally own
• how those symptoms impact those KPIs

Prospects don't wake up thinking about "root causes." We, as sellers, spot patterns across industries, understand the value chain, and see how everything connects. But our prospects wake up thinking about what's hurting today. They don't rebuild their strategic map every morning.

When we lead with symptoms, prospects recognize themselves instantly. When we link symptoms to the KPIs they are measured on, they see why solving it matters now. Salesforce's State of Sales research puts numbers on this: 86% of business buyers say they're more likely to buy when the seller understands their goals, and 59% say most sellers don't take the time to.

Symptom or problem: how do you tell the difference?

A simple test: the problem is the mechanism; the symptom is the experience.

"No consistent discovery methodology across the team" is a problem. "Every rep's forecast means something different, and I find out at the end of the quarter" is a symptom. "Fragmented data across tools" is a problem. "I spend Sunday evenings rebuilding the pipeline review by hand" is a symptom.

If a sentence could appear in your product brochure, it's probably problem language. If it could be said, verbatim and slightly tired, by your prospect on a Tuesday, that's a symptom. Symptoms are concrete, personal, and time-stamped. Problems are abstract, organizational, and timeless. People move on the first kind.

The persona map: symptom, KPI, message

Here's the same underlying issue, an unreliable sales process, as three personas actually experience it:

| Persona | The symptom they feel | The KPI they own | The message that lands | |---|---|---|---| | CEO | Forecasts the board can't trust; surprises at the end of the quarter | Revenue growth, predictability, valuation | "Your forecast shouldn't be a negotiation. What would change if the number you give the board actually held?" | | VP Sales | Deals slipping quarter after quarter; every rep selling their own way | Win rate, quota attainment, pipeline coverage | "Your best rep and your average rep run completely different discoveries. What is that gap costing you in win rate?" | | CMO | Sales says the leads are bad; pipeline contribution questioned in every QBR | Marketing-sourced pipeline, conversion rates, CAC | "Half your MQLs die in the first sales call. What if the problem isn't the leads: it's what happens to them next?" |

Same root cause. Three different doors in. Notice what each message does: it names the symptom in the persona's own words, then attaches it to a number that person personally defends.

A 4-step method to target the symptom

1. List the persona's symptoms in their words, not yours. Read their job postings, their LinkedIn posts, their earnings-call language. A VP Sales says "deals keep slipping," not "revenue process inefficiency." If your list sounds like your website, start over.
2. Map each symptom to a KPI that persona owns. Not company KPIs: the ones on their scorecard, the ones they are asked about in their own reviews. A symptom that doesn't touch a KPI they're measured on is background noise to them, however serious it looks from where you sit.
3. Craft the message symptom-first, KPI-second, solution-last (if at all). Open with the felt experience so they recognize themselves in one sentence. Connect it to their number. Then stop. The goal of the message is a conversation, not a conversion.
4. Validate in discovery, never assume. Your symptom hypothesis is a door-opener, not a diagnosis. Use the conversation to test which symptoms are real, how much they actually weigh, and what solving them would justify. A structured map like discovery in 13 dimensions helps you gauge the true gravity of the problem without turning the call into an interrogation.

From recognition to decision

This is where great discovery changes the dynamic: helping connect the dots and craft precision messaging that speaks directly to each persona's real pains. But keep the sequence honest: symptom-first messaging gets you the meeting. It doesn't win the deal.

What wins the deal is what happens next. Showing up with real strategic preparation instead of a questionnaire: we've written about where sales teams will win on exactly this. And running the conversation so the prospect connects their own symptoms to the root cause themselves, rather than hearing you announce it: the posture we call coaching-based selling. The Challenger research found that 53% of B2B customer loyalty is driven not by product or price, but by the sales experience itself; the experience of being precisely understood is hard to beat.

In our coaching sessions, this is the shift that takes longest. Sellers know the root cause so well that they can't resist explaining it. But a prospect who discovers that their Sunday-evening forecast pain and their board-credibility problem are the same problem will move faster than one who was told.

Want to practice the questions that help each persona see their own symptoms and connect them to their KPIs? Practice it with Lumia, your AI coach: pick one persona, and rehearse your opening until it sounds like their words, not yours.