aord.txt 8.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126
  1. October 2015When I talk to a startup that's been operating for more than 8 or
  2. 9 months, the first thing I want to know is almost always the same.
  3. Assuming their expenses remain constant and their revenue growth
  4. is what it has been over the last several months, do they make it to
  5. profitability on the money they have left? Or to put it more
  6. dramatically, by default do they live or die?The startling thing is how often the founders themselves don't know.
  7. Half the founders I talk to don't know whether they're default alive
  8. or default dead.If you're among that number, Trevor Blackwell has made a handy
  9. calculator you can use to find out.The reason I want to know first whether a startup is default alive
  10. or default dead is that the rest of the conversation depends on the
  11. answer. If the company is default alive, we can talk about ambitious
  12. new things they could do. If it's default dead, we probably need
  13. to talk about how to save it. We know the current trajectory ends
  14. badly. How can they get off that trajectory?Why do so few founders know whether they're default alive or default
  15. dead? Mainly, I think, because they're not used to asking that.
  16. It's not a question that makes sense to ask early on, any more than
  17. it makes sense to ask a 3 year old how he plans to support
  18. himself. But as the company grows older, the question switches from
  19. meaningless to critical. That kind of switch often takes people
  20. by surprise.I propose the following solution: instead of starting to ask too
  21. late whether you're default alive or default dead, start asking too
  22. early. It's hard to say precisely when the question switches
  23. polarity. But it's probably not that dangerous to start worrying
  24. too early that you're default dead, whereas it's very dangerous to
  25. start worrying too late.The reason is a phenomenon I wrote about earlier: the
  26. fatal pinch.
  27. The fatal pinch is default dead + slow growth + not enough
  28. time to fix it. And the way founders end up in it is by not realizing
  29. that's where they're headed.There is another reason founders don't ask themselves whether they're
  30. default alive or default dead: they assume it will be easy to raise
  31. more money. But that assumption is often false, and worse still, the
  32. more you depend on it, the falser it becomes.Maybe it will help to separate facts from hopes. Instead of thinking
  33. of the future with vague optimism, explicitly separate the components.
  34. Say "We're default dead, but we're counting on investors to save
  35. us." Maybe as you say that, it will set off the same alarms in your
  36. head that it does in mine. And if you set off the alarms sufficiently
  37. early, you may be able to avoid the fatal pinch.It would be safe to be default dead if you could count on investors
  38. saving you. As a rule their interest is a function of
  39. growth. If you have steep revenue growth, say over 5x a year, you
  40. can start to count on investors being interested even if you're not
  41. profitable.
  42. [1]
  43. But investors are so fickle that you can never
  44. do more than start to count on them. Sometimes something about your
  45. business will spook investors even if your growth is great. So no
  46. matter how good your growth is, you can never safely treat fundraising
  47. as more than a plan A. You should always have a plan B as well: you
  48. should know (as in write down) precisely what you'll need to do to
  49. survive if you can't raise more money, and precisely when you'll
  50. have to switch to plan B if plan A isn't working.In any case, growing fast versus operating cheaply is far from the
  51. sharp dichotomy many founders assume it to be. In practice there
  52. is surprisingly little connection between how much a startup spends
  53. and how fast it grows. When a startup grows fast, it's usually
  54. because the product hits a nerve, in the sense of hitting some big
  55. need straight on. When a startup spends a lot, it's usually because
  56. the product is expensive to develop or sell, or simply because
  57. they're wasteful.If you're paying attention, you'll be asking at this point not just
  58. how to avoid the fatal pinch, but how to avoid being default dead.
  59. That one is easy: don't hire too fast. Hiring too fast is by far
  60. the biggest killer of startups that raise money.
  61. [2]Founders tell themselves they need to hire in order to grow. But
  62. most err on the side of overestimating this need rather than
  63. underestimating it. Why? Partly because there's so much work to
  64. do. Naive founders think that if they can just hire enough
  65. people, it will all get done. Partly because successful startups have
  66. lots of employees, so it seems like that's what one does in order
  67. to be successful. In fact the large staffs of successful startups
  68. are probably more the effect of growth than the cause. And
  69. partly because when founders have slow growth they don't want to
  70. face what is usually the real reason: the product is not appealing
  71. enough.Plus founders who've just raised money are often encouraged to
  72. overhire by the VCs who funded them. Kill-or-cure strategies are
  73. optimal for VCs because they're protected by the portfolio effect.
  74. VCs want to blow you up, in one sense of the phrase or the other.
  75. But as a founder your incentives are different. You want above all
  76. to survive.
  77. [3]Here's a common way startups die. They make something moderately
  78. appealing and have decent initial growth. They raise their first
  79. round fairly easily, because the founders seem smart and the idea
  80. sounds plausible. But because the product is only moderately
  81. appealing, growth is ok but not great. The founders convince
  82. themselves that hiring a bunch of people is the way to boost growth.
  83. Their investors agree. But (because the product is only moderately
  84. appealing) the growth never comes. Now they're rapidly running out
  85. of runway. They hope further investment will save them. But because
  86. they have high expenses and slow growth, they're now unappealing
  87. to investors. They're unable to raise more, and the company dies.What the company should have done is address the fundamental problem:
  88. that the product is only moderately appealing. Hiring people is
  89. rarely the way to fix that. More often than not it makes it harder.
  90. At this early stage, the product needs to evolve more than to be
  91. "built out," and that's usually easier with fewer people.
  92. [4]Asking whether you're default alive or default dead may save you
  93. from this. Maybe the alarm bells it sets off will counteract the
  94. forces that push you to overhire. Instead you'll be compelled to
  95. seek growth in other ways. For example, by doing
  96. things that don't scale, or by redesigning the product in the
  97. way only founders can.
  98. And for many if not most startups, these paths to growth will be
  99. the ones that actually work.Airbnb waited 4 months after raising money at the end of Y Combinator
  100. before they hired their first employee. In the meantime the founders
  101. were terribly overworked. But they were overworked evolving Airbnb
  102. into the astonishingly successful organism it is now.Notes[1]
  103. Steep usage growth will also interest investors. Revenue
  104. will ultimately be a constant multiple of usage, so x% usage growth
  105. predicts x% revenue growth. But in practice investors discount
  106. merely predicted revenue, so if you're measuring usage you need a
  107. higher growth rate to impress investors.[2]
  108. Startups that don't raise money are saved from hiring too
  109. fast because they can't afford to. But that doesn't mean you should
  110. avoid raising money in order to avoid this problem, any more than
  111. that total abstinence is the only way to avoid becoming an alcoholic.[3]
  112. I would not be surprised if VCs' tendency to push founders
  113. to overhire is not even in their own interest. They don't know how
  114. many of the companies that get killed by overspending might have
  115. done well if they'd survived. My guess is a significant number.[4]
  116. After reading a draft, Sam Altman wrote:"I think you should make the hiring point more strongly. I think
  117. it's roughly correct to say that YC's most successful companies
  118. have never been the fastest to hire, and one of the marks of a great
  119. founder is being able to resist this urge."Paul Buchheit adds:"A related problem that I see a lot is premature scaling—founders
  120. take a small business that isn't really working (bad unit economics,
  121. typically) and then scale it up because they want impressive growth
  122. numbers. This is similar to over-hiring in that it makes the business
  123. much harder to fix once it's big, plus they are bleeding cash really
  124. fast."
  125. Thanks to Sam Altman, Paul Buchheit, Joe Gebbia, Jessica Livingston,
  126. and Geoff Ralston for reading drafts of this.