Project red flags: when to say no to a client

In my first two years working solo, I said yes to everything. Money was money. After five bad projects, I learned the opposite is true: a wrong client costs more than saying no.

A bad project isn’t just about money. It’s time spent that could be invested in good clients. It’s stress. It’s sleepless nights debugging code that the client wants to change three times. It’s relationships affected because someone asks for “a quick tweak” that becomes a week of work.

Warning signs

Completely unrealistic budget. “I need an Instagram-like app but with USD 400.” Forget the price. The problem is the client who thinks an Instagram-like app is cheap. This person won’t understand why it takes time to build a photo filter. They’ll think you’re overcharging.

“Do it quickly and we’ll see the rest later.” This ends in ten scope changes mid-project. You start with five pages, end with forty. The client never decided they wanted more because they never planned. Eventually you’re renegotiating price down or working for free.

Infinite scope. A client who can’t describe what they want. Asks you to “create something beautiful” with no briefing. After you deliver, they say “no, it was like this” pointing to a competitor’s site. Without clear specification you’re set up for failure.

Client who devalues your work. “My nephew does design for free.” “I only pay when it’s 100% perfect.” “You don’t even spend time, you just copy and paste code.” Someone who doesn’t respect technical work won’t respect your time.

Bad relationship offline. If the client is polite in email but angry on calls, or starts pressuring you in the first week, that’s their problem, not something your work will fix. Disrespectful people stay disrespectful.

Real stories

I took a clinic scheduling system project. Budget was low but the clinic was from a friend. Started in September. By January it still wasn’t done because she wanted to change colors, add reports, integrate with non-public software. I made USD 400 for four months of sporadic work. Never again accepted a project from a friend.

Another client showed up saying “I need an e-commerce website.” We started with 10 products. Ended with 300 because he was afraid of leaving something out. Didn’t know if he wanted to sell internationally. Didn’t know how much he wanted to spend on ads. Made decisions based on “what my competitor has.” Project took five months when we budgeted one.

Had a client who called me Saturday nights with “urgent fixes” that weren’t urgent. Wanted code faster because he was in a hurry. When I explained that quality takes time, he said I was slow. Finished the project, got paid, blocked him from everything.

How to say no without burning bridges

You can decline without being rude.

“Your goals are totally valid, but this isn’t my area of expertise. Let me recommend someone who’s better for this type of project.” Done. You look like a good person.

If it’s a low budget, answer honestly. “With budget X, I can do Y. If you need Z, we talk about price.” If he says he needs Z but won’t pay more, you have your answer.

If scope is undefined, set a limit. “I’ll do a one-week discovery so we align exactly on what you want. After that I give you a precise quote.” If he refuses discovery, it’s a sign he won’t spend even on planning. He won’t spend on execution either.

Sometimes the answer is simply “I’m fully booked right now, don’t have availability. But let me take your contact and I’ll call when I’m free.”

The hard truth

Quick money from bad clients costs more than slow money from good ones.

You sacrifice time on the wrong project. Time that could be spent maintaining good clients, learning new tech, or resting. This bad client won’t be a reference. Won’t recommend you. Probably speaks badly of you.

After declining ten bad projects, you become more selective. Good projects take less time to execute because the client cooperates. Client knows what they want. Approves quickly. Pays on time.

I worked eight years to learn this. You don’t need to make the same mistakes.

• Define your minimum project budget
• List your personal warning signs (3-5)
• Practice saying “I can’t do this project right now”
• Create a discovery briefing template
• Turn down the next client with an unrealistic budget
• No project is worth stress affecting your personal life
• Good clients cost less than bad ones

Saying no is part of being professional.

Testing for red flags

Client arrives uncomfortable. Asks aggressive questions. “How much?” “When’s it done?” “That’s expensive, right?”

Someone like that will be difficult. Starts complaining about price before understanding value.

Response: “Let me show you some cases? See if the value makes sense.” If they still complain after seeing the value proposition, it’s a sign.

Another sign is client who takes forever to respond. You ask for info, respond in 2 hours, they take 5 days to answer back. Then in the project they’ll ask for urgent features that are actually specs they messed up.

Communication misalignment is already a red flag.

Recovering problematic projects

Sometimes you take the project and then it starts going wrong. What to do?

First thing: clear conversation. “I see the project is difficult. Can we realign? What’s wrong?” Sometimes the client doesn’t realize and can fix it.

Second: reformulate contract. “Let’s separate what’s already done (paid) from what’s new (rediscuss). That way we get unstuck.”

Third: if client won’t cooperate, time to consider leaving. Costs money now, saves stress later.

I never rescued a project that was truly bad from the start. Thought I could. Couldn’t. Learned that early intervention works better.

How your best clients arrive

Good client comes via referral. “So-and-so recommended you.” Client already has adjusted expectations because they were told good things.

Good client did research. “Saw your portfolio, liked case X, how do you charge?”

Good client has pre-defined budget. “I have USD 1000, what can I get?”

Good client accepts contract. “Of course, makes sense.”

That client who shows up for free on LinkedIn like “hey make a site for me?” usually turns bad.

Take advantage of momentum and build good online presence. Let clients find you. Don’t accept every proposal that comes in.

Statistical truth

Eight in ten devs who lose money with a client? Their fault for accepting.

Two in ten had bad luck (client really changed situations or was dishonest).

You control 80% of the outcome by selecting good clients at the start.

Read also: Client doesn’t know what they want | Freelance dev contract essentials | What to charge for small tweaks