[nocommandline]

Yes, but it depends on the software.

From a builder's POV, I also thought about this whenever I had ideas. Thoughts like - if I build this alone, will my customers be stuck or drastically affected if something happens to me? What will be the impact to my customers if I'm unreachable for a day or more (sick, traveling, etc).

For me, if it's a utility tool or software where my data is on my system, then I'm more likely going to be okay if it was built by a solo developer (this is how I green-lit my current project - https://nocommandline.com).

But if it's something where my data is on the cloud and/or the software is a key part of my workflow, then I would do some further analysis if I know it's a solo developer e.g. can I easily backup/extract my data, are there alternatives that I can easily move to, do I need to be able to reach support within a very short window (e.g. 6 hours). To be clear, this automatically doesn't mean I won't buy the software but the analysis will help me reach the decision. I have previously launched an idea that fell into this category but I provided the ability for users to export their data in JSON format from day 1 and I knew there were alternatives that users could move to with very little down-time