Manufacturing Cold Call Script: How to Earn 20 Minutes With a Plant Manager

1. 1

   90-second prep — do not dial without these four answers

   Say each one out loud before you touch the keypad. 1. WHO: Exact title and how long in seat. "Dave Kessler, Plant Manager, in the chair fourteen months, came over from the Fort Wayne plant." A Plant Manager at month fourteen owns the downtime number personally. A VP of Manufacturing over five sites cares about which plant is dragging the network. A Maintenance Manager cares about wrench time and callouts. Same company, three different calls. 2. TRIGGER: New plant leadership, a maintenance tech req that's been open 90+ days, a new program award, an acquisition, a shutdown week posted publicly. No trigger? The segment is the trigger: "Every stamping plant we work with running presses past their design life is dealing with the same thing." 3. THE ONE PROBLEM: Written on a sticky note. One. Not three. 4. THE ASK: "Twenty minutes, not a demo," plus two named slots. Also: have the follow-up email drafted in a window before you dial, and know your best dial windows — Plant Managers pick up 6:40–7:10am before the production meeting, and again after 4pm when first shift clears. Second-shift Production Supervisors are reachable 3:30–4:30pm and almost nowhere else.

2. 2

   The opener — name, honest frame, permission, pause

   "Dave — it's Marcus at Cordell. We haven't spoken, this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?" Then STOP. Two full seconds. Do not fill it. Downward inflection on "get lost." If it goes up you sound like you're asking for a favour. Pattern-interrupt variant (good for Maintenance Managers, who hate preamble): "Dave — Marcus, Cordell. You don't know me. Is this a terrible time or just a bad one?" Trigger-led variant: "Dave, Marcus from Cordell. You've had a maintenance tech and a CNC machinist req open since January — that's actually why I called. Sixty seconds?" Banned openers: "How are you today?" — "Did I catch you at a bad time?" — "I'll be brief" — "The reason for my call is to introduce myself and our company."

3. 3

   The reason — problem, not product (two sentences, then a check-in)

   For a Plant Manager or VP of Manufacturing: "We work with a dozen or so tier 1 and tier 2 plants in the Midwest. The thing that comes up every single time with plant managers is that they can tell me unplanned downtime hours by asset to the decimal — but when I ask why the line went down, the downtime code says 'mechanical' and the tech wrote three words on the work order. So the same failure comes back in six weeks and it's Saturday overtime again to catch the schedule up. Is that anywhere near your world, or have you got that nailed down?" For a Maintenance Manager or Reliability Engineering Manager: "The reliability managers I talk to are usually sitting at high PM compliance and still eating unplanned hours on the constraint — because the intervals are calendar-based, so they're pulling bearings that had life left and missing the ones that didn't. Their planned-versus-reactive ratio hasn't moved in two years. Is that fair for your top three assets, or is yours trending the right way?" For a Quality Manager: "Every quality manager I talk to can absorb internal scrap. What ruins the quarter is one escape — the containment sort, the 8D, and if it's a bad one, a third-party inspector standing in your plant on your dime. Is that a live worry for you right now or is your PPM behaving?" Notice: no product name yet. None. And every one ends with a graceful exit so the honest answer is safe.

4. 4

   Two questions maximum — narrow and factual

   If they engage, you are not running discovery. Two questions, then close. Good: - "What's your constraint — is it a press, a cell, a paint line?" - "Roughly how many unplanned hours a month is that asset costing you?" - "Is the downtime data coming out of a system or off a whiteboard?" - "Is anything budgeted against that this year, or is it just being lived with?" Bad — save these for the discovery call: - "What are your top three priorities this year?" - "Walk me through your maintenance process." - "What would solving this be worth to you?" Listen for the ADMISSION: "yeah, line 3 is a nightmare," "we've been meaning to look at that," "our OEE on that cell is embarrassing." The second you hear it, stop asking and ask for the meeting.

