Outbound

Cold calling script generator for SaaS sales

By Charles Summers · Updated · Free, no signup

Short answer

SaaS cold calls usually clear a gatekeeper or a screening assistant before they reach a decision maker who has already fielded a dozen vendor pitches this month, which makes a permission-based opener a necessity rather than a style choice. This variant builds the same opener, hook, discovery ladder and objection response as the base tool, but the worked example and the framing below address the gatekeeper hand-off and the pitch fatigue a SaaS buyer specifically brings to the call.

Use the cold calling scriptwriter

Why SaaS sales need a different approach

A SaaS decision maker, especially a VP or director in a mid-sized company, rarely picks up their own phone, and when a call does connect it has often been screened by an assistant or routed past a switchboard first. That first thirty seconds is not really the pitch, it is the negotiation for permission to give the pitch, which is why naming the call as a cold call and asking for a specific small amount of time works better here than trying to sound like an expected call.

The second challenge is pitch fatigue rather than access: most SaaS buyers have taken several structurally identical calls this quarter, so a generic value statement blends into the last five they heard. The discovery ladder in this script is built to get the prospect describing their own process in their own words before you say anything about the product, since a specific answer to a specific question is harder to dismiss than a feature list.

It runs entirely in your browser. Nothing you type is sent to a server, no account is required, and there is no usage limit, because there is no cost per run to control.

What does the output look like?

This is the exact output the tool produces from the example inputs. It is generated by the same code that runs when you click the button, so what you see here is what you get.

COLD CALL SCRIPT: a revenue forecasting tool for RevOps teams -> VP of Sales OPENER Hi, [Your Name] here from [Your Company]. Quick one: is now a terrible time, or just a bad one? PERMISSION HOOK I will be direct: I am calling VP of Saless about a revenue forecasting tool for RevOps teams. If this is not relevant, just say so and I am gone in five seconds. DISCOVERY LADDER (ask in this order, do not skip a rung) 1. SITUATION: Walk me through how your team currently handles [the process a revenue forecasting tool for RevOps teams touches] today. 2. PROBLEM: What is the part of that process that takes longer than it should, or breaks the most? 3. IMPLICATION: If that stays broken for another two quarters, what actually happens to [the outcome it affects]? OBJECTION HANDLING (your top one, plus the two that usually follow it) 1. "I do not have time" [THE ONE YOU HEAR MOST] Framework: The 10-Second Permission Ask Say: I hear that a lot, which is exactly why I am not asking for ten minutes, I am asking for ten seconds: [one-sentence value statement about a revenue forecasting tool for RevOps teams]. If that is not relevant, tell me and I will let you go. Avoid: Do not say "this will only take a minute" and then talk for five. That is the fastest way to lose credibility for the rest of the call, including any follow-up. Context: VP of Sales hear this pitch often, so the response has to sound unlike the last five calls they took. 2. "Just send me an email" [commonly follows] Framework: The One-Line Email Test Say: Happy to. So it actually gets opened instead of buried, give me one line: what is the one thing that would make this worth five minutes of your time if I put it in the subject? Avoid: Do not agree and hang up without asking anything first. An unqualified email into a cold inbox gets close to a zero percent read rate, this question is the entire point of asking. 3. "Not interested" [commonly follows] Framework: Labeling (Chris Voss, mirror the objection back) Say: Fair enough, sounds like this is either not a priority right now, or something you have already tried to solve and it did not work. Which is it? Avoid: Do not argue or launch straight into a pitch. Reflecting the objection back as a question, not a rebuttal, is what gets people to explain the real reason, so you can respond to the actual objection instead of the brush-off. NOT COVERED HERE "We do not have budget for this", "We already have a vendor for this". Re-run with one of those selected to get the script for it. Three responses you can actually recall beat five you cannot. WHY THIS ORDER The situation question is low-effort and gets them talking. The problem question finds the crack. The implication question gets them to size the crack in their own words, which is far more persuasive than you sizing it for them. Your most common objection, "I do not have time", is first so it is the one you have freshest in your head when the call starts.

Frequently asked questions

How do you get a SaaS cold call past a gatekeeper?

Treat the gatekeeper as a person with their own judgement, not an obstacle to talk around. State who you are and why you are calling in one plain sentence, and ask a direct question such as who handles that decision, rather than trying to sound like an expected call. Gatekeepers route calls that sound honest more often than ones that sound scripted.

Why does a permission-based opener work better on a SaaS exec than a direct pitch?

Because most SaaS decision makers have already taken several near-identical cold calls this quarter and can recognise a scripted pitch within a few seconds. Naming the call as a cold call and asking for a specific, small amount of time is disarming precisely because it does not pretend otherwise, and it hands the prospect control, which a hard pitch does not.

Should you call the economic buyer or the day-to-day user first?

It depends on deal size and how the tool gets adopted. For a tool with a clear budget owner and a fast approval cycle, calling the economic buyer directly saves a step. For a tool that needs bottom-up adoption before it gets budget attention, the day-to-day user is often the faster path in, then you ask them who owns the budget conversation.

What discovery question actually lands with a SaaS buyer who has heard every pitch?

A question about their current process, asked before you say anything about your product. Buyers who have heard dozens of pitches can dismiss a value statement instantly, but describing their own workflow requires them to think, not just decline, and their own answer usually surfaces the exact problem your product solves without you having to claim it first.

Related free tools

Some links on this site are affiliate links, which means HackingDemand may earn a commission if you buy through them at no extra cost to you. This does not influence which tools are listed. The tools on this page are free and have no affiliate relationship of any kind.