Good fences make good neighbors just as good contracts make for good developer/client relations. At the very least your agreement with your developer should contain a complete description – in non-vague terms – of each feature to be built as well as a paragraph description of the overall project. Remember if it is not described in this document, your developer will not build it. Read it over carefully; don’t assume they mean “shopping cart with UPS, FedEx and DHL shipping options” if it just says “shopping cart”. The contract should describe exactly what is to be built, how much you are willing to pay and a payment schedule tied to features or milestones. If negotiating the contract with your developer is a hassle, consider it your last opportunity to walk away and find another developer.
When you are ready, move on to part 7 of 8 and read “How to Plan a Website – Do your part.“
Want more helpful advice?
Are you looking for more helpful advice? Check out our book, Avoiding a Goat Rodeo. It was written to help non-programmers understand website development. It shows you how to get the website you want.