Manufacturing ERP Software Selling — 60-Min Training

What the drill is and why manufacturing ERP deals need it

Manufacturing ERP and MES deals are among the slowest, most committee-heavy purchases in enterprise software. A multi-plant manufacturer evaluating a system that touches production scheduling, bills of material, inventory, quality, and finance is not buying a tool — it is agreeing to rewire how the company runs for the next decade. Cycles routinely stretch across three or four budget quarters, the committee spans Operations, Finance, and IT, and the most common outcome is not a competitive loss but "no decision." The status quo wins because nobody in the room could defend the spend to a CFO.

The 60-minute drill exists to attack that specific failure mode. It is not a product-knowledge session and not a pep talk. It is a working session where every rep in the room takes a live opportunity from their own pipeline and runs it through a single gate: is the process pain written down as a dollar figure, tied to a named owner, with an identified economic buyer and the metric that person is measured on this fiscal year? Reps who cannot answer leave with homework, not applause.

The intellectual scaffolding comes from three places worth naming out loud in the room. MEDDICC — the qualification framework popularized in enterprise software and taught in John McMahon's *The Qualified Sales Leader* — supplies the discipline of Metrics and Economic Buyer as non-negotiables. Mike Bosworth's *Solution Selling* supplies the diagnose-before-you-prescribe rule that makes an early demo a malpractice rather than a courtesy. And the ASCM/APICS CPIM body of knowledge supplies the vocabulary: MRP, master production schedule, available-to-promise, cycle counting, routings, work centers. Every business rule inside a manufacturing ERP descends from that discipline. A rep who cannot use those words correctly loses the plant manager inside ten minutes, and once Operations decides you are a tourist, no amount of Finance charm recovers the deal.

Why 60 minutes and not a two-day offsite? Because the behavior being installed is small and repeatable. The drill is a weekly or biweekly ritual, not an event. Sales enablement platforms consistently report that the strongest predictor of training ROI is not session length but whether the team builds a shared vocabulary and inspects against it repeatedly. Sixty minutes on the calendar every week beats sixteen hours once a year, because the ERP sales motion is a habit problem, not a knowledge problem. Reps already know the software. What they lack is the reflex to convert a plant tour observation into a number before they open a laptop.

The manager's prep matters as much as the content. Have the deal-inspection dashboard already on screen when the meeting starts, a recent discovery call recording queued as the coaching artifact, and the follow-up cadence tool open in a second tab so commitments get written into sequences before anyone leaves. Three browser tabs, staged in advance, save roughly eight minutes of fumbling — which in a sixty-minute drill is thirteen percent of the session.

The step-by-step process: pain to dollars to business case

Run the session in six timed blocks. Keep a visible timer. The discipline of the clock models the discipline you want in the demo.

Block one — the uncomfortable truth (5 minutes). Write on the whiteboard: *manufacturing ERP reps demo too early and quantify too late.* Then contrast the two motions. The old motion: the plant manager asks whether the system handles multi-level bills of material, the rep opens the software, and the deal degrades into a feature checklist nobody can build a budget around. The new motion: quantify the process pain in dollars first, earn the demo, leave with a CFO-ready business case. Name the committee reality out loud. Operations cares about throughput, scrap, and schedule attainment. Finance cares about inventory carry, close cycle, and auditability. IT cares about integration surface, data migration, and uptime. Win one function and you have a champion. Win all three and you have a deal.

Block two — process-pain discovery to a dollar (15 minutes). This is where the deal is actually won, so it gets the largest block. Every rep fills out the template below for a live opportunity, right now, in the room.

The discovery template, completed before any demo request: account and number of plants, and whether the operation is discrete or process manufacturing. The bleeding process, stated concretely — manual scheduling in spreadsheets across three sites, not "inefficiency." The metric of pain today, with a number and a unit — a scrap rate of 6.2 percent representing roughly $1.4M annually, or eleven hours of unplanned downtime per week. Who feels it, by name, in Operations, Finance, and IT. The economic buyer and the specific metric that person is graded on this fiscal year. And finally the decision criteria and decision process: which committee, which gates, which budget cycle, which compelling event.

Coach the "no number, no demo" rule hard. When a rep writes "they want better visibility," push back immediately: visibility into what, costing how much, measured by whom? "The current system is clunky and they want to modernize" is a feeling, not a pain. Pain is $1.4M of scrap and eleven hours of weekly downtime. Force Management's Command of the Message discipline says the same thing in different words — tie every capability to a quantified metric and a named business outcome, or do not mention the capability.

