The ERP Advisor

The episode provides practical, operational guidance on staffing different phases of ERP selection with concrete phase-by-phase recommendations (needs analysis, mini demos, discovery, final demos, due diligence, contract negotiation). However, the insights are relatively straightforward and lack novel analysis - the core advice (involve the right people at the right time, balance team size, communicate with stakeholders) is standard practice in enterprise software projects. There is substantial filler, throat-clearing, and repetitive explanation that dilutes the density of new ideas.

“you really want to look for those people who try to drive change, who are innovative thinkers”

“if they can't see the art of the possible and see past maybe a bad demoer, which you can't always control know up front if that's going to happen. Um, it can really stall or even get you to a no decision.”

The episode recycles well-known project management principles (stakeholder engagement, phased approaches, change management). The framing of staffing decisions across ERP selection phases is somewhat structured but not particularly novel - practitioners familiar with enterprise implementations will recognize these concepts. The advice about finding people who can 'see the art of the possible' is the most original insight, but it remains anecdotal without deeper methodological development.

“you want to have some of them because they're going to get you through the process”

“if you have too many cooks in the kitchen, you're never going to get it done.”

Quentin DeWitt has 20+ years in IT leadership, has directed teams as a Director of IT and Director of Technical Support, and now serves as principal consultant at ERP Advisors Group. He demonstrates genuine practitioner experience with hundreds of ERP demos and implementations. However, he is speaking primarily as a consultant/advisor rather than as an operator who has executed selections at a large company, which limits his caliber relative to true executive practitioners who have owned P&L impact from these decisions.

“Quentin has been in the information technology business for over 20 years. He has led teams as a director of IT”

“I've been in hundreds and hundreds of demos and that's often one of the greatest challenges”

The episode lacks concrete data, named examples, or quantified metrics. There are no specific case studies, dollar figures, implementation timelines, or named companies referenced. The advice is abstracted to general principles (e.g., 'usually four or five people' for core team, 'maybe 20 different software platforms'). While Quentin references his experience with 'hundreds and hundreds of demos,' no specific outcomes, metrics, or examples are provided to substantiate the guidance.

“You might go through 4, 6, 8, 10, 20. There are thousands of different software platforms out there.”

“usually you don't want more than like four or five people involved with that.”

The host (Speaker B) asks clear, logical follow-up questions that progress through the ERP selection phases methodically. However, there is minimal pushback, challenge, or productive disagreement. The host occasionally adds personal anecdotes (e.g., changing Zoom) but rarely probes Quentin's claims deeply or asks for evidence. The conversation is cordial and well-structured but lacks the friction and deeper questioning that would elevate it to sharp, investigative interviewing.

“And funny enough, this next phase that we're going to talk about, I think is one where people. Mini demos, where people think we all need to be involved, everybody needs to come, everyone needs to see the product, but that's not the case. So can you talk a little bit about that phase?”

“And that's interesting because, I mean, these final demos can go full days. Right. Like, they can be. They're deep.”