A good SaaS cold call script wins the first 30 seconds with three moves: ask permission to keep talking, give a specific reason you called this company, and name one problem people in the prospect's role usually live with. Then it asks one question and requests a short meeting, not a purchase. The objections that follow, like "we already use a tool for that" or "send me an email," are mostly polite ways to end the call, and each has a calm, honest answer that keeps it open.
Below is the script line by line, a full sample call, and word-for-word responses to the eight objections SDRs and AEs hear most when cold calling businesses about software.
Why SaaS cold calls are different
Selling software to a business is not like selling a single product to a single person. The person you reach often did not choose the current tool, may not own the budget, and has been called by a dozen vendors this month. They also have a stack of tools already, so "we already have something" is close to automatic.
That means your call has a narrower goal than most. You are not selling the product on the phone. You are earning a 20 or 30 minute conversation with the right person, where a demo or discovery call can do the real work. The general mechanics of a cold open are covered in cold calling scripts that book meetings. This post is the software version.
The first 30 seconds, line by line
Seconds 0 to 5: the permission-based opener
Say who you are, admit it is a cold call, and ask for a small slice of time. Honesty about the interruption lowers their guard more than any clever hook.
"Hi [name], this is [your name] with [company]. This is a cold call, so I'll be quick. Can I take 30 seconds to tell you why I called, and you can decide if it's worth another minute?"
Most people say "sure" or "go ahead" because you asked instead of barreling through. If they say "I'm busy," respect it: "Totally fair. Is there a better time this week, or should I just send two lines by email?"
Seconds 5 to 15: the reason for this call
Give a specific reason you called this company, today. A trigger beats a generic pitch every time.
"I'm calling because I saw you're hiring [two more support reps / a revenue operations manager], and teams usually call us right around that point."
Good triggers for software calls: a job posting, a new office or market, a recent funding announcement on their own site, a new leader in the role, or a product launch. If you have no trigger, use their role: "I talk to a lot of [role] at companies your size."
Seconds 15 to 30: one relevant problem
Name a problem, not your product. Phrase it as something peers say, so they can agree or correct you without feeling sold.
"When [support] teams grow that fast, the thing I hear most is that [tickets get routed by hand and the same questions get answered five different ways]. Is that anywhere close to what you're seeing, or is that not an issue for you?"
The question at the end matters. It hands them control and invites a real answer. A "no, not really" is useful too, because it tells you to try a second problem or end the call politely.
One discovery question, then the meeting
If they engage, ask one question that deepens the problem, then ask for the meeting. Do not demo on a cold call.
- "How are you handling that today?"
- "What happens when it goes wrong, who feels it?"
- "If you could fix one part of it this quarter, which part?"
Then: "That's exactly what we help with, and it's worth more than a hallway pitch. Can we grab 25 minutes this week so I can show you how teams like yours handle it? I have Tuesday at 2 or Wednesday at 10."
Offer two specific times. "When are you free?" invites "I'll let you know," and that usually means never.
The full SaaS cold call script, start to finish
Here is the whole call, with the pushback where it usually lands. Bracketed pieces are yours.
You: Hi [name], this is [your name] with [company]. This is a cold call, so I'll be quick. Can I take 30 seconds to tell you why I called, and you decide if it's worth another minute?
Prospect: Okay, go ahead.
You: I saw you're hiring three more support reps. Teams usually call us right around that point, because the same questions start getting answered five different ways and routing turns into a full-time job. Is that anywhere close, or not an issue for you?
Prospect: We already use a tool for that.
You: Makes sense, almost everyone does. I'm not calling to rip it out. Out of curiosity, what's the one thing it doesn't do that you wish it did?
Prospect: Honestly, reporting. I spend Friday afternoons building it by hand.
You: That's the most common one I hear. How long does that take you each week?
Prospect: A couple of hours. Look, just send me an email.
You: Happy to. So it's useful and not another generic deck, I'll send a two-minute example of the weekly report other support leads use, built for a team your size. If it looks relevant, can we hold 25 minutes Thursday at 10 to walk through it? If it's not, reply "no" and I'll leave you alone.
Prospect: Fine, Thursday at 10. But I don't sign off on budget for this.
You: Good to know. Who usually weighs in on a tool like this, and would it make sense to include them Thursday or keep it to the two of us first?
Prospect: Keep it to us. If it's good, I'll bring my director in.
You: Perfect. Sending the invite and the example now. Thanks for the minute.
The call never pitched features, never argued with the current tool, and ended with a calendar invite and a next step that includes the budget owner.
The objections, with word-for-word responses
1. "We already use a tool for that."
This is the most common one, and it is rarely a dead end. Do not attack their current tool. Look for the gap.
"That makes sense, most teams your size have something in place. I'm not asking you to replace it. What's the one thing it doesn't do well that you've had to work around?"
The broader playbook for incumbents is in handling "we already have someone".
2. "Not interested."
Said in the first ten seconds, it is a reflex, not a decision. Acknowledge it and ask one low-pressure question.
"Fair enough, and I'll let you go. Can I ask, is it that [the problem] isn't a priority right now, or just that the timing of my call is bad?"
If the answer is "it's just not a priority," accept it: "Got it. Mind if I check back in six months in case that changes?"
3. "Send me an email."
Sometimes it is real, often it is the exit. Agree, then make the email specific and tie it to a time.
"Happy to. So I don't send you something generic, what would make it worth reading, the cost side or how it works day to day? I'll send that, and can we pencil 20 minutes Thursday to go over it? You can always cancel."
More on this stall in the "leave me some information" objection.
4. "We don't have budget."
Budgets get made for problems that are expensive enough. Do not push for money on a cold call. Find out whether the problem is worth solving.
"Understood, and I'm not asking you to buy anything today. Is it that there's no budget this year, or that this problem hasn't been big enough to justify any? If it's the second, a short conversation would at least tell you what it's costing you."
5. "I'm not the right person."
Thank them, then ask for a name. People will usually point you in the right direction if you make it easy.
"Thanks for telling me. Who would usually own a decision about [area]? And is it okay if I tell them you suggested I reach out, or would you rather I didn't mention you?"
Asking permission to use their name is respectful, and it often gets you a warmer intro than a blind call.
6. "Call me next quarter."
Sometimes timing is real, like a budget cycle or a current contract. Get the reason and a date.
"Happy to. What's happening between now and then, a renewal on your current tool, a budget cycle, something else? I'll put a call on the calendar for [specific week]. Is there anything you'd want me to have ready by then?"
If there is a renewal coming, ask when it is. Calling before a contract renews is far more useful than calling after.
7. "How did you get my number?"
Answer it plainly. Never dodge.
"Fair question. It came from [a business contact database / your company's public site]. If you'd rather I not call again, I'll take you off my list right now."
8. "We built something in-house."
Do not tell them their tool is bad. Ask about the cost of keeping it running.
"That's impressive, and a lot of teams start there. Who maintains it today, and is that the best use of their time? Some teams keep their own tool, and some move off it once upkeep starts pulling engineers from the product."
Three mistakes that kill SaaS cold calls
- Pitching features in the first 30 seconds. Nobody can evaluate a feature list on a surprise call. Lead with their problem.
- Asking "is now a good time?" with no reason attached. It invites an easy "no." Ask for 30 seconds and give a reason.
- Ending without a specific next step. "I'll follow up" is not a next step. A calendar time is.
How to practice the script out loud
You can memorize every line above and still freeze when a prospect says "not interested" before you finish your name. The answers only become natural after you have said them out loud many times, under some pressure.
Practice with a teammate, swapping who plays the prospect, or use a voice practice buyer. ColdOpen builds a practice buyer from your own company's website, so the pushback sounds like your actual market, and each call is scored on your opening hook, rapport, discovery, objection handling, value clarity, and securing the next step. Donna, the Busy Brush-Off, is good practice for the "send me an email" and "not interested" exits that end most cold calls early. You can try it on the 10-minute free trial.
