Quote:
Originally Posted by woopwoop  The bit in bold is the bit that I find the most difficult to get a grasp on.
I think that there would need to be specific points in a contract regarding what is expected, and how it can be measured. |
You're right, it is the hard bit. You aren't just hiring someone to do a specific job, you are looking to develop an on-going partnership. This means that you need to set up a framework that is not only going to be fair to both sides, but is going to keep the developer enthused about the project so they are going to make ongoing improvements to the site(s).
There's a big difference between the quality of work done by someone who is going through the motions, doing just enough to satisfy the contract & someone doing their best because they still believe in the project.
Have you ever seen the TV show
Dragon`s Den? When they choose to invest, the investors there obviously want to do the best deal for themselves, but they are also careful to leave enough of the company to the inventors to ensure that both sides keep their enthusiasm for the project. They are also very interested in what the exit strategy is. What happens if the business is sold? What happens if either side wants to pull out of the project?
You and the developer need to consider these points as well. What if the website is sold? How do you decide when enough effort has gone in and it's a failed project you should both walk away from? What if one partner wants to pull out & the other wants to continue?