Operator vs Executive: The Same Product, Two Completely Different Conversations

A plant manager, a general superintendent and a claims supervisor are the same buyer. So are a CMIO, a COO and a managing partner. Not the same industry, not the same product, not the same words — but the same buyer, because they are accountable for the same shape of thing.

The first group is accountable for what happens Tuesday at 6am. The second group is accountable for a number they have to defend in a room they don't control.

If you run one script at both, you will win one of them and confuse the other. Usually you confuse the operator, because most sales training is written by people who have only ever sold up. Sometimes it goes the other way and you walk a COO through a workflow diagram until she politely says she'll loop in her director of operations, and then nothing ever happens again.

Here is what actually changes between the two conversations.

Title doesn't decide it. Accountability does.

Don't sort your contacts by seniority. Sort them by one question: when it breaks, how fast do you find out?

If the answer is "the shift lead calls me within ten minutes," you are talking to an operator, whatever their title says. Some VPs are operators. Some plant managers at large sites have been promoted out of the shift and are executives in everything but name.

If the answer is "I see it in a report the following month," you are talking to an executive. Their exposure to the problem is mediated. They experience it as a trend line and a conversation with someone above them.

That single distinction drives everything else — what proof they accept, how they say no, how long they'll sit with you, and whether you should meet them first or third.

The unit of proof: a shift versus a quarter

An operator's unit of proof is one shift, one crew, one workflow, one bad Tuesday. They will believe you if you can describe their worst morning back to them accurately and then show them where the tool sits inside it. They do not need it to work everywhere. They need it to work on their line, with their people, including the temp who started last week and the guy who refuses to use anything with a login.

An executive's unit of proof is a quarter, sometimes a fiscal year. They need a number they can say out loud to a board or a partner group without being embarrassed six months later. That means they care less about whether the thing works and more about whether the claim survives scrutiny. Where does the number come from? Who owns it? What has to be true for it to hold?

This is why "your guys are going to love it" lands flat with a COO, and why "reduces total cost of ownership across the portfolio" makes a superintendent stop listening. Neither statement is wrong. Both are measured in the wrong unit.

The practical version. With an operator, I open with time:

"Walk me through Tuesday. First shift hits the floor at six. What's the first thing that goes sideways?"

With an executive, I open with the room they have to defend the number in:

"Next time you have to explain field productivity to the board, what's the number you point at, and where does it come from today?"

Same product. Two entirely different first ninety seconds.

They say no in completely different ways

This is the part that costs reps the most, because one of the two nos looks like a yes.

Operators interrupt. You are eleven seconds into your framing and they cut in with "that won't work, our tags are in the truck." New reps hear hostility. It isn't. It's the single highest-signal thing that happens on a call. The operator is running your product against their real environment in their head, in real time, and telling you exactly where it snags. An operator who lets you finish your deck uninterrupted has already checked out and is being polite until the calendar releases them.

So you stop the deck. You go to the interruption. You ask what happens today when the tags are in the truck, who ends up retyping it, and what time that happens. I wrote out the full mechanics of running a demo when the buyer keeps cutting in over in the manufacturing demo script for plant managers who interrupt, because on the floor the interruptions are the meeting. There is no meeting underneath them.

Executives defer. "This is really interesting. Let me loop in Dave." "Send me something I can circulate." "Let's pick this up after planning." It is warm, it is complimentary, and nothing has happened. Polite deferral is the executive form of no, and it is designed to end the call without conflict, because executives spend their day avoiding unnecessary conflict.

You can't out-enthusiasm it. You have to convert it into either a decision or a clean disqualification:

"Happy to talk to Dave. Before I do — if Dave comes back and says this solves it, is that something you'd fund this fiscal year, or are we talking about next year's budget cycle? I'd rather know now so I bring him the right thing."

That question is not aggressive. It gives them an easy, dignified exit if the answer is no. Half the time you get "honestly, next year," and you have just saved yourself two months of pipeline theatre. The other half you get a real answer about the funding path, which is the thing you actually needed.

What counts as evidence

Operators want a workflow walkthrough in their nouns. Work order. Tag. Punch list. Shift handoff. Claim queue. Chart. If you use your product's internal vocabulary — "records," "objects," "entities" — you have told them you have never been in their building. Show the ugly path, not the happy path. What happens when the network drops in the back bay. What happens when someone with gloves on tries to sign something. What the screen looks like at 5:50am when nobody has had coffee.

Executives want a business case with its seams showing. Not a slick number — a number with a visible derivation. Where it comes from, what assumption it rests on, what happens if that assumption is half as good as claimed. Executives have been burned by vendor math, and the fastest way to earn credibility with one is to volunteer the weak point in your own case before they find it. "The savings depend entirely on whether your supervisors actually stop rebuilding the schedule by hand. If they don't, this is worth much less. That's the thing I'd want to test in the first sixty days."

The other executive evidence category is risk of being publicly wrong. Who else like us has done this? Did it blow up? What did they tell you afterward? An operator risks a bad shift. An executive risks their judgment being questioned in front of peers. Those are not the same fear and they don't respond to the same reassurance.

Meeting length and shape

