Example 1
“Can we include these extra pieces too even though they were not part of the original plan?”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
Pricing pressure scenario
When the agreement and the request no longer match, the reply should make that mismatch visible fast.
Paste your client messageStart here on this page
2 free drafts
Paste the client message and the original agreement details. FlowDockr will help you reply clearly when the request no longer matches what was agreed. Start with the exact message and generate without leaving this scenario page.
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.
These are the kinds of pushback messages this page is designed to help you answer.
Example 1
“Can we include these extra pieces too even though they were not part of the original plan?”
Example 2
“I thought this was all part of the same project anyway.”
Example 3
“This was not listed before, but I assume it is still covered?”
Use these scenario pages when you need the exact wording for a live client message, not just the pricing decision framework.
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 handle scope creep politely
The extra asks seem small on their own, but together they are stretching the project. You need a polite way to protect the boundary before it becomes the new baseline.
How to say no to extra work for free
The client wants more work without reopening scope or budget. You need to protect the project economics without making the reply feel hostile.
When to use: Use when the mismatch with the original agreement is straightforward.
Risk: If you only reference the agreement without options, the reply can feel like a dead stop.
Example wording: That would go beyond the scope we originally agreed, so the clean next step is either to keep the current scope or reopen the project around this added work.
When to use: Use when the client is blending the two together in one thread.
Risk: If the separation is not explicit enough, expectations remain muddy.
Example wording: I am treating this as a new request rather than part of the original deliverables, so I would scope it separately from the current agreement.
When to use: Use when you want the reply to move quickly into execution.
Risk: If the process sounds too heavy, the client may resist the structure rather than the actual tradeoff.
Example wording: If you want to include it, I can send a small scope update with timing and pricing so we can keep everything aligned before work expands further.
That request would go beyond the original agreement, so I would treat it as added scope rather than fold it into the current plan by default.
I am happy to look at it. Since it sits outside what we originally agreed, the cleanest path is to scope it separately so expectations stay clear on both sides.
This would be additional work beyond the agreed scope. If you want to include it, I would need to reopen scope, timing, and budget rather than treat it as already covered.
Most reply quality drops when freelancers concede or over-explain too early.
Restate that the request is beyond the original scope, then offer a clean path such as a revised quote, scope tradeoff, or a later phase.
Only after the new work is clearly separated from the old agreement. Otherwise the client may still see it as included.
Direct enough that the boundary is unmistakable, but calm enough that it still feels professional and collaborative.
Move to the next likely decision path instead of restarting from scratch.
Handle direct “more work than agreed” wording and route it into a clean scope-boundary response.
Trigger stage
mid project
Pressure type
scope boundary
Real risks
open scope creep, low margin trap, boundary erosion
Decision goals
set boundary, reduce scope, move to close
In scope
Out of scope
Paste the client message and the original agreement details. FlowDockr will help you reply clearly when the request no longer matches what was agreed.
Choose another pricing situation from the decision console.