Path 1: Clarify what's included
When to use: Use when the client may simply not realize the request is outside the original agreement.
- State current scope clearly
- Keep the tone non-accusatory
- Reset the frame early
Pricing decision
Use before replying
Protect the project boundary before 'just one more thing' becomes a new scope.
Draft a reply for this situationStart here on this page
2 free drafts
Paste the extra request and your original scope. Flowdockr will help you respond clearly without sounding defensive or opening the door to unpaid work. Start with the exact message, add your quote or scope context, choose the tone, and generate without leaving this scenario page.
Start with the real client message
Paste the prospect's wording, add your quote or scope context, and generate a reply tuned for this pricing situation.
Review the suggested approach and choose the response that best fits your client conversation.
The client wants additional work, revisions, or deliverables without changing the budget. This is where pricing pressure starts to merge with scope creep.
When to use: Use when the client may simply not realize the request is outside the original agreement.
When to use: Use when the new request clearly changes the workload or deliverables.
When to use: Use when you want to preserve the relationship without absorbing all the additional work now.
Happy to help. That request would sit outside the current scope, so I can either quote it separately or suggest a lighter adjustment to fit the existing budget.
Why this works: Use this when you want to acknowledge the objection quickly and test whether budget is the real blocker.
I'm glad to support the direction you're aiming for. Since this would add to the original scope, the cleanest option is either to quote the extra work separately or reshape priorities within the current budget.
Why this works: Use this when you want to preserve trust while still holding the line on the original pricing logic.
That request goes beyond the scope covered in the current pricing. I'm happy to add it, but it would need either a revised quote or a change in deliverables elsewhere.
Why this works: Use this when you need to reset boundaries clearly and move the conversation toward scope trade-offs instead of discounts.
Do not frame it as a personal refusal. Frame it as a scope boundary and explain that new work needs either a revised quote or a reshaped set of priorities.
As soon as the new request changes workload, time, or deliverables in a meaningful way, it should be treated as a scope change rather than a favor.
Small additions are exactly how scope creep starts. Clarify whether it truly fits inside the existing agreement before you say yes.
Move to the next decision state instead of dropping into generic related posts.
Paste the extra request and your original scope. Flowdockr will help you respond clearly without sounding defensive or opening the door to unpaid work.
Choose another pricing situation from the decision console.