F.U.E.L. Podcast

The episode contains a handful of real operational benchmarks (40% MPI close rate, 407 hours/month benchmark, sub-2.5-year average advisor tenure) that a service manager could use, but the overall density is low due to extended conversational meandering, mutual agreement loops, and repetition. Most insights are industry-conventional rather than genuinely non-obvious.

“Three years in a row, it keeps shaving a few months off, just under two and a half years now, average turn on an advisor.”

“if we get 40 hours of recommendation coming from my team, I need to close 16 hours of that as an advisor. That's what we say at the Institute, 40%.”

The episode mostly recycles conventional fixed-ops wisdom - onboard better, document processes, tie pay to performance. The one semi-fresh reframe (blaming the trainers rather than the trainees) is briefly raised but not developed. 'People don't quit their job, they quit their leadership' is a well-worn phrase offered without attribution or challenge.

“are we blaming the generation of learners, right? Are we, are we blaming the advisors for not being efficient... or should we actually be blaming the generation of the trainers and leaders”

“people don't people don't quit their job right they quit their leadership”

Rick Ulin is a genuine 36-year retail practitioner who ran dealerships and transitioned into curriculum-based instruction at NCM Institute - a credible, practitioner-turned-educator profile. His knowledge is applied and specific to the domain, though the conversation doesn't fully exploit his depth of experience.

“coming off of 36 years in retail at the dealership level. Started in the parts department back in the early days”

“always ran them through a fixed ops brain so passionate about the business”

Several concrete benchmarks are cited - 40% close rate on MPI hours, 407 hours/month industry benchmark, sub-2.5-year advisor tenure trend, hours per tech per day under 8 - which gives the episode real evidential weight. However, no specific stores, geographic markets, named case studies, or dollar figures are referenced, keeping specificity at a moderate level.

“benchmark is 407 now some of that is going to be the cdk numbers are filtering through and that's going to clean up in time by the end by the time we get through august”

“Hours per tech per day or only are under eight”

The host routinely answers his own questions, shares extended personal anecdotes, and defaults to agreement ('I love that,' 'I'd have to agree,' 'you hit it right on the head') rather than following up with probing questions. There is no pushback, no challenge to any claim, and the questions are frequently multi-part and unfocused.

“Yeah, I mean, I think you hit it right on the head. And I also think it kind of gets missed a little bit when we're, when we're putting goals out there and like, you know, again, and kind of putting the math behind it.”

“I like you, you know, you're saying that we're kind of lacking in the process. So if we were working with a store, if we were working with some people and we said, you know, Hey, if you're going to start instituting a process of retaining advisors, really retaining advisors, you know, where would be the first step”