I see. And you're absolutely right: per-project pricing is less risk for the client.
Yes, a few of my clients I really had to convince. I normally argue, that per hour is fair for both sides otherwise I would have to raise the per-project price because of possible additional expenses.
what kind of clients are more likely to accept it in your experience?
I don't know if there is a "kind of clients" that accept it more. In my experience, it depends on how you sell it. If someone reaches out to me for a project, I set the conditions: This is my hourly rate, this many hours will the project presumably take, so in this range will the total price most likely be. If they are not happy with that, I explain that I can do it for less hours, but leaving out this and that requirement.
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 see. And you're absolutely right: per-project pricing is less risk for the client.
Yes, a few of my clients I really had to convince. I normally argue, that per hour is fair for both sides otherwise I would have to raise the per-project price because of possible additional expenses.
I don't know if there is a "kind of clients" that accept it more. In my experience, it depends on how you sell it. If someone reaches out to me for a project, I set the conditions: This is my hourly rate, this many hours will the project presumably take, so in this range will the total price most likely be. If they are not happy with that, I explain that I can do it for less hours, but leaving out this and that requirement.