Cold Calling an Operator vs Cold Calling an Executive: Same Product, Different Proof

Two dials in the same hour. Same product, same one-pager, same rep. First call is a plant manager at a mid-size injection moulding shop. Second is a CRO at a software company. Both hang up inside twenty seconds. The rep logs both as "not interested," which is the wrong lesson, because those two calls failed for opposite reasons.

The plant manager hung up because you did not sound like you had ever stood on a floor. The CRO hung up because you took too long to say anything worth a minute of his time. One wanted depth. The other wanted density. Give the operator density and you sound like a brochure. Give the executive depth and you sound like you are stalling.

I have sold inside AWS and Dell and I have built and exited four businesses, and in every one of them the same rep would crush one of these calls and get flattened by the other. It is almost never a skill gap. It is that they only have one call in them, and they run it at everybody.

Here is the side-by-side.

The opener

What the operator hears

An operator — plant manager, SOC lead, warehouse supervisor, RevOps manager, support director — spends their whole day inside a process. They know the queue depth. They know which machine runs hot on second shift. They know the spreadsheet somebody built in 2019 that everything still depends on and nobody will touch.

When you call them, they are running a live silent audit: does this person know what I actually do all day, or did they get my title off a list?

That audit is over fast. First sentence, maybe two. And you cannot pass it with enthusiasm. You pass it by naming something specific enough that a vendor could not have guessed it.

Bad:

"Hi Dave, I'm calling from [company], we help manufacturers improve operational efficiency and reduce downtime. Do you have a couple of minutes?"

Every word in that is true of a hundred vendors. Dave has heard it this month. He has heard it this week.

Better:

"Dave, cold call — you can throw me off in twenty seconds. Reason I called: every plant manager I talk to who runs mixed lots on the same line ends up with a changeover log that lives in one person's head, and when that person is on holiday the line runs slow and nobody can say why. Is that a thing at your place, or have you got it nailed down?"

That is longer. On this call, longer is correct. You are not selling yet. You are paying an entry fee, and the currency is specificity. The moment Dave thinks this person has had this conversation before, you get your twenty minutes. I go through this in far more detail in the manufacturing cold call script, including how to talk about downtime without sounding like you are accusing him of running a sloppy plant.

Notice the last clause: "or have you got it nailed down?" You are giving him a way to be good at his job. Operators are proud. If your opener implies they are failing, you are done, regardless of how accurate you were.

What the executive hears

An executive is not auditing your domain knowledge. They assume you have some or you would not have got their number. They are auditing your cost. Every second on this call is a second not spent on the board deck, the pipeline review, or the person waiting outside their office.

So the CRO's silent question is: is there a number, a name, or a deadline in the next fifteen words, and if not can I go?

Bad on an exec call is the same opener that worked on Dave. Watch what happens:

"...every VP of Sales I talk to who runs a mixed motion — self-serve plus enterprise — ends up with a forecast process that lives in one person's head, and when that person is on holiday..."

By "self-serve plus enterprise" the CRO has decided you are describing your product's use case back at her. She does not need the setup. She lives the setup. What she needs is the punchline, immediately, with a proof point attached.

Better:

"Sarah, this is a cold call. Thirty seconds and you can tell me to go away. Two of your competitors moved their SDR ramp from twelve weeks to something under two months this year, and both did it by changing how reps rehearse rather than hiring more of them. If ramp is on your list for Q3, that's the conversation. If it isn't, I'll stop."

Density. A peer reference, a specific outcome, a timeframe that matches her planning cycle, and an explicit exit. If you have a real named account you can cite and you are allowed to cite it, use the name. Anonymous peer claims are worth much less than named ones and executives know the difference. The full version of this, including how to handle the "we already have a tool for that" reflex, is in the SaaS cold call script for CROs and RevOps leaders.

The structural difference is where the specificity sits. With the operator, specificity goes into the problem. With the executive, specificity goes into the outcome and who else got it.

What counts as proof

This is the part reps get most wrong, because they carry one proof kit and open it on every call.

The operator does not care about your logo slide. Telling a plant manager that three Fortune 500 manufacturers use you does not move him, because he suspects — often correctly — that a Fortune 500 plant has nothing in common with his. What moves him is you describing the workaround he built himself, before he tells you about it.

"Most of the shops I talk to have someone maintaining a spreadsheet that reconciles the MES export against what actually shipped. Usually it's one person and usually it takes them a few hours a week. Is that roughly your setup?"

If you are right, you have earned real conversation. That is proof for an operator: evidence that you have been inside enough environments like his to describe his unglamorous reality without being told. Case studies help only when they are about someone his size, in his process, with a detail in them that he recognises.

The executive accepts almost the opposite. She will not be impressed that you understand her workflow, because understanding her workflow is not her problem — she has people for the workflow. She wants evidence that a decision like this one has been made before by someone she respects and that it worked out. Peer names. Outcomes attached to a time period. A number she can repeat to her CFO without checking it.

And she will pressure-test it. If you say a peer cut ramp time, expect "from what to what, and over how long?" If you cannot answer that, the number you just quoted turns into a liability. My rule: never bring a number onto an exec call that you cannot defend two questions deep. A soft, defensible claim beats a sharp one that collapses.

Cybersecurity is where this split is most brutal, because the operator is technical and the executive is political. A SOC manager will test whether you know what alert volume actually looks like at 2am and whether you understand why their team ignores a particular detection rule. A CISO will test whether you understand board reporting, audit exposure and what happens to their job if this goes wrong. Same product, two entirely separate proof sets, and the cybersecurity cold call script breaks down how to carry both without blending them into mush.

