Excellent article over at Fast Company that’s a really good read. http://www.fastcodesign.com/3024819/how-not-to-get-screwed-by-clients?partner=newsletter I’ll wait for you to come back.
Get it in Writing
Never do any work unless you have it in writing. If you do happen to be talking via phone or video send an email afterward what you think you heard. It’s up to the client to tell you differently then.
Don’t do any work without a contract. You can find some simple contracts over a http://www.docracy.com.
No Spec Work
We get this line a lot, “There’s additional work in the future. What kind of a price break can we get on this small starter project?” Really? You want the discount, now, before we’ve established that we can work together? Um…no. Discounts are for when you trust each other and it’s a really big project (as in you don’t have to find additional work).
Upfront payments & never send final work before final money
If you ever have a client tell you that they’ll pay you afterwards just walk away. Seriously.
I turned down a project a few years back for a lot of reasons but one of them was that my gut was telling me the client seemed ‘slimy’. For one, he insisted that in his 30 years of working with developers no one had EVER asked him for money upfront. We said no and he went on his way. He shopped his project around to a number of other consultants who also turned him down (for similar reasons).
Finally he found a Xojo developer that was just doing consulting for fun (really!) and who didn’t ask for any money up front. What could go wrong, right? He agreed to the project (no contract, by the way, but that’s another story) and delivered the project. Guess what, the client stiffed him.
This developer did the work with no down payment and gave the client the final product before payment. If he had at least gotten a down payment he would have been compensated a little. Instead he got nothing. Make sure you have your bases covered. And of course with no contract in place the developer has no recourse.
Look for red flags. Run for the hills
Don’t be afraid to run away from a prospective client. Trust your instincts. The linked to article has some good ones (including the This will lead to paid work line). Some of our red flags:
• No specifications. It’s common for a client to not have the fine details but when they have zero idea what they want then it’s time to move on (or charge them to write the specifications).
• Worse yet, worthless specifications. I once had a client give me an 80 page specification document that made zero sense. We had four people review it and all of us came out scratching our heads. Funny enough, after meeting with him it was written exactly the way he talked. Sadly, I should have walked away from that project even though the alarm bells were ringing.
• They fight you over every penny. I’m not saying that the client shouldn’t be prudent with their money, but if they are professionals looking for professional help they should realize that your time, effort, and experience is not cheap.
• You’re the third or fourth developer they’ve either approached or worked with. There’s a reason why they keep not finding or losing developers.
There are more red flags but those are a start. What are some of your red flags with clients?