Manufacturing ERP Software Selling — 60-Min Training
Direct Answer
The ERP Deal Inspection Drill is a 60-minute training for reps selling manufacturing ERP and MES platforms ($150K-$2M total contract value) into multi-plant manufacturers, where the buying committee spans Operations, Finance, and IT and the cycle runs 9-18 months. The session installs one ritual: every rep maps process pain to a dollar before they earn a demo, then converts that demo into a written business case the Economic Buyer can defend.
Built on the MEDDICC qualification framework popularized by Force Management and John McMahon's "The Qualified Sales Leader," the ASCM/APICS CPIM body of knowledge that every ERP business rule descends from, and Mike Bosworth's "Solution Selling," this drill teaches reps to quantify scrap, downtime, and inventory carry before they ever open the software.
Section 1 — Why Demos Lose ERP Deals (5 min)
Open with the uncomfortable truth on the whiteboard: manufacturing ERP reps demo too early and quantify too late. The plant manager asks "can it do bills of material?", the rep opens the software, and the deal becomes a feature checklist nobody can build a budget around.
Set the frame:
- The old motion: Demo first, hope the features sell themselves, lose to "no decision" after 14 months.
- The new motion: Quantify the process pain in dollars first, earn the demo, leave with a CFO-ready business case.
- The committee reality: You are selling to Operations (cares about throughput and scrap), Finance (cares about inventory carry and audit), and IT (cares about integration and uptime). Win one, you have a champion. Win all three, you have a deal.
John McMahon is blunt in "The Qualified Sales Leader": a deal with no quantified Metrics and no identified Economic Buyer is not a deal, it is a science project. ASCM/APICS reminds us that every ERP business rule descends from production-and-inventory-management discipline — so a rep who cannot speak master scheduling, MRP, and cycle counting loses credibility in the first 10 minutes.
Read the MEDDICC letters aloud and make the room recite them.
Section 2 — Process-Pain Discovery to a Dollar (15 min)
This is where the deal is won. The rep does not demo until each pain is tagged with a number. Walk the room through the verbatim template — have every rep fill it out for a live opportunity right now.
Verbatim Process-Pain Discovery Template (rep completes before requesting a demo):
- Account and plants: [Manufacturer] — [Number of sites] — [Discrete or process manufacturing]
- The bleeding process: [e.g., manual scheduling in spreadsheets across 3 plants]
- Metric of pain TODAY: [e.g., scrap rate 6.2 percent, $1.4M annual; unplanned downtime 11 hours per week]
- Who feels it: Ops owner [name] — Finance owner [name] — IT owner [name]
- The Economic Buyer and their number: [VP Ops / CFO] — [the metric they are measured on this fiscal year]
- Decision Criteria and Decision Process: [What committee, what gates, what budget cycle, what compelling event]
Coach the "no number, no demo" rule. Force Management's Command of the Message insists the rep ties every capability to a quantified Metric and a named business outcome. If a rep writes "they want better visibility," push back hard: *"Visibility into what, costing them how much, measured by whom?"*
Show the bad example: *"They said the current system is clunky and they want to modernize."* That is not pain, that is a feeling. Pain is $1.4M of scrap and 11 hours of weekly downtime.
Section 3 — The Discovery Trap Words (10 min)
Manufacturing buyers are practitioners. One lazy line and you lose the room. Drill the language.
- Take notes on the plant tour by hand, then read them back: *"You said scrap on Line 4 runs 6 percent — what does that cost in scrapped material and rework labor?"*
- Always convert hours to dollars in front of the buyer. Downtime is not hours, it is lost units times contribution margin.
- Speak APICS vocabulary — MRP, master production schedule, ATP, cycle counting — so Ops trusts you.
What to NEVER say in front of a manufacturing buying committee (read these aloud, slowly):
- "Our solution is fully integrated" (every loser says this; means nothing without the named systems and the integration cost)
- "We can customize it to do anything" (terrifies IT; customization is the #1 source of failed ERP go-lives)
- "You will see ROI immediately" (no manufacturer believes a 12-month go-live pays back instantly; you lose credibility)
- "What keeps you up at night?" (lazy discovery filler that signals you did no homework on their plant)
- "We are the market leader" (Ops does not care about your logos, they care about their scrap rate)
- "Let me just show you a quick demo" (before quantified pain, a demo is a feature parade that anchors on price, not value)
Mike Bosworth's "Solution Selling" is the rule here: you diagnose before you prescribe. A rep who demos before quantifying is a salesperson handing out aspirin without taking a pulse.
Section 4 — The Demo-to-Business-Case Handoff (10 min)
The demo exists to prove the quantified pain goes away — nothing more. Run it from a script. Use the verbatim opening.
Verbatim Demo Opening Script (rep delivers these exact words):
Rep: "Before I show you anything, let me confirm what we are solving. You told me scrap on Lines 3 and 4 costs $1.4M a year and manual scheduling burns 11 hours of supervisor time weekly. Today I am showing exactly three things, each tied to one of those numbers. Fair?"
[Ops owner confirms. If they add a fourth thing, the rep writes it down and does NOT demo it today.]
Rep: "Watch this: real-time scrap capture on the shop floor flows straight to the scheduling engine. On your numbers, cutting scrap from 6 percent to 4 percent recovers about $470K a year."
[Rep demos the scheduling reschedule.]
Rep, turning to Finance: "Sarah, the same data feeds your inventory carry. If we cut on-hand inventory 15 percent, what does that free in working capital?"
[Finance answers the number themselves — that is the close.]
Rep: "I will put all three numbers in a one-page business case by Friday so your champion can defend it to the committee. Who else needs to be on that page?"
Do NOT:
- Demo a feature that is not tied to a quantified pain — every extra screen dilutes the business case.
- Let the demo run long. APICS-trained Ops people respect tight, on-spec demos; rambling reads as a weak product.
- Leave without scheduling the business-case review — a demo with no written follow-up is a demo the committee forgets in a week.
Section 5 — The Business Case and the Long Cycle (15 min)
This is the part reps skip, and why ERP deals stall at "no decision." Build the operating cadence on the whiteboard.
The math (for a 4-plant discrete manufacturer):
- Scrap recovery: 6 percent to 4 percent on $23M material spend = ~$470K per year
- Downtime recovery: 11 hours per week × 4 plants × $3,200 per hour contribution = ~$1.5M per year
- Inventory carry: 15 percent reduction on $8M on-hand × 22 percent carry cost = ~$264K per year
- Total annual benefit ~$2.23M against a $850K license + $400K implementation = payback in under 7 months
Force Management insists the second touch with the committee inspects the Decision Process — who signs, in what order, against which budget. Without a dated compelling event (a legacy ERP sunset, an audit finding, a capacity wall) the deal slips a quarter every quarter.
Common ERP-buyer objections (rehearse the comebacks):
- *"Implementations always blow the budget."* — Agreed, which is why we phase by plant and tie each phase to a recovered dollar. We do not go live everywhere at once.
- *"Our IT team is already underwater."* — Then we scope a managed go-live and put the integration hours in the SOW so nobody discovers them later.
- *"We tried ERP before and it failed."* — Most failures are change-management, not software. Show me your last go-live and I will show you where the user adoption plan was missing.
Have each rep name the compelling event on their top deal before they leave the room. No exit without a dated trigger.
Section 6 — Commitments and Close (5 min)
Each rep leaves with three written commitments, pinned to their CRM opportunity:
- Every open opportunity has a quantified process pain — scrap, downtime, or carry in real dollars — by EOD Friday.
- My top deal has a named Economic Buyer and their fiscal-year metric documented in the MEDDICC fields.
- No demo goes out this quarter without a quantified pain attached and a business-case review scheduled.
Close by reading John McMahon aloud: *"Hope is not a strategy and a demo is not a discovery. If you cannot put the customer's pain in dollars, you do not have a deal — you have a relationship."*
Then pin the deal-inspection checklist in the team channel and have every rep tag their top opportunity for review.
FAQ
Q1: What if the prospect insists on seeing a demo before any discovery? A: Run a tight 12-minute "teaser" tied to the one pain they named on the call, then redirect: "To show you the rest, I need 20 minutes on your scrap and downtime numbers." A demo with no quantified pain anchors them on price.
Q2: How do I sell when Operations loves us but Finance and IT are cold? A: You have a champion, not a deal. MEDDICC says map the full committee. Get your champion to introduce you to the Economic Buyer, and build separate proof points for Finance (carry cost, audit) and IT (integration, uptime).
Q3: The cycle is 14 months — how do I keep the deal alive? A: A mutual action plan and a dated compelling event. Inspect the Decision Process every 30 days. Deals that slip have no trigger forcing a decision; find the ERP sunset, the audit finding, or the capacity wall.
Q4: Do I need to know APICS terminology to sell ERP? A: Yes. Ops buyers test your credibility with MRP, master scheduling, and cycle counting in the first meeting. You do not need the CPIM certification, but you must speak the language fluently or you sound like a tourist.
Q5: How is selling MES different from selling ERP? A: MES lives on the shop floor — real-time production, quality, and machine data. The buyer skews more to plant engineering and quality than to Finance. The discovery is still pain-to-a-dollar, but the dollar is usually scrap, OEE, and compliance.
Q6: What is the single biggest reason these deals die? A: "No decision." Not a competitor — the status quo. The fix is a quantified business case the champion can defend without you in the room, plus a dated compelling event. Force Management calls the absent compelling event the silent deal-killer.
Sources
- John McMahon, *The Qualified Sales Leader*, McMahon Group, 2021.
- Force Management, *Command of the Message* and *MEDDICC* qualification playbooks, 2023-2025.
- Michael Bosworth, *Solution Selling: Creating Buyers in Difficult Selling Markets*, McGraw-Hill, 1994.
- Association for Supply Chain Management (ASCM), *APICS CPIM Learning System* body of knowledge, ascm.org.
- Keith M. Eades, *The New Solution Selling*, McGraw-Hill, 2003.
- Neil Rackham, *SPIN Selling*, McGraw-Hill, 1988.
- Matthew Dixon and Brent Adamson, *The Challenger Sale*, Portfolio/Penguin, 2011.
- Manufacturing Enterprise Solutions Association (MESA International), *MES/MOM functional model and ERP integration guidance*, mesa.org.