Ep #41 Is Your Company AI-Assisted or Actually AI-Native?

Kevin Williams and Matt open Alex Lieberman’s 30 Features of an AI Native Company and get through the first handful of items, starting with the one most organizations get wrong. Blueprinting your processes is the right first move. Replicating every existing step inside an AI system is not, because a model like Astra will happily reproduce a five-step handoff that was designed around people and tools that predate it.

Before that, Kevin walks through what he actually built with Astra last week: a 45-page presentation deck assembled from client research, downloaded imagery and past decks; a technical SEO project that produced a new page, four updates and seven draft articles in about 45 minutes; and a part-based 3D printable model of a cabin he used to own in West Virginia, generated from two photos and optimized for multi-color printing.

They also get into why the intelligence layer has no good off-the-shelf answer, why AI-first organizations that are smaller and founder-led can move when ISO-certified companies can’t, and whether the sunk cost fallacy still applies to systems you built nine months ago.

Topics covered:

– The caveat on blueprinting processes: input and output, not five steps

– Why every person in the organization needs a daily driver, plus a literacy layer

– Building an intelligence layer across email, Slack, transcripts and documents

– What Astra did with a deck, an SEO campaign and a 3D print

– Why security-mature organizations struggle to move at all here

– When to rebuild a working system and when to leave it alone