How to Handle Website Client Revisions and Scope Creep

Local business clients rarely mean to abuse you. A restaurant owner sees the site, shows it to their cousin, and suddenly the menu page needs a new layout. Without limits written down, "small tweaks" quietly eat your profit. Here's how to handle it without losing the client.

1. Put revision limits in the proposal

Write the exact number of rounds in your proposal before any work starts: for example, "two rounds of revisions on the design, two on the built site." Vague phrases like "a few revisions" turn into arguments later. If you don't have a proposal template yet, see how to write a website proposal for a local business.

2. Define what one "round" means

A round is one consolidated list of feedback sent at one time. Ten separate texts over a week is not one round. Put that sentence in your proposal and repeat it when you send the first draft.

Ask for one point of contact

Small businesses often have the owner, a manager, and a spouse all weighing in. Ask the owner to collect everyone's notes and send them together. Agency folks on Reddit call this one of the most important fixes.

3. Get specific feedback, not "make it pop"

Ask clients to point at the exact element and say what they want it to do: be easier to read, make the phone number stand out, build trust. Feedback tied to a goal and a specific section produces fewer back-and-forth rounds.

4. Separate revisions from change requests

• Revision: change within the approved direction (swap a photo, reword a heading, adjust a color).
• Change request: new scope (an extra page, online booking nobody quoted, a new layout after sign-off).

Get a written "approved" at each stage. Once the design is signed off, reopening it is a change request.

5. Say "yes, here's the price" instead of "no"

When a request is out of scope, try: "Happy to do that. It's outside what we agreed, so here's a quick quote and how it affects the timeline." Or offer to ship the current site on time and do the new items as phase 2. That keeps the launch on schedule and often turns into ongoing work. A monthly maintenance plan is a natural home for the small edits that keep coming in after launch.

6. Keep the project organized

If you find clients with Locasly, move each business through the pipeline (Lead, Contacted, Proposal, Sold) so you know which ones have a signed proposal before you build. Locasly's AI website generator, or its copy-paste prompts for other AI builders, also makes the first draft fast, so your revision rounds go toward real feedback and not starting from scratch.

What Reddit users reported

• A web dev/design agency owner with over 12 years in the business said scope creep was worst early on and got better once they capped revision rounds, defined a round, and had clients use a single point of contact to consolidate feedback (r/agency).
• In a thread about a client who approved everything then asked for major content changes, one developer said they reply that the changes are billable and offer a change order: "Most pay." They now add a 30% buffer to every quote (r/webdev).
• In the same thread, another developer said every time they pushed back and charged, the relationship stayed fine; when they didn't, they ended up doing double the work for half the hourly rate (r/webdev).

FAQ

How many revisions should a small business website include?

Two rounds per stage (design, then build) is a common default. Use one for small, tightly defined jobs and three for bigger projects you've priced for it.

What if the client already approved the design and wants a redo?

Treat it as a change request: reference the approval, send a short quote and new timeline, or schedule it as phase 2 after launch.

Will charging for extra changes make clients angry?

Usually not if the limit was in the proposal from day one. Then it's a reminder, not a surprise.

Should I charge hourly or a flat price for extra changes?

Either works. Just quote it before you do the work, and get a yes in writing.