Most typical phrasing
“Now that this is wrapped, could you also send a couple of additional versions for our other channels?”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
The main deliverable has already been approved, but the client comes back asking for extra assets related to the project. Get a professional reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“Now that this is wrapped, could you also send a couple of additional versions for our other channels?”
Situation snapshot
The main deliverable has already been approved, but the client comes back asking for extra assets related to the project.
Reply goal
Prevent completed work from reopening as unpaid extra work.
Client message generator
Prevent completed work from reopening as unpaid extra work.
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
Prevent completed work from reopening as unpaid extra work.
How it sounds
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.
Next step
Stay helpful, but do not let approval become an excuse for unpaid expansion.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Now that this is wrapped, could you also send a couple of additional versions for our other channels?”
Other ways this shows up
“Since this is approved, can you also send a few extra assets off the back of it?”
“Can you add some extra versions now that the main deliverable is done?”
Reply playbook
Use this when the search intent is "client asks for more deliverables after signoff" and the client message matches this negotiation stage. It also covers searches like "post signoff extra deliverables client reply".
Step 1
The main deliverable has already been approved, but the client comes back asking for extra assets related to the project.
Step 2
Treat signoff as a real project boundary and make any additional deliverables a new scoped request.
Step 3
Stay helpful, but do not let approval become an excuse for unpaid expansion.
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
Treat signoff as a real project boundary and make any additional deliverables a new scoped request. 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.
Treat signoff as a real project boundary and make any additional deliverables a new scoped request.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Prevent completed work from reopening as unpaid extra work.
Client wants more revisions than agreed
The agreement includes a fixed number of revision rounds, but the client is now asking for more as if they are included.
Client assumes extra formats or versions are included
The original scope covers one core deliverable, but the client assumes alternate sizes, formats, or channel versions are included automatically.
Client expects ongoing support after the project ends
The project is ending, but the client is starting to treat you like open-ended support without a maintenance or retainer agreement.
Similar scripts for revisions, extra work, scope creep, and changing deliverables.
Similar scripts for revisions, extra work, scope creep, and changing deliverables.
Client wants more revisions than agreed
The agreement includes a fixed number of revision rounds, but the client is now asking for more as if they are included.
Client assumes extra formats or versions are included
The original scope covers one core deliverable, but the client assumes alternate sizes, formats, or channel versions are included automatically.
Client expects ongoing support after the project ends
The project is ending, but the client is starting to treat you like open-ended support without a maintenance or retainer agreement.