November 22, 2025 · 5 min read
Client Red Flags I Learned the Hard Way, a List
Every one of these red flags showed up before the project went bad, and I ignored every one of them at least once before learning to take them seriously.
None of these are theoretical. Each one on this list showed up before a specific project went badly, and I noticed it at the time and talked myself out of taking it seriously, every single time, until I stopped doing that.
- "We've been through three other consultants/agencies" said casually, without the client reflecting on why — usually means the problem isn't the vendors, and you're about to become the fourth data point.
- A decision-maker who isn't on the discovery call and whose approval is described as a formality — it's never a formality.
- Scope described entirely in outcomes ("we need more leads") with no willingness to get specific about current state or constraints when asked.
- Urgency framed as "we need this yesterday" at the proposal stage, before any actual scoping has happened — real urgency and performed urgency look identical until you're three weeks in.
- Pushback on a reasonable discovery fee or paid audit, from a client who otherwise has budget — reluctance to pay for diagnosis often predicts reluctance to pay for anything that isn't a flashy deliverable.
A red flag noticed and ignored isn't a surprise later. It's a decision you made and forgot you made.
What changed
I don't treat any single flag as an automatic decline anymore — context matters, and plenty of fine clients have one of these without the others. But two or more together, in the same discovery call, is now a hard pause, and I say so directly rather than talking myself past it the way I used to. The projects I've declined on this basis have, without exception, gone on to confirm the pattern with whoever took the work instead, which is cold comfort but at least confirms the list is worth keeping.