1. You are forgoing current wages for potential future profit. I might be willing to bootstrap a project where the first year's expectation of profit is low, bu

1. You are forgoing current wages for potential future profit. I might be willing to bootstrap a project where the first year's expectation of profit is low, but I wouldn't develop the same project for 15,000 dollars (as an example.) Are you suggesting you'd be willing to work for 30,000 dollars for 6 months? (That's for a team of 3) Oh, and that's including specs and technical documentation and test plans that many customers expect to see before deployment. 2. You are developing for someone else's design, which often changes midstream, and it has irrational requirements due to data flows from previous products. I worked with a product that had to support the public health information network logical data model (PHIN-LDM), an absolute monstrosity of a database. If we were building the system privately, we could have shaved the effort in half, if not more. Importing previous client data can be monstrous, due to poor system checking and user hacks to make a system do what it was never meant to do. 3. Deployment is more expensive. Gathering clients is more expensive. Each means traveling over to the client to gather requirements and install, and to conduct training. Now, if you can do all this, there are a slew of contracts ready to happen. Get a team of three together, and subcontract out to integration teams and prime contractors. All you have to do is find a first and second project to gain momentum.