Live data from Hacker News

Ask HN: Crashed founders, what was the point of failure?

news.ycombinator.com

51–56 of 56 posts

Re: Ask HN: Crashed founders, what was the point of failure?

#51
Solo technical founder here.

I've helped build several other startups since 2012 but this was my first time solo founding. Mid last year I had a lot of runway and had been meaning to learn Flutter for a while. I decided to build project that had been floating around my mind for a few years.

My largest mistakes were:

* Choosing 3 different revenue streams instead of just 1, which meant I was building for 3 different customers. I'd interviewed a few dozen people early on and identified those 3 key pain points, but I should have just left two as an optional pivot. This also meant that I was juggling too much and context switching too often.

* Choosing a technology stack I'd had minimal experience with (mobile & Flutter for the frontend), so the MVP that could have taken a month to build took around 4 months. There are so many annoyances to deploying mobile apps that don't exist with web apps. Nobody but friends want to install your app just to try it out. Use technology that you're already familiar with so that you can move fast.

* Getting a shitty MVP version onto people's phones. Note: Good luck getting your shitty MVP onto Apple's App Store. Google's store had some decent functionality for running a closed-alpha. Overall web is a much better platform for testing ideas with minimal friction (imho).

* Spending too much time integrating Segment, Stripe, and all the other swag you can get as a startup these days. Each new integration has their own learning curve and every new one slows you down.

* Wasting time meeting with and talking to investors when I knew deep down that I wanted to bootstrap. I met some cool people but I should have been laser focused on iterating instead.

* COVID happened and my app depended on countries not being locked down, so as a precaution against burning through my runway I put the startup on hold and took on another contract to increase it instead.

I've had some ideas for a pivot since February along with a few other things in different spaces that reuse what I've got so far. I'll try out some experiments to try over the new year period, so I don't consider it failed yet, but it does feel like I'll almost be starting from scratch.

edit: I might as well talk about other startups I've worked with that eventually failed.

* A: After raising a seed, instead of using the money to fund development, it was used to bring on big-name executives in the hopes of raising a larger round. The next round was successful but nothing had been built, so milestones were missed and investors pulled out. The company lasted a little bit over 1 year.

* B: After a few months the founder brings on a CFO who thinks current devs are too expensive and wants to outsource to India. A handover occurs and it goes as you'd expect. The company lasted around 2 years.

* C: The CTO lacked the technical experience to realise they were over-promising and lacked the humility to receive constructive criticism, then went on a power trip which led to an exodus. Yes-men devs were hired from a different part of the country and completely isolated from the rest of the company, so that the CTO could have complete control over the flow of information, then those devs were unable to deliver what had been over-promised. Fast-forward a year or two and there's an external audit to find out what's taking so long, investors discover they'd been paying for unicorn farts, they pull out and publicly fire the CTO on their way out. The company lasted around 3 years.

Re: Ask HN: Crashed founders, what was the point of failure?

#52
Not a startup in the typical sense, but I created a side project maybe 10 years ago that had great traffic growth and was signing up users.

It was basically a content website so I was using Wordpress and MANY plugins without really understating how the worked together. Traffic kept growing and I was getting pretty excited.

My other (and current) business was growing more so I focused on that. After a few months I checked back in and the other site had actually broken in an update of Wordpress and been getting zero traffic for months and didn’t ever recover once fixed.

While I would like to say that the point of failure was the site breaking, the actual point of failure was me not being able to focus on it like I should have.

Related, but had I given it the focus it deserved, my other business might not have been as successful and my life would likely look incredibly different now.

Re: Ask HN: Crashed founders, what was the point of failure?

#53
I thought I was smarter than I was and I was trying to do a lot by myself. It didn't work and my ego made me not admit it wasn't working far longer than I wish I had spent on it.

It was all a very humbling experience.

In the future

1) recruiting at least 1 other person to work on anything like a startup with me. The bar for me is can I get at least 1 other person to work on this and do I have a plan to get to the first 5? If not I'm not doing it.

