Manufacturing · Manager Coaching Call
Sales Coaching Roleplay for Manufacturing Teams: The 1:1 After Two Missed Quarters
Your rep sells uptime, quality, or maintenance software into plants. Their pipeline is full of Maintenance Managers who love the demo and can't sign a $40K AR, and their closed-lost notes say "capex locked" nine times in a row. They've missed two quarters. Not off a cliff — 82% and then 78% — which is worse, because it's arguable. They will walk in with the list already loaded: the AR cycle killed Q2, the territory got recarved when the tier 1 automotive accounts moved to the strategic team, the challenger is quoting a $12K downtime-tracking tool against your $60K platform, and every plant they touch got burned by a sensor pilot two years ago that died in a shared inbox.
Some of that is true. That's what makes this hard. Underneath it, their discovery is thin — they're getting to minute nine of a first call with a Plant Manager and pitching condition-based monitoring before they've asked what an hour of downtime costs on line 3 — and they stopped prospecting around week three of last quarter while they "worked" two deals that were never getting through a corporate appropriation request. They will not volunteer either of those. You'll only get there if you stay curious longer than they expect, put real numbers on the table instead of arguing about feelings, and make it obvious that admitting the true thing is safer than defending the fake one.
This playbook is built as a sales coaching roleplay for Manufacturing teams — run it in DrillCall against a rep persona who defends the AR cycle for twenty minutes before cracking. Below: what to pull before you sit down, the exact language for each phase, a 16-turn dialogue with a rep who does not fold easily, and the six manufacturing-flavoured excuses you'll have to sort into real, partly real, and story. In this playbook, "Rep" is you, the manager. "Buyer" is Marcus, the rep you're coaching — your difficult counterpart in this conversation.
The manager coaching call script
Say it in your own words. The structure is the part that matters.
- 1
Before you open your mouth: pull the tape
Do not walk in with a feeling. Walk in with six things: 1. **New opps created per week, last 90 days.** Marcus created 11 in month one, 6 in month two, 3 in month three. That graph is most of the conversation. 2. **Pipeline coverage against next quarter.** 1.6x is a different meeting than 4x with dead conversion. 3. **Stage conversion vs. team median.** Where do his deals die? Specifically: first-call-to-second-call, or proposal-to-no-decision? 4. **Buyer title mix on his open pipe.** Count how many opps have a Plant Manager or VP of Manufacturing on a call versus how many are only a Maintenance Manager or Reliability Engineering Manager. In this market that ratio *is* the forecast. 5. **Closed-lost reasons.** Count the ones that say "capex" or "price." Then count how many of those had a documented unplanned downtime number on the constraint asset. Usually near zero. 6. **Two recordings, timestamped.** One win, one loss. You will play 90 seconds of one of them. If "the leads are junk" is real, you'll see it in lead-to-meeting rate against peers working the same list. If it isn't real, you'll see his meeting rate is normal and the floor drops out after the first call.
- 2
Open: name the stakes in two sentences
> "Two quarters is a pattern, not bad luck, and I'm not going to pretend otherwise. But I didn't book this to read you your numbers — you know them better than I do. I want to figure out what's actually going wrong, because I think it's one thing and not five, and I genuinely don't know yet which one. Fair?" No "how's the family." No "how are things going?" He knows why he's here. False warmth reads as a setup and he'll lock down before you've asked anything.
- 3
Drain the tank — every excuse, before you touch any of them
> "Before I say a word, give me the whole picture. What's making this hard right now? All of it — not the diplomatic version." Then, after each one: **"What else?"** Ask it three times. Write the list where he can see you writing it. In this market the list usually comes out as: capex is frozen everywhere and every AR is deferred to next cycle; the tier 1 automotive accounts got moved to strategic; the challenger is quoting a $12K downtime tracker against our platform; every plant already has a CMMS and thinks they're covered; IT/OT security kills deals at week six; nobody on the floor answers a phone between 6am and 3pm. Read it back flat, no judgement: > "So: AR cycle, territory, the challenger's price, CMMS incumbency, IT/OT, and reachability. Six things. Is that the list, or is there a seventh?" Getting him to agree the list is complete closes the escape hatches for the next twenty minutes.
- 4
Sort the list: real, partly real, story
Take each one completely seriously, then test it against what you brought. Start by conceding the true one out loud: > "Territory's real. You lost Kettering, Vandergrift and the two Hollandale plants when tier 1 automotive went strategic — that's about a quarter of your historical pipe and I'm not going to pretend it isn't a headwind." Then press on the one you can measure: > "Capex next. You got 38 accounts on the same list Renee did — she got 41. She booked 16 first calls, you booked 15. So we're converting to meetings the same. Where it splits is after: she moved 9 of 16 to a second conversation with a VP of Operations or a Director of CI in the room. You moved 3 of 15, and eleven of your twelve open opps have never had anyone above a Maintenance Manager on a call. Help me understand that gap." Then let the silence run. Ten seconds. Don't rescue him. On price and capex: > "Seven of your ten losses say capex or price. Of those seven, how many had a number in the pain field — like, line 3 is eating 34 unplanned downtime hours a month at $9,800 an hour? Walk me through Hollandale. What did the Plant Manager say a shutdown hour costs him?" When he can't answer, do **not** say "exactly, that's the problem." Say: > **"Okay. What do you make of that?"**
- 5
Make it safe to say the real thing
> "Let me say the thing that's sitting between us. I'm not building a file right now. If the answer is 'I got spooked in week three and stopped dialling' — that's fixable and I've fixed it with reps before. What I can't fix is a version where nothing is in your control, because then neither of us has anything to do Monday morning." Then the two questions that usually crack it: > "If I handed you 40 clean plants tomorrow, all mid-market tier 2, all with a known bottleneck problem — do you hit the number?" The hesitation is the admission. Follow with: > "What's the part of this you'd fix if nobody was watching and there were no consequences?" Or the direct route into activity: > "Walk me through the last three weeks of the quarter. What did a Tuesday morning look like, 7:30 to 11?" Reps who stopped prospecting cannot describe a Tuesday morning. They'll describe deals instead of activity. That's the tell.
- 6
Go to the tape — a moment, not a theme
"Your discovery needs to be deeper" is a horoscope. Play 90 seconds. > "This is minute nine of the Hollandale first call. Dale — he's the Plant Manager — says, and I'm quoting: 'the press in cell four has been a problem since before I got here.' Listen to what you do next." [play it] "You went into the alert workflow. What are the three questions you didn't ask?" What you want him to name himself: - "How many unplanned hours did cell four cost you last month, and what does an hour cost when you're down?" - "What's your OEE on the constraint right now — and is the loss availability, performance, or quality?" - "When it went down in March, what did the downtime code say versus what actually broke?" If he can name the misses, this is execution — he knows the move and isn't making it, usually because he's rushing to prove value before someone hangs up. If he genuinely can't name them, it's a skill gap and you're training, not coaching. That distinction sets your plan. Don't skip it.
- 7
Land on one root cause and say it plainly
> "Here's where I've landed. Territory cost you real pipe, that's true. But the thing killing you is that you're selling to Maintenance Managers who can't clear a $50K appropriation request, and you're doing it without a downtime number — so when it reaches the Plant Manager or the VP of Ops it's a feature comparison against a $12K tool and you lose on price every time. And because you're only creating three new opps a month, you can't afford to disqualify anything, which keeps you in those deals for a full quarter. Does that match what you see from where you sit?" Ask for agreement. If he pushes back with a real argument, listen — you might be wrong. If he pushes back with a seventh excuse, name it: > "That's a seventh thing. We agreed the list was six. I think you're looking for a reason this isn't about the calls."
- 8
Let him write the plan, then make it checkable
> "So — what do you want to change first?" Whatever he says, convert it into something you can both look at on Friday: - "Prospect more" → **"Tuesday and Thursday, 6:30 to 8:30, before first shift meetings start. Five new opps a week."** - "Better discovery" → **"No product on a first call for three weeks. If they push, you say: 'I'd rather show you the two things that matter on your constraint than all forty — give me ten more minutes of questions first.'"** - "Get higher" → **"No opp advances past stage 2 without a Plant Manager, VP of Manufacturing or Director of Operational Excellence on a call, plus a cost-per-downtime-hour figure in the pain field. Maintenance Manager alone is a stage 1."** Then your half of the deal: > "My side: I'm on your first two discovery calls this week and we debrief within ten minutes of hanging up. And I'll go pull you a list of tier 2 stampers and injection moulders in the corridor to backfill what territory took." Coaching that only assigns work to the rep reads as a warning, not a partnership.
- 9
Close with the standard, not a pep talk
> "So: Tuesday and Thursday 6:30 to 8:30, five new opps a week. No product on a first call. Nothing gets to stage 2 without a Plant Manager or VP and a dollar figure on downtime. I'm on your Hollandale follow-up Wednesday. We meet Friday at four and look at opps created — not deals, opps. And to be straight with you: a third quarter like the last two changes what this conversation is. I don't think that's where we're going, but I'd be doing you a disservice not saying it." Then: **"What did you hear me commit to?"** His summary tells you whether any of it landed.
- 10
If he never admits anything
Don't force a confession — you'll get a fake one and lose the next four weeks. > "Alright. We disagree on cause. Let's test it. Three weeks: no product on first calls, five new opps a week, and every stage-2 has a Plant Manager or VP of Ops and a downtime dollar figure. If the AR cycle is genuinely the whole story, none of that moves and I'll go fight for a pricing motion that fits an MRO line instead of a capital request. If it does move, we've learned what we're dealing with. Either way we know more in three weeks than we do sitting here." That turns a stalemate into data and gives you a clean decision point.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Two quarters is a pattern, not bad luck, and I'm not going to pretend otherwise. But I didn't book this to read you your numbers — you know them. I want to work out what's actually going wrong, because I think it's one thing, not five, and I don't know which one yet. Fair?
Buyer
Fair. Though I'll tell you right now, the one thing is that nobody's buying. Every plant I walk into, the Plant Manager tells me capex is locked until the AR cycle in Q3. Dale at Hollandale said it to my face — 'come back in August.' That's not a call problem, that's a calendar problem.
Rep
Okay. What else?
Buyer
Territory. I lost Kettering and Vandergrift and both Hollandale plants when tier 1 automotive went to strategic. What's left is tier 2 job shops running a single shift with a Maintenance Manager who also does purchasing.
Rep
What else?
Buyer
Price. There's a $12K downtime tracker everybody's getting quoted and I'm at sixty. And half these plants ran a sensor pilot two years ago that generated alerts nobody actioned, so the second I say 'condition-based' they've already decided. Plus IT/OT security kills me at week six — the minute someone hears 'gateway' it goes into a queue and dies there.
Rep
So: AR cycle, territory, the challenger's price, dead sensor pilots, IT/OT. Five. Is that the list or is there a sixth?
Buyer
That's the list.
Rep
Territory's real — I'll say that out loud. Those four accounts were about a quarter of your historical pipe and losing them mid-year is a genuine headwind. Now let me put the AR thing next to something. You and Renee worked the same list — 38 accounts to her 41. She booked 16 first calls, you booked 15. Basically identical. She moved 9 of 16 to a second conversation. You moved 3 of 15. And eleven of your twelve open opps have never had anyone above a Maintenance Manager on a call. Help me understand that.
Buyer
Renee's got two plants in her patch that already had budget approved before she touched them. That's not the same fight. And I get to Maintenance Managers because they're the ones who pick up. Plant Managers are on the floor from six in the morning, they don't sit at a desk.
Rep
That's true about the floor. Take Hollandale though — you were on a call with Dale, an actual Plant Manager, in April. Seven of your ten losses say capex or price. Of those seven, how many have a downtime number in the pain field? Like, cell four ate 34 unplanned hours last month at nine grand an hour.
Buyer
…Probably none of them. But that's because they won't give me that number. Nobody wants to hand a vendor their OEE.
Rep
Let me play you ninety seconds. Minute nine of the Hollandale first call. Dale says, quote, 'the press in cell four has been a problem since before I got here.' Listen to what you do next. [plays] You went straight into the alert workflow. What are the three questions you didn't ask?
Buyer
…I didn't ask what an hour of downtime costs him. I didn't ask what the OEE split was — whether he's losing availability or quality. And I didn't ask what the downtime code said versus what actually broke. Yeah. I know. I was nine minutes in and he'd already told me he had a stand-up at ten, so I went for it.
Rep
Okay. What do you make of that?
Buyer
That if I'd asked, he might have said forty grand a month and then sixty thousand doesn't sound like a capital request, it sounds like a payback. But honestly — look, the other thing is I stopped dialling around week three. I had Hollandale and Vandergrift and I convinced myself they were closing. They weren't. So I've got three new opps in month three and I can't walk away from anything.
Rep
Thank you for that — that's the honest version and it's the one I can actually do something with. So here's what I think is true: territory hurt you, and the rest of it is that you're pitching Maintenance Managers who can't clear a $50K AR, with no downtime number attached, which turns every deal into a feature fight against a $12K tool. Does that match what you see?
Buyer
Yeah. It does. What do you want me to do differently?
Rep
Wrong way round — you tell me. What's the one thing you want to change first?
Buyer
No product on a first call. I'll hold the line for three weeks. And I'm not letting anything sit in stage 2 without a Plant Manager or a VP of Ops on it and a cost-per-downtime-hour in the notes. The prospecting block I'll do at 6:30 Tuesday and Thursday — that's actually when Plant Managers pick up, before first shift meeting.
Rep
Five new opps a week off those blocks. I'm on your Hollandale follow-up Wednesday and we debrief within ten minutes. I'll pull you a list of tier 2 stampers and moulders in the corridor to backfill territory. Friday at four we look at opps created — not deals, opps. And straight with you: a third quarter like these two changes what this conversation is. What did you hear me commit to?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Every Plant Manager tells me capex is locked until the Q3 AR cycle. That's not on me."” | Concede the calendar, then split it. "The AR cycle is real — nobody's arguing it. Two things though. One: how many of those conversations did you test whether this is capex-shaped or whether it could run monthly against MRO or controllable spend, which is usually inside the Plant Manager's own signing authority? Two: if we're building next year's AR anyway, the downtime baseline on their worst three assets has to be built now or they're writing it from memory in August. Which of your twelve opps have you offered to help build the number for?" If he's never asked the opex question on a single call, the AR cycle isn't the blocker — it's the exit ramp he takes when the call gets hard. |
| “"My territory got carved — I lost the tier 1 automotive accounts and I'm left with tier 2 job shops."” | Give him this one completely, out loud, with a number: "You lost four accounts, about a quarter of your historical pipe, mid-year. That's legitimate and I'm not going to pretend it isn't." Then convert it into your side of the plan — "I'll pull the tier 2 stamper and moulder list this week" — and move on. Conceding the true grievance is what buys you the right to press on the ones that aren't. A rep who feels heard on one stops defending all five. |
| “"We're 20% over and there's a $12K downtime tracker in every deal."” | "Pull up your last seven losses. How many have a documented unplanned downtime figure and a cost per hour on the constraint? If it's zero, the buyer never had anything to compare sixty thousand against except twelve thousand — of course we lose that. A Plant Manager doesn't buy the cheaper tool, he buys the one that clears his hurdle rate. Price objections in this market are almost always a symptom of a missing number, not a pricing problem. Show me one loss where they knew the downtime cost and still went cheap and I'll take it to pricing myself." |
| “"Everyone got burned by a sensor pilot two years ago — they've already decided before I open my mouth."” | This one is real and it's also the best discovery question he owns and isn't using. "Good — then lead with it. Ask them what happened to the alerts. Nine times out of ten they went to a shared inbox and maintenance learned to ignore them inside three weeks. Then ask the question that actually separates us: 'what would your team do at 2am on second shift with a notice that says this bearing fails in nine days?' If there's no work order, no named owner, no spare on the shelf, we've just found the real problem together and we're not a vendor anymore. You're treating the dead pilot as a wall. It's a door." |
| “"IT/OT security kills me at week six every time."” | "Then stop hitting it at week six. Ask for fifteen minutes with their IT/OT security person in week one — read-only, no PLC connection, cellular gateway that never touches the plant network. If there's a hard blocker I'd rather you find it before the Reliability Engineering Manager has spent two months building a business case that dies. Look at your pipe: how many of the twelve have had an IT conversation at all? If the answer is one, IT isn't killing your deals — the sequencing is." |
| “"Maintenance Managers are the only ones who pick up. Plant Managers are on the floor all day."” | Half true, and half of it is a schedule problem he can fix. "You're right that a VP of Manufacturing isn't sitting at a desk at 2pm. So when are they reachable? Before first shift and after second-shift handover. Which is exactly the window you're not dialling in. Here's the harder part: a Maintenance Manager is a great coach and a terrible economic buyer — he can tell you MTBF on the top three assets, he cannot clear a $50K appropriation request. Eleven of your twelve opps have never had anyone above him on a call. That's not access, that's comfort." |
Questions reps ask about this call
- How is a sales coaching roleplay for Manufacturing teams different from a generic manager 1:1 drill?
The excuses are different, and they're partly true, which is what makes them hard to coach. A rep selling into plants will tell you capex is frozen until the Q3 appropriation request cycle, that every prospect got burned by a sensor pilot that died in a shared inbox, and that IT/OT security kills deals at week six. Those things happen. A generic drill has the rep complaining about "bad MQLs." A manufacturing drill makes you separate the AR calendar — which is genuinely real — from the fact that your rep has eleven open opportunities with no one above a Maintenance Manager on any of them.
- What numbers should I pull before running this call for real?
New opportunities created per week over 90 days; pipeline coverage against next quarter; stage conversion against team median; closed-lost reasons with a count of how many say capex or price; and one manufacturing-specific cut — the buyer title mix on the open pipe. Count opportunities where a Plant Manager, VP of Manufacturing or Director of Continuous Improvement has been on a call versus those that are only a Maintenance Manager or Reliability Engineering Manager. In this market that ratio predicts the quarter better than deal count does. Then bring two recordings, timestamped.
- My rep says the AR cycle genuinely blocked their quarter. How do I know if that's real?
Test it against a peer working comparable accounts. If lead-to-first-meeting rates are similar and the drop-off is after the first call, the AR cycle isn't the cause — it's the reason the buyer gives when there was never enough pain quantified to justify a capital request. The specific check: how many of the rep's losses have a downtime cost per hour on the constraint asset in the notes? If none do, no Plant Manager ever had a payback number to put in front of corporate, and "capex is locked" was always going to be the answer.
- What does good discovery actually sound like on these calls, so I know what I'm coaching toward?
Three questions before anything gets shown. What did unplanned downtime cost on your top three assets last month — hours and dollars per hour? On the constraint line, is your OEE loss availability, performance or quality? And when the last big failure happened, what did the downtime code say versus what actually broke? A rep who lands those has a payback calculation. A rep who goes to product at minute nine has a feature comparison against a $12K downtime tracker, and they lose it.
- How long should the roleplay run, and how difficult should the rep persona be?
Thirty to forty-five minutes, same as the real thing. The persona should not fold before minute fifteen — a fast, flat "you're right, I need to prospect more" at minute six is a rep managing you out of the room, and the tell is that it arrives before any number has been discussed. Set the persona to defend the AR cycle and the territory carve-up hard, concede the discovery gap only after a call recording is played back, and to volunteer the stopped-prospecting admission only if the manager has explicitly said they're not building a file.
- What counts as a successful outcome for this drill?
One root cause named plainly, agreed by both people, and one changed behaviour the rep wrote themselves — converted into something checkable on Friday. In this market the plan usually looks like: prospecting blocks at 6:30am Tuesday and Thursday because that's when Plant Managers pick up, no product on a first call for three weeks, and nothing advances past stage 2 without a Plant Manager or VP of Operations on a call plus a cost-per-downtime-hour in the pain field. Plus one commitment from the manager. If the drill ends with a nine-point improvement plan or a motivational close, it failed.