Okay, my post was quick because I forgot to mention a very important trait for a web developer. You have to learn when to say NO! It takes time to recognize t

Okay, my post was quick because I forgot to mention a very important trait for a web developer. You have to learn when to say NO! It takes time to recognize the warning signs though. Once you do, then part of your process from initial contact to getting the client signed on should be to unveil those flags. Again, it's not the fault of the client, ultimately the responsibility lies with the web developer not to get into these situations. In other words, if your business tanks, you can only blame yourself. You still don't need to burn any bridges though. And turning down future work isn't burning bridges.