Earlier quoted context omitted.
> Lie like hell --- and try to turn small into a positive. Don't do that. Unless you don't care about your reputation. > But truthfully, you really do need at least 2 people as a bare minimum to sell a viable product. When did this become an immutable law? > Lots of customers will want some assurance that if you die in a car crash on the way home, there is someone left to continue on with. One can also figure out a b…
Place code in escrow Doesn't help most customers because they lack the expertise to use it. Most people looking to buy software are not in the software development business and don't want to be. subcontract some of the work What about the rest of the work? avoid writing software that only runs when a specific person is constantly tending to it. If it is a hosted solution, someone needs to tend to paying the bill. If…
The point of that analogy is to get people thinking about business continuity (https://en.wikipedia.org/wiki/Business_continuity_planning) and how to mitigate various types of risks. The keyword being mitigate. One cannot eliminate risk, and no sane customer expects their use of a client or software to carry 0 risk.
If a vendor tells a client that nothing can disrupt their ability to deliver their product, they are either lying, or have failed to understand the risks their company actually faces.
And the final point, "my partner can take of it". That addresses only one, frankly minor aspect of business continuity, which is "what happens if someone important becomes incapacitated". The number products that failed because someone important literally died (not just left the company) is probably extremely minute. There are way bigger risks a company should focus on mitigating first, including:
- software fails to meet regulatory compliance (if applicable)
- company fails to manage finances properly and has to close shop
- someone important leaving the company
Can some of these be mitigated by adding another partner? Depends on what they bring to the table.