Block three — the trap words (10 minutes). Manufacturing buyers are practitioners with decades on a plant floor. One lazy line and the room closes. Drill the language: take notes on the plant tour by hand, then read them back — "you said scrap on Line 4 runs six percent; what does that cost in scrapped material plus rework labor?" Always convert hours to dollars in front of the buyer, because downtime is not hours, it is lost units times contribution margin. Speak APICS vocabulary so Operations trusts you.

Then read the forbidden phrases aloud, slowly, because reps need to hear how bad they sound. "Our solution is fully integrated" — every losing vendor says this, and it means nothing without named systems and an integration cost. "We can customize it to do anything" — this terrifies IT, because over-customization is the classic root cause of failed go-lives. "You'll see ROI immediately" — no manufacturer believes a twelve-month implementation pays back instantly, and the claim burns your credibility for the rest of the cycle. "What keeps you up at night?" — lazy filler that announces you did no homework on their plant. "We're the market leader" — Operations does not care about your logo wall, 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 the buyer on price instead of value.

Block four — the demo-to-business-case handoff (10 minutes). The demo exists to prove the quantified pain goes away. Nothing more. Run it from a script. The opening: "Before I show you anything, let me confirm what we're solving. You told me scrap on Lines 3 and 4 costs $1.4M a year and manual scheduling burns eleven hours of supervisor time weekly. Today I'm showing exactly three things, each tied to one of those numbers. Fair?" If the buyer adds a fourth item, the rep writes it down and does not demo it today. Mid-demo, turn to Finance and make them say the number themselves: "the same shop-floor data feeds your inventory carry — if we cut on-hand fifteen percent, what does that free in working capital?" When the buyer computes the benefit out loud, the close has already happened. Exit with a commitment: a one-page business case by Friday, and the question of who else needs to be on that page.

Block five — the business case and the long cycle (15 minutes). Reps skip this and their deals die at "no decision." The champion must be able to defend the numbers alone, in a room you are not in. Rehearse it with them. Then sequence the committee: IT signs off on integration, Finance finds the budget slot, and the whole thing needs a dated compelling event or it slips a quarter every quarter.

Block six — commitments (5 minutes). Three written commitments per rep, pinned to the CRM opportunity: every open opportunity carries a quantified process pain in real dollars by end of week; the top deal has a named economic buyer and their fiscal-year metric documented in the MEDDICC fields; and no demo ships this quarter without a quantified pain attached and a business-case review already scheduled.

Costs, timelines, and the numbers reps must be able to build

Reps cannot sell a business case they cannot construct on a whiteboard. Teach the arithmetic explicitly, using a worked example the whole team memorizes. Take a four-plant discrete manufacturer with roughly $23M in annual material spend, $8M in on-hand inventory, and eleven hours of weekly unplanned downtime per site.

Scrap recovery: moving from a six percent scrap rate to four percent on $23M of material spend recovers on the order of $460K–$470K a year. Teach reps to state the assumption out loud — this counts scrapped material at cost and does not yet include rework labor, which is upside they can add once the plant gives them a loaded labor rate.

Downtime recovery: eleven hours per week across four plants at a contribution margin of roughly $3,200 per production hour lands near $1.5M annually. The critical coaching point is that reps must get the contribution-margin-per-hour figure *from the customer*, not from a slide. Ask Finance directly: what does an hour of line stoppage cost you in contribution margin? When Finance supplies the number, Finance owns the number, and it survives committee scrutiny.

Inventory carry: a fifteen percent reduction on $8M of on-hand inventory at a twenty-two percent carry cost — capital, warehousing, insurance, obsolescence, shrink — is roughly $264K a year. Carry-cost percentages vary widely by industry; a rep who asserts twenty-two percent without asking should instead ask what rate Finance uses internally and run the math on their number.

Stacked, that example totals roughly $2.2M in annual benefit. Set that against a license and implementation package — the drill's worked example uses $850K in license plus $400K in implementation services — and payback lands inside a year. Teach reps to present payback in months, because capital committees think in payback periods and IRR, not in feature counts.

On timelines, be honest in the room and honest with the buyer. Manufacturing ERP total contract values in the mid-market and lower enterprise commonly run from roughly $150K to $2M, and the sales cycle for a multi-plant, multi-function evaluation typically runs nine to eighteen months. Implementation is measured in quarters, not weeks, and phasing by plant is almost always the right structural answer — it lets the customer tie each phase to a recovered dollar and gives you a reference site inside their own company before phase two starts.

