I would be VERY careful about charging a flat rate for a project. I know many people do this, but I it can be incredibly dangerous. Money is often paid upon "completion" of the project, or at least a majority of the payment. The definition of "complete" can change drastically. Especially if you have clients who are new to web development and do not appreciate the amount of planning required to budget correctly. In short, the client can change the definition of complete, getting more and more hours of work, essentially for free. Charge hourly!
I think that the best solution to manage customer requests (and avoid continuous modifications for free) is to prepare good and detailed specifications.
in this case the monthly payments can work fine.
when an extra request comes, you evaluate it hourly and charge the customer outside the original contract.
do you think it could work fine?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would be VERY careful about charging a flat rate for a project. I know many people do this, but I it can be incredibly dangerous. Money is often paid upon "completion" of the project, or at least a majority of the payment. The definition of "complete" can change drastically. Especially if you have clients who are new to web development and do not appreciate the amount of planning required to budget correctly. In short, the client can change the definition of complete, getting more and more hours of work, essentially for free. Charge hourly!
this is a really good point!
I think that the best solution to manage customer requests (and avoid continuous modifications for free) is to prepare good and detailed specifications.
in this case the monthly payments can work fine.
when an extra request comes, you evaluate it hourly and charge the customer outside the original contract.
do you think it could work fine?