If you have a laundry list of features and grand plans to do more, I'd avoid you like the plague. Reliable software is time consuming, and piling on more and more features tends to break corner cases.
If your software is extremely simple, with a few well-defined use cases, and it's clear that you only spend 1/3rd of your time actually programming, I'd probably consider it. (And in this case, there's a good chance you'll hire contractors or employees when your company grows.)
In the former case, (laundry list of features,) I'd conclude that you're a programmer who doesn't want a boss, and quality will probably suffer. In the latter case, I'd conclude that you're a businessman who happens to be selling software.
If you have a laundry list of features and grand plans to do more, I'd avoid you like the plague. Reliable software is time consuming, and piling on more and more features tends to break corner cases.
If your software is extremely simple, with a few well-defined use cases, and it's clear that you only spend 1/3rd of your time actually programming, I'd probably consider it. (And in this case, there's a good chance you'll hire contractors or employees when your company grows.)
In the former case, (laundry list of features,) I'd conclude that you're a programmer who doesn't want a boss, and quality will probably suffer. In the latter case, I'd conclude that you're a businessman who happens to be selling software.