Pavone
SIGN IN

SaaS Cold Call Script

Selling software to people who already buy software is a different sport. The buyer on the other end has sat through a hundred demos, has a tool for everything, and can smell a sequence-generated pitch in the first four words. This SaaS cold call script is built for that buyer: short, specific, and honest about why you are calling.

Want one built around your product? Use the Cold Call Script Generator.

Who you are calling

Your target is usually a VP or head of a function at a company between 50 and 2,000 people: VP Sales, Head of RevOps, Director of Customer Success, Head of Engineering, Head of People. They own a number, they own a budget line, and they own a stack of eight to twenty tools they inherited or bought themselves. They are in back-to-back Zoom calls from nine to five and check their phone between meetings, which is the only window you have.

This person gets more outbound than anyone else in the building. SDRs from every vendor in their category have their direct dial from the same data providers you use. They have heard 'we help companies like yours' and 'I noticed you are hiring' so many times that those phrases now trigger an instant hang-up. They have also been burned: they bought a tool on a confident pitch, spent three months on implementation, and the team never adopted it.

What they actually want to hear is that you understand the specific workflow that is broken, that you know what they are using today, and that you are not going to waste a thirty-minute slot on a generic demo. If you can name the tool they have and the gap in it, you have earned the next sentence.

The script

Opener

Hi [first name], it's [your name] at [your company]. You don't know me and this is a cold call, so I'll be upfront: I've got one question about how your team handles [workflow], and if the answer is 'it's fine', I'll let you go. Fair?

SaaS buyers hang up on fake familiarity. Naming the call as cold and offering an exit in the first sentence lowers their guard because it is the opposite of what the last ten SDRs did.

Reason for the call

The reason I'm calling you specifically is that [their company] is running [tool they use] for [workflow], and the teams we talk to on that setup usually hit a wall around [trigger: headcount, volume, second product line]. I wanted to check whether that's happening for you yet.

Naming their current tool proves you did the work. Naming a trigger makes the problem feel like a stage of growth rather than a criticism of their choices.

Value hook

What we do is [one-sentence description]. The reason teams switch is not features, it's that [specific outcome: reps stop updating the CRM by hand, onboarding drops from six weeks to two]. Most of the companies we work with ran [competitor or category] before and kept it for a year longer than they should have.

Lead with the outcome and the switch story, not the feature list. This buyer has seen your feature list on G2 already.

Qualifying question

Can I ask: when [workflow] breaks today, who feels it first, you or your team? And is fixing it something that's on the roadmap this quarter, or is it a next-year problem?

Two things you need to know on a SaaS call: whether the pain is personal to this buyer and whether there is a budget cycle attached. This asks both without sounding like a BANT checklist.

Handling the first pushback

Fair. You've got something in place and it's not on fire. I'm not asking you to rip it out. I'm asking whether [specific symptom] is costing your team a few hours a week, because if it is, that's the whole case and if it isn't, there's nothing for us to talk about.

The default pushback in SaaS is 'we already have a tool'. Agreeing with it and narrowing to one symptom keeps the call alive without arguing.

Close

Here's what I'd suggest. Give me 20 minutes next week, I'll show you exactly how a team on [their current tool] handled [problem], and you tell me whether it's relevant. If it's not, I'll say so first. I've got Tuesday at 10 or Thursday at 2. Which is worse for you?

SaaS buyers book meetings they can picture. Promise a specific walkthrough, name two times, and give them the easy out of picking the less bad one.

Objections you will hear in SaaS

"We already use a tool for that."

I'd expect you to. Can I ask which one? The reason I ask is that most of the teams we work with came off [competitor], and the thing that moved them wasn't a missing feature, it was [specific gap]. If that's not something you're seeing, then honestly you're in good shape and I'll leave you alone.

"Send me some information and I will look at it."

Happy to, and I will. So I don't send you a generic deck: is [workflow] actually a problem you'd fix this year if the right thing showed up, or is it more of a 'nice to know'? If it's the second one, I'll send a one-pager and not chase you.

"We just finished a procurement cycle and have no budget until next year."

Understood, and I'm not asking you to buy anything this quarter. What usually happens is that the teams who evaluate in Q3 are the ones who get it into the Q1 budget. Would it be worth a short look now so you have the numbers when planning starts, rather than scrambling in December?

"Our engineering team would have to approve any new tool."

That's normal and we build for it. Most of our customers had the same gate. What helps is that [integration or security detail: SOC 2, native CRM integration, no data leaves your tenant]. Would it make sense to have your engineering lead on the first call so you're not relaying questions back and forth?

Tips for calling SaaS buyers

  • Call between 8 and 9 in the morning or after 4:30 in the afternoon. SaaS leaders are in meetings all day; the edges of the day are when they pick up.
  • Know their stack before you dial. BuiltWith, job postings and their own case studies tell you what they run. Naming it in the first 20 seconds is the single biggest lift in connect-to-meeting rate.
  • Drop the words 'platform', 'solution', 'synergy' and 'all-in-one'. This buyer has read those words on five hundred landing pages. Describe what the product does in plain verbs.
  • Reference a trigger event: a funding round, a new VP, a hiring spike, a product launch. SaaS companies change fast, and a trigger makes the call feel timed rather than random.
  • Expect to be asked for pricing on the first call. Have a straight answer, including the range, instead of 'it depends'. Dodging the number reads as a red flag to someone who buys software for a living.
  • If you are calling mobile numbers in the US, make sure your list is scrubbed against the National DNC Registry and that you are not using an autodialer without consent. B2B calls to business lines are generally exempt, but cell numbers are not a safe assumption.

Mistakes to avoid

  • Pitching the product category instead of the gap. 'We're a revenue intelligence platform' means nothing; 'your reps are logging calls by hand' means something.
  • Running a feature tour on the phone. The call's only job is to earn 20 minutes of screen time; every feature you describe now is a reason they do not need the demo.
  • Asking 'who is the right person for this?' A VP who gets asked that will give you a junior name to get rid of you. Call the person who owns the number.
  • Using a trigger you did not verify. Congratulating someone on a funding round that happened two years ago ends the call.

Frequently asked questions

What is the best time to cold call SaaS companies?

Early morning, 8 to 9:30, and late afternoon after 4:30 in the prospect's time zone. Mid-day is wall-to-wall meetings for most software leaders. Tuesday through Thursday outperform Monday and Friday; Monday is planning and Friday is checkout.

How long should a SaaS cold call be?

Aim for three to five minutes if it goes well. The opener should be under ten seconds, the hook under thirty, and the rest is a conversation. If you are still talking at minute eight, you are running the demo on the phone and losing the reason for the meeting.

Should SDRs still cold call SaaS buyers in 2026?

Yes, because email reply rates to software buyers have collapsed under the volume of automated sequences. A short, well-researched call that names their current tool stands out precisely because almost nobody does it well. The phone is the channel with the least competition for attention.

Who should I cold call at a SaaS company?

The person who owns the outcome your product changes, not the person who would use it day to day. For a sales tool that is the VP Sales or Head of RevOps, not an AE. For a developer tool it is the engineering manager or Head of Platform. Users can champion, but they cannot sign.

How do I handle "we already have a tool" on a SaaS cold call?

Agree, ask which one, and then name the specific gap your customers hit on that tool. Never argue that yours is better; argue that one workflow is still broken. If they confirm the gap, you have the meeting. If they do not, thank them and move on.

More cold call scripts by industry

Start practicing in minutes

AI Roleplays for any scenario

  • Build a roleplay from your scenario
  • Practice with AI, voice to voice
  • Get instant, structured feedback after practice
  • Free to start — no credit card required