Ask HN: Solo founders, what’s your got-hit-by-a-bus strategy?
If you’re the sole person in charge of codebase, hosting, support, etc. - what sort of measures do you have in place to support your users/customers in the event that your life is unexpectedly taken?
Apologies for the morbid question. I suspect this is a real concern that is shared by many solo founders.
51 comments
[ 5.3 ms ] story [ 102 ms ] threadI don't think you would be in any relevant position at all to care about a startup which is run by you in case you die.
Your family can't run it, others can't just take it over and you are 6 feet under.
Get life insurance and stop worrying about this if you haven't brought the company far enough yet.
I had no idea that they origin had to be rediscovered after nearly 100 years.
[1] https://www.straightdope.com/21343427/what-does-the-filler-t...
Probably not.
I legitimately look _thrice_ before crossing: expected traffic side, other side and back once again.
I am paranoid about getting hit by a bus/car/...
I'll likely be done for by a falling piano.
I guess the customers that ask for support would just churn, but the stable set of customers that know what they're doing would keep enough cash in the accounts to keep the lights on until AWS permanently shuts down.
Amazon allows ACH / direct debit payment methods with more longevity than a credit card.
There will always be competitors. Some may spawn or be inspired later. Someone eventually does the same thing but better.
It's probably overengineering to try to keep a company alive longer than me. The primary responsibility is keeping my kids alive should I die within the next two decades, so I'd rather focus on that first.
There's also a lot of stuff that isn't clearly handled by inheritance laws - crypto, steam games, income from say, Google Play, passwords, so you have to set that up as well.
Also because software made me paranoid about failsafes, I took a separate life insurance in case the people in charge of my will screws over the kids, so they'll get a lump sump once I die.
:) There is an interesting advice on this topic in a book "Make a million before lunch". It states that your job as a founder should be to make yourself redundant as soon as possible. It helps a lot strategically in the long-run.
I’m on (what sounds like) a similar path to yours - in that the SaaS is growing nicely (and will one day afford a team and hopefully scale sustainably) but currently there is significant key-man risk.
My main concern is for my customers, so your open source idea sounds very practical.
How did you set this up? Do you have a private GitHub repo for example? With a Will / procedure to open it to customers?
Just trying to understand the practical execution of this idea.
These friends are also coders tho. They don't have interests (neither do I at the moment) into became part of the business. I told them openly in case I died, they could open-source the project or take over the project. Passwords I keep with my wife / direct relatives so they can contact them to just take control of the project.
However, open-sourcing would probably be enough for some of my customers to run the system by themselves. With the code and getting the access by contacting my relatives, these friends can potentially take the project and continue supporting my current customers.
> There are, roughly, three very different rationales to have business succession planning in place, and at the scale of a solo operator they have very different best options available:
> 1) I want to avoid negatively impacting paying clients in the event of a bus factor issue.
> 2) I want to avoid negatively impacting "the community" in the event of a bus factor issue.
> 3) I want to ensure my heirs receive the residual value of the income stream.
It's too long to repeat it here, but the the the rest of the comment by patio11 with his answers to 1, 2 and 3 are in https://news.ycombinator.com/item?id=21908638
It doesn’t need the internet to work, by design, and is standards based. (Mobile App is optional)
The reason for a solo founder to at least think about these things is, sure, if you’re dead, you’re dead. But if you have any family they will inherit the mess left behind when you die. Even if your intent is the business should die with you there’s paperwork and pissed off clients/customers. If you run a sloppy LLC or C corp (minimal paperwork to keep up the corporate veil) your family will absolutely love to learn that you’ve dumped this pile of crap on them after your death.