Scope Creep Reply Prompt

Sooner or later a client asks, "Can you just add one more thing?" The request is usually small and the client usually means well. But if you say yes for free every time, the project grows while the price stays the same. If you say a flat no, the client may feel brushed off. This page gives you a middle path and a prompt that writes the reply for you.

What a good reply does

A good scope creep reply does four things:

1. Thanks the client for the idea. The request often means they are engaged with the project, which is a good sign.
2. Names the original scope. Point back to what you both agreed on, briefly and without blame.
3. Offers a clear option. Either the new item becomes a paid add-on with a price and timeline, or it replaces something already in scope (a swap).
4. Makes the next step easy. Ask the client to confirm which option they prefer.

The tone matters as much as the content. Keep it warm and matter-of-fact. You are not refusing; you are explaining how the request fits into the project.

The prompt

Paste the client's message where shown, fill in the brackets, and run it in your AI assistant of choice.

My client sent me this message:
"""
[paste the client's message]
"""

Context:
- What we originally agreed on: [original scope]
- The new request is outside that scope.
- Add-on price I can offer: [$X]
- Extra time it would take: [time]
- Something in the current scope it could replace instead, if any: [item, or "none"]

Write a friendly reply that:
1. Thanks them for the idea.
2. Briefly explains that it falls outside the scope we agreed on.
3. Offers it as a paid add-on for [$X] with the extra time, and, if I listed an item, offers a swap as a second option.
4. Asks which option they would like.

Keep it under 100 words. Sound warm and professional, not defensive. Do not apologize repeatedly and do not invent any details.

Tips for using it

• Know your scope before you reply. If the original agreement was vague, the reply will be harder to write. For future projects, list deliverables and revision rounds in writing at the start.
• Decide the price first. Work out what the add-on is worth to you before you open the AI tool. Don't let the tool choose it.
• Small things can still be free. Sometimes a five-minute favor is worth doing to keep a good relationship. The point is that you choose, rather than letting the project drift.
• Reply soon. The longer you wait, the more it looks like the request is already accepted.
• Put the decision in writing. Once the client picks an option, confirm it in a short message so you both have a record.

Example of the structure

A reply built with this prompt might follow this shape: a thank-you line, one sentence that the request is outside the agreed pages, an offer to add it for a set price and a few extra days, an alternative to swap it for another item, and a question asking which they prefer. Short replies like this are easy for clients to answer, which keeps the project moving.

When to escalate

If a client keeps adding requests after you have explained the scope several times, it may be time for a call to reset expectations or a written change order. The prompt above handles the everyday cases; repeated scope creep is a conversation about the project as a whole.