What does a truly 'fast' startup launch look like?

A fast launch means being uncomfortable and accepting imperfection. Examples like Instacart and Magic show products that were 'hacked together' or extremely minimalist, designed to get user feedback quickly rather than being fully polished.

Are waitlists a valid way to measure launch readiness?

No, waitlists are often a form of self-deception. While they indicate interest, they don't provide actual product feedback. Founders can get caught in a loop of collecting sign-ups without putting a usable product in front of users.

What are founders afraid of when they delay their launch?

Founders fear that their product will be perceived as ugly, that flaws will be immediately obvious, that competitors or investors will find out too early, or that the reaction will be crushing and devastating.

How should I view companies like Dropbox, Rippling, or Stripe that didn't launch immediately?

These are exceptions, often due to founders having unique, deep domain expertise or having already built and launched similar successful products. Their path involved a significant advantage that most early-stage founders don't have.

What is the key difference between Rippling's first and second product builds?

Rippling's first product was a lean MVP with a simple form-based system, launched quickly. The second, more robust product build was justified because Parker Conrad had already gained deep insights and earned the right through prior success.

What's the core advice for an early-stage founder about launching?

If you are not an exception (like Parker Conrad with prior deep experience), the advice is clear: launch fast and move fast. Choosing not to launch or moving slowly is a daily decision; consider choosing differently today.

Key Moments

When to Launch Your Startup and When to Wait

Y Combinator

Science & Technology5 min read14 min video

Mar 15, 2022|142,632 views|3,308|127

YC Y Combinator yt:cc=on

Save to Pod

Key Moments

TL;DR

Most startups avoid launching early and fast, fearing a poor reception, likened to arriving at the Oscars unprepared. This fear causes them to over-optimize for a perfect, imagined launch instead of iterating quickly.

Key Insights

Startups often avoid launching early due to a misconception of launch as a singular, Oscar-like event, fearing a negative reception and wanting to present a polished product.

Instacart's early version was 'pretty dirty,' with founders and Craigslist hires doing deliveries instead of a sophisticated backend, demonstrating that a functional if unpolished product is key.

Waitlists are presented as a form of launching but are effectively a way to avoid launching, as they don't provide genuine product feedback.

Parker Conrad's Rippling is cited as an exception where a longer development cycle was justified due to his prior deep product insight and domain expertise from building Zenefits.

The key difference for exceptions like Rippling is that the founder had already built and scaled a similar product, earning the right to invest more time in a robust initial build.

Founders are encouraged to look at the early history of successful companies (e.g., GitHub screenshots from 10 years ago) to see how much simpler their initial versions were.

The "Oscar Ceremony" fallacy of launching

Many founders envision their product launch as a grand event, comparable to an 'Oscar ceremony' where they hope for widespread acclaim and celebrity-like treatment. This perception leads them to delay launch until the product is perceived as 'looking good' and in perfect shape, much like one wouldn't want to attend the Oscars in scruffy attire. This desire for a flawless debut instills a fear of turning up unprepared, causing them to spend excessive time honing the product rather than getting it into users' hands. The reality, however, is that most launches are met with little fanfare, and the focus should be on iterative development rather than a single, perfect reveal.

Understanding what "fast" truly means

Moving fast is a core tenet of startup success, yet many founders struggle to define or achieve it. Speed in a startup context is often uncomfortable and significantly faster than the pace adopted by large companies. For instance, when Instacart first went through Y Combinator, its initial product was far from polished. Co-founder Apoorva Mehta even used a friend to manually deliver orders during a demo, indicating a lack of a sophisticated backend. This 'dirty' but functional MVP, where founders and people hired off Craigslist fulfilled orders, allowed them to learn and iterate rapidly. This contrasts sharply with a year spent building complex algorithms and fulfillment centers before launch.

The danger of self-deception and optimization for an imagined reality

A significant hurdle for founders is the tendency to believe they are exceptions to the rule of launching fast. They might acknowledge the general advice but convince themselves that their specific situation warrants a different approach. This self-deception often manifests as optimizing for a hypothetical, 'perfect' launch that exists only in their minds. Founders imagine the ideal reaction to their product, a parallel universe where everything goes perfectly. When this imagined scenario receives more weight than the practical need to get a product in front of real users, it slows down development and iteration. This pursuit of an idealized launch, rather than focusing on gathering actual user feedback, can be a major impediment to progress. The fear is that users will immediately notice flaws or that competitors and investors will see an unpolished product, leading to missed opportunities or negative judgment.

