A Cold Calling Script for B2B Services Firms, With Objection Replies

Your opener has three jobs: say who you are, show that you know something about them, and ask permission to continue. For example:

"Hi Dana, this is Sam from Northline Advisory. I know I'm calling out of the blue. Do you have a minute for me to say why I called, and you can tell me whether it's worth continuing?"

Then give the reason in one sentence, tied to something real, such as a role change, a hiring post, a product launch or an industry event: "I saw you're hiring three account managers, and firms at that point often find their handoff from sales to delivery gets messy."

Avoid asking "how are you today?" and avoid reading a long company description. Say who you are, why them and why now, then stop and let them respond.

Use this structure, and keep each part short:

1. Opener and permission: your name, company and a request for a minute.
2. Reason for the call: one sentence tied to the prospect's situation.
3. Qualifying question: an open question that tests whether the problem exists, such as "How do you handle X today?"
4. Listen and probe: follow up on what they say once or twice. Take notes in the fields you'll need afterward, like the discovery notes structure.
5. Bridge: if there's a fit, connect their words to what you do in one sentence.
6. Next step: ask for a specific short meeting, with a date, and confirm the invite.
7. Graceful exit: if there's no fit, thank them and ask whether it's okay to send a short note.

The aim is a next step, not a sale. A second call with a clear agenda is a good result from a cold call.

Expect four objections, and prepare a reply that acknowledges the concern, offers something specific and asks a small question. The objection handling scripts go further.

• "Send me an email." "Happy to. So I send something useful, what's the main thing you'd want it to cover?" This turns a brush-off into a discovery answer. If they still say nothing, send a short email and follow up.
• "We already have someone for that." "That makes sense. Most of the firms I talk to do. What would need to be true for you to look at a second option?"
• "Not interested." "Understood. Just so I don't waste your time again, is it the timing or the topic?"
• "I'm busy." "Of course. Would it be better if I called Thursday morning for five minutes?"

For questions about fees, use the pricing objection script and avoid quoting a price cold. Take no for an answer politely. It preserves your reputation and the option of a later approach.

Keep it under 25 seconds and make it easy to return. A workable voicemail has your name and company, a specific reason for the call, and one way to respond:

"Hi Dana, it's Sam from Northline Advisory. I'm calling because I saw your team is hiring, and I have a thought on keeping handoffs clean between sales and delivery. I'll send a short email with the idea. If it's useful, reply to it and we can talk for ten minutes."

Leave your number slowly and once. Then send the promised email straight away, so the voicemail and email reinforce each other. Look at email templates for professional services for the follow-up. Don't leave a voicemail every attempt, since repeated messages read as pressure.

Ten minutes of preparation per account is enough: the person's role, one recent trigger and your best guess at the problem. Batch calls in blocks of an hour or two, with notes ready and distractions off.

Log every call in the CRM with a disposition, such as connected, voicemail or wrong person, and a note on the objection or outcome. Review a sample of recordings or notes weekly. Where recording applies, follow the consent rules that cover your calls, and ask your attorney about them.

A phone tool like OpenPhone can give a team shared numbers and call history, and Close can combine calling with a CRM so calls log themselves, though you should confirm features and calling limits in a trial. See the phone tool comparison for options. Compare your call results with your email results too, using cold email reply rate benchmarks as context. Then change the opener or reason for calling one variable at a time, so you can tell what worked.