4 ms·

yeah per project. Sorry if my question was misleading.

• tudorizer 15y ago
  The you should try per hour. Example: Project X has an estimate of 200 hours, but if at the end of the project 230 hours are used, you bill 230. This is usually the best way to protect yourself from late changes, feature creeps and undecided clients. This approach also puts more responsibility on the decisions made by the client. If your friend already has some proven track record, clients should trust him as a professional. The downside to hourly payed is that some clients don't like it and it's understandable. A failed project is not only the responsibility of the coding team. Here's a neat article about this: http://www.webdesignerdepot.com/2010/10/charging-per-hour-vs-per-project/ http://www.webdesignerdepot.com/2010/10/charging-per-hour-vs...