I think a common practise is to charge per hour for smaller less expensive projects and per service on larger project. I'm based in the UK so as an example when I first started freelancing I would breakdown projects into how many hours each part of the project would take and then what I was charging per hour. But when you start working on larger projects It's probably better to work purely on a per project basis, perhaps with a tier system , (if you want A it will cost X, if you want B it will cost Y and so on).
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 think a common practise is to charge per hour for smaller less expensive projects and per service on larger project. I'm based in the UK so as an example when I first started freelancing I would breakdown projects into how many hours each part of the project would take and then what I was charging per hour. But when you start working on larger projects It's probably better to work purely on a per project basis, perhaps with a tier system , (if you want A it will cost X, if you want B it will cost Y and so on).