Hacker News Clone new | comments | show | ask | jobs | submit | github repologin
Ask HN: Contracting – dealing with ambiguous requirements and liability
4 points by hnacct2001 2 hours ago | hide | past | web | 1 comment | favorite





Reject all liability. Software is almost always sold as-is. You should stand by your work, fix defects, offer help, offer advice, be a decent human, etc. But that should be done as more hourly work. If they are unhappy with how it goes, they might never hire you again, but that does not put it on you to be liable for their operations.

So you are already in a good place - hourly rates, define and communicate the specs to the other devs, and reject liability. If the client says no to that, walk away.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: