ScopeProcessApprovalPricingFAQDone for youBlogToolsProtect a project →

Replies / one more small change

How to say no to "one more small change"

"Can you just make one more small change?"

The most dangerous word in freelancing is "just". One small change is fine. The problem is it is never one, and it always shows up after the work was approved.

Get the repliesLock your scope in Scopease, free

Why this is scope creep

  • Small changes stack. Five "quick" tweaks after sign off is a full extra revision round you never priced.
  • Every change after approval means re-checking, re-exporting and re-sending. The tweak is 10 minutes, the context switch is not.
  • If you say yes for free once, the next one is expected to be free too.

Copy-paste replies

Fill the [brackets] and send. Pick the tone that fits the client.

Firm

Hi [Name], happy to look at it. Quick heads up though: we wrapped the included revision rounds on [date], so anything from here is a change. Send me the full list of what you want adjusted in one message and I'll tell you what it costs and when it can be done.

Friendly

Hey [Name]! Totally get it, there's always one more thing once you see it live. I want to keep this tidy for both of us, so let's batch it: send me everything you'd like changed and I'll come back with one small quote. If it's genuinely a 5 minute fix I'll just tell you that too.

Yes, for a fee

Hi [Name], sure thing. This one is outside the approved scope, so here's a quick change order: [describe change], [X] hours at [rate], so [price] total. It adds [Y] days to delivery. Reply 'approved' and I'll start on it today.

The "yes, for a fee" reply works best when the scope was written down first. In Scopease the client approves the scope through one private link, every extra ask becomes a priced change order they approve or decline, and the invoice builds itself from approved work. Free for your first project.

Start freeHave us set it up for you ($79)

Questions

Is "Can you just make one more small change?" scope creep?

Yes, if it was not in the agreed scope. Small changes stack. Five "quick" tweaks after sign off is a full extra revision round you never priced. The fix is not a fight, it is a clear reply that points to the scope and offers a priced option.

How do I tell a client no more changes without sounding rude?

Point to the revision rounds you agreed on, say they are used up, and offer a priced option for anything else. You are not saying no to the client, you are saying no to doing it for free.

Should I ever do a small change for free?

Sometimes, on purpose. If you choose to, say it out loud: "This one is on me, anything after this goes on a change order." That way the freebie is a gift, not a precedent.

Free tools that help you say no

More ways to say no