Some freelancers say yes to every project that comes their way. Different people have different reasons, but it often comes down to:
- Not wanting to turn down money.
- Not liking the feeling of turning people away.
But I don’t say yes to every project, and here’s why:
The passion isn’t always there.
Not every project excites me. That’s not something I can help, so I’m not ashamed to admit it.
If the idea of a project incites dread, then there are two good reasons not to take it:
- I’m doing myself a disservice by setting myself up for stress and unhappiness.
- I’m doing the client a disservice by robbing them of the chance to find someone who is passionate about their project.
Surely the client would rather wait and find someone who is THRILLED at the idea of working with them? I owe it to them to let them have that chance.
Am I really the best person to be doing this?
There may come a time when you’re asked to do something you don’t even know how to do. Or even if you do know, you’re not an expert in that field and someone else would be much better suited to work on it than you.
Again, this is where I usually put the client first. If I don’t feel I’m the best person for the job, then I’ll recommend someone else instead.
For example: sometimes I get people asking me to help customize their Genesis child theme. Could I do it? Sure, I could figure it out. But I don’t particularly like Genesis, and as a result, I don’t know the platform inside and out. It would take me longer to backtrace all the actions and filters I need to use. The client would be much better off if I passed them off to someone who specializes in Genesis. The project would get done a lot faster and more efficiently.
You have the right to pick and choose projects you truly love and will deliver on.
Don’t feel bad about disappointing the would-be client. Sure, maybe saying no sucks a little. But ultimately you’re doing them a favour by giving them the opportunity to work with the best person possible for the job.