Developer open-sources 200+ hr project after client refuses to pay
1–10 of 136 posts
Re: Developer open-sources 200+ hr project after client refuses to pay
#2After spending 200+ hours developing the system, not a dime has been seen or given
Freelancers should always try to get at least a deposit upfront. When I was freelancing, I would get 100% upfront for projects under $500, 50% upfront for projects between $500 and $2000. For projects over $2000, I would get 25% upfront, and then set milestones with payments attached. I had a $7500 project once where the guy made the first 25% payment, I completed the first milestone (graphic comps and UX flowcharts) then he disappeared for a year, not returning phone calls or emails. He then contacted me out of the blue and made the second payment, and I completed the second milestone (HTML/CSS/JS coding), and then he disappeared permanently. Clients like these are exactly the reason you need to get some payment upfront.
Re: Developer open-sources 200+ hr project after client refuses to pay
#3Developers blog: http://fredwu.me/post/8254974029/its-year-2011-why-arent-peo...
Re: Developer open-sources 200+ hr project after client refuses to pay
#4I suggest incremental payments and a deposit for any work of any size (which this definitely counts of). We do 20% upfront, 50% on adhoc reasonably functional demo, and 30% before uploading to apple/releasing code.
My company's iPhone fixed fee contracts state that you surrender all rights to the work after a (long) term of non-payment and still owe the amount due so things just like this can be done when people just disappear off the face of the earth but yet salaries and contractors and artists still need to be paid for all that time.
Re: Developer open-sources 200+ hr project after client refuses to pay
#5You could always copyright and register the code with the uspto for $35 as a collection.
I believe statutory damages are $150,000 per infringement.
Re: Developer open-sources 200+ hr project after client refuses to pay
#6Publicizing your work may be a fun way to 'get back' at an nonpaying client, but is it good for business? Would the professional thing to do be to simply drop work on this client and move on, or is any publicity good publicity for the coder?
This is damaging to the client. Yes, they may have deserved it, but will future clients be discouraged by this behavior?
Edit: To be clear, I'm not saying the coder was in the wrong in any way. That is to be determined based on whatever agreement existed between the coder and client. I'm asking if as a business decision it was wise to release the work. The client now has all of the work, and there is no possibility of reconciliation.
Re: Developer open-sources 200+ hr project after client refuses to pay
#7Publicizing your work may be a fun way to 'get back' at an nonpaying client, but is it good for business? Would the professional thing to do be to simply drop work on this client and move on, or is any publicity good publicity for the coder? This is damaging to the client. Yes, they may have deserved it, but will future clients be discouraged by this behavior? Edit : To be clear, I'm not saying the coder was in the w…
I'm very doubtful future clients would be discouraged from working with the developer. Future employers might look sideways upon such behavior though.
Re: Developer open-sources 200+ hr project after client refuses to pay
#8Publicizing your work may be a fun way to 'get back' at an nonpaying client, but is it good for business? Would the professional thing to do be to simply drop work on this client and move on, or is any publicity good publicity for the coder? This is damaging to the client. Yes, they may have deserved it, but will future clients be discouraged by this behavior? Edit : To be clear, I'm not saying the coder was in the w…
On the other hand, it will discourage clients who might not have the ability to pay. The clients who can pay shouldn't have any reason to be worried.
Re: Developer open-sources 200+ hr project after client refuses to pay
#9Publicizing your work may be a fun way to 'get back' at an nonpaying client, but is it good for business? Would the professional thing to do be to simply drop work on this client and move on, or is any publicity good publicity for the coder? This is damaging to the client. Yes, they may have deserved it, but will future clients be discouraged by this behavior? Edit : To be clear, I'm not saying the coder was in the w…
Future clients who have no intention of paying will probably be discouraged by this behavior.
Re: Developer open-sources 200+ hr project after client refuses to pay
#10For those who would like to avoid this situation, Mike Monteiro (@Mike_FTW) has humorously useful advice for contractors:
F*ck You. Pay Me. http://vimeo.com/22053820