Verified against Claude · 2026-07-18
Say no to scope creep without sounding like you're punishing them for asking
Turn down an out-of-scope request politely and specifically — acknowledging the ask is reasonable, naming why it sits outside the agreement, and offering a real path to get it done instead of a flat no.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing an email that declines an out-of-scope request from a client, without damaging the relationship or sounding punitive.
Context:
- Agreed scope: Website redesign: homepage, services, contact page. 2 revision rounds.
- New request: Client is now asking us to also build an online booking system into the site
- Proposed path forward: Quote it separately as a $1,200 add-on, 2-week timeline
- Our business: Northline Studio
Task: Write an email that:
1. Acknowledges the request as reasonable to ask for — do not make the client feel wrong for raising it.
2. States specifically what part of the request falls outside the agreed scope, and why, referencing the original agreement rather than a vague "that's extra."
3. Proposes the concrete path forward from Quote it separately as a $1,200 add-on, 2-week timeline as the solution, not as a consolation prize.
4. Ends with one specific next step or question (e.g. "want me to send a quote for that?").
Tone: warm but plain — no passive-aggressive hedging ("just to clarify," "as per my last email"), no over-apologizing for having a scope in the first place.
Format: short email, 3 short paragraphs max.Customize the highlighted detailsoptional — the prompt above already works
Why this works
A flat "that's not in scope" reads as a rejection of the person, not the request, and tends to provoke an argument rather than resolve one. Separating "this is a reasonable thing to want" from "here's specifically why it sits outside what we agreed" reframes the boundary as a fact about the contract, not a judgment about the client for asking — that distinction is what keeps the conversation collaborative instead of defensive. Offering a concrete, priced path forward converts what could become a standoff into a sale: the client gets a way to get what they want, and you get paid for the extra work instead of quietly absorbing it to avoid an awkward conversation.
What you get back
Subject: Re: adding online booking Hi Alex, Good instinct — booking would be a great addition. Our current scope covers the homepage, services and contact pages with two rounds of revisions, so a booking system sits outside what we scoped and quoted. I can put together a separate quote for it — roughly $1,200 and a 2-week build, running alongside or after the current work, whichever you prefer. Want me to send that quote over? — Northline Studio
Verified against
Claude Sonnet 5 · 2026-07-18
ChatGPT GPT-5.1 · 2026-06-14
Changelog
- 2026-07-18 — Re-verified, no changes.
- 2026-06-14 — Added the explicit "acknowledge as reasonable" opening step after early drafts jumped straight to the boundary and read as defensive.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
