You know the moment. A prospect says something like “Our compliance process is a complete pain in the ass” or “Token management is killing us.” That language matters.
We noticed it about two weeks ago. One of our reps reached an attorney at a financial services firm. The call lasted 433 seconds. In that time, the prospect didn’t ask a single qualifying question about our product. Instead, she spent most of the call describing how manual token optimization was eating up her team’s time. She used the exact phrase “pain in the ass” to describe the problem. By the time the rep asked for a meeting, she said yes immediately. No objections. No stalling. Just commitment.
We dug into our recent call data to see if this was a pattern or a fluke. It’s a pattern.
Look at Lourdes Lam, Compliance FIU Manager at Ria Money Transfer. Call length: 575 seconds. She never said no to a meeting. She said she was busy that week but committed to next Friday at 3 PM to discuss their regulatory compliance process. The rep didn’t push. She volunteered the time. Why? Because she’d explicitly named the problem: automating regulatory compliance. She owned that problem. She wanted to solve it.
John Hammill, President at Capview, took a 541-second call and booked immediately for the next Tuesday at 1:15 PM ET. His CFO is joining because John framed it explicitly: they need to streamline compliance for hundreds of LLCs. Again, specific problem. Immediate booking.
Here’s what we think is happening. When a prospect uses their own language to describe a workflow problem, they’re signaling something critical: they’ve already done the mental work of recognizing it’s a problem. They’ve probably complained about it internally. They’ve felt the cost. By the time we call, we’re not introducing the idea of a problem. We’re confirming that a solution exists for something they already know they need to fix.
The difference is huge. Most cold calls spend time on problem discovery. “Tell me about your current process.” “What challenges are you facing?” Valuable questions, but they push the prospect to construct an answer in real time. They force thinking.
When a prospect leads with their own problem language, they skip that step entirely. They’ve already done it. They just need to know if we can help.
The counterpoint is telling. We pulled a call with Muhammad Mohsin from GO MOBIT, 1025 seconds. He explained his team already built a custom internal gateway. His bottleneck wasn’t technical infrastructure. It was customer acquisition. He asked for an email to follow up. No meeting. Why? Because he named a different problem than what we solve. His language told us we weren’t aligned. That’s actually useful.
The pattern holds across dozens of calls now. When prospects volunteer explicit language about a workflow problem, conversions happen in under 600 seconds. When they don’t, meetings are slower, objections are higher, and follow-ups stretch out.
So here’s what we’re testing this week. Instead of leading with product, we’re listening harder for whether a prospect names a pain first. If they do, we get specific about that problem. We don’t pivot to our solution immediately. We let them own it. We confirm we’ve seen it before. Then we ask for 15 minutes.
The attorney who said “pain in the ass” knew what she needed before we called. We just had to get out of the way.