The trade-off reps must be able to argue: a big-bang go-live across every plant is faster on paper and cheaper in professional services, but it concentrates all the change-management risk into one weekend. A phased rollout costs more in total services hours and stretches the revenue recognition, but each phase produces a provable number that funds the next. For a nervous buying committee that has been burned by a prior ERP failure, phasing is the concession that unsticks the deal — and it should be offered deliberately as a trade, not surrendered as a discount.

Also teach the honest cost lines reps love to omit: data migration and cleansing effort, integration work to the systems the customer names in discovery, internal backfill for the plant staff seconded to the project, and training time on the floor. Reps who surface these first are trusted; reps who let IT discover them in month four are dead.

Where teams get this wrong

The most common failure is treating this session as content delivery. A manager who spends fifty of the sixty minutes narrating slides about the framework has taught nothing. The drill only works when reps do the work on live deals in the room and the manager inspects the output. Budget at most fifteen minutes of teaching and forty-five of doing and inspecting.

The second failure is accepting qualitative pain because it is easier than pushing. "They want better visibility," "the current system is end-of-life," "leadership wants to modernize" — none of these survives a capital committee. If the rep genuinely cannot get a number, the correct next action is a follow-up discovery call with a specific ask ("twenty minutes with your plant controller on scrap and downtime"), not a demo. Managers who let unquantified deals through the gate destroy the entire ritual within three weeks, because the team learns the rule is optional.

The third failure is the champion who cannot defend the case alone. Reps confuse enthusiasm with capability. Test it directly: ask the champion to walk you through the numbers as if you were the CFO, and stay silent while they do it. If they stumble on the carry-cost assumption or cannot name the payback period, you have a coaching job, not a signature.

The fourth failure is the missing compelling event. A deal with no dated trigger — a legacy ERP sunset, an audit finding, a capacity wall, a customer compliance mandate, a plant acquisition — slips one quarter every quarter, forever. This is the single most reliable predictor of a stalled manufacturing ERP deal. Make every rep name the compelling event on their top opportunity before they leave the room, with a date attached. No exit without a dated trigger.

The fifth failure is faking the vocabulary. Reps who half-know APICS terms are worse off than reps who admit they are learning. If a plant manager says the master production schedule is not firming correctly and the rep nods without understanding, the next question exposes them. Coach reps to say "walk me through how you firm the schedule today" instead of bluffing. Curiosity reads as competence; bluffing reads as a vendor.

The sixth failure is demo sprawl. Every screen shown that is not tied to a quantified pain dilutes the business case and invites a feature comparison with a competitor. Three screens, three numbers, done. If the buyer requests more, that is a second session with its own agenda — and a reason to bring another committee member into the room.

The seventh, and the one that quietly kills the most pipeline, is leaving without scheduling the business-case review. A demo with no written follow-up is a demo the committee has forgotten inside a week. The written one-pager is the artifact that circulates when you are not there, and circulation is how a nine-to-eighteen-month cycle survives reorganizations, budget freezes, and champion turnover.

Finally: rehearse the standard objections rather than improvising them. "Implementations always blow the budget" — agreed, which is why we phase by plant and tie each phase to a recovered dollar rather than going live everywhere at once. "Our IT team is already underwater" — then we scope a managed go-live and put the integration hours in the statement of work so nobody discovers them in month four. "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. Each comeback concedes the buyer's point, then reframes it as a design decision you make together.

Decision framework: which motion to run, and when

Not every manufacturing opportunity deserves the same play. Teach reps a routing decision they make after first discovery, so effort matches deal shape.

If the buyer has a hard compelling event with a date — a vendor sunset notice, a failed audit, an acquisition closing — run the compressed motion: quantify two pains rather than four, get to the business case fast, and spend your energy on the decision process and procurement path. Speed is the value you are selling.

If there is no compelling event but the pain is large and quantified, run the champion-development motion: invest in building an internal advocate who can create urgency you cannot. That means arming them with the one-pager, rehearsing their pitch, and getting Finance to supply their own carry-cost and contribution-margin numbers so the case is theirs, not yours.

If the pain is unquantified and no compelling event exists, the deal is not qualified. Park it in a low-touch nurture and spend the hours on a deal that is. Managers should be willing to say this out loud in the drill — pipeline hygiene is a coaching act.

The MES-versus-ERP distinction changes the buyer, not the method. MES lives on the shop floor: real-time production, quality, and machine data. The buying center skews toward plant engineering and quality rather than the CFO, and the dollars usually come from scrap, overall equipment effectiveness, and compliance exposure rather than from inventory carry and close-cycle time. The pain-to-a-dollar discipline is identical; only the denomination changes.

