Manufacturing · Warm Call
Warm Call Script for Manufacturing: Cashing a Referral With a Plant Manager Before the 7am Production Meeting
A warm call into a plant is a strange animal. The plant manager picked up because Ray from the sister plant told him to, but he picked up standing next to line 3 with a headset on, twenty minutes after a press went down on second shift and eleven minutes before he has to explain the throughput miss to the group VP. He can name Ray. He cannot name what you sell. And if your first two sentences are "so let me give you a bit of background on us," you have just converted borrowed credibility into a cold call he now feels slightly embarrassed to be on.
What the referral buys you is the pickup, roughly ninety seconds of suspended disbelief, and a permission slip to be direct. It does not buy you a problem. Ray's plant runs three shifts of stamping with a 22-week gearbox lead time; this guy runs injection molding with a full spares crib and a CMMS he actually likes. Transplanting Ray's pain onto him — "Ray was drowning in unplanned downtime so I imagine you are too" — is the single fastest way to tell a plant manager you did no work on him specifically. He'll be polite. He'll ask you to send something over. That's the funeral.
The job on this call is narrow: cash the referral in twenty-five seconds, bridge to one specific, testable reason you might matter to his constraint, ask three real questions about how the work actually gets done on his floor, and leave with a date, a length, and the maintenance manager's name on the invite. Everything below is written to be said out loud, in their language, with the numbers a plant manager already has on the board by the door — unplanned downtime hours by asset, OEE on the constraint, planned versus reactive work orders, customer PPM.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: write the provenance line (do this before you dial)
One sentence, out loud, small and checkable: "[Referrer] mentioned you because [specific reason]." Good: "Ray Delgado pulled down our downtime-baseline worksheet last month and said you'd taken over Bowling Green in January after the consolidation." Dead: "Ray thought you'd be interested in what we do." Also pre-decide three things: 1. **Exactly what Ray said, word for word.** If he said "you should call Marcus," you say that. Never inflate it to "Ray said you'd really want to see this" — plant managers in the same corporate group talk on Monday morning ops calls and you will get caught inside a week. 2. **Your relevance hypothesis about their plant, not Ray's.** Built from something real: a new program launch, a PPAP submission on the website, a job ad running four months for a maintenance tech or CNC machinist, an acquisition, a customer they just added. 3. **The 15-second re-brief**, assuming the intro email was skimmed on a phone and archived. It should contain zero product language.
- 2
The open — name, provenance, permission (25 seconds, no deviation)
"Marcus — Dani Cortez, from Harlow. Ray Delgado said I should call you. He grabbed our downtime-baseline worksheet a few weeks back and mentioned you'd picked up Bowling Green in January when they folded the two plants together. He may have been overselling my usefulness. Have you got four minutes for me to find out whether that's true, or is now a bad time — I know what a Tuesday morning looks like." If he says "yeah, Ray said you'd call" — that is the entire warmth budget landing in your hand. Do not spend it asking how they know each other. Five words and move: "Good, he said he would. Then I'll be quick."
- 3
If they can't place the referrer
Don't argue them into remembering it. It was a two-line intro on a Friday. "No reason you would — it was a two-liner and you've got a plant to run. Short version: I work with maintenance and ops teams on the gap between the downtime code on the work order and what actually broke. Ray thought you'd have a view. Worth four minutes or not really?" Notice: no product, no company overview, no "we're a leading provider of." Just the shape of the problem in their words, and an exit ramp offered voluntarily.
- 4
The relevance bridge — the move the call lives or dies on
Structure: what the referrer's plant looked like → the specific difference at *your* plant → a question that hands them control. "What Ray was dealing with was one 40-year-old transfer press that everything routes through, and a 22-week lead time on the gearbox, so every unplanned failure turned into a Saturday and an air-freight charge on his controllable spend. That's his shop, not yours. You're molding, you've got redundancy across most of the presses, and from the outside your constraint looks more like the assembly cell than any one machine. So I genuinely don't know whether this lands with you. Where do your unplanned downtime hours actually pile up month to month — is it one asset or is it spread?" Why this works: it proves you looked at *his* plant, and naming a reason you might be irrelevant is the fastest credibility move available on a warm call. It also disarms the brace for the pitch that every plant manager holds when a vendor gets through.
- 5
Discovery — three questions, four maximum
This is not a booked discovery call. Three questions, then close. More than four and it reads as an abuse of the referral. **1. Current state, mechanical.** "When line 3 goes down at 11pm on second shift, who actually decides what happened? Does the tech's write-up on the work order tell you anything, or is it three words and a 'mechanical' downtime code?" **2. Cost in their numbers.** "What's OEE running on that cell — and is the availability loss the thing dragging it, or is it changeover and short stops? And roughly what does a shutdown hour cost you there? You'd have that number for the constraint even if you don't for the rest." **3. Priority test.** "Is that a this-quarter problem or a live-with-it problem? Because if it's on next year's AR I'd rather help you build the number now than pitch you something you can't buy until October." **Optional fourth:** "Besides you, who'd care about this — is that your maintenance manager, or do you have a reliability engineering manager sitting over it?" Listen for the correction. When he says "honestly it's less the downtime, it's that Ray's guy who could hear a bearing going bad is retiring in eighteen months and I've got nobody behind him" — write that down verbatim. That sentence is your second-meeting agenda.
- 6
Reading the cool-off
Warmth withdraws politely in this industry. The signals: - Answers shorten. "Yep. Yep, makes sense." - He starts narrating logistics: "Can you send me a one-pager and I'll circulate it." - He asks price before you've established a problem — that's a disqualification attempt in a polite jacket. - He mentions the referrer as an exit: "Well, if Ray rates you." Stop and name it: "I'm getting the sense this isn't the pressing thing for you right now, which is fine — Ray was guessing. Is it not the problem, or not the moment? If your unplanned hours are flat and your PPM is clean, tell me and I'll stop." A clean "not the problem" is a good outcome here. It protects Ray and it stops you burning a quarter on a plant that doesn't have the pain.
- 7
The close — a date, a length, a reason in their words, a name
Never close on "I'll send some information." Close on the sentence he gave you. "Then here's what I'd suggest. You said the issue isn't the hours, it's that nobody can tell you *why* it failed, and the guy who could is retiring. Give me thirty minutes and I'll walk you through what another tier 1 molder did with exactly that — and I'd want your maintenance manager on it, because he's the one who'd have to do something differently. Who is that, Dave? Thursday 6:30 before your production meeting, or Monday after lunch?" If he genuinely can't commit a diary slot: take a smaller real commitment with a date on *your* calendar, not his. "Fine. Send me your top three assets by unplanned hours and I'll come back with the payback math on the worst one. If it doesn't clear an eighteen-month payback I'll tell you on the call and stop bothering you. I'll follow up Thursday."
- 8
Close the loop with the referrer — same day, two lines
Non-negotiable, routinely skipped, and it's the only reliable way one referral becomes two. "Ray — spoke to Marcus, thanks for that. Different problem to yours actually; his availability is okay, it's the knowledge walking out the door in eighteen months. Thirty minutes with him and his maintenance manager Thursday. Appreciate the nudge." This thanks him, tells you whether you can use his name again, and keeps the source producing.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Marcus — Dani Cortez, from Harlow. Ray Delgado told me to call you. He picked up our downtime-baseline worksheet last month and said you'd taken over Bowling Green in January after the consolidation. He may have been overselling my usefulness. Four minutes, or is now bad?
Buyer
Ray said someone would call. I've got until 6:55, I've got a production meeting. And I'll tell you now, we're not buying anything — capex is locked. AR went in Q3 and it's a new press and a roof.
Rep
Understood, and I'm not going to pretend I can unlock it. Can I use the four minutes to figure out whether you and I should even be talking in October? What Ray was dealing with was one 40-year-old transfer press everything routes through and a 22-week gearbox lead time. That's his shop, not yours — you're molding, you've got redundancy across the presses. Where do your unplanned hours actually pile up?
Buyer
Assembly cell 2. Always assembly cell 2. But look, we've got a CMMS, we're at ninety-six percent PM compliance, my maintenance manager runs a tight program. This isn't a plant that ignores maintenance.
Rep
I believe you — most plants I walk aren't at ninety-six. Different question though: is your unplanned downtime on cell 2 going down as PM compliance goes up? Because if compliance is high and unplanned hours are flat, that usually means the intervals are calendar-based, not condition-based. You're changing bearings that had life left and missing the ones that didn't.
Buyer
...It's flat. Maybe worse. We did about sixty unplanned hours across the plant last month and probably thirty of it was that cell.
Rep
Okay. When it goes down at 11pm on second shift, who decides what actually broke? Does the write-up on the work order tell you anything?
Buyer
It tells me 'mechanical.' Three words and a downtime code. Then I'm on a Teams call with the customer's supplier quality guy explaining why we're short, and we run Saturday to catch up. But I'll save you some time — we tried a sensor pilot at the old plant two years ago. Vibration sensors, whole thing. Generated a pile of alerts nobody acted on and it quietly died. I'm not doing that again.
Rep
What happened to the alerts — did they go to a shared inbox?
Buyer
Something like that. A group email. Maintenance stopped reading it in about a month.
Rep
That's the usual failure and it's not a sensor problem. An alert that isn't a work order in the CMMS with a named owner and a spare on the shelf is just noise, and a maintenance team learns to ignore it in three weeks. So before I say a word about product — if your tech got a notice at 2am on second shift saying a gearbox on cell 2 fails in nine days, what does he actually do with it?
Buyer
Honestly? Probably nothing, because the spare's not in the crib. We squeezed the crib for working capital two years ago. He'd flag it to Dave in the morning and Dave would put it on the list.
Rep
Then that's the real conversation, and it's worth having whether you buy anything or not. Nine days' notice is only worth something if it turns into a purchase order and a planned weekend job. What's your planned-versus-reactive ratio right now?
Buyer
Nowhere near where corporate wants it. Maybe 40 percent planned. Look — this is a decent conversation but I can't spend money and my IT/OT guy is not letting anything onto the network. Send me something and I'll look at it when we start the AR cycle.
Rep
I'll send it, but a PDF won't help you write an AR. Two things instead. One — this doesn't touch your control layer, no PLC connection, read-only, and it can run on a cellular gateway that never sees your plant network. I'd rather find out in week one if your IT/OT person still says no than after you've spent two months building a case. Two — if we're talking about the Q3 AR anyway, the payback math on cell 2 has to be built from real downtime data, and if you write it in August you'll write it from memory.
Buyer
Fair point. I've written that number from memory before and finance took it apart.
Rep
So: thirty minutes, me, you, and Dave, and I'll come with the payback structure for cell 2 — thirty unplanned hours a month, your shutdown cost per hour, and what moving four emergency callouts into planned weekend work does to that. If it doesn't clear your hurdle rate I'll say so on the call. Thursday 6:30 before your production meeting, or Monday after lunch?
Buyer
Thursday 6:30. Bring the math, not a deck. And if Dave says the sensors are junk, that's the end of it.
Rep
That's the right test. I'll send an invite with three lines on it — no attachment. And I'll tell Ray it was a different problem than his.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Capex is locked for the year — come back next budget cycle.” | Fair, and I'm not going to pretend I can unlock it. Two questions. First, is this shaped like capex, or can it run as a monthly opex line under MRO or controllable spend? That's usually a different approval path and often inside your signing authority. Second, if we're talking about next year's AR anyway, the work of building it — the downtime baseline on your worst three assets, the payback math — has to happen now, or you'll be writing it from memory in August and finance will take it apart. Let me help you build the number. If it doesn't clear your hurdle rate, throw it out. |
| “The floor barely uses the systems we already have. Why would this be different?” | That's the most honest objection I get, and it usually means the last thing you bought asked operators to enter data. So ask me: who on your floor has to do something new for this to work? The answer should be nobody. If the value depends on an operator remembering to log a stoppage at shift change, throw us out. What I'd actually want from you is which system went unused and why — because if that was a change management failure rather than a tooling failure, we'll fail the same way and I'd rather know that now than in month four. |
| “We already have a CMMS and we're at 95% PM compliance.” | Good — most plants I walk aren't. But PM compliance and unplanned downtime aren't the same metric. If you're at 95% and still eating unplanned hours on the constraint, that tells you the intervals are calendar-based, not condition-based: you're changing bearings that had life left and missing the ones that didn't. What's the MTBF trend on your top three assets over the last twelve months? If it's flat or worsening while compliance is high, that gap is the whole conversation. |
| “You're not touching my PLCs and my IT team will never approve it.” | Understood, and honestly I'd be nervous if you said yes fast. No control-layer connection, read-only, and it can run on a separate cellular gateway that never sees your plant network. What I'd ask for is fifteen minutes with your IT/OT security person early rather than late — if there's a hard blocker I want to hit it in week one, not after your team has spent two months building an AR around it. |
| “We tried a sensor pilot two years ago. Alerts nobody acted on. It died.” | Where did the alerts go — a shared inbox? That's almost always the failure. An alert that isn't a work order in the CMMS with a named owner and a spare on the shelf is noise, and maintenance learns to ignore it inside three weeks. So before product: what would your tech actually do at 2am on second shift with a 'this gearbox fails in nine days' notice? If there's no answer — if the spare's 22 weeks out and the crib's been squeezed — that's the thing to fix first, with or without me. |
| “My maintenance team is stretched. They're reactive all day. They don't have time for another tool.” | That's the trap, though. Reactive teams stay reactive because every unplanned failure eats the hours you'd need to get ahead of the next one. I'm not asking for more of their time — I'm asking whether moving four of last month's emergency callouts into planned weekend work frees enough wrench time to matter. What was your planned-versus-reactive ratio last quarter? |
| “Just send me some information and I'll take a look.” | I'll send it, but a PDF won't tell you anything you can put in an AR. What's worth your time is fifteen minutes where you give me your top three assets by unplanned hours and roughly what a shutdown hour costs you on the constraint — you'll have that number even if you don't have it for the rest of the plant. If the math doesn't get to a payback under eighteen months, I'll say so on that call and stop bothering you. |
Questions reps ask about this call
- How is a warm call into a plant different from a warm call into any other industry?
Two things. First, the buyer is physically on a floor — the plant manager has a headset on next to a running line and a production meeting at seven, so your open has to survive noise and a hard time box. Second, the referral rarely transfers, because two plants that look identical on paper have different constraints. Ray's problem was a 22-week gearbox lead time on a transfer press; your prospect's problem might be that the 30-year millwright retires in eighteen months. Name the difference out loud in the first minute — "that's his shop, not yours" — instead of copying Ray's pain across.
- What should the opening 25 seconds actually say?
Four beats: your name and company, the referrer's name immediately, the specific checkable reason they thought of you, and a time-boxed permission question. "Marcus — Dani Cortez from Harlow. Ray Delgado said I should call. He pulled down our downtime-baseline worksheet and mentioned you'd taken over Bowling Green in January. He may have been overselling my usefulness. Four minutes, or is now bad?" Do not open with "how do you know Ray?" — it costs three minutes of a four-minute window and returns nothing.
- Which metrics should I put in the script so it sounds like I've been in a plant?
Use the ones already on the board by the door: unplanned downtime hours per month by asset, OEE on the constraint (most plants sit 55–70%, world-class is 85%, and they will argue about how it's calculated), planned versus reactive work order percentage, MTBF and MTTR on critical assets, customer PPM and escapes per quarter, and overtime as a percent of direct labor. Ask about them as diagnostics, not as claims. "Is your unplanned downtime going down as PM compliance goes up?" does more work than any statistic you could quote.
- The prospect says capex is locked. Is the call over?
No, but the shape of the ask changes. Test two paths out loud: whether it can run as monthly opex under MRO or controllable spend — often a different approval route and sometimes inside the plant manager's own signing authority — and whether you can help build the AR for the next cycle now, while the downtime data is real rather than remembered in August. What you must not do is spend a quarter demoing to someone whose signing limit is $25K on a $180K purchase. Ask early: "is this a this-quarter problem or a next-AR problem?"
- Who else should be on the second meeting besides the plant manager?
Almost always the maintenance manager, because he's the one whose team has to do something differently and he can kill it in one sentence. Depending on the plant, add the reliability engineering manager if one exists, the director of continuous improvement if the pitch touches OEE or changeover, and the quality manager if you're anywhere near escapes, PPM or a controlled-shipping situation. Ask for the name on the call: "who owns maintenance — is that Dave?" Warm calls have an unusually high hit rate on that question because you're already a known quantity by association.
- What counts as a successful warm call here?
A booked thirty minutes with a date, a named attendee, and an agenda built from a sentence the buyer said — not "I'll send some info." A clean "that's not our problem" is the second-best outcome, because it protects the person who referred you. The worst outcome is a pleasant call that ends in a PDF and a vague October. Either way, close the loop with the referrer the same day in two lines; sources who never hear back stop referring.