2 ms·
You should start with convincing people that it is a non-negligible risk and then sell an apt mitigation. Nobody expects to die suddenly, and with a technical c
by lucb1e 8y ago
You should start with convincing people that it is a non-negligible risk and then sell an apt mitigation. Nobody expects to die suddenly, and with a technical co-founder you don't expect them to leave the company to die, either. Depending on the actual risk (which I'm guessing is low), it seems much more efficient to have an insurance that will pay for costs incurred due to their untimely death/departure: pay for a replacement dev (for a reasonable amount of time so they can get to know the product), perhaps hiring costs, perhaps missed income for the company... Like with contents' insurance, I expect there would be a configurable amount that is paid out for all of these things, where lower amounts mean a lower premium.
Having a developer continuously kept up to date might only be affordable for larger companies, which might as well have someone doing that internally. I also don't think a single person can memorize enough about multiple startups to be worth it: either they hear about each customer's tech stack at least once every month (that already seems quite little, but is already relatively expensive so far as insurance-type services go), or they won't be worth more than written documentation.