Related questions

How long should the demo itself run in a manufacturing ERP cycle?

Twenty to thirty minutes for the first demo, covering exactly three capabilities tied to three quantified pains. Longer demos invite feature comparison and dilute the business case. Additional depth earns its own session with named committee members attending.

Who should own building the business case, the rep or the champion?

The rep drafts it; the champion owns it. If the champion cannot defend every assumption without the rep in the room, the case is not finished. Test this by having them present it back to you as though you were the CFO.

What if Operations loves us but Finance and IT stay cold?

You have a champion, not a deal. Build separate proof points: carry cost and audit trail for Finance, integration surface and uptime for IT. Ask your champion for warm introductions rather than emailing cold into two functions.

Should reps get APICS CPIM certified?

Certification is not required, but fluency is. Reps must use MRP, master production scheduling, available-to-promise, and cycle counting correctly in a first meeting. Studying the CPIM body of knowledge is the fastest route to that fluency.

FAQ

What if the prospect insists on a demo before any discovery?

Run a tight ten-to-twelve-minute teaser tied to the single pain they named on the call, then redirect: "to show you the rest properly, I need twenty minutes on your scrap and downtime numbers." A full demo with no quantified pain anchors the buyer on price and hands your competitor the value conversation.

The cycle is fourteen months. How do I keep the deal alive?

A mutual action plan plus a dated compelling event. Inspect the decision process every thirty days — who signs, in what order, against which budget. Deals that slip almost always lack a trigger forcing a decision; go find the ERP sunset, the audit finding, or the capacity wall.

How is selling MES different from selling ERP?

MES sits on the shop floor and deals in real-time production, quality, and machine data, so the buying center skews toward plant engineering and quality rather than Finance. The discovery discipline is unchanged — pain to a dollar — but the dollars usually come from scrap, OEE, and compliance rather than inventory carry.

What is the single biggest reason these deals die?

"No decision." The competitor is the status quo, not another vendor. The fix is a quantified business case the champion can defend alone plus a dated compelling event, because a committee with no deadline will always choose to revisit next quarter.

How often should this training run?

Weekly or biweekly, sixty minutes, same slot on the calendar. It is a ritual, not an event. The behavior being installed — quantify before you demo — only sticks through repeated inspection of live deals, and a quarterly offsite cannot deliver that cadence.

How do I handle a buyer who was burned by a previous ERP failure?

Agree with them immediately and get specific: ask what happened in the last go-live and listen for the missing change-management or adoption plan, which is the usual culprit. Then structure your proposal to answer that exact failure — phased by plant, adoption plan in the statement of work, each phase tied to a recovered dollar.

Sources

1. John McMahon, *The Qualified Sales Leader* — https://www.amazon.com/Qualified-Sales-Leader-Proven-Lessons/dp/0578895064
2. Association for Supply Chain Management (ASCM), CPIM certification and body of knowledge — https://www.ascm.org/learning-development/certifications-credentials/cpim/
3. MESA International, MES/MOM functional model and ERP integration guidance — https://www.mesa.org/
4. Michael Bosworth, *Solution Selling* — https://www.mheducation.com/
5. Neil Rackham, *SPIN Selling* — https://www.amazon.com/SPIN-Selling-Neil-Rackham/dp/0070511136
6. Matthew Dixon and Brent Adamson, *The Challenger Sale* — https://www.penguinrandomhouse.com/books/305198/the-challenger-sale-by-matthew-dixon-and-brent-adamson/
7. Force Management, Command of the Message methodology — https://www.forcemanagement.com/
8. APICS Supply Chain Operations Reference (SCOR) model overview — https://www.ascm.org/corporate-transformation/standards-tools/scor/

Related on PULSE

• [SIEM Software Selling to the Enterprise CISO — 60-Min Training](/knowledge/st386)
• [Identity Verification (IDV) Software Selling to Fintechs and Banks — 60-Min Training](/knowledge/st383)
• [Fraud and AML Software Selling to Tier-1 and Tier-2 Banks — 60-Min Training](/knowledge/st382)
• [Top 10 sales enablement drills for enterprise software reps](/knowledge/st0638)
• [Top 10 sales training workshops for enterprise software teams](/knowledge/st0637)
• [The Sandler Selling System: Ready-to-Run Mini-Training for New Hires](/knowledge/st0794)