If you build websites for clients, you know the feeling. The project is 95% done, and you get the email: "Could we just add a quick careers page? Oh, and maybe a small integration with our CRM? Should be quick!"
It's never quick. But saying "No" feels confrontational, and saying "Yes" eats into your margin until you're working for below minimum wage.
The "One More Thing" Trap
The problem isn't the client asking. The problem is that freelance web designers usually respond with a paragraph of text explaining why it's hard.
Clients don't read paragraphs. They read prices and timelines.
How to standardize scope changes
Next time a client asks for something out of scope, don't write an essay. Put the request through a structured filter and offer them one of five explicit choices:
- Included: It's genuinely tiny. Do it, but document that you did it for free so it holds value.
- Price: "Yes, we can add that CRM integration. It will add $850 to the budget and push launch back by 4 days. Let me know if you want to proceed."
- Swap: "We can add the careers page, but to keep the launch date and budget the same, we'll need to drop the custom team-member illustrations."
- Park: "Great idea. Let's put this in the 'Phase 2' backlog and tackle it right after we launch Phase 1."
- Decline: "This requires a custom backend we don't specialize in. I recommend bringing in a dedicated backend dev for this."
Standardize your response
When you remove the emotion and present choices, clients respect the boundary. They usually choose "Park" or happily pay the "Price".
If you struggle with wording these emails or estimating the impact of a request, I've put together a structured workbook and offline calculator to handle exactly this.
You can grab the Scope Change Control Kit for Web Designers on my Gumroad here: https://gridquill.gumroad.com/l/scope-change-control-kit-web-designers
It includes the offline calculator, copy-ready client messages for all five scenarios, and a reusable request log. Stop working for free, and start getting paid for your expertise.
Top comments (2)
Logging the requests in the client's exact words is the crucial detail here. It completely removes the "that's not what I meant" debate when reviewing the list later.
The empty Phase 2 bucket in the initial proposal works for the same reason—it gives the client a designated holding area they already agreed to rather than feeling like their idea got rejected. Documenting the zero-cost concessions also creates an audit trail that makes future scope boundaries self-explanatory instead of adversarial.
The five-option filter is the part most scope-creep advice misses — clients aren't hostile, they just can't price their own request. One thing that made this stick for me: I log every out-of-scope ask in a single running list with three fields — date, request in the client's own words, and which of the five outcomes it got. By week four you can show the client "here are the 9 requests, 4 were free, 3 were parked, 2 were paid," and the boundary stops feeling personal because it's visibly consistent. I also stopped answering these same-day; a 24-hour delay before quoting kills the reflex to say yes and gives you time to check the real hours. The other cheap win is naming Phase 2 in the original proposal, even if it's empty — then "Park" isn't a rejection, it's a slot the client already agreed exists. And documenting the free ones matters more than people think, because that's the evidence you point at when a renewal conversation turns into a rate conversation.