Cold Call Teardown: The Buyer Said "Actually, We're Looking at That Right Now" — And the Rep Blew It

The Luckiest Dial of the Month

I was listening to a recorded call from a rep — let's call him Marcus — who was dialing into mid-market accounts selling a workflow automation tool. He was forty-something dials into his afternoon block when a VP of Operations picked up, and after Marcus delivered his opener, the buyer said the seven words every SDR dreams about:

"Actually, we're looking at that right now."

Marcus's voice changed. You could hear it. The pitch went up half an octave. He got excited, which is human and forgivable, and then he did the thing that is neither: he booked a demo in eleven seconds flat.

"That's awesome — we should get you in front of our AE. How's Thursday at two?"

The buyer said sure. Marcus hung up, probably fist-pumped, logged the meeting, and moved on to the next dial.

Two weeks later, the AE showed up to that demo and learned the buyer was already deep into evaluations with two other vendors. One of those vendors had been in the account for three weeks, had already done a technical deep-dive, and had a champion on the buying committee. Marcus's AE was column three in someone else's spreadsheet. The deal closed thirty days later. They lost.

This is not a story about a bad rep. Marcus is a good rep. He hits activity numbers, his openers are sharp, and he gets people talking. This is a story about what happens when adrenaline overrides process at the exact moment process matters most.

Why This Moment Is Different From Every Other Dial

Most of your dials end in voicemail. A meaningful chunk end in some version of "not interested." A smaller chunk turn into a conversation. And then, maybe one in forty — if you are dialing well-targeted lists and your timing is decent — you land on someone who is actively evaluating a solution like yours.

That one-in-forty call is not the same animal as a cold call that generates curiosity. When someone says "we're looking at that," the dynamic flips. You are no longer trying to create interest. Interest already exists. The danger is no longer that you bore them — it's that you waste the advantage.

Here is what Marcus had in that moment: a live buyer, already spending time and mental energy on the exact problem he was calling about, willing to talk. Here is what Marcus did with it: traded all of that for a calendar invite.

The calendar invite felt like a win. It was not a win. It was a receipt for a transaction where he gave away leverage and got nothing back.

The Eleven-Second Book: What Went Wrong, Line by Line

Let me reconstruct the exchange, because I want to be specific about where the wheels came off.

Buyer: "Actually, we're looking at that right now."

Marcus: "That's awesome — we should get you in front of our AE. How's Thursday at two?"

Buyer: "Uh, sure, Thursday works."

Marcus: "Great, I'll send you an invite. Looking forward to it."

That's the whole thing. Eleven seconds from "we're looking at that" to "I'll send you an invite." No questions. No discovery. No understanding of what triggered the evaluation, who else is involved, what the timeline looks like, or what the buyer actually cares about.

Marcus treated an active evaluation like a cold meeting-set. The playbook for a cold meeting-set is: generate enough interest to earn the next conversation. But this buyer was past that. They didn't need to be convinced the problem was real. They needed to be convinced that Marcus's company was worth adding to a process that was already underway.

Those are two completely different jobs, and they require two completely different conversations.

The Four Questions You Need in the Ninety Seconds After "We're Looking at That"

I am not saying Marcus should have turned this into a thirty-minute interrogation on a cold call. The buyer picked up the phone, they weren't expecting this conversation, and you still need to respect that. But there is a window — roughly sixty to ninety seconds — where a buyer who just told you they're in-market will answer real questions, because the topic is already on their mind. They're living in it.

Here are the four questions Marcus should have asked, and why each one matters.

Question 1: "What kicked this off?"

Or some version of it. "What got you guys looking?" or "What happened that put this on the radar?" The phrasing matters less than the intent: you need the trigger event.

The trigger tells you everything. If the trigger is "our CEO saw a competitor using it," that's a top-down mandate and the timeline is probably aggressive. If the trigger is "we're doing our annual vendor review," that's a process-driven evaluation and you might be dealing with a longer cycle and a procurement team. If the trigger is "we just lost three people and the manual work is killing us," that's pain, and pain is the best thing you can sell into.

Without the trigger, your AE walks into the demo blind. With it, your AE walks in knowing exactly which story to tell.

Question 2: "How far along are you?"

This is the question that would have saved Marcus's deal. If the buyer says "we just started looking last week," you are early and you have room to shape the evaluation. If the buyer says "we've been at this for a month and we're narrowing down to two," you are late and you need to move fast — and honestly, you need to decide whether it's even worth pursuing.

The buyer in Marcus's call had been evaluating for three weeks. Marcus didn't know that. His AE didn't know that until they showed up to the demo and realized they were behind. By then, the other vendors had already anchored the buyer's criteria around their own strengths. Marcus's company was playing someone else's game.

Question 3: "Who else is involved in the decision?"

You are not asking for an org chart. You are asking whether this person can actually say yes, or whether they're a researcher who will take your demo, summarize it in a Slack message, and hand it to someone you've never spoken to.

"Is it just you evaluating this, or is there a team looking at it together?" That's enough. If they say "my boss and I are leading it, but procurement will get involved at the end," now your AE knows the real audience for the demo. If they say "I'm just doing some initial research for my VP," now you know you need to get to the VP.

Question 4: "When are you trying to have something in place?"

Timeline. The most basic qualification question in sales, and Marcus never asked it. If the answer is "end of quarter," your AE needs to compress the cycle and probably skip the standard demo flow in favor of a targeted proof-of-concept. If the answer is "sometime next year," you might still book the meeting, but you're going to stage it differently and set different expectations internally.

Timeline also tells you how seriously to weight this in your pipeline. An active evaluation with a deadline is a real opportunity. An active evaluation with no deadline is a science project.

