Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

41–50 of 136 posts

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

#41

Post by joshaidan »

joshaidan wrote: post #39
dkokelley wrote: post #6

Publicizing 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 doubt future clients would be discouraged by this kind of behaviour. The good clients, the kind you want, understand the value of work and the importance of being paid. They will no doubt be able to emphasize with this coder.

If anything, it shows future clients that this coder is hard working and can actually produce code and get projects done. That by itself insures your reputation.

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

#42

Post by joaquin_win »

thebigredjay wrote: post #15
byoung2 wrote: 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://mylawyergabe.com might help you answer some questions or at least learn a bit.

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

#43

Post by stel »

vaksel wrote: post #32
thebigredjay wrote: post #15

Earlier quoted context omitted.

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…

contracts usually aren't worth the paper they are written on. Because even if you win in court, it doesn't mean the guy will pay you...you'll still need to chase after the money.

Contracts are useful for spelling out the rights and responsibilities of each party so there are no misunderstandings later. But I agree with you, if the person you're contracting with doesn't want to pay you, you may well waste more than the contract is worth trying to get your money.

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

#44

Post by mattgreenrocks »

byoung2 wrote: 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…

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

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

#45

Post by getsat »

mattgreenrocks wrote: post #44
byoung2 wrote: 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…

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.

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

#46

Post by [deleted] »

nknight wrote: post #21
dkokelley wrote: post #6

Publicizing 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…

Wouldn't a lawsuit be more damaging? Would future clients be wary of someone who appears litigious?

[deleted]

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

#49

Post by FuzzyDunlop »

vaksel wrote: post #32
thebigredjay wrote: post #15

Earlier quoted context omitted.

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…

contracts usually aren't worth the paper they are written on. Because even if you win in court, it doesn't mean the guy will pay you...you'll still need to chase after the money.

They do at least offer you a leg to stand on when it comes to clients asking for constant new features without wanting to pay for them. You can refer to it to back up your refusal to do extra work and by the same token it sets a bare minimum standard for you to meet before the job is considered done.

I did some freelance without a contract once and because I didn't have an agreement in writing I didn't have much recourse to tell them there'd be a charge for additional services.

A contract will never be a quick and easy solution to stop people doing a runner but you can at least limit the damage caused with one.

Post reply on HN