Manufacturing · Renewal Call
Manufacturing Renewal Call Script: Saving a Plant Account That's Already Half Gone
Your contract at their Plant 2 expires in six weeks. Sixty wireless vibration and temp sensors, forty platform licenses, and the only person who logs in more than twice a week is the Reliability Engineering Manager who built the Monday asset-health review himself. The Maintenance Manager's planners never got trained. Second shift has never opened it. Ticket 41-882 sat nine days in June while their 800-ton press was throwing alarms. And a competitor rep has been in the Plant Manager's inbox since October with a number 28% under yours.
They took this meeting for one reason: to say out loud what went wrong. If your first sentence is "so, what would it take to get this done?" you have confirmed everything they already believe about you — that you disappear when the sensors are humming and reappear when the PO is due. Plant Managers have a very specific allergy to this. They have been sold an MES, a downtime tracking tool, tablets at every line, and a CMMS module they paid to configure and nobody uses. Shelfware is not an abstract risk to them; it is a line item they defend to corporate.
The save is built on three things, in this order: naming the failures by ticket number and date before they do, finding out what your one working use case is actually worth in unplanned downtime hours on the constraint, and handing them a 90-day plan where half the owners are their people. The order form is the last five minutes. Below is the script, the objections you'll actually hear on a plant floor, and a dialogue where the Plant Manager is as hard on you as he'll really be.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-Call: The Renewal Autopsy (before you dial — you cannot fake this live)
Walk in knowing their bad year better than they do. Have these on one page, not in a CRM tab you have to hunt through: • Every ticket, 12 months. ID, open date, first response, resolution. Know your three worst by number. Ours in this scenario: 41-882 (opened June 11, first response nine days), 42-119 (gateway on the press line offline 11 days before anyone flagged it), 42-604 (battery replacements shipped three weeks late). Seven P1 SLA misses in Q2. • Sensor health, not just logins. How many of the 60 sensors have been dark more than 30 days? If 14 are offline because of mounts or batteries, that is your fault and they may not even know it yet. • Usage by role. "Reliability Engineering: 2 weekly active. Maintenance planners: 3 of 12 have ever logged in. Second shift: zero." Never "adoption is around 40%." • CSM turnover on your side. Two changes in fourteen months is a cause of their bad year, not a footnote. • QBR promises never delivered. The CMMS write-back that was going to auto-create work orders — committed in Q1, still not shipped. • Their org changes. Did the Plant Manager who signed get moved to another site? Is the Maintenance Manager new? Did corporate pull signing authority down from $50K to $25K? • Their operating reality this quarter. If they're in controlled shipping level 1 at a tier 1 customer, or running Saturdays to recover an OTIF miss, that outranks your renewal and you should know it before you open your mouth. Then get internal alignment in writing: what Support has actually changed, what onboarding hours your CS lead will commit, and your floor on price, term, and sensor count. A second broken promise ends this account permanently and it will be attributed to you by name.
- 2
Opening — name it before they have to (first 45 seconds, you go first)
"I know the contract's up on the 31st. I'm not here to talk about the renewal yet — I want to talk about this year first, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 41-882 went nine days without a first response in June, and that was the week you had alarms on the press. The gateway on line 3 was dark for eleven days in Q2 and we didn't tell you — you told us. You've had two different CSMs since last April. And of the forty licenses you're paying for, your planners — twelve of them — have three logins between them. Second shift has never opened it. That's what I've got from my side. What am I missing, and what did it actually cost you?" Then stop talking. Do not fill the silence. This pause is where the meeting is won.
- 3
The listening phase — let it be worse than you thought (40-50% of the call)
No "but." No "to be fair." Do not defend the one incident where their tech mounted the sensor on the wrong bearing housing. You may be right and you will lose the renewal being right. Use these, and follow the emotional word: • "You said the August press failure — walk me through that day. When did you know?" • "Who did you have to explain that to? Did it come up with your VP of Manufacturing or at the corporate ops review?" • "What did it cost you in unplanned hours on line 3 that month? Do you have the number by asset?" • "When the planners didn't pick it up — was that a training gap on our side or did the work never get assigned to anybody?" • "What did you tell your Maintenance Manager when he asked whether we were worth keeping?" Then read it back visibly: "So: nine-day response in June during your worst stretch, a dead gateway you found before we did, the CMMS write-back we promised in Q1 and never shipped, and a rollout to the planners that never happened. Anything else?" Ask "anything else?" a second time. There is almost always a second thing, and it's usually the political one.
- 4
The apology — once, specific, no hedge
"The Q2 response times were our failure. We reorganised the support queue in April and your tickets got stacked behind enterprise escalations. That's an explanation, not an excuse — you're paying for a 24-hour P1 SLA and we missed it seven times between April and June. And the gateway monitoring should never have been on you. We built alerting for sensor dropout and it wasn't switched on for your site." One apology. Do not repeat it later in the call — repeated apology reads as a negotiating position. Move.
- 5
Proof of change — show, don't promise
"I'm not going to tell you we're investing in support. You've heard that. Three things I can show you: One — the queue is split by segment now and you have a named support engineer, Marcus, as of September. Since then you've opened nine tickets and your median first response is 3.2 hours. That's your data, not a company average. I'll send the list. Two — I had the team clear the three tickets sitting open in your queue last week. The battery kit for the fourteen dark sensors shipped Thursday, and a field tech is booked to re-mount the four on the press line. You didn't ask for that and I'm not charging for it. Three — there's a stamping plant two hours from you, similar size, who had the same Q2 experience with us and stayed. Their Reliability Manager will take a call from your team. I'll make the intro, you can ask him anything you want including whether we're worth it." If nothing has actually changed on your side, say so and change what you control: your own coverage cadence, a named escalation path, an exec sponsor. Do not manufacture progress. They will check.
- 6
Rebuild on what works — find the person, not the feature
"You said the asset health review is the one thing you'd miss. Tell me about that — who runs it and what did it replace?" "The gearbox on line 3 in March. Walk me through what happened — how many days' warning did you get, and what did you do with it?" "You told me last year that a shutdown hour on line 3 costs you around $9,400 all-in with the recovery overtime. Is that still the number? Because if we converted that gearbox from an unplanned six-hour hit into a planned Saturday job, that's the one event I want in the payback math." "What's your planned-versus-reactive work order ratio doing? You were at 38% planned when we started. Has it moved at all, and does your Reliability Engineering Manager attribute any of it to us?" "If we went away on the 31st, whose Monday breaks?" That last answer names your remaining champion. He probably wasn't invited to this call. Getting him into the next one is a bigger move than any discount.
- 7
Handling the competitor — surface it yourself
"I'd assume you've been talking to [Competitor] — I'd be surprised if you hadn't after the year you've had. What did you like about them?" Listen. Do not disparage. Then find out how far it's gone: • "Have they been on site? Did they scope the mounting on line 3 and the two cells with the guarding issue?" • "Is the pricing in writing, and does it include gateways and installation or is that a separate line?" • "Has your IT/OT security person looked at their architecture yet? Because that took us five weeks here and I don't think that's unusual." • "Have they scoped the migration of your eighteen months of vibration history? Because your MTBF trend on the top three assets only exists because of that baseline." Then reframe, plainly and without heat: "Here's the honest comparison. Their number is lower and I'm not going to argue it isn't. What it doesn't include is re-mounting sixty sensors, retraining the one team that did adopt, and eighteen months of baseline data that resets to zero the day you switch — which means your condition thresholds go back to guessing for two quarters on the constraint. And the risk you can't price is that you inherit their version of the support problem you just lived through with us, with none of the goodwill and none of the credits." Do not match on price here. Price is the last section.
- 8
The 90-day plan — build it live, in their words, with their names on it
"Can we build the next ninety days out loud, right now? Four columns — what, who by name, by when, and what done looks like. And I want half these rows to have your people on them, because last year's rollout failed partly because nobody on your side owned it. Row one — planner adoption. Dana runs two on-site sessions for the twelve planners and the two second-shift supervisors, week of the 14th, on the floor not in a conference room. Done looks like eight of fourteen weekly active by day 60. Your side: your Maintenance Manager makes the Monday health review a standing item in the daily production meeting. If that doesn't happen, the training won't stick and we both know it. Row two — alerts become work orders. Right now an alert goes to a shared inbox and dies there. By day 30 every critical alert generates a work order in your CMMS with a named owner. If the write-back integration isn't ready, we do it manually via Marcus. Done looks like zero alerts older than 72 hours with no owner. Row three — spares. Your Reliability Engineering Manager and I pull the top ten monitored assets and check which replacement parts are actually on the shelf. The gearbox lesson from August was that a nine-day warning is worth nothing if the part is 22 weeks out of Germany. Done looks like a critical spares gap list on your Plant Manager's desk by day 45. Row four — support. Named engineer, direct line, 4-hour P1 first response, written into the contract with service credits. Effective at signature. Row five — governance. 30/60/90 reviews with a written usage and downtime report. First one dated, in your calendar before we hang up. And the one I can't do: the eMaint write-back isn't shipping before Q3. I committed to it last year and it didn't happen and I'm not going to say it twice. It's in the plan as a Q3 item with no earlier date. What's missing? What would you add, and what can your side realistically commit to?"
- 9
The commercial conversation — only after they've agreed the plan is real
"If we can agree that plan is real, can I walk you through what renewal would look like?" Structure before number: "You're paying for forty licenses and using six. I'm not going to renew you on forty and discount them — I'd rather be right than big. Take it to twenty, which covers the planners, both shifts, reliability, and your Quality Manager if she wants the scrap correlation view. That's a real reduction in your annual spend, not a courtesy discount, and it kills the shelfware argument with your VP of Operations permanently. On term — I'd normally ask for two years. Given the year you've had, I'd rather do twelve months with a break clause at six. If we haven't hit eight of fourteen planners weekly active and your unplanned hours on line 3 haven't moved, you walk with 30 days' notice and no penalty. I'm putting the risk on my side because that's where it belongs. On the Q2 misses — I'm not offering a discount as an apology, because a price cut isn't an apology and you'd read it as one. What I'll do is service credits for April through June, the three months we actually failed you. That's specific, it's finite, and it doesn't pretend the year didn't happen. If you want a lower run rate than that, I need something traded for it — a reference call for the plant down the road, or a case study once the planner numbers are real, or signature before the 31st so I'm not chasing this into your fiscal year." If they need it off the capital line entirely: "Is this shaped like capex for you, or can it sit as a monthly line under MRO or controllable spend? Different approval path, and monthly usually lands inside a Plant Manager's signing authority without an AR."
- 10
Multi-thread and close — do not hang up without these four
"Walk me through what actually happens between now and the 31st. Who else signs — does this go to your VP of Manufacturing, does corporate procurement have to touch it, does Legal need to see the SLA language?" "Does procurement already have [Competitor]'s quote? If they've had it since October I'd rather know now than find out in week five." "I want your Reliability Engineering Manager in the next meeting. He built the workflow, he's the one who'd have to rebuild it somewhere else, and he hasn't been in this conversation at all. Can we get him and your Maintenance Manager on a 30-minute plan review?" "I'd also like to bring my VP in for fifteen minutes. Not to sell — to say to your face what he said to me about the Q2 queue." Book the date live. Never "I'll follow up." Then test the temperature honestly: "On a scale where 1 is you've already decided to leave and 10 is this is done — where are we right now, and what moves it a point?" Take the honest answer over the polite one. Within 24 hours send: the 90-day plan with names and dates, the ticket log you referenced, the reference intro, and a one-page summary of what they told you went wrong — in their words, not yours. That last document does more work than any proposal.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Contract's up on the 31st, and I know that's why this is on the calendar. I don't want to talk about the renewal yet. I want to talk about this year, because it wasn't the year we sold you. Ticket 41-882 sat nine days without a first response in June — that was the same week you had alarms on the 800-ton press. The gateway on line 3 was dark eleven days in Q2 and your guy told us, we didn't tell you. Two CSM changes. And of forty licenses, your twelve planners have three logins between them. That's what I see. What am I missing?
Buyer
What you're missing is August. Your system flagged the gearbox on the press nine days out. Great. The replacement was 22 weeks out of Germany. So I sat there with a nine-day warning and no part, and I still ate six hours unplanned and a Saturday. Tell me what I paid you for.
Rep
Tell me about that Saturday.
Buyer
The Saturday's not the problem. The problem is I'd already told my VP of Operations we bought this so we'd stop being surprised. Then I'm on the phone Monday morning with a tier 1 supplier quality guy explaining why we're short, and my own boss is asking me what happened to the monitoring investment. I looked like I'd bought a dashboard.
Rep
So the cost wasn't the six hours. It was that you'd spent credibility on us and we didn't cover you when it mattered. Who else heard about it?
Buyer
Corporate ops review. It's a slide now. "Predictive maintenance pilot — status." And I've got a rep from your competitor emailing me a number 28% under yours, which is going to look very reasonable on that slide.
Rep
It will. Before I say anything about them — anything else on our side? Anything I haven't named?
Buyer
The write-back. You told me in the Q1 QBR that alerts would drop straight into eMaint as work orders. That was the whole reason my Maintenance Manager agreed to it. It never shipped, so alerts go to a shared inbox, and inside three weeks my planners learned to ignore the inbox. Same thing that happened with the downtime tracking tool we bought in 2021.
Rep
That one's the actual failure, isn't it. The nine-day ticket was bad. The write-back is why adoption never happened. Let me say the Q2 piece straight: we reorganised the support queue in April, your tickets got stacked behind enterprise escalations, and we missed your 24-hour P1 SLA seven times. That's an explanation, not an excuse. And the write-back I committed to in Q1 isn't shipping before Q3. I'm telling you that now rather than promising it again.
Buyer
At least that's honest. But you understand my position. My maintenance team is reactive all day. They don't have time to babysit another tool, my 30-year millwright retires in the spring and nobody behind him reads a vibration chart, and capex is locked — the AR window for next year closed in Q3.
Rep
On the AR — is this shaped like capex for you, or can it run monthly under MRO or controllable spend? Because monthly usually sits inside your signing authority and doesn't go near an appropriation request. On the millwright — that's actually the argument for keeping something, not dropping it. When he goes, the only place his judgement exists in writing is the eighteen months of baseline on those sixty assets. But let me ask you the thing I care about most. In March your Reliability Engineering Manager caught the line 3 gearbox nine days out and you converted it to a planned weekend job. Same asset class, different outcome. Why did that one work and August didn't?
Buyer
Because Ray was watching it himself and he had the bearing on the shelf. That's it. That's the whole difference. It's not the software, it's Ray.
Rep
Right. So the gap isn't detection, it's whether the alert becomes a work order with a named owner and a part on the shelf. Which is a thing we can put in a plan and both own. Here's what I'd propose for the next ninety days, and I want half the rows to have your people's names on them. Dana runs two on-floor sessions for the twelve planners and both second-shift supervisors, week of the 14th — done is eight of fourteen weekly active by day 60. Your Maintenance Manager makes Ray's Monday health review a standing item in the production meeting. And Ray and I pull the top ten monitored assets and check which spares are actually on the shelf, so August doesn't repeat. Gap list on your desk by day 45. What's wrong with that?
Buyer
Nothing's wrong with it. What's wrong is I've heard a version of it before and then you disappeared for two months. And I'm still looking at a number that's 28% lower.
Rep
Then don't take my word for it, take a break clause. Twelve months, and at six months if we haven't hit eight of fourteen planners weekly active and your unplanned hours on line 3 haven't moved, you leave with 30 days' notice, no penalty. Plus the 4-hour P1 SLA in the contract with service credits attached, so the failure costs me money automatically instead of you chasing me. And I'm dropping you from forty licenses to twenty because you're not using forty — that's a real reduction, not a courtesy discount. On their number: has anyone scoped what happens to your eighteen months of baseline when you switch? Because your MTBF trend on the top three assets is the only reason Ray can call a gearbox nine days out. Day one on a new platform, that's back to zero.
Buyer
Nobody's mentioned that, no. Procurement's had their quote since October though, so I'm not the only one in this.
Rep
Then let's get in front of it. Two things before we hang up. One — thirty minutes next week with you, your Maintenance Manager, and Ray, to review the plan. Ray built the workflow and he hasn't been in this conversation once. Two — my VP joins for fifteen minutes of that, not to sell, to say to you directly what he said to me about the Q2 queue. Tuesday or Thursday?
Buyer
Thursday, and bring the ticket log. If Ray says the migration is a real problem, I'll listen. If he shrugs, I'm going to take the cheaper number and I won't feel bad about it.
Rep
That's fair and I'd do the same. Thursday, and the ticket log, the 90-day plan with names, and a one-pager of what you told me went wrong today — in your words — all in your inbox by tomorrow morning. Last thing: 1 is you've already decided to leave, 10 is this is done. Where are we?
Buyer
Four. It was a two before you opened with the ticket numbers.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Capex is locked. The AR window closed in Q3 and I'm not reopening it for a renewal."” | Fair, and I'm not going to pretend I can unlock it. Two questions. First — is this shaped like capex for you, or can it run as a monthly opex line under MRO or controllable spend? That's usually a different approval path and often inside a Plant Manager's signing authority without touching an appropriation request. Second — if it has to be an AR either way, the work of building the number has to happen now. The downtime baseline on your worst three assets and the payback math is a two-week job, not an August-from-memory job. Let me help you build it. If it doesn't clear your hurdle rate you throw it out and I've cost you an hour. |
| “"My planners never used it. Same as the MES, same as the downtime tool. That's not a contract problem, that's a floor problem — and it won't be different next year."” | It's a floor problem and it's my problem, and I'd rather split it honestly. Our half: the write-back never shipped, so an alert landed in a shared inbox with no owner, and maintenance teams learn to ignore an inbox inside three weeks. Your half: nobody on your side owned the rollout, so the planners were never told it was part of the job. If we do this again, the plan has your Maintenance Manager's name on a row — the Monday health review becomes a standing item in the production meeting — or we don't do it. What I need from you is honest: was the last failure change management or tooling? Because if it's change management, we'll fail the same way and I'd rather find that out today than in June. |
| “"You gave us nine days on the gearbox and the part was 22 weeks out. Warning without a spare is useless."” | You're right, and that's the part of last year I'd fix first — with or without a contract. Detection is only half of it; the other half is whether the critical spare for that asset is on the shelf, and yours has been squeezed for working capital like everyone's. Row three of the plan is Ray and me going through the top ten monitored assets and building a spares gap list, so the next nine-day notice lands on a part that exists. If the answer for a given asset is "22 weeks, never in stock," then that asset needs a different strategy — run-to-failure with a rebuild kit, or a redundant path — and knowing that is worth something too. |
| “"Your competitor is 28% cheaper and procurement's had the quote since October."” | I'd assume so, and I'm not going to argue their number isn't lower. What I'd want priced next to it: re-mounting sixty sensors, retraining the one team that did adopt, and eighteen months of vibration baseline that resets to zero the day you switch — which means your condition thresholds are guesswork for two quarters on the constraint, right when your millwright retires. Then the risk nobody quotes: their support has a Q2 too, and you'll have no credits, no history, and no leverage when it happens. Have they scoped the migration and been through your IT/OT security review? Ours took five weeks here. If they've done all that and it still nets out cheaper, that's a real decision and I'll respect it. |
| “"My team is reactive all day. They don't have bandwidth for another tool, and I've got a controlled shipping level 1 at my tier 1 customer right now."” | Then this is the wrong month to start anything and I'm not going to pretend otherwise — the plan starts when the containment ends, and I'll date it that way. On bandwidth: 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 four of last quarter's emergency callouts moving into planned weekend work would free enough wrench time to matter. You were at 38% planned when we started. Where is that ratio now? If it hasn't moved at all in twelve months, that's a fair reason to fire us. |
| “"Just tell me your best number and I'll take it to my VP of Operations."” | I'll get you a number today, but if I lead with a discount I've told you the whole year was a pricing dispute, and it wasn't. Here's what I'd rather do. Drop you from forty licenses to twenty, because you're using six and I'd rather be right than big — that's a real reduction your VP can see. Service credits for April through June, the three months we actually failed you, because credits are the honest instrument and a price cut isn't an apology. And a break clause at six months tied to adoption and your unplanned hours on line 3, so the risk sits with me. If you want to go below that, trade me something — a reference call, a case study once the planner numbers are real, or signature before the 31st. |
Questions reps ask about this call
- What makes a manufacturing renewal call different from a normal renewal?
Two things: the buying calendar and the shelfware scar tissue. Plant Managers submit appropriation requests in Q3 for the following year, so a renewal that has slipped into capex is often unwinnable inside six weeks — which is why the first commercial question is whether it can run as a monthly opex line under MRO or controllable spend instead. The second difference is that every plant has already bought an MES, a CMMS module, or a downtime tracking tool that nobody uses. Your adoption failure isn't read as a vendor problem; it's read as confirmation of a pattern they've been burned by three times. You have to name the adoption gap by role and by number before they do.
- How early should I start a save call cycle before a manufacturing contract expires?
Six weeks is late but workable if you multi-thread immediately. The real constraint is that procurement at a manufacturing parent company often already has the competing quote — in this scenario since October — and the business-side conversation you're having is not where the decision dies. Ask on the first call: "Does corporate procurement already have their quote, and who signs above you?" If your renewal touches an AR at all, you should be building the downtime baseline and payback math six months out, not six weeks.
- Should I match a competitor who is 20-30% cheaper on a sensor or monitoring renewal?
Not in this call, and probably not at all as a straight match. Matching before you've re-established value tells them your list price was always soft and permanently resets your floor. Reframe to total switching cost instead: re-mounting the sensor fleet, retraining the one team that did adopt, the IT/OT security review they'll have to run again, and the historical baseline that resets to zero — which means condition thresholds on the constraint line are guesswork for two quarters. If you must move on price, cut seats to actual usage rather than discounting the whole contract, and use service credits for the specific months you failed rather than a permanent reduction.
- How do I acknowledge a bad year without sounding like I'm grovelling?
Apologise once, specifically, with numbers, then move. "We missed your 24-hour P1 SLA seven times between April and June because we reorganised the queue and your tickets stacked behind enterprise escalations — that's an explanation, not an excuse." What kills you is the generic version ("sorry things haven't been perfect"), which tells them you never actually looked at the tickets, and the repeated version, which reads as a negotiating posture. Never defend an incident where their own team was at fault — the sensor mounted on the wrong bearing housing, the alert nobody opened. You can be right and lose the renewal.
- Who else should be on the call besides the person who signed last year?
Whoever built the one workflow that works — usually the Reliability Engineering Manager or a maintenance planner — because they carry the switching cost in their head and they are rarely invited to renewal meetings. Then the economic buyer above your contact: a VP of Manufacturing or VP of Operations, especially if signing authority moved or your renewal now needs an AR. Also check whether your original champion is still in the seat. Plant Managers rotate between sites, and treating the person on the call as the decision-maker because they signed twelve months ago is how saves fail in week five.
- How do I practise this call before I run it live?
Rehearse the first 45 seconds out loud until you can say the ticket numbers, the dates, and the license-versus-usage split from memory without reading. That opening is the whole call. Then drill the hard turns: the buyer who says your nine-day warning was worthless because the spare was 22 weeks out, the one who says capex is locked, and the one who says "just give me your best number." DrillCall lets you run those as voice roleplays with a Plant Manager persona who pushes back the way a real one does — flat, unimpressed, and more interested in his corporate ops review slide than your roadmap.