B2B SaaS cold call scripts for SDRs who want a second conversation
Mid-market department heads get cold calls, emails, and LinkedIn messages from software vendors every week, and most of them sound the same. The calls that land are built around a specific problem in that person's function, not a product tour, and they ask for a short, clearly defined next meeting. You're rarely talking to the only decision maker, so part of the job is learning how they buy, not just whether they're interested.
Who you're calling
Heads of department (VPs and directors of sales, marketing, finance, operations, HR, or IT) at mid-market companies. They care about hitting their team's goals, keeping their tool stack manageable, and not being the person blamed for a failed rollout. They're tired of 'Did you get my email?', 15-minute demos that run 45, and reps who clearly haven't looked at their company before calling.
Work it out from your own connect and meeting rates with the free cold call calculator.
Script 1
Trigger-based call
Use when: You've spotted a specific signal, like a wave of job posts, a new leader, or an expansion, that suggests the problem you solve is growing.
- You
Hi [Name], this is [Your Name] from [Company]. This is a cold call. Can I take 30 seconds to tell you why I called, and then you decide if it's worth continuing?
- Prospect
You've got 30 seconds.
- You
Thanks. I saw [Prospect Company] is hiring [Number] [Role]s right now. When [Role] teams grow that quickly, [Specific Problem, e.g. onboarding takes longer and the enablement team gets stretched] tends to show up. Is that happening for you, or is it under control?
- Prospect
Onboarding is a pain, sure. But we have a process.
- You
Makes sense. Roughly, what does that process look like from day one to someone being fully productive?
- Prospect
About two months. A lot of shadowing, and our enablement person runs sessions.
- You
And with [Number] new people coming in, can your enablement person keep up, or is that where it starts to stretch?
- Prospect
Honestly, she's stretched. But we're not looking at new tools this quarter.
- You
Fair. I'm not asking you to buy anything this quarter. Would 20 minutes be worth it to see how other [Department] teams have approached that ramp, so you have options when you do plan for it? If it's not relevant, you can tell me on the call.
- Prospect
Maybe. Send me something first.
- You
Happy to. So it isn't a generic deck, I'll send a one-page example specific to [Department] onboarding. Can we hold a tentative 20 minutes on Thursday at 2? If the one-pager doesn't look relevant, just decline the invite.
- Prospect
Okay. Thursday at 2, tentatively.
Script 2
New leader in role
Use when: The prospect started a leadership role in the last few months and is likely reviewing their team's tools and processes.
- You
Hi [Name], it's [Your Name] with [Company]. I saw you joined [Prospect Company] as head of [Department] a couple of months ago, congrats. I'm calling cold, so I'll be quick. Is now a terrible time?
- Prospect
It's not great. What's this about?
- You
Understood. New [Department] leaders often spend their first few months deciding what to keep and what to change. We help with [Outcome, e.g. pipeline reporting]. Is that on your list of things to fix, or is it working fine?
- Prospect
It's on the list, but it's not number one. I'm still figuring out the team.
- You
That's fair. What is number one right now?
- Prospect
Getting forecasting into decent shape before the board meeting.
- You
Okay. Does the forecast pull from [System, e.g. your CRM], or is it pieced together in spreadsheets?
- Prospect
Spreadsheets, mostly. Which is part of the problem.
- You
That's the kind of situation we get brought into. I don't want to pitch you on a call you didn't plan for. Could I get 25 minutes in the next couple of weeks to understand how the forecast gets built today? If we're not a fit, I'll tell you, and you'll at least have an outside view.
- Prospect
We already have a tool for that. It's just not set up right.
- You
That's useful to know, and sometimes the right answer is fixing what you have. I'm happy to look at it from that angle. Who else would want a say in how the forecast gets built?
- Prospect
Our RevOps lead, probably.
- You
Then it makes sense to include them. Would Tuesday or Wednesday afternoon next week work better for the two of you?
- Prospect
Wednesday afternoon. I'll forward the invite to her.
Script 3
Competitor user
Use when: You know from job posts, their website, or technology data that the prospect's team already uses a competing tool.
- You
Hi [Name], [Your Name] from [Company]. I'll be upfront, this is a cold call. Do you have a minute, or should I try another time?
- Prospect
A minute. Go.
- You
I noticed your team uses [Competitor]. I'm not calling to tell you it's bad. Teams usually look at us for one specific reason: [Differentiator, e.g. reporting across multiple regions]. Is that something your team runs into, or does [Competitor] cover it?
- Prospect
We're happy with [Competitor]. We just renewed.
- You
Good to hear, and I won't try to talk you out of a contract you just signed. When would you realistically revisit it?
- Prospect
Probably next spring, before the renewal.
- You
That helps. Out of curiosity, if you could change one thing about how it works today, what would it be?
- Prospect
The reporting. My team still exports everything to build the monthly review.
- You
That's a useful detail. Here's a low-key idea: I'll send a short comparison of how reporting works in each tool, focused only on that monthly review. Then I'll check back in early [Month], ahead of your renewal planning. Fair?
- Prospect
Sure, that's fine. Send it to my work email.
- You
Will do. I'll keep it to one page and set a reminder to reach out in [Month]. Thanks, [Name].
- Prospect
Thanks.
Voicemail script
Hi [Name], it's [Your Name] from [Company]. I'm calling because I saw [Trigger, e.g. your team is hiring several new reps], and [Department] leaders in that spot often run into [Problem]. I have an idea about that I'd like to run by you. I'll send a short email with the details so you can just reply if it's useful. My number is [Phone]. Again, [Your Name], [Company], [Phone].
When someone else answers
Treat the assistant as a partner, not an obstacle: 'Hi, this is [Your Name] with [Company]. I'm trying to reach [Name] about [specific topic, e.g. how the team onboards new hires]. Are you the right person to help me find a time, or is there a better way to get on their calendar?' If they ask whether it's a sales call, say yes. Ask what [Name] is focused on right now and whether someone else on the team owns this area.
B2B SaaS objections and responses
- "Just send me an email."
- Happy to. So I don't send something generic, what would make it worth reading: how it works, what it costs, or how teams like yours use it? And if it looks relevant, can we pencil in 15 minutes to talk it through?
- "We don't have budget."
- Understood. Most teams don't have budget sitting around for something they haven't planned. When does planning for next year happen? If this is worth solving, I'd rather help you build the case before then than call after it's set.
- "We built something in-house."
- That makes sense for teams with strong ops people. How much time does your team spend maintaining it? If it's working and cheap to keep up, stick with it. If someone's spending a big part of their week on it, a comparison might be worth 20 minutes.
- "I'm not the right person."
- Thanks for telling me. Who usually owns decisions about [Area]? And would you mind if I mention we spoke, or would you rather I reach out without using your name?
- "We're happy with our current vendor."
- Good, that's the best place to be. I'm not asking you to switch. When does that contract usually come up for review? I'd like to send something useful before then, so you have a comparison when you need one.
More responses in the objection library.
Tips for this industry
- Research one specific signal before you dial: a job post, a new leader, a funding round, or a product launch. One concrete reason beats three generic ones.
- Pitch the problem, not the product. Department heads respond to 'Is X happening for you?' more readily than 'We do Y.'
- Ask how they buy early. A question like 'Who else would weigh in on something like this?' saves you from booking a meeting that goes nowhere.
- Make the meeting small and specific: a stated length, a stated topic, and an easy way out. 'Twenty minutes on your onboarding ramp' is easier to accept than 'a quick demo.'
- Keep separate discovery questions for each persona. A VP of sales and a finance director care about different problems, even when they would buy the same product.
- Drill your opener and your top three objections with AI roleplay before a calling block. Vonvo scores each practice call with feedback, so you can see whether you're asking questions or just pitching.
Questions
What's the best time to cold call B2B decision makers?
Early morning before meetings start and late afternoon as the day winds down are often easier windows, because department heads tend to spend the middle of the day in back-to-back calls. Calendars vary by role and company, so test a few time blocks and track your own connect rates.
Should I tell prospects it is a cold call?
Saying so up front often lowers the prospect's guard, because it's honest and acknowledges the interruption. Whether or not you say it, be clear about who you are and why you're calling within the first few seconds.
How long should a B2B SaaS cold call be?
Long enough to confirm a real problem and agree on a next step, which is often just a few minutes. If the conversation is going well, it's fine to keep talking, but ask permission before stretching a call they didn't plan for.
What should the goal of a SaaS cold call be?
Usually a short, specific meeting with the right person, not a sale. Sometimes the best outcome is a referral to the right colleague or permission to follow up at a better time, like before their renewal.
Make the script sound like you
Practice it against AI prospects until it flows. 250 free credits, about 25 minutes of practice, no card.