The pause each will tolerate

Ask a plant manager a good question and then say nothing. He will think. He may take several seconds. Floor people are used to silence — their environment is loud, conversations are short, and nobody expects instant answers. If you fill that pause, you have interrupted him building the case for you in his own head. Let it sit. Some of the best manufacturing calls I have been on had gaps in them long enough to feel like a dropped connection.

Do that to a CRO and you lose the call. Executive conversation is fast, overlapping, and impatient. Two seconds of dead air reads as unpreparedness. She will fill it herself, usually with "look, what is this about?" — and now you are answering her agenda instead of running yours.

So on exec calls, ask shorter questions with narrower answers, and be ready to move the instant she stops talking. On operator calls, ask wider questions and shut up.

This is also why the same rep sounds nervous on one call and pushy on the other. Their pacing is fixed. Pacing has to be a variable.

What "send me some info" means

Both will say it. It means two different things.

From an operator, "send me something" is often genuine and often useless. He is interested, he does not own budget, and forwarding your email to his boss is the only move available to him. If you just send a deck, the deck goes into an inbox that will never open it, and your deal dies in someone else's outbox.

So when Dave says send me info, I do not argue. I make the send conditional and specific:

"Happy to. So I send the right thing — if this went anywhere at your place, would it be you deciding or would it be whoever owns the capex line? I'll write it for whichever one of you has to read it."

That question is not a qualifying trick, it is a favour. He now tells you who signs, and you have permission to build a document he can forward without embarrassment.

From an executive, "send me some info" is usually a polite ending. She is not going to read it. She said it because it is faster than saying no and she does not want a debate. Treating it as a buying signal wastes weeks.

The response I use:

"I will, but honestly, the info is boring. What's not boring is fifteen minutes where I show you what the two of them changed. If that's not worth fifteen minutes, tell me and I'll stop calling — I won't be offended."

Sometimes she says no. Good. A clean no from an executive in week one is worth more than a maybe you chase until March. Sometimes she takes the fifteen. Either way you learned something real, which is more than the deck would have got you.

Which one you call first

The honest answer: call whoever is closest to the money in that industry, and that is not the same industry to industry.

In manufacturing, the operator usually goes first. Plant managers frequently control real spend, and even when they do not, nothing gets bought without their blessing. A plant manager who says "this would save my team a day a week" is a stronger internal advocate than an operations VP who was sold to over his head. Go around a plant manager and you will find out what quiet sabotage looks like.

In SaaS, particularly for anything touching revenue process, the executive usually goes first. Budget sits at CRO or VP level, the operator layer is often newer and less tenured, and a RevOps manager can love you for a quarter without anything happening. You still want the operator — but as validation after the exec has expressed interest, not as your entry point.

In cyber, it depends entirely on deal size. Anything that lands inside the SOC's daily workflow, start with the SOC lead, because a CISO who buys a tool their analysts hate has bought a shelf ornament and knows it. Anything that hits compliance, insurance or board reporting, start at the top.

The test I use when I do not know an industry well: ask on the first discovery call, out loud, "when something like this gets bought here, does it come out of your budget or does it go up?" Reps are weirdly shy about that question. Nobody has ever been offended by it.

The bridge: turning an operator conversation into an exec meeting

This is the move that separates reps who work the top of the org from reps who accumulate friendly practitioners who never buy anything.

The wrong version is going around your contact. You have a great call with Dave, you find his VP on LinkedIn, you email her citing the conversation, and Dave finds out. Now you have an internal enemy who will bury you and never tell you why.

The right version is asking Dave to come with you.

At the end of a good operator call, once you have something concrete — a real problem he described in his own words — I say some version of this:

"Dave, this has been useful. Here's what usually happens next. I put together twenty minutes for you and whoever owns the budget line, and I show what this looks like specifically at a plant your size. You don't have to sell anything in that meeting — I'll do the talking, you tell them whether I've described your job accurately or not. Does that work, and who should be in the room?"

Three things are happening there. You have made the exec meeting his idea to permit rather than yours to steal. You have given him a role that is low-risk — he is not championing, he is fact-checking — and you have asked for the name in a way that is procedural rather than nosy.

Then the crucial part: when the exec joins, you run the executive call, not the operator call. Reps blow this constantly. They get in the room, they are comfortable with Dave, so they run twenty minutes of shop-floor detail while the VP checks her phone. Open with the outcome and the peer name, exactly as you would have on a cold dial, then use Dave as your proof: "Dave described the changeover log situation to me last week — Dave, is that fair?"

Now your operator's domain knowledge and your executive framing are in the same room, doing different jobs. That is the whole point. You never had to choose which call to run. You ran both, in sequence, to the right person each time.

The habit underneath all of it

Everything above collapses into one discipline: decide who you are talking to before the phone rings, and change your pacing, your proof and your ask accordingly. Not your product — your product does not change. Your evidence changes.

Most reps I have watched cannot do this cold because they have only ever practised one version of the call, usually on live prospects. That is an expensive place to learn. If I were building this skill now, I would take my three most common titles, write the opener and the two hardest objections for each, and rehearse them as three separate calls until switching between them felt automatic. That is exactly what we built DrillCall for — you pick the persona, the AI pushes back the way that persona actually pushes back, and you find out on a Tuesday afternoon rather than on the dial that matters.

Dave and Sarah are not the same call. Stop running them like they are.