Latest Interviews
Showing 1–6 of 6 transcripts.
Clear all filters- Y Combinator7 min
The Biggest Mistakes First-Time Founders Make - Michael Seibel
The event outlines critical strategies for startup success, emphasizing that founders must select problems aligned with personal passion and choose co-founders based on pre-existing relationships to ensure long-term commitment. It advocates for rapid product launches within a month to enable user validation, arguing that external distractions like press events often distract from the essential work of shipping an MVP. Furthermore, the discussion highlights the necessity of implementing user analytics and acquiring initial customers through the founder's network to drive effective iteration and growth.
- Y Combinator2 min
Michael Seibel: How do you decide what to build next?
The presentation argues that product development should prioritize rapid, iterative cycles over perfection to quickly validate concepts and isolate successful elements. Using Justin TV as a cautionary case study, it illustrates how a strategy of "swing for home runs" leads to a "spiral of death" due to the inability to pivot from failed features. The speaker concludes that organizations must replace long, visionary planning with short-term "build-measure-learn" processes to sustain momentum and avoid stagnation.
- Y Combinator4 min
How Much Equity to Give Your Cofounder - Michael Seibel
This discussion establishes equity splits as a long-term retention strategy rather than a static negotiation outcome, emphasizing that CEOs must prioritize founder motivation over immediate equity fairness. Standard vesting schedules with a one-year cliff function as a critical safety mechanism, allowing companies to reverse hiring mistakes without long-term damage while encouraging co-founders to internalize true ownership. Consequently, the presentation advises that equitable grants should generally be generous and tailored to ensure co-founders remain deeply committed through organizational challenges.
- Y Combinator5 min
How to Find a Technical Cofounder - Michael Seibel
To secure technical co-founders, the speaker recommends prioritizing direct inquiries to friends and current coworkers who actively code, converting interest into formal offers with specific equity and salary details rather than informal requests. If immediate networks are insufficient, the strategy involves joining a small startup for one to two years to build proximity to engineering teams or acquiring coding skills independently through online platforms. Additionally, college is highlighted as a high-yield environment for identifying future co-founders, as demonstrated by the successful recruitment of peers who were learning to code.
- Y Combinator6 min
How to Get and Test Startup Ideas - Michael Seibel
This session challenges the notion that startup ideas must be perfect at inception, using Justin Kan's co-founding of Twitch to illustrate how prioritizing deep personal connection to a problem over the concept itself drives resilience. Kan advises founders to maintain "problem books" rather than idea logs, validate issues through direct community impact, and rigorously handpick early users to test minimum viable products. Ultimately, the discussion emphasizes that successful entrepreneurs must fall in love with the customer's pain point rather than their initial product, ensuring the team remains uniquely qualified to solve a specific, verified need.
- Y Combinator6 min
How Pitching Investors is Different Than Pitching Customers - Michael Seibel
The event analyzes the critical divergence between investor and customer pitches, noting that investors seek scalable business potential while customers require immediate problem resolution. It details how founders must employ industry jargon to build credibility with clients during sales calls, whereas investor presentations demand plain language to clearly communicate monetization and market size to an uninformed audience. Y Combinator observations highlight that most new founders initially struggle to maintain these distinct narratives, requiring iterative practice to effectively address the different motivations of each stakeholder group.