Back to red flag patterns

Client phrase pattern

"Should Be Simple" — The Phrase That Predicts Rate Pressure

Sometimes clients are right. Some tasks genuinely are simple. The client is trying to calibrate expectations — they want you to know they're not asking for something complex.

Important: this phrase does not prove a client is bad. It is a signal to pause before replying, clarify the missing details, and avoid committing inside an unclear project.

The phrase

"Should be simple" / "It's pretty straightforward" / "Shouldn't take long" / "Simple task for someone with your experience" / "Basic stuff."

Why it sounds harmless

Sometimes clients are right. Some tasks genuinely are simple. The client is trying to calibrate expectations — they want you to know they're not asking for something complex.

The problem isn't the assessment. It's what happens when the work turns out to be harder than "simple."

What it actually signals

The client has pre-decided what your time is worth.

"Should be simple" is not a description of the work — it's a statement about the rate the client thinks is appropriate. They've decided the work is easy, which means they've decided it shouldn't cost much. Your quote will be measured against that expectation, not against the actual scope.

It creates a ceiling before the conversation starts.

When you quote a fair rate for work the client has called simple, you're already in a defensive position. "But I thought it was a simple task?" — that's the negotiation you're walking into.

It predicts scope surprise.

Clients who call work simple have almost always underestimated it. When the project turns out to be more complex — and it usually does — they'll be surprised by the time it takes. That surprise becomes friction: on revisions, on timelines, on the final invoice.

The compound risk

  • "Should be simple" + "quick project" → double devaluation, the client has pre-decided both complexity and time
  • "Should be simple" + "budget TBD" → rate pressure with no floor
  • "Should be simple" + "unlimited revisions" → open-ended commitment on work the client thinks is trivial
  • "Should be simple" + "my cousin could do this" → explicit devaluation, the client is comparing you to free

What to do

Don't accept the framing. Define the scope on your terms:

"Happy to take a look. Once I understand the full requirements, I can give you an accurate estimate — complexity is usually clearer once the details are mapped out."

Then quote based on the actual work, not the client's characterization of it. If they push back on the rate because "it should be simple," you have the scope document to reference.

Scan the full message

"Should be simple" is rarely the only signal. Paste the full message into FreelancerGuard and see what else is there.

Scan this client message →

Scan the full client message

This phrase matters more when it combines with urgency, vague deliverables, missing budget, or pressure to start. Paste the full message to see the complete risk pattern.

Check a client message free

Related patterns