Published 2026-07-04 · Updated 2026-07-04 · Adrieluxe Team
Should I take this client? A 10-signal checklist
Whether to take a client comes down to ten checkable signals — most answerable from the brief and one exchange, before any real discovery call. Zero to two red signals, take it. Three or four, proceed carefully with a deposit and tighter written scope. Five or more, or one disqualifying pattern on its own, decline. None of the ten require reading intent or trusting a gut feeling — each is a concrete thing the client said, wrote, or did, checkable in the time it takes to reread their last email.
Prefer an interactive version? Try the 10-signal quiz and get a scored verdict in under a minute.
TL;DR
Check ten concrete signals before proposing: named deadline reason, named budget, direct access to the decision-maker, outcome-framed brief, an ownable reason for the last freelancer's exit, acceptance that scope changes cost more, a brief that holds up on a second read, written (not just verbal) communication, no pre-emptive rate anchoring, and tolerance for early pushback. Score the reds, don't rationalize them — most bad projects fail a signal you noticed and talked yourself out of.
Why a checklist beats a gut feeling
A new inquiry arrives at the exact moment your judgment is worst — you want the work, so ambiguous signals default to the generous reading. The Freelancers Union found 71% of freelancers have dealt with nonpayment or late payment, losing roughly $6,000 a year, and Proposify's data across 1.28 million tracked proposals puts the average win rate at 43% — most of the effort goes into pitches that were never going to land. A concrete checklist run at intake catches what optimism would talk you out of noticing.
Every one of these signals is something the client said, wrote, or did — not a feeling you're supposed to trust more than the evidence in front of you.
The 10 signals to check before you propose
These map onto the four risk vectors in the Client Risk Score framework, broken into concrete, checkable moments rather than scored dimensions — the fast version to run before deciding whether a deeper review is even worth the time.
They can name the deadline's reason
Real deadlines have a cause — a launch, an event, a compliance date. Ask one follow-up question. If the reason evaporates or shifts, the urgency was manufactured, and manufactured urgency predicts rushed approvals and skipped reviews later.
They name a number when asked for budget
Even a wide range counts. "It depends on the proposal" the third time you ask isn't an open mind — it's a stall, usually so they can anchor on your lowest quote instead of naming their own ceiling first.
You're talking to the person who signs
"I'll need to check with my partner" once is normal. Twice means every deliverable gets a second approval cycle you didn't price in. Find out who releases the budget before you write anything.
The brief describes an outcome, not just a task list
"Reduce cart abandonment" beats "build me a checkout flow." Task-only briefs hide scope inside decisions nobody has made yet — you'll be making them mid-project, for free.
Their last freelancer's ending has a specific, ownable reason
"They stopped responding" is a story about the freelancer. "We changed direction mid-project and didn't adjust the timeline" is a story about the client — and it's the story you're about to be inside.
They accept that added scope costs more
Test it before signing: mention one plausible addition and watch the reaction. "That'd be a change order" is a green light. "I assumed that was included" is the entire rest of the project, previewed.
The brief survives being read twice
Vague on the first pass and still vague on the second means the client hasn't thought it through either. You'll be doing the discovery work they skipped, unpaid, before you can even start scoping.
Communication has been in writing, not just calls
Freelancers Union data shows disputes with clients who never put anything in writing take an average of 98 days to resolve, when they resolve at all. If every exchange so far has resisted a written recap, that pattern doesn't change after signature.
They haven't negotiated your rate before seeing it
"We normally pay $X for this" — said before you've quoted anything — is anchoring against a number you never gave them. It signals the whole relationship will be adversarial on price, not just the opening quote.
Pushback on one thing didn't end the conversation
Push gently on scope or timeline early, in the sales conversation, and see if they engage or disengage. A client who can't tolerate a boundary before signing won't tolerate one after.
How many red signals mean decline?
Zero to two red: take it — every client has some friction, and two isolated signals are noise. Three or four: proceed carefully — require a deposit, stage the payments, put the scope boundary in writing before the kickoff call. Five or more, or a single disqualifying combination (budget refused twice and an unnamed decision-maker, or a brief that's still vague on the second read), decline. The count is a guide, not a formula — a named decision-maker who dodges budget twice is worse than four scattered minor signals, because it means the person with authority is the one stalling.
Related reading
This checklist is the fast version of the full workflow in Client qualification: the complete guide, which covers the four scored risk vectors, the discovery questions each low score generates, and how to decline well when the signals say no. Once more than one person is running this checklist independently, see how agencies decide which clients to reject for the written policy that keeps the calls consistent across people.
Frequently asked questions
Zero to two red signals: take it normally. Three or four: proceed carefully — a deposit, staged payments, a tighter written scope. Five or more, or any single disqualifying pattern (budget refused twice, a vague brief that stays vague on a second read), decline. The count matters less than which signals are red — a mismatched budget combined with an unnamed decision-maker is worse than four minor signals in isolation.
About half the signals, yes — brief clarity, outcome-vs-task framing, whether a number was named, how the previous freelancer's ending is described. The rest (does pushback on scope get a reaction, do they negotiate before seeing your rate) need one exchange or call. Run what you can from the brief first; it tells you whether the call is worth scheduling.
Skip that signal's weight and lean on the other nine — a first-time client can't fail the history check, but a first-time client with a vague brief, a dodged budget question, and manufactured urgency is still a decline. Newness isn't a green flag on its own; it just removes one data point.
Related but not identical. The four risk vectors — scope clarity, budget alignment, timeline pressure, stakeholder position — are scoring dimensions for a deeper written analysis. This checklist is the fast, binary version: ten yes/no signals you can run through in the time it takes to reread an email, mapped onto the same underlying vectors.
Yes — that's what client qualification software does: reads the brief, checks it against these kinds of signals, and returns a scored verdict with the specific gaps named. Pre-Sales OS is built for exactly this. The checklist works by hand too; software just makes it consistent at volume.
Run the checklist on a real brief, scored automatically.
Paste the brief and get the ten signals checked, the risk vectors scored, and the discovery questions generated — new accounts get a 15-day free trial of the full Pro plan, no card required.
Analyze a brief