FlowDockr
TemplatesScenariosMessage generatorPricing
Sign inGenerate message
FlowDockr

Client communication templates and professional message generator for payment reminders, scope creep, discount requests, and boundary-setting.

FlowDockr is a product of Auralis Labs LLC.

Digital SaaS only. Not legal, tax, investment, financial, debt settlement, lending, banking, or money transmission services.

Product

TemplatesGuidesClient message generatorToolsScenario hubPricingAbout

Use cases

Payment reminder templatesScope creep email templatesSay no to extra work for freeDiscount request templates

Legal

Terms of ServicePrivacy PolicyCookie PolicyRefund PolicyBusiness ComplianceContact

© 2026 Auralis Labs LLC. All rights reserved.

FlowDockr is a product of Auralis Labs LLC.

Optional analytics

FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.

  1. Home
  2. /
  3. Reply scenarios
  4. /
  5. How to say no to extra work for free
Scope and revision controlIn project

How to say no to extra work for free

Use this scenario when a client asks for extra work for free and you need to protect the project economics without sounding hostile or petty.

Generate a custom replyBrowse templates

Start with 2 free drafts. No subscription required.

Typical client message

“Can you include this extra part at no additional cost?”

Situation snapshot

Why this reply gets tricky

The client wants more work without reopening scope or budget. You need to protect the project economics without making the reply feel hostile.

Reply goal

Separate the extra request from the agreed work and explain that it needs its own scope, budget, or tradeoff.

Copy-ready templates

Start with wording you can send

Pick the closest version, copy it, then replace the names, invoice details, dates, scope notes, or client names before sending.

Polite no to unpaid extra work

I can help with that, but I would treat it as additional work rather than include it in the current fee. I can quote it separately or we can swap it against something already included.

Best for: Use when you want a firm boundary without closing the door.

Additional budget required

That addition is outside the agreed scope, so it would require additional budget. If you want to include it, I can send a quick estimate before moving forward.

Best for: Use when the request should become a paid add-on.

One-time courtesy boundary

I can include this small item as a one-time courtesy, but anything beyond this would need to be scoped separately so the project stays aligned.

Best for: Use only when you intentionally choose to make a small exception.

Client message generator

Paste the message or situation and draft the reply now

Copy a polite no-extra-work-for-free template or generate a custom client reply.

Message or situation
Paste the exact wording from the conversation and generate a stronger client message you can edit before sending.
2 free credits left
Generated guidance
Professional reply support for this situation

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

Separate the extra request from the agreed work and explain that it needs its own scope, budget, or tradeoff.

How it sounds

I can help with that, but I would treat it as additional work rather than fold it into the existing fee. The cleanest options are to add it as a separate item, swap it against something already included, or save it for a later phase.

Next step

If you choose to make a small exception, name it as one-time so it does not reset expectations.

Typical client message

These are the real wording patterns this scenario is built to handle.

Most typical phrasing

“Can you include this extra part at no additional cost?”

Other ways this shows up

“Can you just add this in for free?”

Reply playbook

What to do before you reply

Use this when a client asks for extra work without extra budget and you need a polite no that protects the project economics.

Use this when

  • The client asks to add work at no additional cost.
  • The request may sound small, but it changes scope, effort, or timeline.
  • You want to offer a paid add-on, scope swap, or later phase instead of absorbing it.

Do not use this for

  • A minor correction that is clearly inside the original brief.
  • A discount request where the deliverables have not changed.
  • A payment reminder or deposit issue.

What to do now

  1. Step 1

    Separate the extra from the included work

    Make it clear that you can help, but the request is additional work.

  2. Step 2

    Offer structured options

    Give the client a paid add-on, a swap within the current scope, or a later phase.

  3. Step 3

    Avoid making free work the baseline

    If you choose a courtesy exception, name it as one-time so it does not reset expectations.

Copy-ready tone options

Concise

I can help with that, but it would be additional work rather than part of the current fee.

Best for: Use when the request is straightforward.

Warm

I understand why that would be useful. Since it adds to the original scope, I would suggest we either quote it separately or trade it against another item.

Best for: Use when the client is reasonable and collaborative.

Firm

I cannot add extra work for free under the current agreement. If you want to include it, we need to update scope and budget first.

Best for: Use when the client is pressing for free work.

Wrong replies to avoid

  • !Saying yes because the request sounds small before checking the total effort.
  • !Using vague wording like "I will see what I can do" when the answer needs a boundary.
  • !Giving away custom work while calling it normal service.

Common questions

How do you say no to extra work for free?

Acknowledge the request, state that it is additional work, and offer a paid add-on or scope tradeoff.

Can I make a one-time exception?

Yes, but name it as a one-time courtesy so it does not become the new expectation.

What if the client says it will only take a minute?

Do not debate the minute count. Point back to scope, priority, and whether it replaces or adds to the agreed work.

Similar scenario, different move

Out of scope professionally

Use when the main challenge is saying the request is outside scope.

Reduce scope instead of lowering rate

Use when the client needs a smaller version rather than free additions.

Discount request

Use when the client is asking for a lower price rather than added work.

Related boundary-setting scenarios

Similar scripts for revisions, extra work, scope creep, and changing deliverables.

Similar scenarios

Close variants of this client conversation that need a similar kind of reply.

  • 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 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.

Next-step scenarios

If the boundary keeps getting tested, these are the next scope conversations likely to show up.

  • 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 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.

  • 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.