Manufacturing · Upsell Call
The Upsell Script for Manufacturing Customers: Turning a Plant Account Review Into an Expansion
You sold this plant eighteen months ago. Condition monitoring on Press 3 and the two extruders feeding the constraint, because that's where the unplanned hours were and that's what fit under the Plant Manager's signing authority without going to a corporate AR. It went fine. The Maintenance Manager likes you. Nobody's complained.
Now you need the weld cells, or the second plant, or the module that pushes alerts straight into their CMMS as work orders with a named owner. And the person who picks up the phone — Plant Manager, VP of Manufacturing, or the Reliability Engineering Manager who championed you — is going to be defensive on three fronts before you finish your first sentence: capex is locked and the AR cycle closed in Q3, their maintenance team is running reactive all day and cannot absorb another rollout, and somewhere in the back of their head is the suspicion that they aren't even getting full value from the sensors already on the floor. Twelve of your gateways went quiet in March and nobody told you.
This call is won in the prep. If you open with their actual numbers — unplanned downtime hours on Press 3 before and after, the planned-versus-reactive work order ratio, how many of your alerts actually became a work order instead of dying in a shared inbox — you get a real conversation about the next asset group. If you open with "I wanted to walk you through our new module," you get a polite ten minutes and a request for a PDF that will never be opened. This playbook is the version that gets signed as an amendment to the existing contract instead of a new AR next fall.
The upsell call script
Say it in your own words. The structure is the part that matters.
- 1
0. Pre-call usage audit — do not dial without this
Fill these blanks from your own systems before you touch the phone: - **Coverage**: assets under contract vs. assets actually reporting. Name the dark corners out loud: "You're licensed for 40 monitoring points, 34 are transmitting, and the 6 on the #2 extruder line have been offline since the March shutdown." - **Alert-to-action**: how many alerts you generated last quarter, how many became a work order in their CMMS, how many were closed. This is the number that predicts whether they'll buy again. - **Outcome, in their data**: unplanned downtime hours per month on the monitored assets before vs. now. MTBF trend on the constraint. Percent planned vs. reactive work orders. Not your benchmark — theirs. - **Champion status**: is the Reliability Engineering Manager who signed off still in the role, or did they get pulled onto the PPAP for the new program? Has the Plant Manager changed? Plants rotate leadership constantly. - **Commercials**: contract value, renewal date, fiscal year end, whether this was bought as capex through an AR or as an MRO/opex line, current signing authority threshold. - **Support history**: open tickets, the gateway that dropped, any escalation in the last 90 days. An unresolved issue kills this call and you should know before you dial. The test: can you say one thing about their plant floor they'd be mildly surprised you knew? If not, do the work.
- 2
1. Frame the call in the first thirty seconds
"Thanks for the time. Two things. First, I pulled your data from the last two quarters and there's a pattern on the extruder side I want to check with you, because I think it means something and I might be reading it wrong. Second, depending on what you tell me, there's a piece of this I think is relevant to your line 4 problem — and if it isn't, I'll say so and we'll spend the rest of the time on the assets you already have. Fair?" No ambush, no sandbagging. You've set an agenda, signalled you did homework, and pre-committed to walking away, which lowers their guard faster than any small talk about the Lions game.
- 3
2. Make them say the result out loud, in their numbers
"When we started, Press 3 was running roughly [X] unplanned hours a month and it was the reason you were running Saturdays. Last quarter my data says it's down around [Y], and your planned-versus-reactive ratio moved from [A] to [B]. Does that match how it feels on your floor, or am I reading it optimistically?" Let them correct you. Their correction is worth more than your number — it tells you which metric they actually defend in front of the VP of Manufacturing. Write it down verbatim; it becomes the first line of the AR justification they'll write later. **If they can't confirm a result, stop the upsell.** "Then let's not talk about anything new today. Let's fix the fact that you're paying for something you can't point to on a downtime report." That's not a lost call — that's the only version of this call that protects the renewal.
- 4
3. Raise the underuse problem before they do
"Here's what I'd push back on if I were sitting in your chair: six of my sensors have been dark since March and you've got alerts from last quarter that never became a work order. Why would you buy more coverage before you've used the coverage you've got? So let me tell you what I think is actually happening — those alerts didn't die because the monitoring is wrong, they died because they went to a shared inbox instead of into your CMMS with a named owner and a spare on the shelf. Your team learned to ignore them inside three weeks. That's a routing problem, not a sensor problem." Reframe unused capacity as **unrouted work**, not wasted spend. Then be honest about whether the expansion fixes it. Sometimes the right answer is: "It doesn't. You have an alert-routing problem, not a coverage gap, and we should fix that first, free, before you spend another dollar." Saying that buys you the right to come back next quarter.
- 5
4. Find the seam — reopen what got cut from the original scope
Never lead with the module. Lead with where value still leaks. Highest-yield questions on this call: - "What did we deliberately leave out of scope last time because it was too big a bite for the first AR?" (Most upsells were already scoped once and cut.) - "What generated the Monday morning fire drill last month — which asset, which shift?" - "When a bearing alert fires at 2am on second shift, what does your supervisor actually do with it?" - "Who's asking you for a report on this that you can't produce today — corporate reliability, your customer's SQE?" - "Which asset is on your downtime Pareto that we're not watching?" Then shut up. The Maintenance Manager will name line 4 or the paint booth or the plant in Ohio without you pitching anything.
- 6
5. Build the incremental case in their arithmetic
The bar isn't "this is valuable." It's "this beats the next best use of the same money and the same three weeks of my Reliability Engineering Manager's time." - **The unit**: "A shutdown hour on line 4 — what's your number? You quoted me [$X] for Press 3." - **The volume**: "Your downtime report shows [N] unplanned hours on those assets last quarter." - **The capture rate**: "If we catch half of those with enough lead time to plan them into a weekend window — and I'd rather under-promise — that's [N/2] hours moved from unplanned to planned." - **The avoided expedite**: "Plus whatever the air freight on that gearbox cost you. That hits your controllable spend, not corporate's." - **The net, price said out loud, unprompted**: "It's [$Z] a month on top of what you're paying today. Against that number, payback lands around [M] months. If you think my capture rate is generous, give me the number you believe and we'll rerun it right now." Handing them the pencil on the assumptions is what makes it a business case instead of a pitch.
- 7
6. Cost the implementation in hours and names
Budget is the stated objection; bandwidth is the real one, and in a plant it's usually true. "Here's the whole ask on your side: one two-hour walkdown with your Maintenance Manager to pick mounting points, one 90-minute session with whoever owns the CMMS to map alert-to-work-order, and then about an hour a week from your Reliability Engineering Manager for three weeks. No PLC connection, read-only, cellular gateway that never touches your plant network. Install is our tech, done during your existing weekend PM window so we're not taking production time. If it needs more than that, I've mis-scoped it and I'll tell you." Put what you can absorb on the table here — install labor, templates, your CSM running the second-shift enablement — not later as a concession.
- 8
7. The ask: small, specific, reversible, co-termed
"Give me the three weld cells for one quarter. You define what success looks like — I'd suggest unplanned hours on those three assets and how many alerts turn into a planned work order. If we don't hit it, we pull the hardware and you owe nothing further. If we do, we roll it to line 4 and the Ohio plant at your renewal and co-term it, so you're managing one contract and one PO instead of two." Co-terming to the existing renewal is the single most underused unlock on a manufacturing expansion. It turns a new purchase — which means a new AR, a new hurdle rate conversation, possibly three competitive quotes — into an amendment on a contract procurement already approved.
- 9
8. Route the money before you leave the call
Ask directly, because the wrong path costs you a quarter: "Two questions on mechanics. First — is this shaped like capex to you, or can it run as a monthly line under MRO or controllable spend? Because if it's opex it's usually a different approval path and often inside your signing authority. Second — last time this went through [name] on the AR. Is that still the path, or has the threshold changed since the new CFO landed?" If a new procurement policy requires three bids above $25K, you need to know today, not in week six. And if the answer is "next year's AR," your job on this call becomes: help them build the number now, while the downtime data is fresh, instead of writing it from memory in August.
- 10
9. Park signals — walk away rather than push
Do not push the expansion through any of these. Fix them first: - An open escalation or a gateway that's been down more than two weeks - Your champion just got pulled onto a launch, promoted, or moved to another plant - Renewal inside 60 days with the value question still unanswered - Flat or declining alert-to-work-order conversion you can't explain - A corporate cost review, hiring freeze, or a customer putting them on controlled shipping level 1 — they have no attention for you this month Pushing through any of these converts a healthy plant account into a churn risk to book an incremental deal.
- 11
10. Close and document — write the email your champion forwards
Same day, one email, structured so the Plant Manager can paste it into an AR justification: 1. The result they confirmed, in their words: "Unplanned hours on Press 3 down from X to Y; planned work orders up from A% to B%." 2. The gap they described, in their words: "Line 4 is now the top asset on the downtime Pareto and nothing is watching it." 3. The math with their assumptions, labelled as theirs. 4. The price, plainly, monthly and annualized. 5. The implementation ask in hours and names. 6. The pilot scope, the success metric they chose, the decision date. 7. One named next step with a date on it. Write it for the VP of Operations who will read it without you in the room, not for your CRM.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for making time. Two things and then I'll get out of your way. First — I pulled your data from the last two quarters and there's a pattern I want to check, because I might be reading it wrong. Second, depending on what you say, there's something I think is relevant to line 4. If it isn't, I'll tell you and we'll spend the rest of the call on what you've already got. Fair?
Buyer
Sure. Though I'll tell you now, before you get too far — capex is done for the year. Our AR went in last September and I got the press rebuild and the roof, not much else.
Rep
Noted, and I'm not going to pretend I can unlock that. Let's do the data first. When we started, Press 3 was averaging 31 unplanned hours a month and it was why you were running Saturdays in Q1. My numbers say last quarter it was about 11, and your planned-versus-reactive work order ratio went from 38% planned to 61%. Does that match your floor, or am I reading it generously?
Buyer
Partly. The 61% is real but I'd be careful giving you credit for all of it — we also rebuilt the PM schedule last spring and my Maintenance Manager tightened up compliance. And honestly, half the alerts your system throws, my second shift supervisor doesn't act on. They come into an inbox nobody owns.
Rep
That's fair on both counts and I'd rather have the honest version. Take the PM schedule out of it — what about MTBF on Press 3 specifically? My read is you went from a mean time between failures of about six weeks to something north of four months on the main drive. Is that consistent with what your reliability guy sees?
Buyer
Yeah, that one I'll give you. We haven't had a drive-side surprise on 3 since last summer. But your alert problem is real. We got a notice in November on the extruder and nobody did anything with it for nine days.
Rep
Then before I ask you for a dollar, that's the thing to fix, and I'd fix it whether or not you buy anything else. An alert that isn't a work order in your CMMS with a named owner and a spare on the shelf is noise, and your team learns to ignore it in about three weeks. I can have our CSM sit with whoever owns your CMMS and route alerts in as work orders directly — no cost, it's in your current contract. Can I get ninety minutes with that person?
Buyer
That'd be my Reliability Engineering Manager, and that's the other problem — he's buried on the PPAP for the new program launch. He's got nothing until at least April. Which is also why I'm going to say no to whatever you're about to ask for. My team is underwater.
Rep
Understood, and I'm not going to argue with bandwidth because you know your plant and I don't. So let me shrink what I'd ask for and you tell me if it's still too much. First though — when we scoped the original job, we cut two things. The weld cells and the Ohio plant. Is line 4 still where the Monday morning fire drills come from?
Buyer
Line 4 is my top asset on the Pareto now, yes. But here's the thing that makes me cynical about all of this — we knew the gearbox on 4 was going. Everybody knew. It's a 22-week lead time out of Germany and working capital won't let me put a spare on the shelf. So knowing earlier doesn't actually help me.
Rep
It helps you differently than you're thinking. Knowing nine days out doesn't help on a 22-week part, you're right. Knowing five months out is the only thing that does — that's the difference between ordering it on a normal PO and eating an air freight expedite plus however many hours of unplanned downtime while you wait. What did that gearbox event actually cost you, all in?
Buyer
Off the top of my head, we were down about fourteen hours across two events, and the expedite was somewhere north of nine grand on freight alone. That hits my controllable spend, not corporate's, which is the part that annoys me.
Rep
Then let's do the arithmetic in your numbers, not mine. Fourteen hours on line 4 — what's a shutdown hour worth there? You gave me a figure for Press 3 last year.
Buyer
Line 4 is worse than Press 3 because everything routes through it. Call it two thousand an hour, and that's conservative, it doesn't count the overtime to catch up.
Rep
So one event, one asset, was roughly twenty-eight thousand in downtime plus nine in freight. Coverage on the three weld cells and the line 4 drivetrain is $1,900 a month on top of what you're paying — $22,800 a year. If we catch one of those a year, and I'd rather under-promise than tell you we'll catch all of them, you're ahead. If you think one a year is optimistic, tell me the number you believe and I'll rerun it while we're on the phone.
Buyer
Even if the math works, $22,800 is over my signing authority — I'm at $25K for capex but procurement changed the rules in January. Anything over $25K annualized needs three quotes now. That's a three-month exercise I don't have time for.
Rep
Then let's not trigger it. Two options. One — it's monthly, it's a service, it's not capex; if it can sit under MRO or controllable spend it's a different approval path and it's inside your authority. Two — we co-term it to your existing renewal in October as an amendment to the contract procurement already approved, rather than a new purchase. I'd want your procurement person's read on which is cleaner, and I'd rather get that in week one than week six.
Buyer
The MRO route might work. What does it cost me in my people's time, honestly? Because if you tell me a project team I'm out.
Rep
One two-hour walkdown with your Maintenance Manager to pick mounting points. Install is my tech, done inside your existing weekend PM window so we're not taking production. Then one 90-minute CMMS mapping session — and I'll do that with whoever backs up your reliability guy, not him, since he's on the PPAP. After that, about an hour a week for three weeks. No PLC connection, read-only, cellular gateway that never touches your network. That's the whole ask.
Buyer
Alright. I'm not committing to anything today, but I'd look at the weld cells if it's a trial.
Rep
Then here's my proposal and you set the bar. One quarter, three weld cells plus the line 4 drivetrain. You define success — I'd suggest unplanned hours on those four assets and what percentage of our alerts became a closed work order, because that's the metric that failed you in November. If we miss it, we pull the hardware and you owe nothing further. If we hit it, it rolls into the October renewal co-termed. I'll send you the recap today with your numbers, not mine, written so you can forward it to your VP without editing it. Who else needs to see it?
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Capex is locked. Our AR went in last September — come back for next year's cycle.” | Fair, and I won't pretend I can unlock it. Two questions. First, is this shaped like capex to you, or can it run as a monthly line under MRO or controllable spend? Because that's usually a different approval path and often sits inside your signing authority. Second, if we're building next year's AR anyway, the work of building it — the downtime baseline on your worst three assets, the payback math, the expedite freight you ate this year — has to happen now, or you'll be writing it from memory in August. Let me help you build the number. If it doesn't clear your hurdle rate, throw it out and I'll stop calling. |
| “We're barely using what we already bought. Six of your sensors have been offline since the shutdown and half the alerts get ignored.” | You're right and I should have caught the dark gateways before you told me. I'll have those back up this month at no cost. On the alerts — that's the more important one, and I don't think it's a sensor problem. An alert that lands in a shared inbox instead of becoming a work order in your CMMS with a named owner and a spare on the shelf is noise, and maintenance learns to ignore it in three weeks. Before we discuss anything new, let me fix routing — that's included in what you already pay. If I can't get alert-to-work-order conversion up, you shouldn't buy another asset from me and I'll say so myself. |
| “My maintenance team is reactive all day. They can't absorb another rollout, and my reliability engineer is buried on the PPAP for the launch.” | That's almost always true and I'm not going to argue with it — you know your plant. So let me shrink the ask instead. Two-hour walkdown with your Maintenance Manager, install by my tech inside your existing weekend PM window, and the CMMS mapping session with his backup rather than him. Then an hour a week for three weeks. If your honest answer is that even that lands after the launch, give me a start date in May rather than a 'circle back' — I'll hold the pricing and put it in the calendar. |
| “We already have a CMMS and our PM compliance is at 95%. What's this actually adding?” | Good — most plants I walk aren't there. 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 your intervals are calendar-based, not condition-based — you're changing bearings with life left in them and missing the ones that fail early. What's your MTBF trend on your top three assets over the last twelve months? If it's flat while PM compliance is high, that gap is exactly what we're covering, and on Press 3 you've already seen what it looks like when it closes. |
| “The second plant's IT team will never let you on the network, and I'm not touching PLCs.” | I'd be worried if you said yes fast. This doesn't touch the control layer — no PLC connection, read-only, and it runs on a separate cellular gateway that never sees your plant network. Same architecture that's been on Press 3 for eighteen months, which is a reference your IT/OT security person can call and verify internally. What I'd ask for is fifteen minutes with them in week one, not week six, because if there's a blocker I want to hit it before your team spends two months on a business case. |
| “Just send me the pricing and I'll look at it when budget season comes around.” | I'll send it, but a price sheet won't help you in an AR. What would help is fifteen minutes to put your numbers into it — what a shutdown hour costs on line 4, what the freight expedite on the gearbox actually ran, what your unplanned hours on those assets were last quarter. You have those numbers; I don't. I'll build the payback on your assumptions, send it in a format your VP of Operations can read without me in the room, and if it doesn't clear your hurdle rate under eighteen months I'll tell you that on the call. |
Questions reps ask about this call
- What has to be in the pre-call usage audit before I run an upsell script for manufacturing customers?
Six things, all pulled from your own systems: assets under contract versus assets actually transmitting (name the dark gateways out loud); alert-to-work-order conversion for the last quarter; the outcome metric in their data, not your benchmark — unplanned downtime hours on the monitored assets, MTBF trend on the constraint, planned-versus-reactive work order ratio; champion status, because Reliability Engineering Managers get pulled onto launch PPAPs and Plant Managers rotate; commercial details including renewal date, fiscal year end, and whether the original deal was bought as capex through an AR or as an MRO line; and any open ticket or escalation in the last 90 days. If you can't say one thing about their floor they'd be mildly surprised you knew, don't dial.
- How do I upsell when the plant says capex is locked for the year?
Don't fight it — reroute it. Ask two questions. Is this shaped like capex, or can it run monthly under MRO or controllable spend, which is usually a different approval path and often inside the Plant Manager's signing authority? And can it be co-termed to the existing renewal as an amendment rather than a new purchase, which avoids a fresh AR and, in many plants now, the three-competitive-quotes rule above $25K. If neither works, the fallback isn't a discount — it's helping them build next year's AR now, while the downtime data and the expedite freight invoices are fresh.
- The customer says they barely use what they already bought. Do I still pitch the expansion?
Not until you've dealt with it, and you should raise it before they do. In manufacturing the usual failure isn't the hardware, it's routing: alerts land in a shared inbox instead of becoming a work order in the CMMS with a named owner and a spare on the shelf, and the maintenance team stops reading them within about three weeks. Fix that first, at no charge, as a value-realization call. If the honest answer is "this is an adoption problem, not a coverage gap," say so. Conceding that buys you the right to come back next quarter with credibility intact; pushing through it turns a renewable plant into a churn risk.
- Which metrics should appear in the script itself?
Use theirs, sourced from their data. The ones that carry weight on this call are unplanned downtime hours per month by asset, percent planned versus reactive work orders, MTBF and MTTR on the critical assets, OEE on the constraint line, and where quality is involved, first pass yield and customer PPM. Pair each with a dollar figure the buyer supplies — the cost of a shutdown hour on the bottleneck, the air freight expedite on a long-lead spare, overtime as a percent of direct labor. Never quote an industry average when you have their instance data in front of you; that is the single fastest way to get downgraded from partner to vendor.
- How small should the ask be on the first expansion call?
Small enough to sign this quarter without an AR. One asset group, one line, one cell, one quarter — with success criteria the customer writes on the call, a pre-agreed decision date, and a clean exit if it misses. Then co-term the roll-out to the existing renewal so procurement handles one contract instead of two. Selling the all-plants, all-assets rollout on call one is how reps end up with a polite ten minutes and nothing signed, because that version requires a corporate appropriation request and a payback calculation that competes with a new press and a roof.
- When should I park the upsell entirely?
Park it if there's an open escalation or hardware that's been down more than two weeks, if your champion just changed roles or got absorbed by a program launch, if renewal is inside 60 days with the value question still unresolved, if alert-to-work-order conversion is flat and you can't explain why, or if the plant is dealing with a corporate cost review or a customer-imposed controlled shipping status. In every one of those cases the buyer has no attention available, and pushing anyway costs you more than the expansion is worth.