Dev.to WebDev 🛠 Dev 👁 0 📖 2 min read

8 client red flags every freelancer should memorize

Every freelancer has a story about the client they should never have taken. The details differ; the patterns repeat so reliably you can memorize them. Here are the eight, each with the response that saves you.

Every freelancer has a story about the client they should never have taken. The details differ; the patterns repeat so reliably you can memorize them. Here are the eight, each with the response that saves you.

1. The fantasy budget

Champagne scope, tap-water budget. They want a full platform rebuild for the price of a landing page. Response: anchor to value, offer a smaller first phase at a real price, and walk away if they will not move. A client who will not pay properly will not behave properly either.

2. The no-contract client

"We don't really do contracts, we work on trust." Translation: they want all of the flexibility and none of the accountability. Response: no contract, no work. Ever. This one is non-negotiable.

3. Manufactured urgency

"We needed this yesterday!" — before you have even scoped the work. Sometimes urgency is real. Usually it is a negotiation tactic or a sign of an organization that plans nothing. Response: a rush fee, or a realistic timeline in writing. Watch which one they choose.

4. The "just" revision

"Just make the logo bigger" becomes a second unpaid project, one "just" at a time. Response: the change-order procedure, every single time. Written estimate, written approval, then work. No exceptions for small asks — small asks are how the big ones get in.

5. The committee

Five stakeholders, no decision-maker, feedback by consensus. Your two-week project becomes a two-month referendum. Response: name one decision-maker in the contract, with a 5-business-day feedback clause, or decline the project.

6. The badmouthing ex

They trash their last three developers unprompted. Every one of them was "terrible," "slow," or "impossible." Response: you will be number four. Decline politely and quickly.

7. The free-work audition

"Build us a small feature so we can evaluate you." Custom work, for free, for a stranger, with no commitment. Response: a paid discovery phase, or a portfolio walkthrough of similar work. Never free custom work — it selects for clients who do not value the work.

8. The scope fog

After two conversations they still cannot describe what they want. This is not always a bad client — sometimes they genuinely need help thinking. Response: sell a paid discovery phase that produces the scope. If they will not pay for thinking, they will not pay for building.

The meta-rule

Red flags cluster. One is a conversation. Three is a pattern. Walk away from patterns — the project you decline is never the one you regret.

This is one chapter of The Freelancer Client-Acquisition Kit — 37 pages covering outreach scripts, proposals, 2026 rate tables, contracts, retainers, referrals, and knowing when to walk away. Every data point labeled with its source and evidence strength. No guru fluff: https://cjettoostudent.gumroad.com/l/qfckgb

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.