5. 5

   The ask — small, specific, two slots

   "Here's what I'd suggest. Twenty minutes, not a demo, no slide deck. You tell me your three worst assets by unplanned hours and roughly what a shutdown hour costs you on the constraint — you'll have that number for the bottleneck even if you don't for the others — and I'll show you what the payback math looks like for a plant your size. If it doesn't clear your hurdle rate I'll tell you on the call and stop bothering you. I've got Thursday at 7:15 before your production meeting, or Friday at 2. Which is less bad?" Then: "Sending the invite now — I'll put your maintenance manager on it as optional. Can you tell me it landed?" Invite goes out while they're still on the line. Every time.

6. 6

   Gatekeeper and front-desk screen

   Plant front desks are the toughest screen in B2B because they've been trained by staffing agencies and scrap metal brokers. "It's about unplanned downtime on their bottleneck line. Marcus at Cordell — he won't know me, it's a cold call." Short, calm, specific, and admit it's cold. Never claim a prior relationship, never say "he's expecting my call," never be cute. If she says he's on the floor: "Makes sense. Is he better at 6:45 in the morning or after four?" — you've just been handed a dial window by the person who knows his day best.

7. 7

   Voicemail — under 20 seconds, no ask

   "Dave, Marcus at Cordell — you don't know me. Calling about unplanned downtime on constraint assets in stamping plants; specifically the gap between knowing the hours and knowing the cause. I'll try you again Thursday morning. 555-0148." No call-to-action. The voicemail's only job is that your name is faintly familiar on the next dial and in the email that follows it thirty seconds later.

8. 8

   The soft no and the recycle — never hang up empty

   "No problem, I'll get out of your way. Last thing — is this a timing thing or a not-a-priority thing?" (Listen. Then:) "Got it. When do you submit your AR for next year — Q3?" … "And who signs off above you, is that the VP of Ops or does it go to corporate engineering?" … "Perfect. I'll come back to you the first week of July, before you're writing that from memory. I'll send one email so my name's in your inbox." A call that produces a dated callback and a named approval path is a good call. A call that produces "send me something" and nothing else is a polite hang-up you agreed to.

9. 9

   Follow-up email — send within five minutes

   Subject: Our call just now — line 3 and the three-word work orders Dave — Marcus, the cold call from this morning. Thanks for not hanging up. You said the 300-ton press eats most of your unplanned hours and the codes don't tell you why. That's the exact thing I'd want to walk through Thursday at 7:15. Twenty minutes, no demo. I'll bring the payback structure other plants have used inside an AR so you're not building it from scratch in August. Invite's in your calendar — Charlie from maintenance is on it as optional. Marcus

1. Rep

   Dave — it's Marcus at Cordell. We haven't spoken, this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?

2. Buyer

   …I've got about that. I'm in the middle of a P&L review. Go.

3. Rep

   Appreciate it. We work with tier 1 and tier 2 plants across the Midwest, and the thing that comes up every single time with plant managers is this — they can tell me unplanned downtime hours by asset to the decimal, but when I ask why the line went down, the code says 'mechanical' and the tech wrote three words on the work order. So the same failure comes back in six weeks and it's Saturday overtime to catch the schedule up. Is that anywhere near your world, or have you got that nailed down?

4. Buyer

   Everybody's got that problem. We're not special. Look, if this is sensors, we already did that. Two years ago we put vibration pucks on four gearboxes, it threw alerts into a shared inbox, nobody actioned any of them, and the thing quietly died. My maintenance team stopped opening the emails inside a month.

5. Rep

   That's the failure I'd have bet on. Can I ask you the question I'd have asked back then — if your second-shift supervisor got a notice at 2am that said 'this bearing fails in nine days,' what actually happens next in your plant? Does that become a work order in the CMMS with a named owner, or does it just sit?

