You sell ERP implementation work. You've found a distributor that's opening a second warehouse, and you think its systems might need to change. Then the operations director answers and you say, "We help businesses streamline their operations. Have you got 15 minutes next week?"
You've left out the one thing that made this call worth making: the second warehouse.
A useful B2B cold call script tells the buyer who you are, gives them a specific reason for the call, and asks a question they can answer without sitting through a pitch. You can write those first two or three sentences in advance. After that, what you say depends on what the buyer tells you.
Here are three illustrative scripts you can adapt. The situations and responses are examples, not transcripts. Use the actual names of the caller and business, and name the client if you're calling on their behalf.
1. When you have a specific reason to call
Situation: A distributor has publicly announced a second warehouse. You provide ERP implementation services and want to speak to the person responsible for stock and fulfilment.
Caller: "Hi Alex, it's Sam from [ERP consultancy]. I'm calling about the systems work behind your second warehouse. We help distributors connect stock and order processing across sites. Have you already worked out how you'll handle stock transfers, or is that still being planned?"
Buyer: "We're keeping our existing system. The transfers are the bit we haven't worked out."
Caller: "Where's the question at the moment? Is it seeing what's available at each site, or how the team will move and record stock between them?"
The warehouse is a fact. A problem with stock transfers was a possibility until Alex confirmed it. That distinction matters. Once Alex explains the issue, you can ask who is working on it and whether it needs a decision before the site opens.
If there's work to do and your experience fits, suggest a narrow next step: "Would it be useful to look at how the transfer process works today and see what could stay in your existing setup?"
If the decision is already made and the buyer doesn't need help, thank them and finish the call. You found out what you needed to know.
2. When you have a hypothesis and need to test it
Situation: Your IT consultancy handles cloud migrations. The account fits your market, but you have no evidence that it has a project underway.
Caller: "Hi Morgan, it's Sam from [IT consultancy]. We help IT teams plan cloud migrations, especially when older applications need to stay running. I'm calling to see whether moving any of those applications is on your team's agenda, or whether you're keeping things as they are for now."
Buyer: "We've moved most of it. There's one application we haven't touched because the finance team still relies on it."
Caller: "What's holding that one back: the connection to the finance system, or finding a time when the team can afford the downtime?"
Now you have something to discuss. Ask what has to happen before they can make a decision. If it turns out to be a priority for next year, note that honestly. A discussion about a possible project next year isn't the same as a project the buyer needs help with now.
3. When you don't know who owns the problem
Situation: You help professional services firms improve project profitability reporting. You can see who heads finance and operations, but you don't know who owns the process.
Caller: "Hi Casey, it's Sam from [advisory firm]. We help professional services firms get a clearer view of margin while projects are still running. I'm calling to find out whether project margin reporting sits with your finance team or with the people running delivery."
Buyer: "Finance puts the numbers together, but delivery owns the process."
Caller: "Thanks, that helps. Is there a role on the delivery side that looks after it across the firm?"
The useful outcome here is a better account map. If Casey tells you the role, write it down. When you call that person, explain your own reason for reaching out. Don't say Casey referred you unless they actually did.
What to say when the buyer pushes back
| What you hear | A response you can use |
|---|---|
| "We've already got a provider." | If they're still engaged: "Understood. Is this work already covered by them, or do you handle it internally?" If they've signalled they want to finish, end the call. |
| "Send me something." | "Sure. Would a short example about stock transfers be useful, or is there something else you'd like to see?" Send what they asked for if you're permitted to follow up. A request for information doesn't make it a sales opportunity. |
| "I'm in the middle of something." | "Understood. I'll let you get back to it." If they offer a better time, use that. |
| "Not interested" or "Don't call again." | "Understood. Thanks for your time." End the call and record any request not to be contacted again. |
What to write before you dial
Keep four things in front of you: the fact you've checked, the possible problem, the first question, and the next step you'd suggest if there is a fit. Read the opener aloud. If you wouldn't say it to someone you just met, rewrite it in words you would actually use.
After the call, write down what the buyer confirmed, who owns it, whether there's a reason to act, and what they agreed to next. That's the information your team needs when it takes over a qualified conversation.
The script is one part of the setup. Check the ACMA's telemarketing guidance before calling, including requirements for identifying the caller and purpose and ending the call when requested. The Leadscaler guide to Australian cold calling rules covers the checks to make before running a campaign.
For the account research that goes into a good opener, read what to do before the first B2B cold call.
