|
|
|
|
|
|
by enobrev
4590 days ago
|
|
|
I agree with this, completely. During the first 5 or 6 years of my 10 years of freelance, I almost never had a contract in place, and I _never_ got fucked over for it. That's not to say it's OK to avoid contracts. Only a single set of data points that says it's possible to do business without them and still do very well. Of course larger clients will generally require them to cover their own asses. And any project that's over x, where x seems like a good deal of money, should _always_ be covered by a contract - both for your safety and the safety of your client. But the cynical idea that everyone is out to get you is silly. Yes, get a lawyer to get a solid standard contract together for you. But then pay attention to the clients you're dealing with. A contract gives you a legal standing in court, but you still have to go to court. There's a lot more to be said for choosing clients that aren't going to cause trouble in the first place. |
|
|
If you give a tech consultant a job they will code from A to B. The client is always the one throwing up roadblocks and change requets. If they don't understand that they are on the hook for those billing hours, yeah you don't have a good client there...
ONLY USE HOURLY RATE + ESTIMATE that's the best advice I can give on top of enobrev's. Maybe others disagree, but in my experience project rates mean the client will try to take advantage or if you get a project price that seems absurdly high & you get that flash of $$ signs in your eyes, the client will usually realize they overpaid and you'll lose potential future business with them. Just use a rate and be somewhat ethical about it. Even if you don't have a huge client base, they will all come back around for more work every few months.