6. Buyer

   Honestly? It sits. And even if it didn't — knowing a gearbox is going doesn't help me when the replacement is twenty-two weeks out of Germany and we've had spares inventory squeezed for working capital three years running. So I get nine days' notice on a part I can't get. What am I supposed to do with that?

7. Rep

   Then that's the real conversation, and it's not a sensor conversation. Nine days is useless. Ninety is a purchase order at ocean freight instead of an air-freight expedite hitting your controllable spend. What's your unplanned hours per month look like on the worst asset — is it a press?

8. Buyer

   Line 3. It's a press from 1998 that everything routes through. Call it thirty, thirty-five hours a month unplanned, and it's the constraint, so every one of those hours is a shipped-part hour.

9. Rep

   And OEE on that line — is it north of 70 or is it living in the 60s?

10. Buyer

    Depends who's calculating it. Corporate wants it one way, my continuous improvement director wants it another, and I don't trust either number. Low 60s if you count planned changeovers honestly. But look — I want to stop you. Capex is locked for the year. I signed my AR in September and it's a new press and a roof. Whatever this costs, I can't buy it until next year, so you'd be selling to somebody who can't buy.

11. Rep

    Fair, and I'm not going to pretend I can unlock it. Two things. First — is this shaped like capex for you, or could it run as a monthly 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 downtime baseline on your worst three assets and the payback math has to get built now, or you're writing it from memory in August against a roof.

12. Buyer

    It's a fair point about August. But I'll tell you the other wall you'll hit — you're not putting anything on my network and you're not touching my PLCs. My IT/OT guy will kill it and honestly I'd back him.

13. Rep

    I'd be worried if you said yes fast. Nothing touches the control layer, it's 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 that person early rather than late — if there's a blocker I want to hit it in week one, not after your team has spent two months building a business case that dies in security review.

14. Buyer

    Alright. What is it you actually want from me? Because I'm not sitting through a demo.

15. Rep

    Twenty minutes, no demo, no deck. You bring your three worst assets by unplanned hours and roughly what a shutdown hour costs you on line 3 — you'll have that number even if you don't have it for the others. I'll walk you through how three plants your size structured the payback inside an AR. If it doesn't clear your hurdle rate under eighteen months, I'll say so on the call and leave you alone. Thursday at 7:15 before your production meeting, or Friday at 2?

16. Buyer

    Thursday. Early. And bring something real, not a case study with the customer name blacked out.

17. Rep

    Done. Sending the invite now — I'm putting your maintenance manager on as optional, because he'll know the MTBF trend on that press better than either of us. Can you tell me it landed?

18. Buyer

    …Yeah, it's here. Charlie's the maintenance manager. He'll be skeptical.

19. Rep

    Good. I'd rather have him skeptical on Thursday than quiet in month three. Talk then, Dave.

Who should I cold call first in a manufacturing plant — the Plant Manager or the Maintenance Manager?

It depends on your price point. If your solution lands under the Plant Manager's signing authority (often $25K or $50K), call the Plant Manager — he can move without an AR. If it's above that, you'll need him anyway, so still start there, but expect to be routed to the Maintenance Manager or Reliability Engineering Manager for technical validation. Calling the Maintenance Manager first works when your product changes his daily life directly (wrench time, callouts, planned-versus-reactive ratio) — but he almost never has budget, so you'll be running a second sale upward. Avoid opening with the VP of Manufacturing unless you're selling multi-site; a VP over five plants will just forward you to the worst-performing one.

What's the best time of day to cold call a plant?

Plant Managers are reachable 6:40–7:10am, before the morning production meeting, and again after 4pm once first shift clears and the floor quiets down. Mid-morning is the worst window — that's gemba walks, layered process audits and customer calls. Maintenance Managers are unpredictable all day because they carry a radio; try right after lunch. Second-shift Production Supervisors are essentially only reachable between 3:30 and 4:30pm. Avoid Mondays entirely: Monday is when the weekend's downtime gets reconciled and the week's schedule gets fought over.

