3 ms·
Even if you have such a clause, it would be very trivial like @beisner has stated, for client to prove reputation damage and loss of business (even if they were
by justboxing 9y ago
Even if you have such a clause, it would be very trivial like @beisner has stated, for client to prove reputation damage and loss of business (even if they weren't making money to begin with).
> it would be trivial for the client to show in court that the dev's actions led to quantifiable damages to their business, and might even be open to criminal prosecution.
Source: @beisner https://news.ycombinator.com/item?id=16326732 https://news.ycombinator.com/item?id=16326732
- Slansitartop 9y agoCouldn't you add another clause stating that the webdev is not responsible for any reputation damage, loss of business, or any other damages caused by the non-payment landing page?
- philipov 9y agoTry to get a client to agree to such a clause, especially when they've probably already decided the likelihood of not paying the developer at the time they are hiring them.
- Slansitartop 9y ago> Try to get a client to agree to such a clause, especially when they've probably already decided the likelihood of not paying the developer at the time they are hiring them. Seems to me like that's not a bad thing. If they're not planning on paying in full, you probably don't want to do any work for them. Better to find out sooner than later.
- sigstoat 9y ago> especially when they've probably already decided the likelihood of not paying the developer at the time they are hiring them if they're the sort of client who is planning at contract signing time to not pay, they're the kind of client you don't even want. who cares if they self-select out?