Fireside Chat, Interview
Investors Said No, Now What?
- Founders should assess rejection patterns only after receiving 15 to 25 consistent reasons, rather than treating single rejections as definitive signals.
- Investors are predicted to reconsider companies that demonstrate concrete progress, such as acquiring 10 new customers or altering fundamental business facts, over timeframes of approximately one month.
- A single founder pivoting an entire company immediately after a two-minute rejection email is interpreted as a signal of low conviction and reduced funding likelihood.
- Approximately 60% of YC-funded companies were previously rejected by the firm, indicating that past rejections do not preclude future investment if the startup shows improvement.
- Rejection rates of up to 90% are considered normal for investors, suggesting that many decisions are based on pattern matching rather than comprehensive market analysis.
- Founders are advised to maintain confidence and continue pitching, as investors may change their minds if founders update them monthly with positive developments.
- Investors generally possess less specific knowledge of a startup's market and product than the founders, yet they may reject companies that appear disorganized or lack enthusiasm.
- Founders lacking clear communication skills or providing conflicting numbers face rejection even if they hold strong credentials, as this prevents investors from understanding the business.
- The belief that "no" is permanent is identified as a wrong assumption, as investors can be won over by actions rather than changes to pitch decks or wording.
- If a founder cannot return with a deeper understanding of users than the investor, it is viewed as a bad sign regarding the founder's capability.
- Investors often reject founders who do not "stack rank" highly compared to previous successes, rather than necessarily disliking the specific business idea.
- Founders are expected to succeed if they internalize rejection without accepting the stated reasons as absolute truth, focusing instead on executing real work and gaining user insights.