DEV Community

Alfred P
Alfred P

Posted on

7 Client Red Flags That Cost Me Thousands (And How to Spot Them in the First Call)

Every freelancer has a horror story.

Mine involved a client who "just needed a few tweaks" for three months straight. No extra pay. Just guilt and vague threats about leaving a bad review.

I stopped blaming them eventually. The red flags were there on the first call. I ignored every single one.

Here is what I look for now before I take any project.

1. They have already fired a previous developer

This comes up as: "We had a developer but it did not work out."

Ask why. If the answer is vague ("we had different visions"), push harder. If they get defensive about a simple question, you have your answer.

Sometimes the previous dev genuinely was bad. But nine times out of ten, the client is the common denominator.

2. They say "it should not take long" before you quote

This is not curiosity. It is pressure.

They are pre-negotiating your price before you even understand the scope. A client who respects your expertise asks what it involves. A difficult client tells you how long it should take.

3. The budget is secret until after you pitch

"Tell us your price first and then we will discuss budget."

No. Budget transparency is a basic sign of good faith. If they will not share a range, they are either way below your rates or they plan to negotiate you down after you are already invested in the pitch.

4. They want to "start small to see how it goes"

Paid discovery is legitimate. Unpaid trial work is not.

A small paid project to establish trust is fine. But if the framing is "do this for cheap or free to prove yourself," walk away. You are not an intern.

5. They contact you at weird hours and expect instant replies

A client who messages you at 11pm on a Sunday and follows up at 7am Monday is not a dream client. That is your future.

Boundary violations start before the contract. If they do not respect your time during the sales process, they will not respect it during delivery.

6. They have "urgent" projects that somehow waited months

"We need this done in two weeks, it is extremely urgent."

Then why did you not start looking for a developer two months ago when you planned this project?

Fake urgency is a negotiation tactic. It makes you feel like you have to drop everything and cut your rates to help them. Real urgency comes with real budget.

7. Approval requires more than two stakeholders

"Our CEO, CTO, marketing lead, and the founder's wife all need to sign off on designs."

Run.

Death by committee means endless revision cycles, conflicting feedback, and a project that never ends. Always ask: who has final say? If no one can answer clearly, that is your answer.


I still get it wrong sometimes. But checking these seven things on every first call has saved me from at least four nightmare projects in the past year.

The goal is not to filter out every difficult client. The goal is to stop ignoring signals you can already see.


Want a system for managing client work without the chaos? The Freelance Command Center is a Notion OS built for freelancers who want everything in one place. EUR 17.

Top comments (0)