Talk to Th3 Doc with Steve Meek

The episode has a handful of operationally grounded observations - backlog of net transactions as an early-warning signal, the build-vs-partner decision framework, and the real cost of scaling AWS infrastructure - but the density is low overall, with long stretches of generic entrepreneurship commentary, AI hype, and personal anecdotes that add little for a B2B operator.

“when we start to get nervous is when we have a whole bunch of kind of what we call net transactions are the, the first part, a whole bunch of those lined up and we're back and we get backlogged on the details”

“we are processing around 7,000 transactions a month in vision. And that equates out to about 1.2 million line, what we call lines of data”

Almost every frame in this episode is recycled: the 'AI is like the early internet' analogy, 'surround yourself with smarter people,' 'don't give up,' and the dot-com bubble cautionary tale are all shopworn takes with zero contrarian or first-principles thinking applied to the niche.

“it feels like the early days of the Internet when we were trying to figure out what the good use cases are”

“surround yourself with people that are smarter than you because they'll make you look good”

Walt is a genuine practitioner who has built a niche fintech/services business from three people to 24 in a specialized domain (mineral interest accounting for trust companies), giving him real operational credibility; however, the company is small in scale and the expertise is narrow enough that it limits broad applicability for most B2B listeners.

“we are headquartered in Fort Worth, Texas and we have offices in Oklahoma City and Ruston, Louisiana also”

“I'll never forget when we. The time we went cash positive in a month. That was pretty cool.”

There are some useful concrete data points - transaction volumes, sprint cadence, multi-office headcount - but the episode lacks revenue figures, client names, asset-under-management totals, or any comparative benchmarks that would make the numbers truly actionable for a listener trying to calibrate their own operations.

“right now, uh, we are processing around 7,000 transactions a month in vision. And that equates out to about 1.2 million line, what we call lines of data”

“we're doing a Sprint release much every six to eight weeks”

The host asks a few genuinely useful questions - particularly on build-vs-partner and on which metric gives the earliest warning of a problem - but undermines the craft with off-topic personal anecdotes, the gimmicky medical framing, and a consistent failure to push back on vague or incomplete answers.

“is there one of those that gives you kind of the um, I guess like the earliest warning that a client relationship or you know, workflow needs attention?”

“how do you decide when to build a capability inside your platform versus partnering with some of these specialized vendors?”