8 Client Red Flags That Look Like Enthusiasm Until You Sign
Instant praise, urgent starts, trashing the last developer: the client red flags that look like good signs, and what each one predicts after you sign.
Kemal Esensoy·Modified on July 15, 2026
Every time a prospect called me a genius on the first call, the project went sideways. Not most times. Every time. After 8 years and 100+ projects, that pattern is too consistent to be a coincidence.
Here's the uncomfortable part: the clients who burned me never looked like problem clients at the start. They looked like dream clients. Excited, decisive, generous with compliments. The obvious client red flags, the missing budget, the missing contract, the haggling over every euro, filter themselves out early. The dangerous ones walk in wearing enthusiasm.
So this is not another list telling you to avoid people who won't sign a contract. You already know that. These are the eight flags that look like good signs, right up until you sign.
Why the Obvious Red Flags Rarely Burn You
Every red flag list covers the same five things: no budget, no contract, asking for free work, haggling, ghosting mid-conversation. That advice is useful in your first year of freelancing. After that it's mostly useless, because those clients announce themselves. You see them coming and you say no.
The clients who actually cost me money passed every obvious check. They had budget. They signed fast. They replied to emails within minutes. On paper, perfect. The problem was never what they refused to do. It was what they did too eagerly.
And if it feels like difficult clients are getting more common lately, you're not imagining it. That makes filtering on the first call more important than it has ever been. Here's what I actually watch for now.
1. The Instant "You're Hired" With Zero Questions
A serious buyer asks questions. About your process, your timeline, what happens when something goes wrong. When someone wants to hire me fifteen minutes into the first call without asking a single one, they're not buying my work. They're buying relief from a problem they haven't defined.
What it predicts: scope shock. They never articulated what they wanted, so whatever you deliver gets compared against a picture that exists only in their head. That gap gets closed with unpaid revisions. Yours.
2. "The Last Developer Was Terrible"
Sometimes the last developer really was terrible. I've inherited codebases that made me question humanity. But listen to how they tell the story. If it's all betrayal and zero self-reflection, no "we probably briefed them badly," no "we kept changing our minds," then you're not hearing a review of the developer. You're hearing a preview of your own exit interview.
What it predicts: you're next in the sequence. A disturbing share of my worst projects started with exactly this sentence.
3. Urgency Dressed Up as Excitement
"Can we start Monday?" sounds like enthusiasm. Often it's panic with better branding. Something upstream went wrong, a launch, a deadline, an investor meeting, and you're the emergency solution.
What it predicts: discovery gets skipped, decisions get rushed, and when the rushed thing breaks, guess whose fault it is. Real urgency exists, but a client with genuine urgency accepts trade-offs. Fake urgency wants everything, fast and cheap, delivered yesterday.
4. Nobody Can Tell You Who Decides
Ask "who approves the final result?" and watch what happens. If the answer is vague, something like "well, me, but I'll show it to my business partner, and my wife has a good eye for design," you're not dealing with one client. You're dealing with a committee, and the most dangerous member is the one you'll never meet.
What it predicts: feedback whiplash. Version one gets approved, then mysteriously un-approved three days later because someone off-stage weighed in. Every revision loop is exactly one invisible stakeholder wide.
5. Flattery Where the Brief Should Be
"You're the expert, just work your magic." Feels great. Means nothing. When compliments replace requirements, you have no acceptance criteria. And a project without acceptance criteria isn't finished when the work is good. It's finished when the client feels it's good.
What it predicts: "it's not what I imagined." Of course it isn't. They never told you what they imagined, and no amount of genius on your side fixes an undefined target. Flattery on call one is the cheapest currency a client has. Notice who spends it heavily.
6. "Budget Is Not an Issue"
Across 100+ projects, the clients who told me money was no object were consistently the slowest payers I've had. Not always the smallest budgets. The slowest payers. People who respect money talk about it plainly. People performing wealth avoid the specifics.
What it predicts: ghosting at invoice time, or the retroactive negotiation. A client once tried to renegotiate the price after I had already delivered. Want to guess what he said about budget on our first call?
And if you're the one who feels awkward naming numbers, that's a separate problem, I've written about that guilt too. But when the client dodges numbers while radiating generosity, that's not comfort. That's a flag.
7. Instant Intimacy
First call, and you already know about their divorce, their business partner's betrayal, and their theory about the industry conspiracy keeping them down. It feels like trust. It's actually a role assignment: you're being cast as the ally, the confidant, the one who finally understands.
What it predicts: you become their therapist, and scope becomes emotional. Saying "that's outside our agreement" to a client is easy. Saying it to someone who treats you as their only ally feels like betrayal, and they know it. Boundaries get renegotiated through guilt instead of change orders.
8. "This Is Just the First of Many Projects"
The promised pipeline. Do this one at a friendly rate, because there's a redesign coming, and a second brand, and their cousin needs a shop too. In eight years, that follow-up empire has materialized approximately never. The clients who actually gave me years of repeat work never promised it upfront. They just paid the full rate, on time, and came back.
What it predicts: discount pressure now, in exchange for a future that isn't real. You're not investing in a relationship. You're just cheaper.
Three Questions That Make These Flags Reveal Themselves
You can't ask a prospect "are you secretly a nightmare?" But you can ask three questions on the first call that do the same job.
"What would make this project a failure for you?" Serious clients have an answer, because they've actually thought about the project. Flag carriers deflect with more enthusiasm: "oh, I'm sure it'll be great!" That's flag 1 and flag 5 revealing themselves in real time.
"Besides you, who needs to approve the final result?" This flushes out the invisible committee from flag 4. If the answer changes between calls, believe the second answer.
"What happened with the last person who worked on this?" Then stay quiet and listen. Not for the facts, for the framing. Self-awareness in this answer is worth more than any budget number.
None of these questions are rude. They're professional. And here's a pattern I keep seeing: good clients like being asked. It signals you've done this before. The only prospects these questions annoy are exactly the ones they're designed to filter. The same logic applies at the end of a project, by the way, which is why I protect the handoff just as carefully.
The Part I Still Get Wrong
I want to be honest: knowing these client red flags and acting on them are two different skills. I still occasionally take a project while a flag waves gently in my peripheral vision, because the work sounds interesting or the calendar looks empty. Pattern recognition doesn't pay invoices. Discipline does. I'm better at the first than the second.
But the flags themselves haven't failed me yet. When a project goes sideways now, I can almost always trace it back to a signal from the first call that I chose to ignore. The information was there. It just looked like enthusiasm.
Enthusiasm from a client is nice. Enthusiasm instead of questions, briefs, budgets, and decision-makers is a warning with good PR. Slow down exactly at the moment a prospect makes you feel fastest.
Been burned before and want the next web project set up properly from day one? Let's talk. I can't promise every client will be a dream. What I can offer: clear scope, clear ownership, and no surprises at invoice time.
About the Author
Kemal Esensoy
Kemal Esensoy, founder of Wunderlandmedia, started his journey as a freelance web developer and designer. He conducted web design courses with over 3,000 students. Today, he leads an award-winning full-stack agency specializing in web development, SEO, and digital marketing.