Every bad client you've ever had gave you warning signs in the first 10 minutes. You ignored them because the lead looked close to signing, or because the month was slow, or because the client promised referrals.
The red flags below are the ones that, in hindsight, predicted every single miserable project I've seen agencies take on. Individually they're yellow. When two or more show up together, they're red — walk away.
This is the companion to our 60-second qualification framework, which covers how to triage cold leads fast. That post is about finding the right "yes." This one is about recognizing the wrong "yes" early enough to say no.
Red flag #1: "How much is a website?" before they've told you anything
A prospect who asks for a price before you've learned their business has already decided you're a commodity. They're collecting quotes. Whoever wins the contract wins on price, not fit.
What to do: Don't quote. Ask them to book a 20-minute call so you can scope it properly. If they refuse, they weren't going to be a real client — they were shopping. Let them go.
Yellow, not red: They ask for a ballpark. Ballparks are fine and signal they're prequalifying you. "Most of our rebuilds come in between $4-8K" answers that without committing.
Red flag #2: They've "tried 3 web designers" and none worked out
You're about to become the fourth person they fire. It might genuinely be the case that the first three were unqualified, but the base rate is: the client is the problem. Chronic firer clients have unrealistic expectations, vague briefs, or simply don't know what they want — and they blame the last vendor for it.
What to do: Ask them what specifically went wrong with the last three. If the answers are structural (scope creep, missed deadlines, communication gaps), these are solvable and you can pitch a process that avoids them. If the answers are vague ("they just didn't get it"), you will also not "get it." Walk.
Red flag #3: "We just need a quick refresh"
"Quick" is almost always a scope lie. The client wants a new site but is trying to price-anchor you by calling it small. By the end of week one you'll have negotiated sitemap changes, a new blog template, and integration with a CRM that didn't exist in the original brief.
What to do: Reply literally: "Great — for a true refresh (new colors, updated photos, minor copy changes on existing pages) we'd be around $1,500. For anything that touches structure, copy architecture, or new page types, it's a different project." The number usually ends the conversation, which is the goal.
Yellow: They know it's actually a rebuild and are just using "refresh" as shorthand for "not starting from zero." Listen for whether they correct themselves when you probe.
Red flag #4: They describe the new site in excruciating visual detail on the first call
The prospect who opens with "I want it to look like Apple but with more personality, a video in the hero, a testimonial rotator, parallax scrolling, and maybe something like what Stripe does with the gradient" is not hiring a designer — they're hiring an executor for their pre-existing vision. You'll end up building what they describe, they'll dislike it, and they'll blame you for following their instructions.
What to do: Redirect. "These are interesting references. Can you tell me what your business actually needs the site to do? I'd rather design for outcomes and use those references as vibe inputs than start from a pixel brief." Prospects who can redirect to outcomes are good leads. Prospects who double down on the pixel brief are telling you the project is about control, not results.
Red flag #5: The budget is mentioned in hundreds, not thousands
"We have about $500 to work with" is not a negotiating opener. That's their actual ceiling. You cannot rebuild a real website for $500 and do it well. Any conversation from this starting point is going to end in either scope starvation or you working at minimum wage.
What to do: Be blunt: "I wouldn't be able to deliver something that moves your business at that budget. The realistic floor for a real rebuild is around $3K, and that's stripped down. If that's above your range right now, totally fair — happy to point you at options that might fit better." No follow-up, no pitch, no proposal. The prospect either finds more budget or doesn't.
Red flag #6: "We need it live by [aggressive deadline]"
Urgency that's not your fault is someone else's planning failure. The prospect missed a launch window, got dropped by their previous vendor, or has an event coming up and expects you to drop everything. Rush projects compress timelines but rarely compress payment — and they always compress your quality.
What to do: Quote 1.5-2x your normal price and name the specific rush constraint. If they want normal pricing, the project must follow your normal timeline. Most clients won't accept the rush premium and will magically discover the deadline is flexible. Great — now you have a normal project.
Red flag #7: They're in a category where web design rarely pays
Some businesses run on referrals or B2B contracts where the website is irrelevant. A solo divorce attorney who gets every new case from other attorneys, a specialty manufacturer whose one buyer renews annually, a plumber whose entire customer base is three property management companies — none of these businesses will grow from a new site, no matter how good you make it.
What to do: Ask on the first call: "How do your best new customers find you right now?" If the answer doesn't involve the website, Google, or inbound of any kind, gracefully disengage. You're not their bottleneck.
Red flag #8: Multiple decision-makers who visibly disagree
On the discovery call there's the owner, the owner's spouse, the marketing person, and maybe a cousin who "knows web stuff." They talk over each other. Nobody's in charge. This project will be designed by committee, re-designed by committee, and eventually abandoned by committee — with you delivering every round for free between the disagreements.
What to do: Before proposal, name the decision-maker in writing: "For the proposal to land on the right desk, can you confirm who the final sign-off is on design direction?" If the answer is "well, we'll all look at it together," charge a 50% non-refundable retainer upfront. Most projects don't survive that filter, which is what you want.
Red flag #9: They ask you to sign an NDA before you've seen anything
Real NDAs happen when you're about to see a specific confidential asset (a financial model, an unreleased product, proprietary data). Pre-proposal NDAs for a local business website are almost always a sign the prospect doesn't understand how vendor relationships work and will treat every request as an imposition.
What to do: Sign simple mutual NDAs without friction. Refuse one-sided NDAs that demand indemnification, IP assignment, or five-year non-competes. If they refuse to reciprocate, walk — this behavior gets worse, not better, after they pay.
Red flag #10: "Can you match the price of this freelancer I found on Upwork?"
You can't. You shouldn't try. The prospect has already told you they see your work as interchangeable with the cheapest bid they can find. No matter how much you over-deliver, they will remember what they could have paid instead.
What to do: Say it plainly: "I can't match that, and I'd rather be honest about why. At $500-1000 you're hiring someone to assemble a template. At $5K you're hiring someone to think about what the site needs to do for your business and design around that. If the template route is what you need right now, it's a legitimate choice — just a different one." Most prospects who hear that calibrate. The ones who don't weren't yours to win.
The "two yellow flags" rule
A single yellow flag is almost never a reason to walk. Good clients have weird requests, messy brief calls, and occasional tight deadlines. Life happens.
But when two yellow flags show up on the same lead — say, they want a "quick refresh" and they've fired three previous designers — you're looking at a pattern. Patterns don't improve after contracts are signed; they get worse. Two yellows = one red. Don't take the project.
How to walk away politely
Declining a lead is a skill. Done badly, it burns referrals and creates lasting resentment. Done well, it protects your quarter without closing the door — and occasionally the prospect returns six months later with a realistic budget, because they remember you as the one who was honest with them.
The template:
Thanks for the details — I want to be upfront that I don't think we're the right fit for this one, and I'd rather say so now than take on a project that won't land well for either of us. [Specific reason, one line.] If anything changes on your end down the line, I'd be happy to reconnect. In the meantime, [name of a lower-price alternative, or "Upwork" or "99designs"] might be a faster route to what you need right now.
You're not selling. You're not apologizing. You're not ghosting. You're naming the mismatch, pointing them elsewhere, and moving on. Prospects respect this more than a half-hearted pitch that you both know isn't going to work.
Related reading
- How to qualify a web design lead in 60 seconds — the 4-question triage
- Finding high-intent web design leads on Google Maps — sourcing quality leads in the first place
- Handling the 5 most common objections — what to do when the lead IS qualified and just needs working through