How to Handle the Client Message: “Can We Make One Small Change?”

Christian Hossu — Tue, 15 Sep 2026 20:34:59 +0000

If you freelance long enough, you eventually get this message:

“Can we make one small change?”

Sometimes it really is small.

Other times, that sentence quietly becomes another revision round, an extra hour of work, or a change that was never part of the original agreement.

The difficult part isn't saying “yes” or “no.”

It's figuring out what kind of request you're actually looking at before you reply.

The 3-question check

Before answering the client, I use three questions.

1. Is this already inside the agreed scope?

Go back to what was actually agreed.

If the requested change is clearly included, it usually makes sense to handle it without turning it into a negotiation.

But if you're already thinking:

“Technically, we never agreed to this…”

that's a signal to stop and check before automatically saying yes.

2. Does it change the amount or type of work?

A request can sound tiny while changing the project substantially.

For example:

changing a headline = probably small
redesigning the whole hero section = not the same thing
correcting a typo = small
adding another page = new work
adjusting an existing component = maybe included
building a completely different version = probably not

The client's wording doesn't determine the size of the request.

The work required does.

3. What should I say next?

Once you know what kind of request it is, the reply becomes much easier.

If it's genuinely included

You can simply say:

Absolutely — that's within what we agreed, so I'll include it in the next update.

If you're not sure

Don't commit immediately.

Try:

Happy to take a look. Let me check how that fits with the current scope and I'll confirm before I change anything.

That gives you time to think without making the conversation awkward.

If it's clearly additional work

You don't need to make it confrontational.

Something like this works:

We can definitely do that. It's outside the original scope, so I'll treat it as an additional change and confirm the cost/time before starting.

The important part is that you haven't said no.

You've simply separated the original project from the new request.

Why this matters

Scope creep usually doesn't begin with a huge unreasonable demand.

It happens through a series of requests that each feel too small to challenge.

One change becomes three.

Three become ten.

And suddenly you're doing substantially more work for the original price.

Having a simple decision process removes some of the emotion from the situation.

Instead of asking:

“Am I being difficult if I charge for this?”

you ask:

“Was this work actually included?”

That's a much easier question to answer.

I turned this framework into a small free checklist with example responses for different situations.

No email signup or account required:

https://luxuriant-barometer-6bf.notion.site/FREE-SAMPLE-The-Small-Change-Check-3d7466309b8f81d885d8fe0f7ba4cb16

I'm curious how other freelancers handle this:

What's the innocent-sounding client request that most often turns into much more work for you?

DEV Community: Christian Hossu