Worse case you build a great team and have a good time with them making something and hopefully get acqihired or better. If you're by yourself and it doesn't work out you're likely just getting another job...

2) Recognize what your strengths are and recruit to fill in the gaps. You only have 24 hours in a day 6 to 8 of which you are sleeping if you want to be effective for the rest at all... So even if you were a super hero at all the things you need to be to make a business successful (hint: you wont be) you will run out of time in the day if you can't get other people to help.

If you can't get ^ in your own project join other people's projects until you can.

Re: Ask HN: Crashed founders, what was the point of failure?

#54
post #10

> the need to compare crashed planes to the survivors As someone who is both a pilot and a "survivor" of three failed startups (and a coattail-rider at one successful one), this is the wrong analogy. The reason it's the wrong analogy is that most airplanes don't crash, but most startups do. This makes a big difference. The reason that it is possible to make reliable aircraft but not reliable startups is that the succ…

>Building a successful startup is much more akin to making a new scientific discovery than designing a good airplane.

Eureka!

Re: Ask HN: Crashed founders, what was the point of failure?

#55
post #23

The value of mentioning survivor bias and selection bias is to highlight that we listen to those who made it because they have wealth and influence and we want or are interested by that. There is no way to prove founders are more talented or wise than failed founders because it's impossible to disentangle luck and chance from their talent, though they would tell you luck favors the well prepared. One great source of…

> serial entrepreneurs That is who I'm looking for. If the odds of success are less than 10%, then it would seem to follow that the thoughts on success by single or several failure individuals would suffer from a similar bias as the survivors. Basically, who actually kept trying long enough to disprove the hypothesis that's it's all about experimenting until you find something that works really well, and then growing…

If you're lucky, perhaps you can roll the dice 10 times. With a 10% chance 10 failures wouldn't be too significant. Given a binomial distribution that's still p~=0.35.

Re: Ask HN: Crashed founders, what was the point of failure?

#56
One startup success, some profitable projects. Founded many which failed, invested in some failures, worked in several startups that failed.

1. Dishonest and manipulative cofounder. He pissed off every partner with aggressive negotiation, blatant lies, and bad deals. He was the type to agree to a deal, then back out and offer a worse one.

2. Founders were not committed. They invested a lot, sure, but didn't close deals. The key partner was rich but technically incompetent and didn't take the joint venture seriously. Project was simple but it dragged on for over a year, and neither party committed to get it done.

3. Good product. But founder oversold it. It didn't meet expectations, the blame was pushed to staff, eventually imploded.

4. Good product, good demand, but unit price economics didn't work.

5. Company was acquired for a profit. Acquiring company had no plans what to do with it. They cut off the primary target market immediately upon acquisition, lost a good chunk of sales. Nobody wanted to take responsibility for it and it died slowly after 3 years, and likely split the parent company as well.

6. Feature bloat. Hit crisis mode where everyone did everything and got nothing done. Pushing bad code to production, which broke. Had progress report meetings every 4 hours by the end of the project before everyone left.

7. Product was built. Sales co-founder lost nerve, despite a major airline showing interest, and abandoned it.

8. Company faked traction, e.g. buying products from the users and justifying it as marketing costs. Main investor lost nerve and pulled out. Founder could have saved it but was exhausted and pulled the plug.

9. Good product. Great team. Huge market. But one of the heads had very aggressively pushed the schedule, screwing over the entire product development plan. E.g. 6 months to release. Marketing wanted 2 months, QA wanted 2 months, leaving development with just 2 months. Dev ran on agile, QA ran on waterfall because they had to deal with visas and all. Crisis mode and meltdown.

10. Experienced, intelligent founders. Good business plan. But no budget and founder ran out of cash to keep it going. Would likely have gone well if founders had the money. Founder went on to do a startup about getting funding and it's still going.

tldr: A lot of this is just human problems. I think the point of failure for many startups is just stopping. Too many founders start a startup because it's to stroke their personal ego and once they have one, it gets neglected. Most people want some kind of passive income thing and won't commit to their startups.

Post reply on HN