How to Slow Down Without Cooling Them Off

I can hear the objection already: "If I start asking questions, the buyer is going to lose patience and I'll lose the meeting."

I have watched a lot of reps navigate this moment, and almost every one who asked these questions kept the buyer engaged. Here is why: the buyer just told you they are actively working on this problem. They are thinking about it. They are probably stressed about making the right choice. When you ask smart questions about their evaluation, you sound like someone who has done this before. You sound like a guide, not a telemarketer.

The trick is in how you transition. After they say "we're looking at that right now," you do not launch into a checklist. You match their energy, acknowledge what they said, and bridge into the questions naturally.

Here is what that sounds like:

"Oh, interesting — so you're already in the middle of evaluating this. What kicked that off for you guys?"

That's it. One sentence of acknowledgment, one question. The buyer answers, and now you're in a conversation. You ask the next question. Then the next. Sixty to ninety seconds later, you have the trigger, the timeline, the buying committee, and how far along they are.

Now — and only now — you book the meeting. But you book it differently.

Book a Discovery Call, Not a Demo

This is the part that most SDRs and even some AEs get wrong. When a buyer is in an active evaluation, the instinct is to get a demo on the calendar as fast as possible. Show the product. Impress them. Win.

But if you don't know what they care about, your demo is a guess. And in a competitive evaluation, a guess loses to a vendor who did their homework.

The meeting you book off an active evaluation should be a discovery call, not a demo. Frame it that way to the buyer:

"Here's what I'd suggest — rather than jumping straight into a demo, let's set up twenty-five minutes where our team can learn about what you've got in place today and what you're trying to solve. That way if we do a demo, it's actually relevant to your situation and not a generic walkthrough. Does that make sense?"

Almost every buyer says yes to that. You know why? Because they have already sat through generic demos from the other vendors and they're tired of it. A vendor who says "let me understand your situation first" stands out.

This approach works across verticals. If you're calling into a SOC leader trying to get twenty-five minutes on their calendar, the same logic applies — these are busy people who have seen every vendor deck, and what earns their time is showing you'll use it well. If you're dialing CROs and VPs of Sales about a SaaS product, same thing. The active buyer wants to feel like you're going to be a serious contender, not another logo on the Gartner quadrant slide.

The discovery call lets your AE walk in prepared. They know the trigger. They know the timeline. They know who else is in the room and who else is in the process. They can tailor every minute of the eventual demo to the things this specific buyer actually cares about. That is how you stop being column three.

What the Call Should Have Sounded Like

Let me rewrite Marcus's call. Same buyer, same moment, different execution.

Buyer: "Actually, we're looking at that right now."

Marcus: "Oh, interesting — so you're already evaluating this. What kicked that off?"

Buyer: "We've been doing everything manually and it's not scaling. We hired four people in the last two months and onboarding is a mess."

Marcus: "Got it. How far along are you in the process?"

Buyer: "We've talked to a couple of vendors. Still pretty early."

Marcus: "Makes sense. Is it just you driving this, or is there a broader team involved?"

Buyer: "Me and our COO. She'll make the final call."

Marcus: "And when are you trying to have something in place?"

Buyer: "Ideally before Q3. We've got another wave of hiring coming."

Marcus: "Here's what I'd suggest — rather than a generic demo, let's set up twenty-five minutes for you and your COO with our team to walk through what you've got today and where it's breaking down. That way, if it makes sense to go further, everything we show you is actually tailored to your setup. Would next Tuesday or Thursday work better?"

That's maybe ninety seconds longer than what Marcus actually did. But now the AE walks into that meeting knowing the trigger (manual processes not scaling), the timeline (before Q3), the decision-maker (the COO), and the competitive landscape (a couple of vendors, still early). That's a completely different starting position.

If you want to see how this kind of questioning flows in a full discovery framework, the discovery call playbook for staffing and recruiting lays out a twenty-five-minute structure that applies well beyond that industry — the sequencing of trigger, impact, timeline, and decision process is universal.

The Meeting You Don't Qualify Is the Meeting That Wastes Your Quarter

I want to be direct about the stakes here. When you land on an active buyer and you book a meeting without qualifying it, you are not just leaving money on the table in that deal. You are burning your AE's time, your SE's time, and your own follow-up bandwidth on a meeting that has a much lower chance of converting because you walked in blind.

I have seen reps book meetings that looked incredible on paper — buyer was in-market, had budget, picked up the phone and said yes — and then watched those meetings go nowhere because the AE showed up without context and delivered a pitch that didn't match what the buyer cared about. The buyer was polite. They said "we'll get back to you." They never did.

Meanwhile, the vendor who asked the right questions on the first call built the relationship from the start. They shaped the evaluation criteria. They got the demo in front of the COO, not just the researcher. They won.

The difference between those two outcomes was ninety seconds of questions on a cold call.

What I Would Do Next

If you are an SDR or a sales leader and you want to practice this exact moment — the transition from cold opener to in-market buyer to qualified meeting-set — that is the kind of thing DrillCall was built for. You can run the scenario with an AI buyer who pushes back, answers differently every time, and forces you to think on your feet instead of reading from a card. Reps I talk to tell me they get more reps on this specific skill in thirty minutes of drilling than they get in a month of live calls, because on live calls, this moment is so rare that you almost never get to practice it.

If you're building your cold call muscle more broadly, whether you're calling sales leaders who cold call for a living or any other persona, the fundamentals are the same: when a buyer tells you they're already in motion, your job is not to book faster. Your job is to learn faster.

The calendar invite is not the win. The context is the win. The meeting that your AE walks into prepared for — that's the win. Everything else is just a line on a report that makes your Tuesday look good and your quarter look the same.