I’m going to start by saying this:
Contracts are there to protect BOTH parties
in web development, not just the contractor
If you are a client getting web work done, don’t enter into the job without a contract. It’s there to protect you too by outlining the work that will be done and the amount of hours it will take, which both parties can agree upon. You don’t go commando to work everyday (do you?) so why would you go contract commando on a job? Don’t be intimidated by contracts. Make sure one exists and use it. If you’re a web development client, we’re going to look at what you should look for when presented with a contract.
If you’re a developer on the other hand, read on as well to get some tips on implementing a good contract.
I’m going to try to keep this short and sweet so you’ll read it because, let’s face it, contracts are not the most interesting and inspiring of topics.
So what makes a good contract?