Transit Unplugged

The episode provides solid foundational knowledge about NEMT operations, broker mechanics, and integration with transit systems, with useful historical context on technology evolution. However, it relies heavily on narrative explanation rather than surprising insights - most claims are straightforward descriptions of how the system works rather than non-obvious observations that would challenge an operator's existing mental models.

“what good is it to have medical insurance if you can't get to the doctor”

“the broker's job is to answer that call, schedule that appointment, and then make sure that the appropriate transportation is available”

The framing of NEMT as integral healthcare infrastructure rather than peripheral transit is conceptually sound but not contrarian - this is industry consensus. The discussion of ecosystem coordination and breaking down silos is sensible but well-trodden. The guest recycles familiar frameworks (economies of scale, technology adoption curves, risk management) without pushing against conventional wisdom or offering first-principles reimagining of the space.

“we would get more bang for our buck”

“the software is definitely evolving, but it has to do more than just math”

Steven Feist is a legitimate operator with 20+ years hands-on experience running NEMT programs across multiple states (Colorado, Texas, Oklahoma, Connecticut, Philadelphia area), and currently serves as COO of a real organization. He speaks from direct execution experience rather than theory, which is valuable. However, the conversation doesn't press him on specific strategic decisions, financial performance, or controversial trade-offs that would fully test his depth.

“over 20 years, uh, and worked very closely with transits in, in Colorado, Texas, Oklahoma, and other places”

“CTS is a not-for-profit going on twenty-five years in the Connecticut area”

The episode includes some concrete details (2,000 passes/month to Philadelphia, SEPTA partnership, use of Momentm software, specific states and programs) but lacks quantitative depth. No budget figures, cost comparisons, health outcomes data, ride volumes, or performance metrics are discussed. Claims about technology evolution and system improvements are largely anecdotal rather than evidence-based.

“about two thousand passes, a little, little shy of two thousand passes a month, uh, for two thousand different people”

“we now are able to create polygons in the software”

Paul Comfort asks reasonable setup questions and occasionally follows up (e.g., asking about Philadelphia specifics, autonomous vehicles), but rarely pushes back or challenges claims. The conversation flows pleasantly but lacks sharp interrogation - Feist is largely allowed to deliver prepared narratives without being pressed on contradictions, costs, failures, or difficult trade-offs. Questions are often surface-level invitations to elaborate rather than probing digs.

“Tell us what all that is and how it works”

“So tell me how that works in Philadelphia”