Manufacturing · Demo Call
The Manufacturing Product Demo Script for Plant Managers Who Interrupt
The demo is not where a Plant Manager learns what your product does. They already sat through that call. They said yes to this one because they want to find out where it breaks — on their network, in their CMMS, at 2am on second shift when the only person in the building is a Production Supervisor and one tech. They will interrupt you inside the first four minutes. That interruption is the call.
This manufacturing product demo script assumes you're selling into a plant that has already been burned: a sensor pilot two years ago that generated alerts into a shared inbox nobody read, an MES with tablets at the line that operators stopped touching by week three, a downtime tracking tool whose codes all say "mechanical." The room's default position is that your thing becomes shelfware too. Every screen you show has to answer a version of the same question — who on my floor has to do something differently, and will they?
Work the loop: problem, screen, consequence, check. Three workflows completely, not twelve partially. Show the constraint asset by the name they call it — line 3, the 800-ton, cell 4 — with their unplanned downtime hours on it, not ACME Corp and Test Machine 1. And when they ask if it handles something, slow down and get the actual case before you answer, because the difference between "we ship to a tier 1" and "we're on controlled shipping level 1 with a third-party inspector in the building" is the difference between a nice-to-have and a signed AR.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Confirmation email (send 48 hours out — this is where the demo gets built)
"So I don't burn twenty minutes on screens that don't apply to your plant — three quick things: 1. What are you running for CMMS/EAM — Maximo, SAP PM, Fiix, eMaint, something homegrown? Hosted or on-prem, and who administers it? 2. Your top three assets by unplanned downtime hours last month. A screenshot of the spreadsheet is fine. I'll build the demo on those three, using the names your floor uses. 3. Who's on the call besides you? If your IT/OT person is joining I'll bring the architecture and port list; if it's just you and your Maintenance Manager I'll leave that out." If they send nothing, call the Maintenance Manager and get it verbally. Do not walk into this demo with generic sample data after they've already told you they have a line 3 problem.
- 2
Opening — 90 seconds, recap in their words
"Last time you told me the 800-ton on line 3 took 34 unplanned hours last month, you ran two Saturdays to catch up, and the work order for the big one says 'mechanical, replaced bearing' and nothing else. You said OEE on that constraint is sitting around 61% and corporate is asking for 70 by year-end. Still accurate, or has something moved?" Then: "Anything change since we spoke — budget, people, a customer issue?" Then the interruption contract, out loud: "I'd rather you stop me than sit politely through something irrelevant. If you're thinking 'that won't work on my floor,' say it in the moment — that's the useful part of this call." Then the deal-breaker: "Before I click anything — what's the one thing that, if this can't do it, we don't need to keep talking?" Demo in that order. If the answer is "it can't touch my PLCs," you're showing architecture first, not asset health.
- 3
Loop 1 — The constraint asset, shown as a moment, not a dashboard
Problem: "Take the Tuesday before last. The press starts making a noise, the operator says something at break, nobody logs it, and Thursday second shift it comes down for six hours." Screen: "This is the 800-ton. Not a plant dashboard — one asset. The vibration signature on the main drive started drifting eleven days before the failure. You're not looking at a green light; you're looking at the trend and the date it crosses." Consequence: "Those six hours don't get eliminated, they get moved. They become four hours on a Saturday you already had planned, with the bearing on the shelf." Check: "Is that how it actually plays out on line 3, or am I making it up?" Do not narrate the software. Narrate the millwright.
- 4
Loop 2 — The alert becomes a work order with a name on it (this is the pilot-failure screen)
Problem: "You told me the last sensor pilot died because alerts went to a shared inbox. Let me show you the only screen that matters for that." Screen: "When this crosses threshold, it doesn't email a group. It opens a work order in your CMMS — priority, asset number, failure mode, and it checks the spare against your MRO stock before it assigns. If the gearbox is 22 weeks out from Germany, the work order says so on the face of it, and it goes to your planner, not to maintenance@." Consequence: "So at 2am on second shift, your supervisor isn't deciding whether to believe an alert. There's a planned job in the queue with an owner and a part number." Check: "Who's the named owner in your shop — your planner, or does the Maintenance Manager triage everything himself?"
- 5
Loop 3 — The failure reason, i.e. the screen that builds the AR
Problem: "Right now you can tell corporate downtime hours by asset. You can't tell them why. The code says mechanical and the tech wrote three words." Screen: "This is 90 days on your top three assets, split by failure mode, not by downtime code. Lubrication, misalignment, bearing wear, electrical. And here's the same view against your planned-versus-reactive work order ratio." Consequence: "When you write the appropriation request in Q3, this is the payback section. Not my number — your unplanned hours, your cost per hour on the constraint, your expedite freight." Check: "What's your hurdle rate, and what payback window does an AR need to clear at your corporate?" This loop is aimed at the Plant Manager and the Director of Continuous Improvement. If neither is on the call, shorten it.
- 6
Pressure line 1 — Integration and the OT boundary (raise it before they do)
"Let me get ahead of the thing your IT/OT person is going to ask. We do not touch the control layer. No PLC connection, no writes to the control network, nothing in your ladder logic. The sensors are wireless to a gateway, and the gateway can run on its own cellular connection that never sees your plant network. If you'd rather keep it on your network, it's outbound-only on one port and I'll send you the list. On the CMMS side: read-only on assets and work order history, write on work order creation and status. It's a REST API to Maximo; if you're on an older on-prem instance we do a flat file to SFTP nightly instead and I'll say so plainly rather than promising a connector that doesn't exist for your version. What I want is fifteen minutes with your IT/OT security person in week one, not week eight. If there's a blocker I'd rather hit it before your team has spent two months writing a business case."
- 7
Pressure line 2 — Who owns it after we're gone
"Here's the honest answer on ownership. Nobody on the floor does anything new. No operator logs anything, no supervisor enforces anything at shift change. If the value depended on an operator remembering something, you should throw us out — that's how the tablets died. Ongoing, it's roughly two hours a month and it's your Reliability Engineering Manager or your maintenance planner, not IT. That's adding assets, adjusting a threshold, changing who the work order routes to. First 90 days we tune the thresholds ourselves so your team isn't chasing false alerts while the baseline settles. If your reliability engineer leaves — and I know you're losing a 30-year millwright in eighteen months — handover is a half day. The logic isn't in someone's head or on a laminated sheet taped to the machine."
- 8
Pressure line 3 — What actually happens when it breaks
"I'm not going to give you an uptime percentage. Here's the failure mode. If the gateway drops, the sensors keep sampling and buffer locally. You lose live trending, you don't lose the data — it backfills when the link comes up. If our platform is down, your CMMS is unaffected; nothing we do sits between your planner and his work orders. The press runs either way. Nothing we install can stop your line. Support: P1 is a phone number, 24/7, a human picks up — that's a gateway or sensor network down. P3 is email, next business day, and I'm not going to pretend otherwise. Your escalation is your named CSM, then the VP of Customer Ops. If you want, ask me about our last incident. I'd rather describe it than claim we haven't had one."
- 9
Pressure line 4 — Time-to-value in three dates, tied to their shutdown calendar
"Three dates, not one. Live: install is a scheduled downtime window, and you said you have one over the July shutdown. Sensors on the top three assets go on in that window — no production interruption. Useful: three to four weeks after that, once we have a baseline on the drive train under real load, so the alerts mean something. Useful means the first condition alert turns into a Saturday planned job instead of a Thursday callout, and you can point at it in your morning meeting. Fully rolled out: the rest of the asset list after you've seen it work on the three. I'd rather earn that than sell it now. What I need from you: the asset list with criticality, your CMMS work order fields, one hour with your planner, and a name for the IT/OT conversation. That's the whole ask. I'm telling you now so nobody's surprised in week three."
- 10
Handling 'will it handle X' mid-demo
Step 1 — get the actual case: "Tell me the specific one. Are you asking about a VFD-driven motor, or a gearbox on a slow-speed application? Those are different answers." Step 2 — answer one of three ways: • Yes, and here it is — go show it live. Strongest thing that happens on a demo. • Yes, but not how you'd expect — "You don't see it on this screen, it's in the asset history tab, and it's two extra clicks." Buyers forgive ugly. They don't forgive finding ugly in month three. • No — "No. We don't do reciprocating compressors well today, and it's not on this year's roadmap." Then: "How often does that come up — is that a weekly thing or once at year-end?" Never say "we can build that." That is the exact sentence their last vendor used. Step 3 — write it down visibly: "Noting that — SAP PM work order custom fields. Straight answer by Thursday." Then Thursday, not Friday.
- 11
Recovering when the room goes quiet (you'll hear typing)
Stop. Don't talk faster, don't add a feature, don't say 'one more thing.' Pick one: • "I've been talking a while — is this the part you care about, or should I jump?" • "Let me kill the tour. What's the thing you're worried about that I haven't touched?" • "Do you want to drive? Tell me what to click." Almost nobody offers this and it works. • "I think I'm showing you the wrong screens. Can I stop, take ten minutes on what actually matters, and come back with a demo built for that?" Losing twenty minutes of a demo to save the deal is a good trade.
- 12
Close — gaps out loud, temperature, next thing on the calendar
"Three things landed: the trend on the 800-ton before the failure, the work order going to a named planner with the spare check, and the failure-mode view for your AR. Two open: whether your SAP PM instance supports the write-back on custom fields, and the reciprocating compressor question — no on that one today, and I'll confirm in writing. Where does this sit for you now — worth pursuing, or is there something that's already ruled it out?" (Let them say no. A clean no beats four weeks of chasing.) "Who else needs to see it? I'd run twenty minutes for your IT/OT lead that's architecture and security only, nothing else. And if this becomes an AR, I'd rather build the payback math with your controller in the room than hand you a spreadsheet." Book it live: "Calendar's open — Tuesday the 14th at 7:30, before your production meeting?" Invite sent before you hang up. Within 24 hours: the gap list with answers, the four screens that mattered, the port list and security doc if IT was on, and one line on what you need from them.
- 13
Language swaps for the plant floor
Instead of "our unified asset performance platform" → "this is the one screen your planner opens at 6am." Instead of "we integrate with everything" → "we write work orders into your Maximo over REST. Here's the payload." Instead of "it's very intuitive" → "your operators do nothing different. Your planner gets twenty minutes." Instead of "we can build that" → "we don't do that today. How often does it come up?" Instead of "99.9% uptime" → "if the gateway drops, sensors buffer and backfill. Your line never notices." Instead of "most customers see ROI in six months" → "live at the July shutdown, first planned catch by mid-August, and we build the payback from your unplanned hours — not somebody else's press."
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share anything — last time you said the 800-ton on line 3 took 34 unplanned hours last month and OEE on that constraint is running around 61%. Still where it is, and has anything changed since we spoke?
Buyer
It's 34 hours the way corporate counts it. We exclude planned changeovers from availability, so our 61 isn't your 61, and I'm not going to sit here and argue OEE math with a vendor. What changed is we had an escape at our tier 1 in April, so my quality manager is writing an 8D and I've got less patience than I did.
Rep
Then let's not touch OEE. Two questions instead — what's the one thing that, if this can't do it, we stop talking? And does the escape trace back to a machine condition or to a process issue?
Buyer
Deal-breaker is my PLCs. Nobody's putting anything on the control network, my IT/OT guy will die on that hill. And the escape was a dimensional drift on the press — tool wear, probably. But I'll tell you the real deal-breaker: we did a sensor pilot two years ago. Alerts went to a shared inbox, maintenance ignored them inside a month, and it quietly died. Nobody even cancelled the subscription.
Rep
Then I'm going to show you two screens, and the first one is architecture, not asset health. Nothing touches your control layer — no PLC connection, no writes, nothing in your logic. The gateway can run on its own cellular link that never sees your plant network. If your IT/OT guy wants to unplug it from everything, it still works. Fair start?
Buyer
Fine. But the pilot didn't fail because of the network. It failed because nobody did anything with the alerts.
Rep
Agreed, and that's the screen I actually care about. Tell me first — at 2am on second shift, if your supervisor got a notice saying this bearing fails in nine days, what would he actually do?
Buyer
Honestly? Nothing. He'd tell the day shift, maybe. And if the part's not on the shelf it doesn't matter anyway — we've got a gearbox on that line that's 22 weeks from Germany and my spares inventory got squeezed last year for working capital.
Rep
That's the whole thing then. Watch this — the alert doesn't email anyone. It opens a work order in your CMMS with the asset number, the failure mode, and a stock check against your MRO. If the part isn't on the shelf, the work order says 'part lead time 22 weeks, order by' with a date on it, and it routes to your planner by name — not to a shared inbox. Your supervisor at 2am does nothing, because it isn't his decision anymore. Who's the named planner on your side?
Buyer
We've got one planner for the whole plant and he's swamped. And look — we're at 95% PM compliance. We run our PMs. Why am I still buying this?
Rep
Because PM compliance and unplanned downtime aren't the same metric. At 95% compliance and 34 unplanned hours on your constraint, that tells you your intervals are calendar-based — you're changing bearings that had life left and missing the ones that didn't. What's your MTBF trend on those top three assets over the last year, and what's your planned-versus-reactive work order split?
Buyer
MTBF is flat, maybe worse on the press. Split's about 60-40 reactive, which nobody upstairs likes. But here's your real problem — capex is locked. AR went in last Q3, next window is Q3 this year for next year's money. My signing authority is $50K and I'm not spending it on this.
Rep
I'm not going to pretend I can unlock it. Two things. First — is this shaped like capex for you, or can it run as a monthly line under MRO or controllable spend? That's usually a different approval path and often inside your $50K. Second — if it's going in the Q3 AR anyway, the baseline has to be built now. You'd be writing that payback in August from memory otherwise. Let me help you build the number off your three assets, and if it doesn't clear your hurdle rate you throw it out and I stop calling.
Buyer
That I'll listen to. But my maintenance team is reactive all day — they don't have time for another tool, and I don't have time for another dashboard nobody opens.
Rep
Then let's test it that way. Nobody on your floor does anything different — no operator entry, no shift-change logging. The only person with a new habit is your planner, and the habit is looking at a work order that's already written. Here's what I'd want by Thursday: your top three by unplanned hours, and what a shutdown hour costs you on the press. Can we get twenty minutes with your IT/OT guy first, so if he's going to kill it he kills it in week one rather than after you've built the AR?
Buyer
Send me the port list and the architecture doc and I'll forward it to him. If he clears it, book something with me and my maintenance manager.
Rep
Doc's out within the hour. I'm going to put a hold on your calendar now for the 14th at 7:30, before your production meeting — you can move it if he needs longer. And I owe you a straight answer on the SAP PM custom field write-back; that's Thursday, either way.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Capex is locked for the year — come back next budget cycle.” | Fair, and I'm not going to pretend I can unlock it. Two questions. First, is this shaped like capex 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 your signing authority. Second, if we're talking about next year's AR anyway, the work of building it — the downtime baseline on your worst three assets and the payback math — 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, you throw it out. |
| “The floor barely uses the systems we already have. Why would this be different?” | That's the most honest objection I get, and it usually means the last system asked operators to enter data. So ask me the question directly: who on my floor has to do something new for this to work? The answer is nobody. No operator entry, no shift-change logging, no tablet at the line. If the value depended on an operator remembering something, you should throw us out. What I want from you is which system went unused and why — because if that was a change management failure rather than a tooling failure, we'll fail the same way and I'd rather find out now than in month four. |
| “We already have a CMMS and we're at 95% PM compliance.” | Good — most plants I walk aren't. But PM compliance and unplanned downtime aren't the same metric. If you're at 95% and still eating 34 unplanned hours on the bottleneck, that tells you the intervals are calendar-based, not condition-based — you're changing bearings that had life left and missing the ones that didn't. What's your MTBF trend on your top three assets over the last year? If it's flat or worsening while compliance is high, that's the gap, and this doesn't replace your CMMS — it feeds it. |
| “You're not putting anything on my network or touching my PLCs.” | Understood, and I'd be worried if you said yes fast. Nothing touches the control layer — no PLC connection, read-only on the CMMS side, and the gateway can run on a separate cellular link that never sees your plant network. What I'd ask for is fifteen minutes with your IT/OT security person early rather than late. If there's a blocker, I want to hit it in week one, not after your team has spent two months building an AR. |
| “We tried a sensor pilot two years ago. It generated alerts nobody acted on and it quietly died.” | What happened to those alerts — shared inbox? That's almost always the failure. An alert that isn't a work order in the CMMS with a named owner and a spare on the shelf is noise, and maintenance learns to ignore it inside three weeks. So before I show you anything: tell me what your team would actually do at 2am on second shift with a 'this bearing fails in nine days' notice. If there's no answer, we should fix that first — with or without me. |
| “My maintenance team is already stretched. They're reactive all day.” | That's exactly the trap. 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 their time — I'm asking whether moving four of last month's emergency callouts into planned weekend work would free enough wrench time to matter, and whether it takes a bite out of your overtime as a percent of direct labor. What was your planned-versus-reactive split last quarter? |
| “Knowing a gearbox is failing doesn't help me if it's 22 weeks out from Germany.” | Correct, and that's why the alert alone is worthless. The point of nine days' notice on a bearing is a Saturday job. The point of ninety days' notice on a gearbox is a purchase order before it fails, at freight rates instead of air freight and expedite charges hitting your controllable spend. So the question for your critical spares list isn't what's on the shelf — it's which long-lead items you're currently gambling on. Can we look at that list together, and I'll tell you honestly which ones we'd give you useful lead time on and which ones we wouldn't? |
Questions reps ask about this call
- What should a manufacturing product demo script open with?
Their constraint asset and their numbers, in their words — "you said the 800-ton took 34 unplanned hours last month and the work order says 'mechanical'." Not a company slide, not a plant-wide dashboard, and not your setup and admin screens. Then set the interruption contract out loud and ask the deal-breaker question: "what's the one thing that, if this can't do it, we stop talking?" That answer sets the order you demo in. If a Plant Manager says "my PLCs," you show architecture before you show a single trend line.
- Who should be on a manufacturing demo call, and does that change the script?
It changes everything. The Plant Manager or VP of Manufacturing wants the throughput and the payback for the AR. The Maintenance Manager wants to know whether his planner gets another queue to babysit. The Reliability Engineering Manager wants to know how thresholds are set and who owns them after go-live. An IT/OT lead wants ports, direction of data flow, and confirmation you don't touch the control network. That's three or four demos in one hour, so run three workflows completely rather than twelve partially, and offer a separate twenty-minute architecture-only session for IT rather than dragging everyone through it.
- How do I demo when they've already had a failed pilot?
Make it the centrepiece rather than avoiding it. Ask what happened to the alerts — if the answer is a shared inbox, you've found the failure mode, and the screen that matters is the one where the alert becomes a work order in their CMMS with a named owner, a failure mode, and a spare parts check. Then ask what a Production Supervisor on 2nd shift would actually do at 2am with that notice. If they can't answer, don't sell past it; that's a process gap and pretending otherwise gets you a second dead pilot with your logo on it.
- How should I answer 'will it handle X' during the demo?
Slow down and get the specific case before you answer. "Will it handle our CMMS?" is unanswerable — SAP PM with heavy custom fields is a different answer to Fiix out of the box. Then answer one of three ways: yes and here it is, live; yes but not how you'd expect, and show the ugly workaround plainly; or no, flatly, followed by "how often does that come up?" Never say "we can build that." That's the exact sentence the vendor who slipped on them last time used, and experienced manufacturing buyers hear it as a slipped date.
- How do I handle 'capex is locked' if it comes up mid-demo?
Don't fight it and don't keep demoing. Manufacturing capital moves through an annual appropriation request submitted in Q3, with a payback calculation, competing against a new press and a roof. Two moves: test whether it can run as monthly opex under MRO or controllable spend, which is often inside the Plant Manager's $25K or $50K signing authority; and if it genuinely has to be next year's AR, offer to build the baseline now — unplanned downtime hours by asset, cost per shutdown hour, expedite freight — so they're not writing the payback from memory in August. Then ask their hurdle rate and payback window, and say out loud that if the math doesn't clear it, you'll tell them.
- How long should the demo be, and what do I do in the last five minutes?
Aim for three or four problem-screen-consequence-check loops and stop. In the last five minutes, summarise the fit and say the gaps out loud — including the thing you said no to. Then ask the temperature question: "where does this sit for you now, or is something already ruling it out?" Let them say no cleanly. Ask who else needs to see it, offer the tailored version for IT/OT or the controller, and book the next meeting on the call with the calendar open. Send the gap list, the port list and the four screens that mattered within 24 hours.
- How do I practise this before a real call?
Rehearse the detours, not the click path. The demo you built is a resource; the call is won on how you handle a Maintenance Manager who interrupts with "we're at 95% PM compliance" or a Plant Manager who tells you his last sensor pilot died in a shared inbox. Run those interruptions out loud until the answers are short and specific — a rep who has said "nothing touches your control layer, here's the port list" fifty times sounds different from one saying it for the first time in front of an IT/OT lead.