Note from the archive: this began as an unfinished 2014 draft about client-services warning signs. I kept the original thesis and completed it as a short, practical piece rather than leaving the draft fragments in public.

Most of us aren’t trained negotiators. I know I’m not. But a little bit of that skill comes in handy when you’re discussing terms, prices, and expectations with clients. It’s hard to know when you’re being played. Sometimes it is subtle: a shift of control, a casual request that changes the project, or a small comment that tells you how the rest of the work is going to feel.

These are the red flags I’ve learned to notice.

Undercut

The first major red flag is being undercut. This is when the client chips away at your rate. It’s one thing to be told that your rates don’t fit within their budget and then discuss what would fit their needs and your time. It’s another thing for someone to suggest that you are charging too much as if your value is the problem.

What this translates into is: “you’re not worth that.” If that is the attitude at the beginning, I doubt that the ensuing project will be smooth. The truth is that they don’t value you, or they don’t understand your value.

I tend to walk away if someone flat out says that my rate is too high and I should be charging less. Typically that’s a client who will try to scrape every bit of your time and energy while they have you. Do the math: if you’re charging $1,000 for a project and work more than 40 hours, you’re earning less than $25 per hour. A client who intentionally undermines your value will usually take more time than you expect, turning that number into less by the minute.

Add-Ons

The next red flag is the person who keeps finding extra things for you to do while they have your attention. These are requests you haven’t agreed to and that sit beyond the scope of the project. They might ask you to proofread copy, redesign a logo, fix email templates, clean up analytics, or “just take a quick look” at something unrelated.

The request itself may be reasonable. The red flag is the assumption that it is already included.

Good clients understand that scope can change. Bad clients treat scope as an inconvenience. If something new matters, write it down, price it, schedule it, and make sure both sides understand what changes. If they resist that conversation, the problem is not the extra task. The problem is how they think your time works.

Copy Cat

Clients who ask for a carbon copy of someone else’s work usually aren’t asking for strategy. They’re asking you to skip the thinking. Inspiration is useful. References are useful. A request to clone another site, another brand, or another competitor’s exact interface is different.

That kind of request puts you in a bad position. It can create legal and ethical risk, but it also makes the work worse. You can’t solve a client’s problem by pretending they are someone else. Push the conversation toward what they like about the reference: the hierarchy, the tone, the density, the interaction, the clarity, the confidence. If they only want the copy, walk away.

Expenses and Access

Another warning sign is a client who won’t pay for necessary expenses or won’t provide access to the things the project depends on. Hosting, domains, type licenses, stock assets, plugins, software, testing devices, analytics access, content access: these are not little favors. They are part of the work.

If a project depends on a paid service, decide who owns it and who pays for it before you start. The best default is usually that the client owns the account and pays the vendor directly. That protects both sides. They keep control of their business infrastructure, and you are not quietly financing the project.

There Are Good People in the World

The point is not to become suspicious of everyone. Most clients are not trying to ruin your life. A lot of people simply don’t know how web projects work, what takes time, or how much ambiguity costs.

The best client relationships come from making the work explicit: what is included, what is not included, who owns what, how decisions get made, how feedback works, and what happens when the plan changes.

Red flags are useful because they tell you where to slow down. Sometimes that means walking away. Sometimes it means writing a better agreement. Sometimes it means having one awkward conversation early so the whole project does not become awkward later.