November 19, 2026
11 min read
Edited by Esdoorn de Vries
B2B cold calling means phoning a company that doesn't know you and hasn't asked to hear from you. The first call has one aim, a meeting for a second conversation. On the phone you say two sentences at most about your product; the rest you keep for that meeting.
You get that meeting most easily when you have a reason to call this particular company now, and when you ask questions before you tell. With warm outreach there has already been some contact, such as a visit to your website, a chat at a trade show or a referral. With a cold call you bring that reason yourself.
In the Netherlands, calling companies is allowed. Sole traders, freelancers, general partnerships (vof) and professional partnerships (maatschap), such as a GP practice, may only be called with their consent. The rules for the Netherlands, Belgium and Germany are in B2B cold calling rules in Europe.
Before you pick up the phone
Say you sell managed IT. You take over the upkeep of computers, network and software for companies that have no specialist of their own for it. Don't call every company in your area. The broader your list, the more general your story, and a general story is easy to say no to. Pick a group whose problems you know, such as transport companies with twenty to a hundred staff. Everything there hangs on the planning system. If it won't start on a Monday morning, lorries stand idle.
First take out the companies you may not call without consent. For Dutch companies, the trade register of the Chamber of Commerce (KvK) shows each company's legal form, so you can spot sole traders and partnerships at a glance. Call from a number that shows and say at the start of every call who you are and which company you're calling for. Note straight away anyone who doesn't want to be called again.
Then look for a reason to call each company now. For managed IT that might be a vacancy for a systems administrator, a new depot, the takeover of another transport company or a new planning system. You find these moments on job sites, on LinkedIn, in trade magazines and in the regional news. If you find nothing for a company, you can still call it, with a question about the subject instead of a reason. That kind of call is harder to open, so start with the companies where something is going on.
Look up the managing director's name before you call, on the website or on LinkedIn, and ask reception whether they also look after IT. What you're asking for is half an hour to see whether you can do something for the company. How to get all of this onto one page is in Cold call script: structure and an example on one page.
Getting past reception and voicemail
At a company this size, someone on reception or in the planning office often picks up first. Say who you are and who you'd like to speak to, by name.
You: Good morning, it's [name] from [company]. Could I speak to [director's name], please?
Reception: Can I ask what it's regarding?
You: It's about IT support for your office and your planning system. Is [director's name] the right person for that?
Don't mention the vacancy to reception, because then you'll be put through to HR or told they don't work with agencies. Keep your answer short and honest. Don't pretend you're expected or have spoken before. That falls apart the moment you're put through, and the call is over before it started.
If the director isn't in, ask whether [name] still looks after IT. Ask too when it's best to call, early in the morning or at the end of the afternoon. If reception says "Just send an email to info@", ask who you should address it to, so it reaches the right person. Then call back at the time reception gave you.
If you get the director's voicemail, leave no message the first time and try again at a different time. A message from a stranger rarely gets a call back, and without one you can simply start with your opening on the next attempt. If you still get voicemail after two or three attempts, leave who you are, what you're calling about and when you'll try again: "Good morning, it's [name] from [company]. I'm calling about your IT support while you're recruiting a systems administrator. I'll try you again on Thursday morning." Then your next call doesn't come out of the blue.
The first thirty seconds
The director picks up and has no idea who you are. In your first sentences you say who you are, what you do and why you're calling now. Then you ask for thirty seconds.
"Good morning, it's [name] from [company]. We look after IT for transport companies, and I saw you're recruiting a systems administrator. I'll be straight with you, this is a cold call. Have you got thirty seconds?"
Say what you do in the same sentence as the vacancy. If you only mention the vacancy, the director assumes a recruiter or a job applicant is calling. The vacancy shows you're not calling at random. Asking for thirty seconds is honest about what's happening, since you're calling unannounced and asking for very little, and anyone who says yes will actually listen. Use that time for your first question and keep your company history for the meeting. If the director says no, ask when suits better: "Shall I call you tomorrow at half eight, or is the end of the afternoon better?"
These openings lose the call straight away:
- "Is this a bad time?" Yes is the easiest answer, because the director doesn't yet know who you are or why you're calling.
- "How are you today?" From a stranger, that sounds like the start of a sales call.
- "Sorry to bother you." An apology makes you smaller, when you're calling because you have something to offer.
Start formally, and if the director is informal with you, go along with it.
Ask first, tell later
The director doesn't have your subject on their mind right now. Start on your solution and you'll hear "not interested", which from the director's side is fair enough. So ask questions first that bring the problem into view. Ask how it's handled now, what happens when it goes wrong and what that costs the director personally. A real conversation rarely runs smoothly at this point.
You: Who looks after your IT at the moment?
Director: Our planner. He's handy with it, and we've got an outside firm for the bigger stuff.
You: And if the planning system won't start on a Monday morning?
Director: That hardly ever happens.
You: When was the last time?
Director: September. We were down for a morning.
You: And what did the outside firm do?
Director: They couldn't look at it until the afternoon.
You: What were you doing that morning?
Director: Ringing round the drivers. All morning.
"That hardly ever happens" is the normal answer to a question about problems, because nobody likes admitting that things go wrong. Ask about the last time instead. A specific moment says more than a general impression, and the director hears themselves tell it.
Then sum up what you heard and ask whether that's right. Only then do you say something about your product, in two sentences that pick up what the director has just said.
You: So when the system goes down, you're on the phone to drivers all morning, and the outside firm doesn't get to it until the afternoon. Is that right?
Director: Yes. Well, it's once a year.
You: That's what we're there for. We take over the day-to-day support, with one number to call when something breaks, and if the planning system does go down, we're on it within the hour.
If the director asks about price earlier on, answer briefly and come straight back with a question: "It's priced per user and per site. How many people have you got in the office?" Your question puts you back in the conversation.
If the director still says it's no big deal, even about the last time, this company doesn't have a problem you can solve right now. Ask when the contract with the outside firm runs out, and agree to call back a few months before.
Proposing the meeting
Propose the meeting once the director has confirmed the problem and responded to your two sentences with something like "that makes sense". If you're not sure you're there yet, ask: "Does this sound like something that would help you?" Better to hear a no now than after your proposal.
Make the proposal specific. Say what you're proposing, how long it takes, who'll be there and when.
You: Shall we sit down for half an hour, with you and your planner? I can do Tuesday at nine or Thursday late afternoon.
With two options, the director only has to choose. "When would suit you?" gets you "Let me check my diary and get back to you", and you'll usually wait for that call in vain. Don't ask whether you could "pop in some time" either.
If it's a yes, repeat the day and time, ask for their email address and send the calendar invite while you're still on the line. Ask whether it has arrived, so the meeting is in both diaries before you hang up. Put two lines in the invite about what it's for, as close as you can to what the director said: "Planning system down for a morning in September, all morning ringing drivers. IT support alongside the outside firm." Anyone who sees the meeting in their diary two weeks later will still know why they said yes, and is less likely to cancel.
When the director says no
A no in the first minute is rarely a considered decision. It's a reflex, like "just looking, thanks" to a shop assistant. The director doesn't know yet why you're calling and mainly doesn't want to be sold to. Don't argue, and don't give up straight away either. Acknowledge the point and ask a question that opens the conversation again.
To "I haven't got time" in the opening, say: "Understood, I've called out of the blue. Shall I ring you tomorrow at half eight?" If it comes later in the call, ask for one question: "Then I'll keep it short. Who sorts it out now when the planning system won't start?"
To "Not interested", say: "I understand, you've got enough on with that vacancy. That's actually why I'm calling, because until someone's in post, we can cover it. How long has the role been open?"
To "Just send me an email", say: "Will do. Is it mainly the outages you'd want to read about, or the work that piles up until the new systems administrator starts? And shall I give you a quick call on Thursday to hear what you thought?" The question tells you what to send, and the call on Thursday keeps the conversation open.
To "Too expensive", as long as you haven't given a price, say: "I haven't mentioned a price yet. What are you comparing it with?"
To "We already have an IT company", say: "Good, then you know what it's worth. I'm not asking you to switch today. What are you happy with, and what could be better?"
A no to the meeting after a good conversation means something else. The director either isn't convinced yet, or the timing is wrong. Ask which it is: "Can I ask why? Is it the timing, or are you not sure it would work?" If it's the timing, ask when it will be on the table, and make it specific: "Then I'll call you in the first week of September." If the director doubts it would work, ask what they'd need to know to be sure. The answer is often exactly what you meant to show in the meeting.
Try to end every call with a next step, such as a meeting, a date to call back or the name of the person you should be speaking to. If that doesn't work, thank them for their time and note why it wasn't relevant now.
After the call
Write down straight away what the director said, as close to word for word as you can. "Ringing round the drivers all morning" is worth more in the meeting than "has trouble with outages". Put the callback in your diary at once, before you dial the next number.
Call in fixed blocks of one or two hours in which you do nothing else. For each call, note where it stalled: at reception, in the opening, at your questions, after your two sentences or at the proposal. Calls that ended in a meeting go in a column of their own. After a few weeks you'll see where it gets stuck. Don't just look at where most calls stall, because that's nearly always the opening. Count for each stage how many calls reached it and how many stalled there. If ten calls reach your proposal and eight stall there, the problem is your proposal, even if more calls stall in the opening.
- If many calls stall in the opening, your reason for calling is too weak or your opening too long.
- If they stall after your questions, you're calling the wrong companies or asking about a problem they don't have.
- If they stall at your proposal, you're proposing too early. Sum up first and ask whether that's right.
Change one thing at a time and call a few blocks with it, so you know what made the difference.
At Esdoorn de Vries, our team calls this way for clients, for a target group we agree together beforehand. Our own software, Radar, finds the reasons to call in vacancies, news and changes in the Chamber of Commerce register. Read how we book meetings with decision-makers.