Framework
Understand the Engine
Why the moat is not what you built.
How it works
- 1Software is democratized. Code is democratized. Anyone can build a thing.
- 2The durable value is workflows, business logic, and their connection to strategy.
- 3Corollary: the moat is not what you built, it is why you built it that way.
Hear it on the podcast
Tokens Go to Zero, Energy Goes to Zero: What Do You Build When Intelligence Is Free?Listen to the episodeMore from this episode
The Panelist DJ MethodRyan's full structure for hosting an hour-long panel without it going off the rails.The Hook EditHow Jason improved Ryan's cold open in under a minute.The Operational Maturity SplitJason's diagnostic for where an AI engagement actually starts.The Trust Ladder, Starting With the Morning BriefJason's ceiling on what a single automation can do without executive buy-in.Model Routing as the DJ of the StackWhy routing models is business logic work, not model work.The Three Buckets of ITJason's structural map of what an IT department actually owns.The Handle, Not Just the CardJason's networking swag doctrine.Win, Loss, or BuffaloThe weekly ritual that closes the segment.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Strategy & Moats
The Shelf RiskMatt's framing for what agentic commerce does to a brand.The 20 Percent AI RuleWhy Filip thinks the model is the least defensible part of the product.Timing as Product StrategyThe founders who tried to build restaurant voice AI before GPT-3.5 had to train their own models - at great expense, with poor results. Loman launched two months after GPT-3.5 and got the same capability for the cost of an API call. Christian's principle: if an LLM cannot yet do the thing your product requires, waiting is sometimes the right strategic move. The technology timeline is part of your roadmap.The AI Holding Company ModelBuild a portfolio of AI-native service businesses under shared infrastructure rather than scaling a single product. The holding company model captures diversified upside from multiple category disruptions while sharing GTM, talent, and capital allocation expertise. Each company stays small by design - a team of five is a feature, not a constraint.Quality-Depth Over Geography-BreadthWhen facing pressure to expand into adjacent markets, choose depth in your current market over thin coverage across many. The quality of your service depends on institutional knowledge, relationships, and operational infrastructure that cannot be replicated overnight in a new geography.10-Year Problem DesignBuild solutions for the problem that will exist five to ten years from now, not the problem visible today. Requires outsider perspective, first-principles thinking, and organizational structures that support multi-year investment horizons.