Field Notes From Seven Years of Dodging Bad Clients (and Finding the Good Ones)
Photo: Tran Mau Tri Tam tranmautritam, CC0, via Wikimedia Commons
Nobody teaches you how to read a client in design school. You learn type kerning, color theory, how to build a case study — and then you graduate and get on a Zoom call with a man who says "we just want something that pops" and realize you're on your own.
So consider this my field guide. Seven years of freelancing, a handful of disasters, and a lot of lessons I paid for in unpaid invoices and Sunday-night dread. All names changed, because I'm not trying to get sued.
The Red Flags I Rationalized
"This is a quick call, I promise." The call with "Marcus" was scheduled for twenty minutes. It ran ninety. Then he wanted "a quick sync" Tuesday. And Thursday. By week three I'd spent more hours in meetings than I'd budgeted for the entire project. Quick calls that multiply aren't enthusiasm — they're a preview of the scope creep coming for your calendar. I now count scheduled touchpoints against the actual contract. If the pre-work conversations outnumber the deliverables, I raise my rate or walk.
Scope creep wearing an excitement costume. This one's sneaky because it feels good. "Dana" was thrilled with everything — so thrilled she kept adding. Would you also do the email templates? The pitch deck? My sister's logo? Each request arrived wrapped in a compliment, which made saying no feel like kicking a puppy. Here's what I learned the hard way: excitement without a change order is just unpaid labor with better vibes. Now, every "one more thing" gets a cheerful "Happy to! Let me send over an updated scope." The genuinely excited clients say yes. The rest go quiet.
The ghost who resurfaces. Great first meeting. Effervescent, even. Then three weeks of silence, followed by "sorry, crazy busy — anyway, can we start Monday?" I used to interpret the silence as them being important. It's actually a data point about how they communicate under no pressure at all. If they vanish when you're just a candidate, imagine how they'll behave when you're waiting on feedback for an invoice.
The budget question they can't answer. When I ask about budget and hear "it depends," I've learned to hear: we haven't decided if this matters to us. Vagueness about money at the start is a promise of vagueness about money at the end.
The Green Flags I Now Hunt For
After enough bad dates, you start noticing what the good ones do differently. These are the signals I actively look for:
They show me their process, not just their dreams. A client who can describe how they make decisions — who signs off, what their last project's timeline looked like, where things got stuck — is a client who respects process. That respect transfers directly to how they'll treat mine.
They ask questions that cost them something. The best client I ever had opened our first call with, "What would make you fire us?" A question like that signals self-awareness and a genuine interest in a working relationship, not just a vendor transaction.
They mention money first. Unprompted. "Our budget is probably in the X range — does that work for what you do?" I nearly fell out of my chair. Clients who lead with numbers have usually done this before, and they know that clarity is kindness.
They give feedback like a person, not a committee. "The second direction feels too corporate for our audience — can we push the warmth?" is a green flag. A wall of contradictory sticky notes from eleven stakeholders is a warning siren. One clear voice with authority to make decisions is worth a rate bump, honestly.
They're kind to someone they don't need to be kind to. Watch how they treat the junior person on the call, the assistant who schedules, the barista if you ever meet in person. That's who shows up at hour eleven of a revision cycle.
The One Question That Filters Most of This
If I could ask only one thing in a discovery call, it would be this: "Tell me about your last creative project that didn't go well."
How they answer tells me nearly everything. Clients who can own their part in a past failure — we gave feedback too late, we changed leadership mid-project — are the ones who'll communicate when this project hits a rough patch. Clients who blame every designer they've ever worked with? That's not a red flag. That's a flare.
Trust the First Data Point
Here's my closing thought, the one I wish someone had handed me in 2018: people show you who they are early, and freelancers are professionally optimistic, so we explain it away.
The missed call before the contract is a data point. The vague budget is a data point. The compliment-wrapped extra request is a data point. None of them alone is disqualifying. But when you catch yourself writing a mental justification for a client's behavior — they're just busy, they're just excited — pause. You don't rationalize red flags for clients you already have. You rationalize them for clients you're afraid to lose.
The good ones exist, by the way. They pay on time, they give clear feedback, they send referrals. And they're easier to spot once you stop spending your energy explaining away the bad ones.
