Get outside the building and show people prototypes
Josh Woodward stresses getting outside the building and showing people prototypes as the way to evaluate product-market fit, rather than relying on internal debate.
Explore
34,920 results · Most relevant
Worth exploring
WHY · 34197 cleared results from 497 sources on record
Take many shots and live in the future to find product-market fit
Josh Woodward advises that finding product-market fit is a numbers game: you have to take a lot of shots, throw yourself out there, and try to live in the future a little bit to chase it. He acknowledges that sometimes you get excited and build a product that's just not good — that's part of the game.
Lock down content, contact, and access with tightly sculpted credentials
Patterson's third pillar of agentic security: restrict what the agent can access with tightly sculpted credentials and restricted permissions. He warns that teams generally give agents access to everything because 'it needs access to do the work,' violating least-privilege principles, and that assuming AI won't make human mistakes leads to over-permissive access even though AI is exploitable by the same vulnerabilities.
Find the courage to be ridiculed
The host urges viewers to develop the courage to be ridiculed, presenting it as one of the core traits of charisma drawn from Trump and Mamdani, and encouraging people to learn it from both regardless of whether they love or hate them.
Iterate on guidelines by watching agent output and tightening as you go
The best guidelines come from watching what the agent makes, noticing where it needs more direction, and tightening things up as you go. When the agent produces off-system output, tighten the guidelines rather than adding instructions to each prompt.
Play your own games of your own design
Hormozi's culminating advice: play your own games of your own design, where if you were to win, you would be happy with the W, and the price it came at was one you were willing to pay.
Start shipping and let your moat develop over time
Anish Acharya advises founders to start shipping and let their moat develop over time rather than trying to design it upfront. He pairs this with the script 'Moats are most often discovered, not designed,' warning against overthinking upfront strategy.
Reorganize the whole company around AI, not just tool access
Anish Acharya distinguishes between merely using AI and reorganizing your entire company around AI, recommending the latter. He suggests asking: if AI were infinitely intelligent and astonishingly cheap, how would you reorganize the company? He also says to give the average employee more credit for embracing AI tools, citing a 'Jedi Academy' concept where everyone at a company, including mechanics, is taught to use the new tools.
Move the conversation forward instead of letting it stall
When an interaction is going well, move it forward by asking when she's free rather than staying in small talk; many guys get into good interactions but fail to do this, wasting momentum.
Get the number and lock in plans mid-interaction
Set up the idea of hanging out in the future during the interaction, then get her phone number and lock in the plans in the middle of the interaction, not after it ends.
Embed Codex into your product via AppServer
Charlie Guo recommends embedding Codex into your product using AppServer. This lets your users use their ChatGPT subscription and token budget to power your product. He says the AppServer is a useful way to integrate into your own platforms if you want to build agents on the cloud, manage different agent providers, or build a unified layer in a large organization.
Define what success looks like before categorizing failures
The speaker advised defining requirements — what a good report looks like for your agent — before categorizing failures, noting that many teams instead ship an agent and react to complaints without ever defining the bar up front.
Pivot to AI-Native to Survive Existential Threats
When facing existential threats from AI-native startups and large incumbents, a company must pivot to being AI-native rather than gradually layering in AI features. Ignore industry experts who claim customers fear new technology; validate directly with customers instead. Push through internal and external resistance, neglect other burning fires, and go all-in on AI.
Consequential creator advice requires independent verification before Today can promote it.
Build an Extremely Opinionated Product for AI Agents
To benefit from AI agents, build an extremely opinionated product that enforces a specific system and best practices. This creates a unique data advantage and a moat that generic AI models like ChatGPT or Claude cannot easily replicate. The software should drive the outcome for the user without manual intervention.
Hire a senior, full-stack generalist as your first developer
Derrick Reimer recommends hiring a developer with at least five years of experience, a full-stack generalist skill set, and a bias toward action and shipping. Avoid specialists and candidates who have only worked at large companies.
confident
Screen for autonomy, flexibility, and cultural fit
Derrick Reimer advises hiring a developer who thrives working autonomously, is flexible about codebase conventions, willing to let the founder make final calls, and open to using modern tools like AI coding assistants. Avoid candidates who are too opinionated or fight over small conventions.
confident
User Experience and Community as Moats
Erik Allebest recommends relentlessly focusing on user experience above all else, especially in a market without patent protection. He states that product, community, and content are the only durable moats, and that taking care of the community and product builds a great business.
Focus on Whether Agreements Are Met, Not Intent
Intent is a red herring; especially early in a relationship, do not judge someone's intent. Focus on whether the agreement was met, as why someone breaks an agreement is less important than that they broke it.
Take 100% Responsibility for Your Side of the Relationship
Taking full responsibility for a relationship is toxic. Instead, take 100% responsibility for your side: be honest, clear, and communicative, and bring your side of the deal. Then, only check if the agreed-upon thing happened or if there is no deal.
Focus on High-Return Activities and Avoid Distraction
Hormozi advises to continue allocating resources towards the things that are getting the highest return, rather than pursuing new, uncertain opportunities. He frames this as prioritizing actions that are certain to produce a return over those that might. He also warns that proposing new initiatives is often a sign of emotional discomfort with the current situation, which leads to distraction from what actually works.
Protocols you can run
WHY · 59 of 59 published protocols
Adversarial Generators and Failure Analysis
Use saved training trajectories and a controlled intervention to explain a failure, separating equilibrium theory from observed empirical stability.
Backpropagation Without Autograd
Demonstrate all 3 repaired bugs and defend why a passed gradient check is necessary but not sufficient for generalization.
Bayesian Inference and Graphical Models
Use the tractable fixture and posterior predictive results to separate approximation, sampling and model errors; justify one revised modeling assumption.
Source analyses
WHY · 664 of 664 current source analyses
Choose sources → to get a library of your own and a daily brief.