Memorisely
Design Business

How to stop scope creep politely

Protect the project without damaging the relationship.

Zander Whitehurst

7 min read

Scope creep rarely arrives as one big request. It shows up as a series of small, reasonable sounding asks. "Could you just add a quick page for this?" "While you are in there, could you tweak the logo?" Each one feels too small to push back on, and together they can quietly double the size of a project.

I used to say yes to everything. I thought it made me look generous and easy to work with. What it actually made me was tired, behind schedule and resentful about a project I had been genuinely excited about. The client was not being unreasonable. I simply never told them where the edges were.

Define the scope clearly at the start

The best defence against scope creep is a clear scope in the first place. Your proposal should say exactly what is included, and just as importantly, what is not.

  • The specific deliverables and how many of each
  • The number of feedback rounds included
  • The timeline and key milestones
  • A short list of things that are out of scope

That last list feels awkward to write, but it saves countless awkward conversations later.

A scope that names what is out, not just what is in, gives you something to point back to.

Explain the scope during kickoff

Do not assume the client has read every line of your proposal. Most people skim. During the kickoff call, walk through what is included and how you will handle new requests.

When you set this expectation early and calmly, raising it later feels like following an agreed process rather than being difficult.

Recognise creep when it happens

Scope creep is easier to manage when you spot it early. Watch for phrases like "just", "quick", "small" and "while you are at it". These words often disguise new work.

It also helps to ask yourself one simple question: was this in the original agreement? If the answer is no, it is new scope, no matter how small it sounds.

Acknowledge the request positively

When a client asks for something extra, start with genuine enthusiasm. They are usually asking because they are invested in the project, which is a good thing.

Something like "That is a great idea and I can see why it would help" keeps the conversation warm. You are not saying no to them. You are working out how to fit their idea in properly.

Offer clear options

Instead of a flat yes or no, give the client choices. I usually offer three:

  • Add it to this project with an updated cost and timeline
  • Swap it for something already in scope
  • Park it for a second phase after launch

Options put the client in control and make the trade offs visible. Most people are perfectly reasonable once they can see what a request actually costs.

Three clear options turn an awkward yes or no into a choice the client controls.

Put changes in writing

Whenever scope changes, confirm it in writing. A short email or a simple change request is enough. Describe the new work, the cost and any impact on the timeline, and ask the client to approve it before you start.

This protects both of you. Memories get fuzzy, and nobody wants to argue in month three about what was agreed in a call in month one.

A short written change request covers the work, the cost and the timeline before anything starts.

Price your changes fairly

Have a simple way to price extra work so you are not inventing numbers on the spot. A day rate or a set price for common additions works well.

I once did an entire extra landing page for free because I felt too awkward to quote for it. The client did not even realise it was extra. They would have happily paid. The only person who lost out was me, and my weekend.

Use phases to your advantage

Some of the best ideas appear halfway through a project. Rather than squeezing them in, create a "phase two" list together. It shows you are listening, keeps the current project on track and often turns into your next piece of paid work.

Clients like knowing their ideas have a home, even if that home is not this month.

Be kind but consistent

The goal is not to be rigid. Sometimes a tiny favour is the right thing to do for a great client. The key is choosing to do it deliberately, and saying so, rather than drifting into it.

Something like "This one is on me, but anything further would be a change request" keeps goodwill high and sets a clear line for next time.

Start with your next proposal

Before you send your next proposal, add an "out of scope" section and a sentence explaining how you handle new requests. Then practise saying "That is a great idea, here are a few ways we could fit it in." It feels strange the first time and completely normal by the third. We cover proposals, pricing and client conversations like this in our Build Your Design Business Bootcamp.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all