Why waitlists are not a launch

Some founders attempt to create a sense of progress by building waitlists, believing this constitutes a form of 'launch.' However, this is often a sophisticated method of avoiding a true launch. While a waitlist might gather interest, it does not provide the crucial product feedback that comes from users actively trying and using the product. The process often involves 'mental gymnastics' to feel like one is launching without actually putting the product out there for real-world testing and validation. A simple form collecting emails is not the same as exposing a product to the market and learning from actual usage.

The rare exceptions and their underlying reasons

While the advice to launch fast is paramount, exceptions exist, often cited by founders like Dropbox, Rippling, and Stripe. The YC partners highlight that these are not typical cases. Rippling's founder, Parker Conrad, took over a year and a half to officially launch, but this was justified by his unique circumstances. He had previously built and scaled a successful company, Zenefits, in a very similar domain. This gave him exceptionally deep product insight and domain expertise, allowing him to accurately predict the product's requirements and invest time in building a more robust MVP. He had, in essence, 'earned the right' to a longer development cycle because he knew precisely what needed to be built.

Lessons from early stage growth of major companies

To counteract the tendency to over-build and delay launch, founders are encouraged to research the early histories of successful companies. By examining screenshots and feature announcements from the initial stages of platforms like GitHub, founders can internalize that these now-dominant companies started with much simpler products and lower stakes. Their initial feature sets were less complex, and they focused on getting on the board, not on presenting a gargantuan, fully-featured product. This historical perspective helps founders set more realistic expectations for their own initial launches and embrace an iterative approach.

The founder's daily choice to launch or wait

Ultimately, the decision to launch quickly or to wait is a daily choice. Each day a founder decides not to launch, or chooses to move at a slower pace, they are making a conscious decision that impacts their startup's trajectory. The advice for the vast majority of early-stage founders is straightforward: if you are not a Parker Conrad with unparalleled prior experience in the exact domain, then the general advice to launch fast and move quickly is the correct path. The call to action is simple: choose differently today; choose to launch faster and iterate.

Mentioned in This Episode

●Companies

●People Referenced

Startup Launch: Do's and Don'ts

Practical takeaways from this episode

Do This

Launch early and move fast, even with a 'dirty' or minimal product.

Embrace iteration; launches are continuous, not singular events.

Focus on getting a product in front of users to learn live.

Be rigorous about understanding the true journey of successful exceptions.

If you're not a seasoned expert like Parker Conrad, launch fast.

Avoid This

Don't wait for a perfect launch or 'Oscar ceremony' moment.

Don't lie to yourself about being an exception.

Don't rely solely on waitlists for product feedback; they are just forms.

Don't get slowed down by optimizing for an idealized, unrealized launch.

Don't assume your situation mirrors founders with deep domain expertise and prior success.

Common Questions

Founders often delay launching due to a desire for a perfect 'Oscar ceremony' launch, fearing negative reactions, and wanting the product to be polished. They sometimes lie to themselves, believing they are exceptions to the 'launch fast' rule.

Topics

Mindset & Self-Improvement Business & Entrepreneurship Product-market Fit Startup Advice Iterative Development Early Stage Startups Founder Psychology Startup Launch Minimum Viable Product (MVP)

Mentioned in this video

Companies

Stripe

Mentioned as an exception to the 'launch fast' rule, suggesting that some successful companies did not launch publicly in their very early days.

Rippling

A company discussed as an example of a longer, more deliberate launch process due to the founder's deep domain expertise and prior experience. Its initial product, however, was a lean MVP.

Magic

A company that launched with just a website and a phone number, instructing users to text them for services, showcasing a rapid and simple approach to testing an idea.

Zenefits

A previous startup founded by Parker Conrad, which was a customer of his later company Rippling, demonstrating his deep domain expertise.

Instacart

A grocery delivery company cited as an example of a 'dirty' or minimally viable product launch, where initial functionality relied on manual workarounds like friends driving to stores.

Dropbox

Mentioned as an exception to the 'launch fast' rule, suggesting that some successful companies did not launch publicly in their very early days.

GitHub

Mentioned as a platform where founders can look at the historical development and early, simpler versions of successful products to understand iterative growth.

People

Paul Graham

Co-founder of Y Combinator, whose advice ('YC Paul Graham 101') on launching early is referenced as fundamental but often ignored.

Parker Conrad

The lauded founder of Rippling, presented as a rare case of a founder with sufficient prior experience and insight to justify a longer, more complex initial product build.