Cold calling

The fastest way to ruin cold calling is to treat every prospect like a row in a spreadsheet. Cold calling works when the rep has a credible reason to call now, not just a phone number and a quota.

In practical terms, cold calling is a targeted phone conversation with someone who hasn’t interacted with your company yet. The first goal isn’t to close. It’s to find out whether a relevant problem exists and, if it does, agree on a sensible next step.

Cold calling starts with a reason

A 120-person fintech company hires its first chief compliance officer. That’s a reasonable trigger for a compliance consultancy to investigate. The new hire might be dealing with an upcoming audit, a larger customer requirement, or a workload that was previously spread across finance and legal.

It doesn’t prove the company needs help. It gives the rep a reason to call that’s better than “you fit our target market.”

That distinction matters. A call to someone who downloaded a pricing guide is warm. A call to an existing customer is an account or expansion call. A call to a finance leader found through a target account list, with no prior interaction, is cold calling.

Cold prospects don’t owe you patience. The opener has to earn the next 20 seconds.

What the process looks like in practice

The work happens before the dial. Start with an ideal customer profile, but don’t stop at company size and industry. Decide what event would make the problem more likely to matter this month.

For example, a 300-person SaaS company with a new VP of Revenue Operations may be a useful target for a forecasting consultancy. The VP probably owns the problem. The CEO probably doesn’t, even if the CEO is technically the decision-maker.

Then check the account. Look for funding, a new executive, a market launch, a processor change, a compliance deadline, or a job posting that exposes the problem. A company hiring five account executives may need pipeline coverage before those new reps start. A company opening in Germany may be dealing with regional payment reconciliation. These details shape the hypothesis.

The rep should be able to answer three questions before calling:

• Why this company?
• Why this person?
• Why now?

That’s the only list worth keeping. If the answer to all three is “the data provider said they fit,” the account isn’t ready.

A 75-person B2B software company has just raised a Series B and posted three account executive roles. An outbound agency might open like this:

“Hi Maya, this is Arun from Nividh. I noticed you’re hiring three account executives after the funding round. We help B2B teams keep pipeline moving while new reps ramp. How are you handling prospecting during that gap?”

It’s specific without pretending to know the company’s internal problems. Maya can say the assumption is wrong, explain what they’re doing, or point Arun to someone else. All three outcomes are more useful than a feature pitch.

An SDR should record the answer, not just the disposition. “No answer” tells the team almost nothing. “Spoke to RevOps, timing is after the June planning cycle” is useful.

The script should be a guardrail, not a speech

Most teams get this wrong. They write a script so polished that the rep sounds like they’re reading legal copy. A script should stop rambling and preserve the important parts. It shouldn’t prevent the rep from listening.

A workable opener has the caller’s name, the reason for calling, a relevant problem, and one question. That’s enough.

For a cybersecurity consultancy calling a company that recently completed a SOC 2 Type II audit:

“Hi Daniel, this is Priya from Northline Security. I’m calling because you recently announced SOC 2 Type II certification. Teams at your stage often find the evidence process gets harder to maintain across vendors after the audit. Are you handling that internally, or is it spread across security and engineering?”

If Daniel says it’s internal, the rep can ask how much time it takes. If he says it’s spread across teams, that’s a possible problem to explore. If he says someone else owns it, the call has produced useful routing information.

The question needs to match the person’s job. A head of finance can talk about reconciliation. A junior marketing manager probably can’t, even if the contact database labels them a decision-maker. Bad routing creates false negatives, and then the team blames cold calling.

Avoid opening with the company biography, a list of awards, or “I’m calling to see if you’re interested in our platform.” The buyer has no reason to be interested yet. That line makes them do all the work.

Scripts should include a few response paths, but keep them short. If the prospect says they’re busy, ask for a specific better time. If they say “send me information,” ask what they want to evaluate before sending anything. If they already have a provider, ask what works and what they’d change. If they say no, respect it. One brief question about timing can be reasonable. Arguing isn’t.

Why cold calling campaigns stall

Usually, the problem starts with the list.

A 90-person HR software vendor might call every HR director in North America. That produces activity, but it doesn’t create a reason for anyone to care. If the offer is for companies replacing payroll systems, the team should look for signals such as a new payroll leader, an acquisition, a job posting for payroll operations, or public complaints about an implementation.

The second problem is bad diagnosis. Teams celebrate dials because dials are easy to count. They don’t tell you whether the market understands the offer.

Track what happens after the dial: connect rate, actual conversations, qualified conversations, meetings booked, meetings held, and opportunities created. If 2,000 dials produce 40 conversations and no meetings, listen to the calls. Maybe the opener is vague. Maybe the contact is wrong. Maybe the problem isn’t urgent.

More dials won’t fix any of those. It just gives you a larger spreadsheet containing the same bad news.

Investopedia cites research suggesting that an average of 18 calls may be needed to reach a buyer, while many sellers stop after four attempts. That supports persistence, not harassment. Four or five attempts across different business days and times can be reasonable when the account is a good fit and there’s a real trigger. Repeatedly calling after a clear decline is different.

Teams also need to check the rules that apply to the campaign. Requirements vary by country, state, number type, and audience. Investopedia’s overview covers the U.S. Do Not Call framework and related issues.

Cold calling works better inside a sequence

A phone call can surface context quickly. Email can give the prospect something to review. LinkedIn can help confirm a role or a trigger. None of those channels rescues weak targeting.

Consider a 60-person analytics consultancy targeting a VP of Sales after the company posts five new sales roles. The rep could call with a question about pipeline coverage, leave a short voicemail if there’s no answer, send a brief email with one relevant example, then call again two business days later with a narrower question.

That sequence isn’t about making the prospect endure every channel. It gives them a few ways to respond and gives the team more evidence about what’s working. The call should always have a reason behind it, and the CRM should capture what happened rather than just marking the activity complete.