Live data from Hacker News

Developer open-sources 200+ hr project after client refuses to pay

github.com

51–60 of 136 posts

Re: Developer open-sources 200+ hr project after client refuses to pay

#51

For 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

Awesome video. Not safe for work, but if you're freelancing, I'd HIGHLY recommend watching it.

When this video was first released I forwarded it to my attorney, who laughed and laughed, and then said "everything they said in that video is true".

Re: Developer open-sources 200+ hr project after client refuses to pay

#53
He could have been a bit more vindictive, perhaps a non-osi compliant license like:

"This code is licensed under MIT license with one exception: for 5 years, this license excludes any use which benefits directly or indirectly the current owners of UnPayingCompany, Inc. On Aug 1st, 2017, the license for this code is MIT without any restriction."

Re: Developer open-sources 200+ hr project after client refuses to pay

#54
post #45

Earlier quoted context omitted.

Do you run into any pushback from potential clients when you tell them this?

I imagine he does, but those are probably also the type of clients you don't want to be accepting anyways.

Exactly. This is the same reason car dealerships or mortgage lenders ask for a down payment. You want both parties to have "skin in the game" so neither wants to walk away from the deal. If you can't come up with $500 upfront as a show of good faith, I don't want you as a client. That is non-negotiable. In my experience, this is more of a problem the lower the project price is. On $5000+ projects, you're dealing with a type of client who is used to paying deposits upfront (just like when you buy a car, a house, or hire a contractor to remodel your bathroom). On the $500-$1500 projects you get more amateurs.

Re: Developer open-sources 200+ hr project after client refuses to pay

#55

He could have been a bit more vindictive, perhaps a non-osi compliant license like: "This code is licensed under MIT license with one exception: for 5 years, this license excludes any use which benefits directly or indirectly the current owners of UnPayingCompany, Inc. On Aug 1st, 2017, the license for this code is MIT without any restriction."

Tempting and amusing, perhaps, but it wouldn't exactly put him in a flattering light as a contractor. It might even scare off potential future clients.

I think he's doing the right thing by releasing it as OSS. Hopefully he'll pick up some support hours if anyone actually ends up using it.

Re: Developer open-sources 200+ hr project after client refuses to pay

#56
post #2

After 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 f…

Where is a good place to learn the ins and outs of contracts? Is there a comprehensive website or book that you can recommend? I am early in my career and have been on both sides of writing contracts. While I am figuring a lot of things out as I go it would be nice to sit down and wrap my head around this for good. Also, to the OP, is a few weeks really enough time? If those were 200 billable hours it seems like it's…

http://www.gyford.com/phil/writing/2006/10/26/a_beginners_gu...

Re: Developer open-sources 200+ hr project after client refuses to pay

#57
post #2

After 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 f…

Where is a good place to learn the ins and outs of contracts? Is there a comprehensive website or book that you can recommend? I am early in my career and have been on both sides of writing contracts. While I am figuring a lot of things out as I go it would be nice to sit down and wrap my head around this for good. Also, to the OP, is a few weeks really enough time? If those were 200 billable hours it seems like it's…

Honestly, it doesn't need to be complicated. If you just require 25-50% down on your contracts that will weed out the scammers from the legit customers, and will make sure you get partially compensated should they ever leave you in the lurch. Make sure you document all communication, try to keep it over email so it's easy to do that, and you'll be fine should you ever need to take something to small claims court (which will probably never happen).

Re: Developer open-sources 200+ hr project after client refuses to pay

#58
post #13

The client wouldn't pay, so he gives it to them for free anyway?

He's trying to make the best of a bad situation- he put in a lot of time for which he was not compensated, but perhaps he can get some good PR out of it. Maybe down the road someone else will use his software and throw him some billable hours for customization.

Re: Developer open-sources 200+ hr project after client refuses to pay

#59

For 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

This is one of the best videos I've seen about this kind of things!

Re: Developer open-sources 200+ hr project after client refuses to pay

#60

He could have been a bit more vindictive, perhaps a non-osi compliant license like: "This code is licensed under MIT license with one exception: for 5 years, this license excludes any use which benefits directly or indirectly the current owners of UnPayingCompany, Inc. On Aug 1st, 2017, the license for this code is MIT without any restriction."

Tempting and amusing, perhaps, but it wouldn't exactly put him in a flattering light as a contractor. It might even scare off potential future clients. I think he's doing the right thing by releasing it as OSS. Hopefully he'll pick up some support hours if anyone actually ends up using it.

Why would excluding his deadbeat client from using the code put him in an unflattering light?
Post reply on HN