Client Red Flags: A Freelancer’s Survival Guide
Learn to spot problem clients before they become your problem. A decade of hard-won wisdom.
The Real Problem With Freelance Clients
I have been freelancing through 211j for 16 years now. I also work full-time as a senior front-end dev at StudioRx, which is an Omnicom agency. So when I say I have seen some things in client relationships, I mean I have seen them from both sides of the fence: as the freelancer trying to keep the lights on, and as the agency developer watching the sales team close deals I will have to actually deliver.
The freelance side taught me the hard lessons. And I paid for every single one of them.
I Am Terrible at Selling Myself
Let me get this out of the way: I am not good at branding. I am not good at marketing. I am not good at pitching. I am a developer who happens to run a business, not a businessperson who happens to develop. There is a massive difference, and it shows up in how I have historically attracted clients.
Because I cannot sell worth a damn, I have spent a lot of my freelance career working as a hired developer for small agencies. Someone else closes the deal, figures out what the client wants, and hands me the work. That arrangement taught me something important: by the time a project reaches the developer, every red flag the client showed during the sales process has already been baked into the scope, the timeline, and the expectations. You inherit the problems.
When you are the one doing both sales and delivery, you at least get to see the red flags in real time. The trick is actually listening to them instead of thinking “I need this money.”
The Distance Problem
A huge chunk of my freelance work has been remote. Not remote like “we are in the same city but I work from home” remote. Remote like clients several time zones away, where you have maybe three overlapping waking hours. Remote like a coast away, where they think 4 PM their time is a reasonable meeting request when I have been done for an hour.
Remote-only client relationships strip away all the social cues that normally help you read a room. You cannot see their face when you quote a price. You cannot tell if the silence on the other end of the call is contemplation or fury. Everything becomes email tone interpretation, which, as anyone who has ever had a relationship will tell you, is a terrible way to communicate.
Here is what I have learned: if the communication feels off during the first three emails, it will not get better once you are knee-deep in their codebase at 11 PM trying to fix something they swore was a five-minute change.
The Money Red Flags
“What is the cheapest you can do this?” is not a question. It is a warning siren. Not because wanting to save money is wrong, but because the person asking it has already decided your work is a commodity. They are shopping for the lowest bidder, and the lowest bidder will always be someone on Fiverr who will deliver a dumpster fire that you will eventually get hired to fix. Let them go find that person first. They will be back.
The cousin thing is real, by the way. “My nephew knows computers” is a whole client archetype. You lose the bid to a teenager, and then you get the call six months later to rebuild the whole thing. The second time around, you charge more. Lessons have tuition.
And the classic: “This could lead to big things.” Know how many times that phrase has actually led to big things? It leads to a small thing that you get underpaid for.
The Scope Creep Machine
“Can we start small and add features later?” is the most dangerous sentence in freelancing. It sounds so reasonable. It sounds like a client who understands iterative development. What it actually means is: they want the big thing but they only have the budget for the small thing, and they are hoping that once you are invested in the project, you will keep building because you are a nice person who does not like leaving things unfinished.
I am that nice person. I have undiagnosed ADHD - strongly suspected, never formally diagnosed - and it means I hyperfocus on problems. Once I am locked in on a project, I physically cannot stop thinking about it. I have absolutely given away free work because my brain would not let me ship something I knew was incomplete. That is my problem, and I own it. But recognizing that pattern in myself made me much better at recognizing the clients who would exploit it.
The Communication Red Flags
If a client takes four days to respond to your email but expects you to reply within an hour, that is not a busy person. That is a person who thinks the relationship is one-directional. This never improves. It only scales.
Refusing to put requirements in writing is the big one though. “We will figure it out as we go” is the client version of “hold my beer.” It means when the project does not match the vision they never articulated, it will be your fault. I have learned to write the requirements myself and send them for approval. If they will not sign off on a scope document, I will not write a line of code.
The midnight texters are a special breed. A message at 1 AM about font sizes is not a broken site. Not a security breach. Font sizes. At 1 AM. That is not urgency. That is a boundary issue wearing urgency as a costume.
The “Too Many Decision-Makers” Problem
“I need to check with my business partner” after every single conversation is a death spiral. I have watched simple projects stretch to six months because every decision required a committee vote between people who disagreed about everything. If the person on the call cannot approve a button color without convening a summit, you are not building a website. You are facilitating a support group.
What Good Clients Actually Look Like
After 16 years, I can usually tell within the first call. Good clients:
- Have a budget and are willing to say the number out loud
- Respond to emails within a business day
- Trust your expertise enough to take recommendations
- Understand that “quick change” is a relative term
- Sign contracts without acting like you just insulted their mother
- Have one person who makes decisions
That last one is the most important. One decision-maker. One throat to choke, as the agency world so delicately puts it.
The Gut Check
The best red flag detector I have is not a checklist. It is a feeling. After enough projects, your subconscious starts pattern-matching faster than your conscious brain can articulate. If something feels off on the first call, it is off. The times I have ignored that feeling, I have regretted it.
Here is the thing about freelancing that nobody tells you: saying no to bad clients is not just about avoiding pain. It is about making room for the good ones. Every month you spend grinding on a nightmare project is a month you are not available for the client who would have been a perfect fit.
I am still terrible at marketing. I am still not great at pitching. But after 16 years, I am fu**ing excellent at spotting the people who will make my life miserable, and I am finally old enough to walk away from them.
