Your Reps Hear the Pain.
They're Not Turning It Into Deals.
We analyzed 2,128 sales conversations to find out why deals stall between "great demo" and "signed contract." The answer: reps are having the right conversations at the wrong altitude.
Your reps are doing discovery. They're hearing what buyers struggle with. They're responsive — addressing buyer needs in nearly every call. But there's a massive gap between hearing a problem and building a business case around it. That gap is where deals go to die.
We ran this study to answer a specific question: what separates the sales conversations that win from the ones that lose? Not in theory — in actual transcripts, at the level of individual sentences and responses.
The answer wasn't about product knowledge or closing technique. It was about one skill: getting buyers to put a number on their problem.
The discovery-to-deal funnel is leaking
We used AI to extract every moment where a buyer expressed a need, a rep positioned value, or a quantifiable business problem surfaced. Here's where things break down.
What's a "CFO-grade value lever"? It's a buyer problem concrete enough that a finance person could put a dollar amount on it. "Integration is messy" is a pain point. "We have 4 engineers spending 30% of their time on integration maintenance" is a value lever — that's $180K/year in quantified cost.
The AI applied a strict "CFO test" to every buyer statement: could a CFO assign a dollar amount or headcount number to this problem? Only 152 out of 4,112 buyer needs passed.
This funnel is the story of the entire study. Buyers are telling reps about their problems freely. But those problems stay vague — "it's messy," "it takes too long," "it's frustrating." Reps hear the pain, respond with features, and move on. Nobody stops to ask: "How much is that costing you?"
Same pain point. Two very different outcomes.
The difference between a won deal and a lost deal isn't what buyers say — they express similar problems in both. The difference is what the rep does next.
Buyer: "Integrating all these tools is really messy for us."
Rep: "Totally get it. Our platform has seamless API integration that handles all of that."
The rep addressed the need. Checked the box. But the buyer still can't explain to their VP why this is worth $6K/year. The deal stalls in procurement.
Buyer: "Integrating all these tools is really messy for us."
Rep: "How many engineers are spending time on that? Is it their primary job, or does it pull them off feature work?"
Now the buyer has a number. Now they can tell their VP: "We're spending $180K/year on integration work that this platform eliminates." The deal moves.
In the data, we tracked how reps responded every time a buyer revealed a quantifiable business problem. The results were stark:
The numbers behind the pattern
We tagged every conversation with its deal outcome (won or lost) and compared the findings. The patterns held across every metric.
How buyers responded to rep positioning
When reps pitched the product's value, how did buyers react?
| Buyer Response | Won Deals | Lost Deals | What It Means |
|---|---|---|---|
| Engaged — asked follow-ups, built on the idea | 54% | 36% | Won deals generate genuine curiosity |
| Skeptical — questioned or challenged | 17% | 31% | Lost deals hit a credibility wall |
| Indifferent or neutral | 28% | 33% | Feature pitches that don't connect |
Why the skepticism gap matters. When buyers are skeptical (31% in lost deals vs. 17% in won deals), it's usually because the rep's pitch doesn't connect to the buyer's specific situation. The rep says "our platform saves time" but the buyer is thinking "prove it for my team." Reps who first quantify the buyer's problem, then position the product as the solution, generate engagement instead of skepticism.
Your reps are talking to users, not buyers
The conversations we analyzed are overwhelmingly technical. Reps and buyers are talking about integration headaches, training pipelines, and tool complexity. This is the language of engineers and team leads — not the language of the people who sign purchase orders.
What the conversations sound like
Here are the top buyer concerns, ranked by frequency:
Every one of these is a real problem. But notice the language: it's about what's frustrating, not what it's costing. Only 0.4% of buyer needs included specific numbers (headcount, dollars, time). The conversations are stuck at the feature altitude.
Value levers are how your champion sells for you. When a buyer tells you "integration is messy," that's a pain point — useful for the demo, useless in a budget meeting. But when you help that buyer quantify it — "we have 4 engineers spending 30% of their time on integration, that's $180K/year" — you've just written their internal pitch. That number travels up the org chart. It shows up in emails to the CFO. It gets the PO signed.
The reps who win aren't better at demos. They're better at turning what the user feels into what the buyer's boss can measure.
Turning pain points into business cases
For each of the top buyer concerns, here are the follow-up questions that elevate a vague frustration into a number the buyer can take to their boss. These are the questions reps in won deals were twice as likely to ask.
Integration Pain
- Headcount "How many people on your team spend time on integration work? Is that their main focus, or does it pull them off other projects?"
- Hard cost "Have you estimated what you're spending annually just keeping your current integrations running — engineering hours, compute, vendor fees?"
- Opportunity cost "What projects are getting delayed because your team is tied up with integration maintenance?"
Slow Training / Deployment
- Timeline impact "When a training run takes a week instead of a day, what does that do to your roadmap? Are you missing market windows?"
- Compute cost "What's your monthly compute bill for model training? Do you know the cost per training run?"
Lifecycle Management
- Failure cost "When a model degrades in production, how long does it take to detect and fix? What's the blast radius?"
- Scale pressure "You're managing N models today — what happens when that's 3x? Does your current approach scale, or does the team double?"
Data Security / Compliance
- Approval bottleneck "How long does it take to get security sign-off on a new tool today? What's that delay costing you in deployment speed?"
Team Collaboration
- Rework "How often do your teams redo work because of miscommunication or version conflicts? Weekly? Daily?"
- Decision latency "When something needs cross-functional approval, how long does that take? What if you could cut that from two weeks to two days?"
The pattern behind every question: take the vague frustration the buyer just expressed and ask for a number — people, hours, dollars, or frequency. One good follow-up question can transform "it's messy" into "we're spending $200K/year on this mess." That's the number that gets deals approved.
Follow-up messages that move deals forward
When your rep uncovers a value lever, the next step isn't a feature pitch — it's a follow-up message that makes the cost of delay concrete. Here's how the value levers from this study become urgency messages your reps can send the same day.
The principle: Don't just state the problem exists. Show how it accumulates with every week, month, or quarter the buyer delays. Use their own numbers. Make time visible. Make the cost of inaction feel irreversible.
Value Lever: High Model Training Costs
WHAT THE BUYER SAID
"We're spending way too much on training models — the costs are insane."
FOLLOW-UP MESSAGE
"You mentioned your team is burning through compute budget on model training. If that's running $15-20K/month — and it sounds like it might be more — every quarter you stay on the current approach is another $45-60K in training costs that automation could cut in half. That's not a future problem. That money is leaving your account this month."
Value Lever: Integration Complexity & Engineering Drain
WHAT THE BUYER SAID
"Our engineering team rebuilds integrations every time a customer has a custom requirement — it's our biggest bottleneck."
FOLLOW-UP MESSAGE
"You shared that your engineers are rebuilding integrations for every custom requirement. If that's pulling even 2-3 engineers off feature work for a week each time, you're looking at $20-30K in lost productivity per custom build. And the next custom requirement is already in the queue. Every one that hits before you have a scalable integration layer is another week your product roadmap slips."
Value Lever: Slow Deployment Cycles
WHAT THE BUYER SAID
"Deployment takes weeks — we're missing market windows."
FOLLOW-UP MESSAGE
"You mentioned deployments are taking weeks and you're missing market windows. Here's what's at stake: every deployment cycle that takes 3 weeks instead of 3 days is another product release your competitors ship first. If even one of those delays costs you a deal or a customer renewal, you've already paid for a year of automation tooling. How many deployments are in your queue right now?"
Combined Lever Message (Most Powerful)
COMBINING MULTIPLE LEVERS FROM ONE CONVERSATION
"While your team evaluates options, three clocks are running: your engineers are spending $20K+/month rebuilding integrations that a platform handles out of the box, your training costs are compounding every compute cycle, and every week-long deployment delay is a market window your competitors are walking through. None of these costs pause while you decide — they accumulate. I'd love to walk you through the math on what the next quarter costs if nothing changes."
Turning these insights into revenue
For Sales Leaders
- Train the "deepen" reflex. When a buyer says "it's messy" or "it takes too long," the immediate response should be a quantifying question, not a feature pitch. This is the single highest-leverage behavior change.
- Use the discovery questions above. Print them. Put them in the CRM. Make them mandatory in discovery calls.
- Arm your champion with math. Your buyer needs to justify the purchase to their boss. Give them a simple equation: "You told me 4 engineers spend 30% on integration. At $150K loaded, that's $180K/year. We're $6K/year."
- Track lever conversion. Measure how many discovery calls produce a quantified business case. Right now it's 6%. Get it to 20% and watch close rates climb.
For Marketing
- Build a "Cost of the Status Quo" calculator. Let prospects input their team size, training frequency, and integration count to see what their current approach is costing them.
- Write at the CFO altitude. Case studies should lead with "$X saved" not "features used." Blog posts should quantify the cost of fragmented tooling.
- Use buyer language from this study: "integration nightmare," "messy lifecycle," "can't justify to management."
- Create a champion's toolkit. A one-pager specifically designed for buyers to forward to their VP/CFO with the ROI calculation pre-built.
For Product
- Make the ROI visible in-product. Dashboards should prominently show "compute saved," "hours reduced," and "integration time eliminated" — these are the numbers champions need at renewal time.
- Simplify the integration story. Integration anxiety is the #1 buyer pain. Every friction point in onboarding is a conversion risk.
- Build for the multi-stakeholder sale. The product needs to serve the engineer who evaluates it AND the VP who approves it. Different views, different metrics.
How we did this
What we analyzed: 2,128 B2B sales conversations (voice and video calls only) for an AI/LLM platform product. The dataset includes 1,090 won deals and 1,038 lost deals — a balanced sample that allows direct won/lost comparison.
How we analyzed it: We built a multi-stage AI research pipeline that processed every conversation through four layers of extraction:
- Highlight — AI identifies the key moments in each conversation (6,641 highlights extracted)
- Distill — AI extracts structured findings from those moments, applying strict quality gates (5,579 findings produced)
- Extract — Findings are classified by type, strength, and response quality
- Synthesize — Patterns are identified across the full dataset
The CFO test: For value lever extraction, we applied a strict quality gate: "Could a CFO assign a dollar amount or measurable business impact to this problem?" This deliberately sets a high bar — the 6% pass rate means the test is working, not that the data is thin.
Data source: These are simulated sales conversations — not real customer data. We use synthetic datasets to develop and validate our analysis methodology before deploying it on real sales conversations. The patterns identified here (discovery depth, response quality, quantification gaps) are consistent with what we see in real customer deployments.
Built with: PonderAI — conversation intelligence that turns sales transcripts into quantified insights.