Lee
Stout

Two practices. One clear line between them.

The platform decides the door. Odoo work goes to Staudt Solutions. Every other ERP goes to Staudt Advisory.

Most ERP advice comes from IT. This came up the other way.

Lee Stout started as a mechanic and at a parts counter, then moved through planning, master scheduling, materials management, and configuration management. Since 2014 he has architected and implemented ERP from the IT side. He learns how a plant actually runs before he reads a spec sheet, which is why the systems he guides into place survive go-live and the three months of drift that follow it.

Straight shooter. Calm in the chaos. A partner, not a vendor. He has seen this movie before: at Cymer (now part of ASML), where he cut sixteen weeks out of the new-product development cycle, and at Hologic, where the stakes of getting the system right were measured in shipped product.

In the trade press

For editors, producers, and event organizers

Everything needed to feature, quote, or book Lee Stout, in one place.

Download headshot ↓

JPG · 1122 × 1122

Short bio · 50 wordsCopy

Lee Stout is a manufacturing ERP architect and the founder of Staudt Advisory, an independent ERP advisory practice, and Staudt Solutions, an Official Odoo Partner. He spent 25 years running MRP and ERP inside manufacturing operations at companies including Cymer, Hologic, and Masco, and has architected and implemented ERP since 2014.

Full bio · 140 wordsCopy

Lee Stout is a manufacturing ERP architect and the founder of two practices: Staudt Advisory, an independent, platform-neutral ERP advisory firm, and Staudt Solutions, an Official Odoo Partner serving manufacturers and distributors.

He came up through operations, not IT. Starting as a mechanic and at a parts counter, he moved through planning, master scheduling, materials management, and configuration management, including roles as Materials Manager and Configuration Manager at Cymer (now part of ASML) and Master Scheduler at Masco. Since 2014 he has architected and implemented ERP on Oracle EBS and Fusion, Microsoft Dynamics, Plex, and Sage, for companies ranging from startups to $8 billion in revenue, with consulting clients including Abbott.

He writes for SupplyChainBrain and Manufacturing Tomorrow on why ERP succeeds or fails after go-live, and why the answer is usually found where the work gets done, not in the software.

Topics Lee writes and speaks on

1. The real go-live happens three months in. Why ERP drifts after launch, and how to catch it before the shadow spreadsheets come back.
2. Recover before you replace. Why a new ERP rarely fixes a broken process, and how to tell which problem you actually have.
3. What operators know that the implementation team never asks. Floor-to-ERP versus IT-to-ERP.
4. BOMs, engineering change, and inventory accuracy. The manufacturing data that decides whether an ERP works.