Ask Me Anything: ERP and Manufacturing

This one skips the slides entirely — it’s just two people who’ve spent their careers in manufacturing ERP talking honestly about where the industry’s headed. Max hosts Jean Magny, Genius’s president, for a wide-ranging conversation that starts with how they each stumbled into this world (Jean from a self-taught coding hobby and an unglamorous first job in quality assurance; Max from aerospace liaison engineering into a pharmaceutical-equipment ERP rollout that hooked him for good) and moves into genuinely useful territory: why ERP will remain a company’s backbone even as AI reshapes the work around it, why an accounting system plus a pile of Excel files isn’t an ERP, and what actually separates a successful implementation from a stalled one. Jean is refreshingly blunt about vendor selection — RFPs stuffed with hundreds of feature questions and almost none about implementation are asking the wrong thing, since implementation, training, and customization can eat up half to three-quarters of total project cost. Both agree an ERP project is, underneath the software, a human transformation project — which is why having a real internal champion (not just a technically sharp new hire) matters as much as the software itself. If you’re evaluating your first ERP or trying to figure out why your last implementation stalled, this conversation is worth the listen.

What You’ll Learn In This Webinar

Chapter 1 — Introduction to ERP Manufacturing

Max welcomes Jean Magny for his first podcast-style session and asks about his path into ERP. Jean traces it back to teaching himself to code as a kid, studying physical then mechanical engineering at Laval University, and taking a first job in quality/ISO implementation in the late ’90s that unexpectedly taught him how an entire business operates — production, purchasing, sales, vendor and customer relationships. From there, he joined a small industrial engineering consulting group doing custom coding for manufacturers, which grew into Genius ERP as a software company — 31 years in manufacturing so far.

Chapter 2 — Transition to ERP and Software Development

Jean reflects that his path wasn’t a grand plan so much as his coding hobby ending up fully merged with his career. Max shares a similar arc: mechanical engineering, then aerospace liaison engineering (documenting undocumented in-service fixes for Pratt & Whitney and Bombardier planes), then project management building stainless steel pharmaceutical equipment at a small family business — where being part of that company’s ERP implementation convinced him IT-driven business optimization was where he wanted to be.

Chapter 3 — Future of ERP in Manufacturing

Asked where ERP is headed over the next ten years, Jean is confident it stays the backbone of the enterprise — the central source of data, KPIs, and decision-making. What’s changing is where the data itself comes from: increasingly from machines and other systems rather than people manually keying it in, which sets up the growing role of AI, since AI is only as useful as the data feeding it.

Chapter 4 — Impact of Artificial Intelligence on ERP

Jean predicts that within ten years, roughly half the skilled headcount needed today — in the shop and the office — may no longer be required to produce the same revenue, given demographic pressures and the efficiency AI-enabled applications bring to routine transactions. Beyond just surfacing data, he expects ERP/AI to eventually simulate the downstream impact of a decision (like reallocating stock from one job to another) across the whole business, rather than relying purely on experienced people’s judgment. He’s careful to note that ERP implementation itself remains fundamentally a human transformation project, not a technological one — some roles may combine or get renamed as individual tasks speed up. Max adds his own framing: the last decade’s cloud revolution enabled today’s AI revolution, and he expects AI to take over clerical, data-entry roles (like AP invoice entry) while shifting people toward oversight and exception-handling, letting companies keep growing without proportional headcount growth.

“An ERP project is more a human resource project in terms of transformation than something that is IT related.” — Jean Magny

Chapter 5 — Understanding ERP vs. Accounting Systems

Max asks why an accounting system plus Excel doesn’t count as an ERP. Jean acknowledges the technical gaps (database integrity, logging, security, multi-user risk) but focuses more on when this actually becomes a problem: Excel and a basic accounting system are a legitimate stage for a young or small business — like prototyping in wood before committing to steel — but become limiting once a company has defined its market and needs structure to onboard new hires quickly. He notes even large companies struggle to fully remove Excel, and that’s fine — it still has a place for prototyping or extracting data. Max adds that Excel’s core weakness is creating data silos between departments and lacking real-time visibility once someone completes a milestone elsewhere in the business.

Chapter 6 — Key Success Factors for ERP Implementation

Jean’s first factor: define your own specific “why” rather than generic reasons like saving time or reducing errors — identify the actual game-changing impact you’re after (like cutting delivery time from 20-24 weeks down to 12-16), since that clarifies priorities across every department. Second factor: since an ERP is a 7-10 year commitment, define a realistic Phase One scope and stick to it rather than letting it inflate chasing every feature shown in demos — Jean compares an unfinished ERP project to work-in-progress inventory sitting on a shop floor with essentially zero realized value until it’s actually completed.

Chapter 7 — Choosing the Right ERP Partner

Max raises the idea of “fit and focus” — choosing a product suited to your specific market rather than defaulting to a big brand name as a way to avoid risk — and frames ERP selection as choosing a long-term partner, not just software. Jean is skeptical of vendor evaluations built purely around feature checklists, noting RFPs sometimes ask 400-500 questions about software functionality and only 5-10 about implementation, even though implementation, training, and customization can represent half to three-quarters of total project cost. His recommendation: prioritize a partner whose team has deep, specific experience implementing companies like yours, since they can guide you toward best practices rather than you having to teach them your industry from scratch. Max adds that an experienced, manufacturing-focused partner already understands industry-specific realities — like nesting material before laser cutting, or managing long-lead items for OEM equipment — without needing it explained.

Chapter 8 — The Role of Internal Champions in ERP Projects

Max asks about the value of an internal “champion” versus customers expecting the implementation partner to handle everything. Jean uses a home-construction analogy: even a general contractor project needs one point of contact managing everything — and an ERP project is even more ongoing, since continuous improvement carries on well past Phase One, unlike a finished house. A champion prepared during onboarding becomes the internal leader driving that continuous improvement; problems arise when a champion role is deprioritized and customers just expect the system to “be implemented” for them. Jean shares a real example of a champion who started as a part-time mechanical engineer and grew into a full continuous-improvement leadership role as the company expanded. On whether a fresh technical hire makes a good champion, Jean argues technical skill alone isn’t enough — a champion needs business acumen, historical context on what’s worked or failed before, and enough organizational standing to navigate difficult role changes and internal politics; Max agrees the champion needs real leadership and influence so people trust their decisions.