Let’s set the scene …
You’re a freelance web writer. When you were first starting out, you were eager for experience … and for paychecks. So you were willing to take on just about any project that came your way. You didn’t negotiate much for fees. You weren’t working for peanuts exactly, but you had room to grow.
And that’s just what you did. You grew. Your skills got sharper. Your clients got bigger. And your fees went up.
You built a name for yourself in your industry, and now you have more work than you can take on. The problem is, you’re still saying Yes to everything that’s coming your way.
It’s a good problem to have. But it is a problem. One that you need to deal with.
Every successful freelancer eventually reaches the point where they have to say No. The question is, when should you say No? And how do you do it without upsetting your client? After all, the relationships and the reputation you’ve built are important to you. You wouldn’t want to damage either.
The first step is to figure out when you’ll say No. If you define ahead of time your criteria for taking on a new project, it’s easier to turn work down that doesn’t fit your pre-defined needs.
Three Times When You Absolutely Should Say No
You may come up with more than a dozen reasons why you wouldn’t want to take on a project, but these three biggies should definitely make your list.
-
You Can’t Meet the Deadline
If a client comes to you with a project that they need in two weeks and you simply don’t have the time in your schedule to do your best work and deliver it within that time frame — or if