Cyber Cold Calls That Asked About Real Pain Booked 3x More
We read 155 cyber cold calls. When the rep asked a pain question, 40% booked. When they didn’t, 12%. Only 1 in 6 calls asked one.

By Cavin Sherman
Last week I had my team pull 155 of our cyber cold calls and read every single one. Real conversations, 90 seconds or longer, six cybersecurity campaigns, 20 reps, all from the first half of November. I wanted to know what my reps actually ask once they’ve got a security person on the phone.
One number jumped off the page. When the rep asked about a real problem, something like “is your AppSec backlog smaller today than it was six months ago, or are you treading water?”, 40% of those calls booked a meeting. When nobody asked, 12% booked.
And only 25 of the 155 calls had a pain question at all.
So what did the numbers say?
Calls | Booked a meeting |
|---|---|
Asked a pain question (25) | 10 (40%) |
No pain question (130) | 16 (12%) |
That’s a little over 3x.
I want to be straight about the sample. We pulled the longest calls first, so it leans toward real conversations and the book rate is higher than what the floor does on a normal day. And a call where the prospect is talking about their problems is usually a warmer call to begin with. So this is a link, and I can’t prove the question caused the meeting. What I can tell you is the calls that went deep almost always had one, and most of our calls never got there.
Everybody runs the same script
This part surprised me more. Almost every call sounds the same.
The permission opener, “mind if I grab half a minute to tell you why I called, and you tell me if it’s relevant?”, was on 86% of calls. “Does [company] ring a bell at all?” was on 44%. The no-oriented ask, “would it be crazy to take 15 minutes next week?”, was on 61%. Then Tuesday or Wednesday, then the best email for the invite.
I wrote most of that skeleton and it works. But it’s built to explain. We open, we pitch, we ask for the time. There’s two modes on a cold call, you’re either explaining or you’re asking, and on most of these calls the rep stayed in explaining mode from hello to goodbye.
What does a good pain question sound like?
These are real lines from calls that booked:
“Is your AppSec backlog smaller today than it was six months ago, or are you treading water?”
“Is there anything top of mind for you right now when dealing with endpoint security that’s really bogging you down?”
“Is it even possible to know at any moment exactly who has access to what across your cloud and SaaS?”
“Out of those three, the cost side, the security side or the hardware side, do any of those stand out for you?”
“Are you more concerned with the governance aspect, or mapping to specific regulations?”
Most of them are either/or. The prospect doesn’t have to confess a problem out of nowhere, they just pick one, and once they pick one they start explaining it to you. The backlog one is my favorite because “treading water” is exactly how a lot of security teams feel, and when you say it out loud they laugh and tell you how bad it is.
Compare that to “would this be something your team could benefit from?” That one got an objection. It’s a yes or no question about your product, and the easy answer is no. A pain question is about their week.
When do you ask it?
Most of the pain questions in the sample came after the ask, 19 of 27. That’s how I teach it and I’m glad it showed up in the data.
You don’t open with discovery. If you lead with five questions before you’ve said why you called, it feels like an interrogation and they’re gone. Pitch, ask for the meeting, and when they push back, that’s your opening. The no-oriented ask got pushback first on 61 of 104 tries, which is normal. That first no is where the loop starts, and a pain question is the best loop I know. “Totally fair. Quick one though, is your backlog getting smaller or are you treading water?” Now they’re talking about their problem and you’re back in the call.
Why don’t reps ask?
Honestly I think it’s mostly because it isn’t on the page. Reps run the screenplay, and on most of our cyber campaigns the pain question was a line you could use if you had time. Nobody had to say it. So when the first no comes, it feels like the end of the call and they go straight to “can I just send you an email?”
If you run a team selling security, go read ten of your own calls this week and count how many had a pain question in them. My guess is it’s fewer than you think. Then write one either/or question into the script, right after the first pushback, and make it as non-optional as the opener.
That’s how we run our cyber campaigns. If you want to hear what it sounds like on your product, grab a time with me.

