Red Flags I Look for Before Taking On a New Client
Not every inbound inquiry deserves a yes, and one of the more expensive lessons in this business is learning that too late instead of too early. I've taken on projects that looked fine on paper and turned into a drain on time, energy, and goodwill I could have avoided entirely if I'd paid closer attention to a few warning signs during the first conversation.
Over enough projects, certain patterns started repeating, and I now treat them as genuine signals worth slowing down for, not just minor annoyances to push through. I go deeper into the full client-screening process I use, including the questions I ask before ever sending a proposal, in The Adventure Travel Photographer's Playbook. Here's the shorter version of what I actually watch for.
Vague Scope That Never Gets More Specific
A client who can't describe what they actually need, even after a direct conversation about it, is one of the clearer warning signs I've learned to take seriously. Some vagueness at the very first inquiry is normal, plenty of good clients start a conversation not fully sure what they want. The red flag is when that vagueness persists after you've asked clarifying questions directly.
Scope that stays fuzzy tends to stay fuzzy all the way through the project, which usually means the deliverables, timeline, and expectations were never actually agreed to, just assumed differently by each side. That gap is where scope creep and disappointment both live, and it's much cheaper to surface it in the first conversation than to discover it mid-shoot.
When I run into this, I'll usually try one more round of specific, closed questions rather than open-ended ones — asking for a concrete number of final images, a specific use case, a specific deadline. If the answers stay vague even then, that tells me something real about how the rest of the project would likely go.
Pressure to Skip the Contract
Any pushback on having a signed agreement before work begins is one of the fastest red flags in my process, and it's non-negotiable regardless of how appealing the rest of the project looks. A client who's uncomfortable putting basic terms in writing is telling you something about how they intend to handle disagreements later, when the terms would actually matter.
This isn't about assuming bad faith from every client who asks a question about the contract. Reasonable questions about specific clauses are normal and healthy. The red flag is resistance to having any agreement at all, or pressure to start production work before terms are finalized because of an urgent timeline.
An urgent timeline is real sometimes, but it's rarely so urgent that a same-day or next-day signature isn't possible if the client actually intends to follow through. When the urgency is used as a reason to skip the agreement entirely rather than just speed it up, that's a different situation, and one I've learned to walk away from.
Unwillingness to Pay a Reasonable Deposit
I ask for a deposit, generally around half the project fee, before production begins on most projects. Pushback on a reasonable deposit request is another signal worth paying attention to, separate from a client simply asking about the reasoning behind it, which is a fair question to ask and answer.
A client who wants to pay everything only after final delivery, with no deposit at all, is asking the photographer to carry all of the financial risk in the relationship. That's not automatically a dealbreaker on its own, but combined with any other flag on this list, it moves from a minor concern to a real one worth taking seriously before committing further time.
I've found that clients who understand and respect standard industry payment structures tend to be easier to work with across the entire project, not just at the deposit stage. The willingness to pay a fair deposit correlates, in my experience, with a generally more professional working relationship overall.
A History of Underpaying or Undervaluing Creative Work
When a prospective client openly references paying very little for past creative work, or expresses surprise that professional photography costs what it costs, that's useful information rather than something to argue past. It doesn't necessarily mean the conversation ends immediately, but it tells me the negotiation is likely to be more difficult and the working relationship potentially less respectful of the actual value being delivered.
I try not to take this personally or treat it as an insult. Some clients genuinely don't know what professional adventure photography costs, and a clear, confident explanation of value can shift that conversation productively. The flag is less about the initial comment and more about how the client responds once that value has been explained clearly.
If the pushback continues even after a clear explanation of pricing and what it includes, that's usually a sign the fit isn't right, rather than a negotiation still worth pursuing. Continuing to argue the point past that stage rarely ends with a client who respects the final agreed price once the project is underway.
Multiple Decision-Makers With No Clear Final Say
Projects that involve several people weighing in on creative direction, with no single person clearly empowered to make a final call, tend to produce the most difficult revision processes I've dealt with. Feedback that contradicts itself between stakeholders isn't unusual on its own, but a client relationship with no clear resolution path for that contradiction is a structural problem worth flagging early.
I've learned to ask directly, early in the process, who has final creative sign-off on the project. A confident, specific answer is a good sign. A vague answer, or one that implies several people all have equal final say, tells me the revision process is likely to be longer and more frustrating than the contract's revision limit was built to handle.
This doesn't mean walking away from every project with multiple stakeholders, since that's genuinely common in commercial work. It means building the contract's revision terms and communication expectations with that reality in mind from the start, rather than discovering the problem partway through editing.
Requests That Blur Usage Rights Into Ownership
When a client's early language treats a standard licensing agreement as if it were a full buyout of ownership, that's worth clarifying immediately rather than letting the ambiguity carry forward into the contract. This usually isn't malicious. A lot of clients genuinely don't know the difference between licensing usage rights and owning the copyright outright.
The flag isn't the initial confusion, it's what happens after a clear explanation. A client who accepts the clarification and adjusts their expectations is a normal, fine outcome. A client who continues pushing for full ownership at a licensing price, even after the distinction has been explained, is signaling something about how they'll approach usage rights on future projects too.
I treat this conversation as an early test of how the client handles a clear professional boundary. How that specific disagreement gets resolved tells me more about the likely working relationship than almost anything else discussed in an initial call.
A Pattern of Disrespecting Your Time Before the Project Even Starts
Repeatedly rescheduled calls, slow responses to simple questions, or asking for free exploratory work before any agreement is in place are all signals I take seriously, even though each one individually might have an innocent explanation. The pattern matters more than any single instance.
A client who doesn't respect the pre-project process, the calls, the proposal turnaround, the basic logistics, rarely becomes more respectful of your time once the project is actually underway and the stakes are higher. If anything, the pressure of an active shoot with a real deadline tends to amplify existing habits rather than correct them.
I've started weighing this more heavily over time, because it's one of the easier flags to actually observe directly, before you've committed any real time or resources to the relationship. It costs nothing to notice how a prospective client treats the process before a contract exists.
What I Do When I Spot One of These
A single flag on this list doesn't automatically mean I decline a project. Context matters, and some of these can have reasonable explanations that a direct conversation clears up. What changes my approach is when a flag doesn't resolve after being addressed directly, or when multiple flags show up together in the same client relationship.
In those cases, I've learned to either scope the project more conservatively, with tighter terms and a firmer deposit, or decline it outright if the combination of concerns outweighs the potential value. Turning down a project that pattern-matches to past problems is rarely as costly as taking one on and discovering the pattern was accurate.
This isn't about becoming suspicious of every new client. Most inquiries are perfectly fine, and treating everyone like a risk would make the business impossible to run. It's about paying attention to the handful of signals that have actually predicted difficult projects in the past, and taking them seriously when they show up.
The Questions I Ask in the First Real Conversation
A lot of these flags never get the chance to surface if the first real conversation with a prospective client stays too surface-level. I've built a small set of direct questions into that early call specifically to bring potential issues into view early, rather than discovering them mid-project. Who has final creative sign-off, what's the actual timeline flexibility, and what's the intended use of the final deliverables are three I ask on nearly every call.
The answers matter less than how directly and confidently they're given. A client who can answer these questions clearly and specifically, even if the answers reveal some complexity, tends to be an easier client to work with than one who gives vague or shifting answers to fairly basic questions about their own project.
I treat this early conversation as a two-way screening process, not just an opportunity for the client to evaluate me. Asking direct questions confidently also signals professionalism on my end, which tends to set a better tone for the entire relationship regardless of how the specific answers land.
When a Flag Turns Out to Be a False Alarm
Not every early flag predicts a genuinely difficult project, and I've been wrong about this more than once, treating something as a warning sign that turned out to have a perfectly reasonable explanation once it was actually addressed directly. A first-time client's unfamiliarity with standard contract or deposit terms, for instance, is often just inexperience rather than an intentional red flag, and a clear, patient explanation usually resolves it without issue.
The distinction I've learned to make is between a flag that resolves cleanly once addressed and one that persists or gets defensive once addressed. A client who says "oh, I didn't realize that was standard, that makes sense" is behaving very differently than one who continues pushing back after a clear, reasonable explanation has already been given.
I try to stay genuinely open to that distinction rather than treating every initial flag as a confirmed dealbreaker. Overcorrecting into reflexive suspicion would cost me legitimate, good clients who simply hadn't worked with a professional photographer before and didn't yet know what standard practice looked like.
Trusting the Pattern More Than Any Single Data Point
No single flag on its own is usually enough to decline a project outright, and I've had to train myself out of overreacting to one isolated concern in an otherwise promising conversation. What actually matters is whether a concern is isolated or part of a broader pattern showing up across several parts of the same early interaction.
I try to keep a rough mental tally during an initial conversation rather than fixating on the first thing that feels slightly off. A single vague answer to one question, on its own, is well within normal range. That same vagueness paired with resistance to a deposit and slow responsiveness scheduling the call itself starts to look like a genuine pattern worth taking seriously.
This pattern-based approach protects against two opposite mistakes: declining a fine client over one minor, explainable concern, and accepting a genuinely risky client because no single flag felt severe enough on its own to justify saying no. Looking at the whole picture, rather than any one moment in isolation, has served the business better than either extreme.
Writing These Flags Down Instead of Relying on Memory
After enough projects, I started actually keeping a short, private note of what specific signals had preceded past difficult projects, rather than trusting myself to remember the pattern accurately in the moment years later. Memory tends to smooth over specifics and replace them with a vaguer, less useful impression of "that client felt off," which isn't specific enough to actually apply to a new situation.
Having an actual written list, even an informal one, means I'm comparing a new client's early behavior against concrete past patterns rather than a fuzzy gut feeling. It's also made it easier to notice when I'm about to repeat a mistake I've specifically made before, rather than discovering the repetition only once the project is already underway and the same problem starts to surface again.
This is a small operational habit, but it's turned a set of instincts I might have otherwise struggled to articulate consistently into something closer to an actual, repeatable screening process, which is a meaningfully more reliable tool than intuition alone.
None of this replaces good judgment on a case-by-case basis, and there will always be exceptions worth making for the right project even when a flag or two shows up. What a written pattern does is make sure those exceptions are deliberate choices rather than accidental ones made under the pressure of an appealing opportunity in the moment.
The goal, ultimately, isn't to filter out every imperfect client. It's to walk into every new relationship with eyes wide open, having actually paid close attention to what was genuinely in front of you from the very first real conversation onward, rather than after the fact.
I break down the exact screening questions and contract terms I use to protect against these situations in The Adventure Photographer's Playbook, if you want a more structured process for your own client intake.
Reflection Questions
- Has a client's scope ever stayed vague even after you asked direct, specific clarifying questions?
- How do you currently respond when a prospective client pushes back on a contract or deposit?
- Do you know, before a project starts, who actually has final creative sign-off among your client's stakeholders?
- What pattern of behavior before a contract is signed has predicted a difficult project for you in the past?
Dalton Johnson is a professional adventure and editorial photographer with over a decade of experience creating images on all seven continents. His client work includes Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, Big Agnes, Ford Bronco, and 160+ other brands. He runs Dalton Johnson Media as a full-service studio, from pre-production through post and distribution.