On one hand, bad clients are a dime a dozen. But on the other side of the coin, being a freelancer means that you set your standards.
There are a million and one great things about freelancing like getting to choose the subject matter you work on, having greater geographic mobility, and my personal favorite: grocery shopping at 2pm on a Tuesday when the store is practically empty. You can take on a huge, challenging project that’s got you heads-down for months, and then follow it up with something more lightweight that allows you to reset. And you get to decide if the person who wants your skills actually gets to become a client.
When freelancing, it’s a challenge not to accept every job that comes down the pipeline, since you never know when your next opportunity is going to pop up, and the money needs to keep coming in. Sometimes, the decision is made easier when there are things you can do, but aren’t that great at, or when you don’t agree with what the company requesting your bid does to make its money. Then there are other times where things start out fine and quickly degrade.
If you’re wondering if it’s time to move on, here are some great ways to recognize when you have a bad freelance client who needs to get the boot for good.
If you’re serious about your freelancing business, you should have plenty of examples of the kind of work you are capable of producing. Whether that is in the form of a portfolio, your GitHub repo, or references to current sites, a prospective client should already have a good idea of the quality of your work. Asking for a sample and not offering compensation is not only taking advantage of you and your time, it’s extremely lame.
If they start out by asking for free work, you can bet that they will continue to ask for free work along the way.
Along the same lines, if you don’t have a contract in hand and signed, you are essentially doing free work. Unfortunately, some people suck and will do everything they can to avoid paying you. Don’t let yourself get caught in the trap of a bad client before you even begin. Get. A. Contract. If you’re new to the game and aren’t sure what to include, or have been having issues and could use some guidance, check out the Contract Creator over at Freelancers Union; it’s a great resource.
Asking to clarify what they receive in return for what you are charging is absolutely a client’s prerogative. Once. If they keep questioning your rates, chances are fairly high that they will question the value of your work along the way. If they have the gumption to tell you how much they think you are worth by offering a lower number, they’re showing you that they think they know more about what you do than you, yourself.
Clients who will start out lowballing and undercutting you are not going to be worth it, full stop.
Even if this comes after a contract has been signed, make sure to leave yourself an out in that all-so-important contract.
Not a single one among us is unfamiliar with scope creep, but when you’re freelancing, you don’t have a project manager level-setting the expectations with the higher-ups; you have to do it alone.
Making change requests to a project isn’t out of the ordinary, but there may come a time when the requests have become so numerous or so grand that you’re not just out of time and over budget–you’re cutting into other work that good clients have paid good money for. Know when to say no if it becomes too much! Reworking button order for a better UI is one thing. Rewriting API hooks to accommodate a new payment schema is entirely different.
People get busy, right? Totally understandable. But when you have a client that never seems to be available, it’s a huge red flag. You know the type: they respond to the blockers seven hours after you asked about them; the expectations they set are unclear, and they’re not in a position to clear them up; it takes a week to execute a full conversation by email. It’s frustrating, it’s not productive, and it’s not a good situation for anyone on either side.
If a client can’t be bothered to provide guidance and clarity on a project they’ve recruited you for, how far are you going to get on that project?
Is it something you’re going to be proud of, knowing you had so little direction to go on? Probably not. It’s best to part ways before too many feelings get hurt, and well before the client realizes their “vision” won’t come to life without their input.
At the other end of the spectrum, we have the helicopter clients: the ones who expect you to be available 24/7; who find a way to micromanage you from afar; who nitpick every decision you make, as if you don’t know what you’re doing. To me, this is almost worse than not being involved enough.
You were hired for the job because you possess a set of skills the client needs and does not have. With the way the job market is now, they probably had a lot of options for freelancers and decided that, out of all of them, YOU were the most expert and most excellent! So they really shouldn’t be hovering. They should know you know what you’re doing. And yet…here they are, asking why the button color looks closer to #02FAE9 when it should be #07F0E0–and you’re in charge of building the databases.
It’s totally okay to walk away from a bad vibe. There could be any number of reasons that fit this category, and all of them are valid. They could be the most petty reasons in the world, and you know what? Still okay. Gut instincts are right all the time, and do you really want to get into a situation you totally saw coming and do nothing to stop it?
One of the greatest things about freelancing is the freedom it gives you, which is also the freedom to decide you don’t want to work for or with someone. If there’s one takeaway here, it’s this: not every dollar is worth it.
Know what you’re worth, in terms of both money and respect, and don’t sell yourself short. There are always going to be gambles with freelancing, and now you know how to approach a few of those.