1. Get used to the idea that your development and production environments are two distinct animals to be kept apart on purpose. Using one machine to develop and to host the production service is a recipe for disaster.
2. Stop using the cloud as a magical entity that holds everything that is online. You can go to many web hosts and pick up a decent IIS and SQL Server hosting plan for just a few bucks per month. If you build your solution so it can allow multiple server instances, you can always move it to the Azure Service or Amazon's cloud service.
3. "Hoped to attract" is not going to cut it. You need to have market research and a lot more before you can even talk numbers, otherwise you are down to a "cool idea that I hope catches on."
4. Offload your non-programming duties on somebody else. After many years programming, I have found that I was consistently miserable when my job description included responsibility for the infrastructure. It doesn't mean you stop learning about the infrastructure, it is just that you just concentrate on what you are building and somebody else is stuck keeping the servers alive.