Framework
The 'Have To' Startup Test
Don't start a company to start a company. Wait for the observation you cannot not pursue. That's the one you'll have the most fun with and the best shot of building well.
How it works
- 1James started five companies — only some passed the 'have to' test before launch.
- 2His previous company: raised too much money before product-market fit, beat his head against the wall for six years.
- 3Guild AI: observed it working at Meta, watched colleagues independently build their own versions, recognized the inevitability.
- 4Confusing burnout with lack of inspiration is common — new company doesn't fix an inspiration problem.
- 5The observation you can't walk away from is the one worth building around.
Hear it on the podcast
Speed Is Killing AI StartupsListen to the episodeMore from this episode
Stability Over SpeedShipping faster is not always progress — fragile wins disappear if you cannot reproduce them.Agents Need Management, Not MythologyEnterprise agents need permissions, controls, logs, and oversight — treat them like employees.The Internal App Store ThesisCompanies will need centralized systems to discover, manage, fork, reuse, and govern agents.Swarms Over Super-AgentsMany specialized agents beat one all-purpose agent — easier to debug, govern, and improve.The Productivity TrapMore code does not always equal more progress — define what productivity means before multiplying it.Historical Pattern RecognitionBrowser wars, spreadsheets, falling input costs — AI is the latest chapter in a very old story.Wait for the Idea You Cannot IgnoreDo not start a company just to start one — wait for the opportunity you feel compelled to pursue.The Enterprise Agent Control PlaneEnterprises deploying AI agents at scale need a centralized governance layer — the same way the iPhone created demand for mobile device management.Bionics vs. RoboticsThe frame you use to think about AI agents determines where you apply them. Bionics augments human capability. Robotics replaces it. The difference changes everything downstream.The Science Fiction Challenge MethodDon't mandate AI tool adoption. Put impossible-sounding challenges in front of your team and let the tools earn their usage organically.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Finding & Validating Ideas
The Tight Circle Photo Sharing ThesisPeople share photos freely when the social environment is tight, secure, and trusted — not because the product is good, but because the people around them feel safe.The B2G Pivot FrameworkWhen you have users but no anchor, it's not a product problem. It's a customer depth problem. Go vertical, raise the price, and let the credit card prove the market.The 10 Uncomfortable Conversations RuleYou do not deserve to write a single line of code until you have survived ten customer conversations where you genuinely tried to be told no. Validation is evidence that bruises — not vibes that confirm what you already believe.The Founder's Three GuardrailsBefore investing time in any idea, run it through three filters: Is it fun? Does it make money? Is it of service? Add a fourth: Can I be best in the world at this? If any answer is definitively no, stop and move on.The Only Hearing Yeses WarningIf you are only hearing yeses from the market, that is not validation — it is a sign you are not pushing hard enough.The Three Checkbox FrameworkBefore building any AI product, three boxes must all be checked: (1) distribution on the cap table — equity to people already inside your target market's networks, (2) defensible IP — proprietary data, SOPs, or formulas that cannot be replicated with another model call, and (3) an industry expert involved. If you cannot check all three, the project does not start. Not pauses — does not start.