15 Client Red Flags to Spot Before You Sign
By Suraj Rao10 min readWhat You'll Learn
- Most bad client relationships show warning signs before anything is signed: vague goals, no budget, a missing decision-maker, or resistance to a contract or deposit.
- A red flag is not always a reason to walk away; many can be fixed with clearer scope, a deposit, shorter terms or a higher price for the risk.
- Score each new lead on the same checklist, so the decision to take or decline the work is based on a pattern, not on how much you need the money that week.

A client red flag is a warning sign, seen before you start work, that a client is likely to cause trouble later: unpaid invoices, endless revisions, scope creep or a project that never ends. The earlier you notice one, the cheaper it is to deal with.
Most red flags show up in the first few conversations. The problem is that you see them when you want the work most, so it's easy to explain them away. A checklist helps, because it asks the same questions whether you're fully booked or worried about next month.
This post walks through 15 red flags in three stages (discovery, proposal and contract), what each one usually means and what to do about it. It ends with a scorecard you can use on every new lead and a polite script for turning work down.
Why it pays to look before you sign
Once a contract is signed and work has started, every problem is harder to fix. You've blocked out time, turned down other work and possibly spent money. Payment problems in particular are common: in a Freelancers Union survey of 5,358 freelancers published in 2015, 71% said they'd had trouble collecting payment at some point in their career.
Not every warning sign means "walk away". It helps to sort them into two groups:
| Type | What it means | Typical response |
|---|---|---|
| Yellow flag | A gap you can close with clearer terms | Ask a question, adjust the proposal |
| Red flag | A pattern that terms alone won't fix | Price the risk heavily, or decline |
The same sign can be either. A client who can't name a budget because they've never hired a freelancer is a yellow flag. A client who refuses to name one so they can push you lower is a red flag. The difference usually shows up in how they respond when you ask.
Discovery stage red flags
These show up on the first call or in the first few emails, before you've written a proposal.
1. They can't say what they want
"We need a new website" with no idea why, for whom or what success looks like. Without a goal, there's no finish line, and the project drifts.
What to do: Ask what happens if they do nothing, and what would make the project a success in six months. If they still can't answer, offer a short paid discovery phase before you quote the full project.
2. No budget, or one far below the work
"What would you charge?" is fine. Refusing to give even a range, or naming a figure that's a fraction of what the work costs, is not.
What to do: Give a range yourself: "Projects like this usually run between $6,000 and $9,000." Watch the reaction. If the budget is far off, say so on the call and suggest a smaller scope that fits.
3. An impossible deadline
"We need it by Friday" for a month of work. Urgent deadlines happen, but an unrealistic one often means poor planning, and that won't stop at the deadline.
What to do: Ask what's driving the date. If it's real, offer a reduced first phase that can ship in time, with the rest after. If it's arbitrary, quote the real timeline.
4. They criticize every previous freelancer
One bad experience is normal. "We've been through three designers and they were all useless" tells you how they may describe you next.
What to do: Ask what went wrong and what they'd want done differently. If the answers point to vague briefs, late feedback or unpaid invoices, that's a pattern on their side.
5. You can't find the decision-maker
You're talking to someone who "just needs to run it past" a boss you never meet. When the boss finally sees the work, the brief changes.
What to do: Ask directly: "Who gives final approval on the work and on the budget?" Ask for that person to join the kickoff, or at least to sign the proposal.
6. They want free work first
"Show us a few concepts and we'll pick the best" or an unpaid "test project". Some clients use this to collect ideas from several freelancers at once.
What to do: Point to your portfolio, or offer a small paid trial with a clear fee. Don't send original work for free.
Proposal stage red flags
These show up once you've sent a proposal and the client responds.
7. They haggle before reading the scope
The first reply is "Can you do it for less?", with no question about what's included. They're buying a number, not an outcome.
What to do: Trade scope for price, never price alone: "I can bring it to $5,000 by removing the blog setup." Our guide to writing a project proposal shows how tiered options make this conversation easier.
8. They want to start before anything is signed
"Let's just get going and sort out the paperwork later." Later rarely comes, and without a signed scope you have nothing to point back to.
What to do: Keep it friendly and firm: "I can start on [date] once the proposal is signed and the deposit is paid. It takes about five minutes."
9. The scope grows during proposal review
Each round of comments adds "just one more thing", and the price is expected to stay the same. This is scope creep before the project has even started.
What to do: Update the price with every addition, and show the change: "Adding the member area brings the total from $7,500 to $9,800."
10. They go silent, then reappear in a rush
No reply for three weeks, then "Can you start Monday? We still need the original launch date."
What to do: Confirm your current availability and set the timeline from the signing date, not from the first conversation. Note it: this client may go quiet again mid-project.
11. "There'll be lots more work if this goes well"
Promises of future volume in exchange for a discount now. Sometimes it's true. Often it isn't, and the low rate becomes the anchor for everything after.
What to do: Charge your normal rate now, and offer a discount on the future work if it arrives, for example 10% off a signed retainer.
Contract and payment stage red flags
These are the most serious, because they affect whether you get paid.
12. They won't sign a contract
A client who refuses a written agreement is telling you they want room to change the deal later. In some places, it's also against the rules: under New York City's Freelance Isn't Free Act, work worth $800 or more, including smaller jobs that add up to $800 within 120 days, must have a written contract, according to NYC's Department of Consumer and Worker Protection. Laws differ by location, so check what applies where you and your client are.
What to do: Send a short, plain-English contract. Our guide to what to include in a freelance contract lists the clauses, and the free contract template is a starting point. If they still won't sign, decline.
13. They refuse a deposit
A deposit shows the client is committed and covers your early work. Pushback is normal from large companies with fixed procurement rules. From a small client, it's a warning.
What to do: Explain that the deposit reserves their slot in your schedule. If they can't pay one, offer smaller milestone payments instead. Our guide on how much deposit to ask for covers typical splits.
14. Unusual payment requests
Long terms like net 90 from a small business, "we pay when our client pays us", or a check for more than the invoice with a request to send the difference back. The last one is a known scam: the FTC's guidance on fake check scams says that if someone sends you a check for more than the price and asks you to send money back, it's a scam, and that the check can bounce even after the money appears in your account.
What to do: Keep your normal terms and payment methods. Never refund an overpayment until the funds have truly cleared, and if anything feels off, don't send money at all. If net 30 is a stretch for you, our guide to net 30 payment terms explains the trade-offs.
15. They want full ownership before paying
A request for all rights, source files and logins before the final invoice is paid removes your only protection if payment stalls.
What to do: Write ownership to transfer on full payment, and say so in the contract. Most fair clients accept this without argument.
A red flag scorecard for new leads
Score each new lead after the discovery call. Two points for a red flag, one for a yellow, none if it's fine.
| Question | 0 | 1 | 2 |
|---|---|---|---|
| Clear goal? | Yes | Partly | No |
| Budget fits the work? | Yes | Close | Far off |
| Realistic deadline? | Yes | Tight | No |
| Decision-maker involved? | Yes | Named, not met | Unknown |
| Willing to sign a contract? | Yes | Questions | Refuses |
| Willing to pay a deposit? | Yes | Prefers milestones | Refuses |
| How they talk about past freelancers | Neutral | Some complaints | Blames everyone |
How to read it: 0 to 3, go ahead. 4 to 6, go ahead only with tighter terms: a bigger deposit, shorter payment terms, a firm revision limit, or a higher price. 7 or more, decline politely.
Worked example
Say a lead has a partly clear goal (1), a budget that's close (1), a tight deadline (1), a decision-maker you haven't met (1), and no problem with a contract or deposit (0 and 0). They're neutral about past freelancers (0). Score: 4.
That's a "yes, with conditions". You might ask the decision-maker to join the kickoff, take a 50% deposit and add a clause that the launch date moves if feedback is late.
What to do when you spot a red flag
You have four choices, roughly in this order:
- Ask about it. Many flags disappear with one honest question.
- Tighten the terms. Bigger deposit, shorter terms, milestone payments, a firm revision limit.
- Price the risk. If a project needs more management, quote for that time.
- Decline. Politely, and early.
Here's a script for turning work down without burning the bridge:
Hi [Name],
Thanks for talking me through [project]. Having thought about it, I
don't think I'm the right fit for this one, mainly because [the
timeline / budget / scope] doesn't match how I work.
I'd rather tell you now than start something I can't do well. If it
helps, [Name] may be a good fit, and I'm happy to introduce you.
All the best with it,
[Your name]If you take the work anyway, write down the red flags you noticed. They tell you what to watch, and our guide on how to deal with difficult clients has scripts for when they show up.
How Tristiks Grow helps with risky clients
Software won't judge a client for you, but it can make the safer terms easy to use:
- Deposits: create an invoice as scheduled payments, such as a deposit now and the balance on delivery, each with its own amount, send date and terms.
- Signed scope: send proposals and contracts with a secure signing link. You see when each one was sent, viewed and signed, and a signed document is locked. See proposal and contract software.
- Payment terms per client: save each client's payment terms on their profile, so a riskier client can be on shorter terms than your regulars.
- Reminders: turn on payment reminders for 3 days before the due date, on the day, and 7, 14 and 30 days after.
- Notes: keep what you learned on the discovery call in the client's notes, so the red flags you saw are still there when a problem starts.
Frequently asked questions
What are the biggest red flags with a new client?
The most serious are refusing a written contract, refusing any upfront payment, an unrealistic budget or deadline with no flexibility, and unusual payment requests such as overpaying and asking for a refund. Each one points to a risk of not being paid or of the project never ending.
Should I turn down a client with red flags?
Not always. If you can fix the issue with clearer scope, a deposit or a higher price, the work may still be worth doing. Decline when several red flags appear together, or when the client refuses the terms that would protect you.
How do I ask about budget without sounding pushy?
Give a range yourself and ask where they sit: "Similar projects usually cost between $4,000 and $7,000. Does that fit what you had in mind?" It shows you've done this before and makes the answer easy.
Is a client asking for a discount a red flag?
On its own, no. Asking is normal. It becomes a red flag when they want a lower price for the same scope, keep pushing after you've offered options, or ask for a discount in exchange for future work that isn't committed.
Wrap up
Most bad client relationships announce themselves early. Score each lead on the same checklist, ask about anything that worries you, and protect yourself with a contract, a deposit and clear terms before the first hour of work.
To send proposals clients sign online and take a deposit before you start, try Tristiks Grow proposals and contracts free for 14 days.
Category: Client Management

Suraj Rao
Suraj Rao is the founder of Tristiks, the team behind Tristiks Grow and its desktop time tracker OneTrack. He writes about time tracking, client work and getting paid, and about DevOps, cloud and AI from years of building software.