How specific should the problem statement in a manufacturing cold call script be?

Specific enough that a rep from another industry couldn't read it. "We help manufacturers improve efficiency" gets you hung up on. "You can probably tell me unplanned hours by asset to the decimal, but the downtime code says mechanical and the tech wrote three words on the work order" gets you thirty more seconds, because it's true in almost every plant and nobody outside the industry knows it. Use their measured metrics as the consequence — constraint OEE, unplanned downtime hours per month, planned-versus-reactive ratio, customer PPM, overtime as a percent of direct labor — not vague words like waste or inefficiency.

How do I handle 'capex is locked for the year' without losing the deal for nine months?

Two moves, in order. First, test the shape of the spend: ask whether it could run as a monthly line under MRO or controllable spend rather than a capital appropriation request, because that's a different approval path and often inside the Plant Manager's own signing authority. Second, if it genuinely has to be an AR, reframe the meeting as building the number rather than buying the thing — ARs are typically submitted in Q3 for the following year, and the downtime baseline and payback math have to be gathered before then. That converts a nine-month dead zone into a dated callback with a named approval path, which is a real outcome.

Should I mention my product on a manufacturing cold call?

Not in the first ninety seconds. Plant Managers have been burned by shelfware — an MES module, a downtime tracking tool, tablets at the line that operators won't touch — and naming a product category early triggers the pattern match to the last thing that failed. Lead with the problem and the consequence. If they ask what you sell, answer in one plain sentence and immediately return to their asset: "Condition monitoring on rotating assets — but the reason I called is line 3." Save the mechanism for the twenty-minute meeting.

What counts as a successful manufacturing cold call if I don't book a meeting?

A dated callback tied to their capital cycle plus one piece of intelligence you didn't have — their constraint asset, roughly what a shutdown hour costs, who signs above the Plant Manager, or which past pilot died and why. Log the exact words they used; those words go in the follow-up email and the discovery call. What does not count is "send me some information." That's a polite hang-up, and if you accept it without trading for a callback date or two facts, you've generated an unopened email and no pipeline.

• All Manufacturing playbooksEvery call type for Manufacturing, in one place.

Other Manufacturing calls

• Demo CallThe Manufacturing Product Demo Script for Plant Managers Who Interrupt
• Discovery CallDiscovery Call Questions for Manufacturing: A 25-Minute Playbook for Plant Managers, Maintenance Leaders and VPs of Operations
• Manager Coaching CallSales Coaching Roleplay for Manufacturing Teams: The 1:1 After Two Missed Quarters
• Pricing Negotiation CallManufacturing Pricing Negotiation Script: Holding Your Number After the Technical Win
• Renewal CallManufacturing Renewal Call Script: Saving a Plant Account That's Already Half Gone
• Upsell CallThe Upsell Script for Manufacturing Customers: Turning a Plant Account Review Into an Expansion
• Warm CallWarm Call Script for Manufacturing: Cashing a Referral With a Plant Manager Before the 7am Production Meeting

The same call in a neighbouring market

• Cold Call for SaaSThe SaaS Cold Call Script for Reps Dialling CROs, VPs of Sales and RevOps Leaders
• Cold Call for Financial ServicesFinancial Services Cold Call Script: Getting a Wealth Management COO to Give You 25 Minutes
• Cold Call for InsuranceThe Insurance Cold Call Script That Keeps a Claims Leader on the Phone

Related reading

• Building a Dial Block That Survives Past 10:40amMost reps don't have a dialling problem, they have a forty-minute problem. Here's the mechanical build for a 90-minute cold call block that holds all the way to the timer.
• Booking the Meeting Before You Hang Up: The Last Forty Seconds of a Cold CallMost cold call training obsesses over the opener and goes quiet at the close — here is exactly what to say in the last forty seconds to walk away with a real meeting.