Building got faster. Validation didn't.

Hey friends 👋

“AI native” is everywhere right now—and almost nobody using the label actually qualifies. This week, Cameron and JDM dig into what it actually means to build with AI at the core of your startup (it’s not about your workflow tools), and why the founders most excited about shipping fast are making the same old mistake in a shiny new wrapper.

There’s a meaningful difference between AI compressing your build cycle and AI being the reason your company exists. Get that wrong, and you’re efficiently moving in the wrong direction—stacking assumptions on top of assumptions, measuring inputs instead of outcomes, and calling it traction.

Building got faster. Validation didn’t. Customers still decide on their own timeline, no matter how quickly you ship.

JDM also has some personal news this week—Emilia has arrived, and the Miller family is officially a party of four. Cameron’s growing his own crew too, but his is decidedly more… reptilian.

As always, thanks for listening.

—Cameron and JDM

Share

00:00 Introduction

03:15 What “AI native” actually means

06:00 The build vs. validation gap

15:00 Efficiency vs. evidence: the core mistake

20:00 Sequencing violations

23:00 Frivolous Thoughts