Cold calling an IT or engineering leader is a different sport. They screen hard, they already run an incumbent tool for whatever you sell, and they can spot a scripted pitch from the first syllable. This script is built for that buyer. You get an honest opener that respects their time, a value prop about outcomes instead of features, and rebuttals to the walls IT throws up: "we already use [incumbent]," "it's not in the budget this year," and "send it to security."
Steal this, swap in your details, and read it out loud a few times. Then go run it live. Reading a script and pulling it off on a real call are two different skills.
Hi, is this [First Name]? Hey [First Name], this is [Your Name] from [Company]. I'll be straight with you, this is a cold call, so I'll keep it to 30 seconds and you can tell me to buzz off. We work with IT teams on [problem area], and I had a specific reason for calling your team and not just anyone. Is now a terrible time, or can I give you the 30 seconds?
We help IT and engineering teams that are already running something for [category] but are hitting a wall on [specific pain, like cost at scale, an integration gap, or manual work their team eats]. I'm not calling to rip out what you have. I'm calling because teams your size usually don't realize how much [that gap] is costing them until someone shows them the number. That's really all I want, to see if that number is worth 15 minutes of your time.
“We already use [incumbent].”
Good, honestly most of the teams we work best with are already on [incumbent]. I'm not here to tell you it's bad; it's a solid tool. The teams that talk to us usually hit one specific wall with it, like [scaling cost, a missing integration, the manual work around X]. Is any of that familiar, or has [incumbent] genuinely handled all of it for you?
“It's not in the budget this year.”
Completely fair, and I'd rather not push you toward something you can't buy this cycle. Two things: first, when does budget planning for next cycle actually happen for your team? And second, most teams we talk to find the gap we're describing is already costing them real money now, it's just buried in engineering time. If I could quantify that, would it be worth being on your radar for the next cycle?
“Send it to security / it has to go through procurement.”
That's exactly the right instinct, and we go through security review with almost every customer. I can send our SOC 2 report and architecture docs so you're not chasing them later. Quick question so I send the right thing: is security a formal gate you'd only trigger once you're interested, or is this your polite way of saying it's not a fit? Either answer is totally fine.
“Just email me some information.”
Happy to, but a generic deck usually dies in an inbox, and I don't want to waste your time. So I send something actually relevant: is the thing you'd care about more the [integration/security/scaling] side, or the cost side? I'll send exactly that plus a short technical one-pager, and follow up next week. What's the best email?
Hi [First Name], it's [Your Name] from [Company]. I work with IT teams running [category] who are hitting a wall on [specific pain], and I had a specific reason for calling yours. Not a mass pitch. If it's worth a quick look, I'm at [Number]. Again, [Your Name], [Number]. I'll also send a short note by email. Thanks [First Name].
Here's what I'd suggest: let me get 15 minutes with you and whoever owns [category] technically, and I'll come with a specific breakdown of where [incumbent] is likely costing you time or money, not a generic demo. If there's nothing there, I'll say so and you've lost 15 minutes. Does later this week work, or is early next week cleaner? And what's the best email for the invite and the security docs?
IT rarely has an empty category. Your first job is to find the specific gap or cost in the incumbent they've quietly been living with, without trashing a tool they chose.
"Send it to security" or "go through procurement" is often a polite brush-off. Qualify whether it's a real process step or a stall, and give the champion a reason to spend political capital.
"Not in this year's budget" is frequently true, not an excuse. Get on the roadmap for the next cycle and quantify the cost of waiting instead of pushing for a purchase that can't happen.
A software buyer discounts anyone who can't talk specifics like integrations, deployment model, and what breaks at scale. Vague "we help teams be more productive" language gets you filed under vendor spam instantly.
The script above is a starting point. Drop in what you actually sell and get a software sales script written around your own offer, free, on this page.
Be honest that it's a cold call, ask for 30 seconds, and signal you know their world: that they already run an incumbent and that you're calling about a specific gap, not to sell them a category they already own. Technical buyers respect directness and specificity far more than a polished pitch.
Agree and don't trash their choice. Most of your best-fit customers already run the incumbent. Then reframe to the specific wall teams usually hit with it (scaling cost, a missing integration, manual workarounds) and ask if that's familiar. You're finding the gap, not attacking their decision.
Treat it as real, not an excuse. Ask when the next budget cycle is planned and offer to quantify what the gap is costing them right now in engineering time, a cost that already exists whether or not there's line-item budget. The goal is to get on the roadmap for the next cycle, not force a purchase that can't happen.
Welcome it, because security review happens on almost every enterprise software deal. Offer your SOC 2 report and architecture docs proactively. Then qualify gently: ask whether security is a formal gate they'd trigger once interested, or a polite way of saying it's not a fit. Both answers help you decide where to spend effort.
Yes, when the rep can talk specifics and handle the three IT walls: incumbent, budget, and security/procurement. Technical buyers tune out vague pitches instantly, so the win comes from drilling objection handling until the rebuttals sound like a peer talking shop, which is exactly what live practice is for.
The best reps practice before they dial. Make your first AI cold call in 2 minutes.