Key Moments
Stop Innovating (On The Wrong Things)
Key Moments
Startups should avoid innovating on non-product-related aspects like corporate structure or pricing, as this 'innovation juice' is scarce and better reserved for achieving product-market fit, the true miracle.
Key Insights
Founders have a limited amount of 'innovation energy' or 'juice' and should focus it on the primary miracle: creating something people want (product-market fit).
Innovating on corporate governance, such as choosing unusual incorporation states (e.g., Wyoming LLC) or complex structures (like OpenAI's nonprofit/for-profit hybrid), is a voluntary red flag and unnecessary risk.
Disproving fundamental startup advice or making contrarian bets unrelated to the core problem the startup solves (e.g., the hydrogen economy bet) distracts from the main goal and adds significant unneeded risk.
Choosing idiosyncratic programming languages or tech stacks simply because it's 'fun' or 'cool' can create long-term hurdles and is rarely justified if it doesn't directly serve the customer or product.
Business model and pricing innovation should be approached with caution; mimicking established practices (e.g., AWS pricing for cloud compute) can provide customer comfort, while overly complex or unique pricing can confuse and deter buyers.
Advice that promotes radical difference and uniqueness, often from branding or fashion, can be misapplied to software, where incremental improvements and adherence to best practices for core functions are often more effective.
Focus your 'innovation juice' on product-market fit
The core message from Dalton Caldwell and Michael Seibel is that startups possess a finite amount of 'innovation energy' or 'juice.' This energy is best directed towards the singular, monumental task of achieving product-market fit—creating something that people genuinely want and need. They liken this achievement to performing a 'miracle.' Attempting to innovate across multiple fronts simultaneously drastically lowers the probability of success. Therefore, founders should reserve their limited capacity for this crucial outcome and rely on established best practices for everything else. The analogy of 'innovation juice' highlights that it's a scarce resource that shouldn't be spread too thin, especially on non-essential aspects of the business.
Avoid unnecessary risks in corporate governance
A common pitfall observed by Y Combinator is founders trying to innovate in corporate structure or governance, viewing it as an advantage or a way to differentiate. This includes choices like incorporating in non-standard states (e.g., a Wyoming LLC) rather than the typical Delaware C-Corp, or adopting complex, untested structures like OpenAI's nonprofit/for-profit hybrid. Seibel describes these as 'voluntary red flags' and unnecessary bets where founders, despite knowing little about corporate law, believe they can outperform established norms. The implication here is that such decisions add complexity and risk without directly contributing to the primary goal of building a successful product, and can even deter investors or future talent who are accustomed to standard practices.
Don't innovate by disproving basic startup advice
Another prevalent anti-pattern is when founders choose to actively 'disprove' well-established startup advice or make highly contrarian bets that are tangential to their core business. Examples include trying to build a startup ecosystem around a small, isolated town or making a grand, long-shot bet on a future technology (like a hydrogen-powered economy) that is disconnected from the immediate customer problem the startup is solving. Even if these contrarian ideas have merit independently, attempting to integrate them into the early stages of a startup introduces unnecessary complexity and risk. The takeaway is that a startup is already a high-risk endeavor; deliberately adding more high-risk, unrelated bets is counterproductive and makes the already difficult game of building a company even harder.
Resist the temptation of 'nerd bait' like custom programming languages
Innovating on technical foundations, such as writing a custom programming language or choosing highly idiosyncratic tech stacks, is often driven by a desire for novelty or because it's perceived as 'fun' for the engineers. While a startup should be engaging, this kind of innovation can create significant long-term problems. It requires more development effort, hiring specialized talent becomes difficult, and it can hinder future scalability or integration. The example of Asana potentially writing its own language or Digg's high-risk technology choices that led to rollback issues illustrates how optimizing for engineering 'fun' over customer needs or stability can be a detrimental form of innovation. It’s a distraction from the core value proposition and can create future technical debt and operational hurdles.
Innovating business models and pricing can confuse customers
When it comes to business models and pricing, founders often make the mistake of innovating simply to be different, rather than prioritizing customer understanding and comfort. If a startup operates in a market where customers are familiar with established pricing structures (e.g., cloud compute pricing similar to AWS), adopting a radically different and complex pricing model can be a significant deterrent. Potential customers may not understand what they are buying or how much it will cost, leading them to abandon the purchase, even if they like the product. The key is that pricing should be clear and accessible, not a barrier to entry. Innovation here should aim to simplify and clarify, not to create confusion or implement a "gotcha" system.
Differentiate where it matters: product, not branding tropes
There's a tendency for founders to apply advice from other industries, like fashion or branding, where being radically different is often key to success. In the technology and software world, however, founders often succeed by doing '80% the same' as existing successful companies and innovating on the critical '20%' that solves a unique customer problem. Innovating on fundamental user interface elements, how buttons work, or website design in ways that decrease usability is a prime example of harmful innovation. Founders are cautioned against creating unintentional risk by trying to be overly unique in areas where standard practices ensure usability and customer adoption. The core principle is to serve the customer, not to satisfy a desire for novelty for its own sake.
Focus on the first miracle; save other innovations for startup two
The overarching advice is to prioritize the miracle of product-market fit for the first startup. Once a company has achieved a level of success and stability, founders can then indulge in more experimental innovations. This could include building custom languages, exploring complex corporate structures, or pursuing ambitious technological moonshots. However, these should be reserved for a second or subsequent venture, after the primary challenge has been overcome. The goal is to make the first startup's path as clear as possible by leveraging existing knowledge and avoiding unnecessary risks, thus maximizing the chances of achieving that foundational miracle. If a founder has the capacity to 'do other things,' they should recognize that those "other things" are best pursued after achieving that initial success.
Mentioned in This Episode
●Companies
●Concepts
●People Referenced
Stop Innovating on the Wrong Things: Startup Best Practices
Practical takeaways from this episode
Do This
Avoid This
Common Questions
Innovation juice refers to a company's limited energy and resources for innovation. Founders are advised not to spread this 'juice' thin across every problem, but to concentrate it on the core miracle of creating a product that people want.
Topics
Mentioned in this video
Mentioned as an example of a complex corporate structure (non-profit owning for-profit) that is not recommended, and its structure is seen as an 'instruction manual' for potential pitfalls.
Cited as an example of a company that made many high-risk technology choices, including a redesign they couldn't roll back, which was not related to core site functionality and ultimately caused problems.
Used as a counter-example to Dig, highlighting its success by focusing on being a social news site and not taking high-risk technology choices.
Used as a benchmark for pricing in cloud compute. Founders who dislike AWS are advised against creating unnecessarily complex or unfamiliar pricing models.
Mentioned as having written their own programming language when they started, which is presented as an example of 'nerd bait' innovation that might be fun but not core to customer value.
Mentioned as the standard corporate structure for startups, contrasted with founders who try to innovate in this area with less common structures.
Cited as a 'voluntary red flag' when used for startup incorporation, indicating a founder might be trying to innovate in corporate law unnecessarily.
More from Y Combinator
View all 562 summaries
14 minInside The Startup Reinventing The $6 Trillion Chemical Manufacturing Industry
1 minThis Is The Holy Grail Of AI
40 minIndia’s Fastest Growing AI Startup
1 minStartup School is coming to India! 🇮🇳
Found this useful? Build your knowledge library
Get AI-powered summaries of any YouTube video, podcast, or article in seconds. Save them to your personal pods and access them anytime.
Try Summify free