One Order of Operations for Starting a Startup by Michael Seibel

Core Thesis and Framework

• The primary barrier to founding a startup for technical talent is the misconception that a startup requires a pre-existing "great idea" rather than a problem-solving process.
• Founders are advised to treat idea generation as an active process using a specific four-step framework rather than waiting for organic inspiration.
• The recommended order of operations is:
  • Identify Passion: Pinpoint a specific problem the founder is personally passionate about solving.
    • Personal problems (e.g., affordable childcare, stroller accessibility) are prioritized because the founder possesses deep domain knowledge and validates if the solution works for them.
  • Brainstorm Solutions: Gather friends to discuss the problem, treating initial solutions as hypotheses to be tested rather than final answers.
    • Select co-founders based on the ability to iterate on ideas collaboratively (e.g., pivoting from "make the sky red" to "tint windows red") rather than simply agreeing or disagreeing.
    • Involving others early fosters a sense of ownership that helps sustain the venture.
  • Build and Launch MVP: Immediately focus on building a Minimum Viable Product (MVP) to convert the idea into a functional reality.
    • Founders should avoid premature steps like incorporation or fundraising, which often serve as procrastination tactics.
    • MVPs can be simple (e.g., manual processes powered by spreadsheets) and require no legal structure to begin.
    • Securing the first one to two paying customers serves as a critical test of team compatibility and generates necessary excitement and leverage for future fundraising.
  • Iterate: The goal is to validate the hypothesis through repetition rather than achieving a perfect solution upfront.

Rejected Paths and Common Pitfalls

• Path 1: Idea-First Pitching: Attempting to pitch investors based solely on an idea without a working product is considered ineffective in the current market.
  • Venture capitalists are inundated with pitches; a deck alone is insufficient to differentiate a startup.
  • This approach fails to demonstrate "real fire" or traction, which is now a standard requirement for investment.
• Path 2: Outsourcing Development: Founders without technical skills often hire external contractors to build the MVP.
  • This path frequently leads to financial depletion due to the high cost of repeated iterations required to fix subpar outsourced code.
  • Contractors often lack the incentive to fix fundamental flaws, resulting in a "shitty V1" that offers no traction.
  • Founders who outsource often find themselves unable to attract technical co-founders later because they arrive with no users, a broken product, and depleted savings.
  • The speaker argues that securing a technical co-founder is typically cheaper and more sustainable than paying for outsourced development and iterations.

Specific Observations on Problem Validation

• Founders should evaluate potential problems based on two criteria: frequency and intensity.
  • Case Study: A woman initially proposed a "meta-startup" offering advice to other startups, which was dismissed as a cop-out lacking a direct market.
  • When asked about her personal life, she identified a lack of affordable childcare.
  • Childcare was validated as a high-intensity problem affecting a massive demographic, guaranteeing significant value if solved.
  • The initial "stroller-friendly" idea was initially dismissed due to low frequency (only a problem in unfamiliar areas), whereas childcare is a constant, high-intensity pain point.
• Successful startups often originate from work-life frustrations where the founder identifies a repetitive task or system failure ("this sucks") and builds a tool to sell to their own job.

Forward-Looking Statements and Market Trends

• The startup landscape has shifted from the 1990s, where high barriers to entry (software costs, hosting) made a business plan the only asset founders could present.
• In the current environment, the ease of building and hosting software means founders must bring tangible progress (users, product) to investor meetings rather than just concepts.
• The speaker predicts that the "lucky" path of raising on an idea alone is rare; the sustainable path relies on being "good" through early execution and MVP validation.
• Founders who attempt to raise money before securing a technical co-founder or building a product are likely to waste their own savings on iterations that fail to gain traction.