Most typical phrasing
“Can we also add one more page to this? It should be quick since we’re already doing the rest.”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
Use this scenario when a client casually asks for one more page after scope is already agreed. Get a reply that keeps the tone cooperative while making the change explicit and billable.
Start with 2 free drafts. No subscription required.
Typical client message
“Can we also add one more page to this? It should be quick since we’re already doing the rest.”
Situation snapshot
You already aligned on project scope and pricing, but before kickoff the client casually adds another page and treats it like a minor extra.
Reply goal
Acknowledge the request while making the scope change explicit and billable.
Client message generator
Generate a one-more-page reply that protects scope without making the project relationship tense.
Review the suggested approach and choose the response that best fits your client conversation.
Your polished reply will appear here
Generate a result to see the send-ready message, the reasoning behind it, and follow-up guidance if the client keeps pushing.
Why this works
What it protects
Acknowledge the request while making the scope change explicit and billable.
How it sounds
Happy to add that page. Since it sits outside the scope we already agreed, the clean options are to add it as an extra item, swap it with something currently included, or update the scope and budget so everything stays clear.
Next step
Offer a simple choice between keeping the current scope or updating scope and budget.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Can we also add one more page to this? It should be quick since we’re already doing the rest.”
Other ways this shows up
“Can we squeeze in one extra page while you’re already building this?”
“We just need one more page added. I assume that fits into the current scope.”
Reply playbook
Use this when the search intent is "client asks for one more page after scope agreed" and the client message matches this negotiation stage. It also covers searches like "extra page request client reply".
Step 1
You already aligned on project scope and pricing, but before kickoff the client casually adds another page and treats it like a minor extra.
Step 2
Name the additional deliverable clearly instead of absorbing it as a casual add-on.
Step 3
Offer a simple choice between keeping the current scope or updating scope and budget.
Concise
I can help with that. Since it changes the scope from what we originally discussed, the cleanest next step is to decide whether we keep the current scope, swap priorities, or update the budget for the added work.
Best for: Use when you need a short reply that keeps the thread moving.
Warm
That request makes sense, but it does sit outside the current agreement. I'm happy to map out the options so you can choose between keeping the current plan or expanding it with updated terms.
Best for: Use when you want to preserve trust while still keeping the boundary clear.
Firm
Name the additional deliverable clearly instead of absorbing it as a casual add-on. If the client wants a different path, make the tradeoff explicit before you continue.
Best for: Use when the client is repeating the pressure or treating the boundary as optional.
Name the additional deliverable clearly instead of absorbing it as a casual add-on.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Acknowledge the request while making the scope change explicit and billable.
Client asks for extra work outside the agreed scope
The work is already in motion, and the client wants something extra without clearly reopening budget or scope. You need to protect the boundary without sounding difficult.
How to say work is out of scope professionally
A client is asking for extra work outside the agreed scope, and you need a clear scope creep email that protects the boundary without sounding blunt.
Client keeps adding small requests
Each request is framed as minor, but the total is adding up. You need a reply that protects the project from death by a thousand extras.
Similar scripts for revisions, extra work, scope creep, and changing deliverables.
Similar scripts for revisions, extra work, scope creep, and changing deliverables.
Client asks for unlimited revisions
The client is pushing on revision policy before work starts or while terms are being clarified. You need a clear boundary that still feels cooperative.
Client keeps changing requirements
The moving target is starting to affect time, quality, and momentum. You need to slow the drift down without sounding inflexible.
How to say work is out of scope professionally
A client is asking for extra work outside the agreed scope, and you need a clear scope creep email that protects the boundary without sounding blunt.