That mirrors my experience. It's easy to release a project when there are no users. You just barf code out and deploy it. Once people start using it, or paying

That mirrors my experience. It's easy to release a project when there are no users. You just barf code out and deploy it. Once people start using it, or paying for it, you just have to be more careful. A feature that you could whip out in an hour with an 90% chance of working bug-free now takes a day, because you need it to be 99%. It becomes easy to put things off "until you have time to do it right" - even small and easy things. The way to combat this is to work on your environment. Build a solid staging environment. Automate some integration tests (http://fakeapp.com http://fakeapp.com is awesome for this) for the must-have functionality. Work on your admin dashboard so you know the instant something goes wrong. In other words, build the tools that make your next deployment as worry free as is practical. For me, the friction and misery of the QA cycle slows down my releases until I get all this stuff right. It's a head game. I know when to stop writing tests when I'd rather be working on the app.