Operator meetings are short, interrupted, and often happen somewhere loud. You'll get a phone call from a truck, or twenty-five minutes in a site trailer with two people walking in mid-sentence. Plan for it: no deck, no agenda slide, screen share only when they ask to see it. Get to a real question inside the first thirty seconds. The construction version of this — where you have to earn the right to the second question before you get to the third — is laid out in the discovery playbook for construction and trades, and the shape transfers cleanly to any environment where the buyer's day is measured in crews and hours.

Executive meetings are calm, scheduled, and start with the executive having read nothing you sent. That is not disrespect. It is triage. So don't spend the first five minutes on rapport and don't ask them to recall your email. Open with a one-sentence frame of why you asked for the time, then a question that assumes they are the expert. Getting that first block of time from a clinical executive is its own craft, which is why the healthcare cold call script for CMIOs and VPs of clinical operations spends most of its length on the ask rather than the pitch — with executives, the hard part is the meeting, not the meeting.

And when both are in the room, which happens constantly in mid-market: talk to the operator, look at the executive. Ask the operator the workflow question. Then turn to the executive and ask whether that matches what she sees in the numbers. Never let the executive answer the operator's questions — you will get the sanitized, board-ready version of the workflow, which is not the workflow.

Translating without inflating

Here is where reps get in trouble. You hear something real from an operator, you carry it upstairs, and somewhere on the stairs it grows a percentage sign. Then the executive asks where that came from, and you can't say, and you're finished.

The rule I use: keep the mechanism, change the unit, never add a number the operator didn't give you. Attribute everything. "Your superintendent in the east yard told me" is more powerful than any figure you could invent, because it's checkable and it proves you were there.

What the operator said	What the executive needs to hear	What will get you killed
"We rebuild the schedule every morning because half the crew calls out."	"Your morning schedule is rebuilt by hand daily. That's supervisor time going into rework instead of into the field."	"You're losing a fifth of your supervisor capacity."
"The tags are in the truck."	"Asset data lives on paper in the field and gets keyed in days late, so the register in your system trails reality."	"Your asset data is inaccurate at scale."
"I hear about a denial three weeks after the fact."	"Denials surface late in the appeal window, so recovery depends on how fast one supervisor happens to notice."	"You're leaving six figures on the table."
"Nobody reads the handoff log."	"Shift handoff is verbal and undocumented, so a quality issue can't be traced back to a shift."	"You have a serious safety exposure."

The right-hand column isn't wrong because it's dramatic. It's wrong because you can't source it. The middle column is defensible in every single case, because it's a description of a mechanism the executive can go verify in ten minutes by asking their own people.

It runs the other direction too, and reps are worse at this one. Executives speak in initiative language, and if you carry that language onto the floor you sound like corporate.

What the executive said	What the operator needs to hear
"We're standardizing on one system."	"You'd stop typing the same job number into two places."
"Margin compression in the service business."	"Your techs are doing callbacks nobody's paying for."
"Digital transformation on the front line."	"The tablet has to work with gloves on and no signal."
"Audit readiness."	"When the auditor asks who signed off, you don't have to call three people to find out."

When an operator hears the left column, they assume the tool is being done to them. When they hear the right column, they start telling you where it would break — which, as established, is them buying.

Who to meet first

Start wherever your product's value shows up first, not wherever your manager's territory plan says.

If the value lands inside a shift — fewer callbacks, a cleaner handoff, one less system to key into — start with the operator. Build the story with them, in their words, then go up with an internal sponsor who can say it themselves. An executive will believe an operator's description of the operator's own job. They will not believe yours.

If the value lands across a quarter — consolidation, licensing, compliance exposure, something that only shows up when you add all the sites together — start at the top. But get explicit permission to go talk to two operators before you write the business case. Otherwise you'll build a case on assumptions the floor will dismantle in the first pilot review.

One warning about starting at the top: being delegated down is not the same as being sponsored down. Delegated means the executive forwarded your email with "thoughts?" and has now stopped thinking about you. Sponsored means the intro carries an opinion and a date. Ask for it directly: "Would you introduce me to Dave and tell him you want a read from him by the end of the month?" If they won't put a date on it, you're delegated, and the deal is worth less than your CRM says.

This is also why the professional-services version of this looks different again. A managing partner is an executive and an operator simultaneously — she defends a number to her partners and she also has clients calling her at 7am — which is why the financial services discovery playbook for wealth management buyers has to switch registers mid-call rather than picking one.

The failure mode, plainly

Run the executive script at an operator and you get treated as overhead. Run the operator script at an executive and you get "send me something." In both cases the rep walks away from the call feeling fine, because neither buyer was rude. That is what makes this so expensive — the mismatch is invisible from inside the call.

The fix is not a better deck. It's being able to tell, inside the first minute, which of the two people you're on the phone with, and having the other opening ready to go.

What I'd do next

Pick the two hardest personas in your patch — one operator, one executive — and write the first ninety seconds for each. Not the whole call. Just the frame and the first question. Then practice them out loud, back to back, until switching between them is automatic, including the moment where the operator cuts you off at second eleven and the moment the executive says "let me loop in Dave." That's the drill I'd build if I were ramping today, and it's the reason we built DrillCall the way we did: you can run the plant manager who interrupts and the CMIO who politely defers on the same afternoon, and find out which one you've quietly been losing.