Tech With Galvan
Back to Articles
FreelancingJun 26, 2028 • 4 min read

How to Say No to Extra Work Politely (Scripts + Templates)

Say no to scope creep politely — scripts, templates, and strategies for declining extra work without losing clients. Professional pushback guide.

Galvan
Galvan

Founder & Creator

Introduction

Saying “no” is the hardest part of freelancing. You want to please the client, but saying yes to everything leads to burnout, scope creep, and resentment. The secret: you don’t say no — you say “yes, but…”

This post gives you scripts and strategies for declining extra work while keeping the client happy.

The “yes, but…” framework

Instead of “No, that’s not in scope,” say:

“Yes, I can do that! It’s outside our current scope, so here are the options…”

This reframes the conversation from “no” to “how.” The client feels heard, and you maintain boundaries.

5 scenarios and scripts

Scenario 1: “Can you add one more page?”

Client: “The website looks great! Can you also add a blog section?”

Script:

“I’m glad you like it! A blog section would be a great addition. It’s not included in our current scope, but I can add it for ₹[amount] with an additional [X] days. Would you like me to proceed, or should we save it for Phase 2?”

Why it works: Acknowledges the idea, states it’s extra, gives options, and asks for a decision.

Scenario 2: “Can you change the color scheme?”

Client: “Actually, can we try a blue theme instead of green?”

Script:

“Sure! I can create a blue version for you. Since we’ve already finalized the green design, this would be an additional revision round. I can do it for ₹[amount] or include it in your remaining revision round if you’d prefer. What works best?”

Why it works: Offers the change but frames it as a revision (limited) or paid extra.

Scenario 3: “Can you make it work on mobile too?”

Client: “Oh, I assumed it would work on phones too.”

Script:

“Absolutely — mobile optimization is important! It wasn’t included in the original scope, so let me provide a quote. Mobile-responsive design for [X] pages would be ₹[amount] and add [X] days to the timeline. Shall I send over a formal quote?”

Why it works: Clarifies the misunderstanding, explains the cost, and offers to proceed.

Scenario 4: “Can you integrate with our CRM?”

Client: “Can you connect this form to our Salesforce account?”

Script:

“That’s a great idea for streamlining your workflow! CRM integration is outside our current scope, but I can add it. The integration would involve [brief technical explanation] and cost approximately ₹[amount]. Would you like me to include this as an add-on?”

Why it works: Explains why it’s extra (technical complexity) and offers a clear price.

Scenario 5: “Can you do this by tomorrow?”

Client: “We need this done by tomorrow for a presentation.”

Script:

“I’d love to help! My standard turnaround is [X] days, but I can expedite this. A rush delivery (24-48 hours) would be ₹[amount] with a 50% rush fee. I can also deliver a partial version by tomorrow and the rest by [date]. Which option works for you?”

Why it works: Offers options instead of a flat no. The rush fee compensates for the disruption.

The “not now, but later” approach

If the client can’t afford the extra work now:

“I understand budget is tight right now. I can note this as a Phase 2 enhancement and we can revisit it after the current project launches. I’ll send you a separate quote for Phase 2.”

This keeps the door open without giving free work.

Setting boundaries upfront

The best way to handle scope creep is to prevent it. Set boundaries in your contract and proposal:

In your proposal

### Scope
Included: [specific deliverables]
NOT included: [explicit exclusions]
Additional work: ₹[rate]/hour or ₹[rate]/feature

In your contract

"Any work beyond the agreed scope requires a written change request
and approval before work begins. Additional work is billed separately."

In your onboarding email

“Just a note on scope: if you need anything beyond what’s in the proposal, just let me know and I’ll provide a quote. I want to make sure we’re always on the same page!”

Common phrases to avoid

Don’t say Say instead
“That’s not in scope” “That’s a great idea! It’s outside our current scope, but I can add it for ₹X.”
“No, I can’t do that” “I can do that as an add-on. Here’s the cost and timeline.”
“That will cost extra” “I’d be happy to include that. It would be ₹X as an additional feature.”
“You’re asking for too much” “I want to make sure we deliver quality. Let’s prioritize and tackle the most important items first.”
“I don’t have time” “My current schedule is full until [date]. I can start this on [date] or refer you to a colleague.”

The “prioritize” technique

When clients ask for multiple additions, help them prioritize:

“I can see you’d like [Feature A], [Feature B], and [Feature C]. To keep the project on budget and on time, I’d recommend we focus on [A and B] for this phase and save [C] for Phase 2. Does that work?”

This shows you’re helpful while maintaining boundaries.

Common mistakes

  • Saying yes to everything — you’ll burn out and resent the client
  • Not having a change request process — ad-hoc changes lead to disputes
  • Being passive-aggressive — “Well, that’s not in the scope, but I guess I can…” is worse than a clear no
  • Not documenting — if you agree to extra work verbally, it’s forgotten. Always confirm in writing.
  • Apologizing for boundaries — “I’m sorry, but…” signals weakness. Be confident: “I’d be happy to add that as an add-on.”

Key Concepts

  • Scope creep = work beyond what was agreed
  • Change request = formal process for adding scope
  • “Yes, but…” = acknowledge the request, then state the cost
  • Phase 2 = deferred work for a future project
  • Add-on = extra service billed separately

What to Try Next

FAQ

What if the client gets angry when I push back?

Stay calm and professional: “I want to make sure we deliver exactly what was agreed. If you’d like to add [feature], I’m happy to provide a quote. My goal is to deliver great work within the agreed scope.” If they’re consistently unreasonable, consider whether this client is worth keeping.

How do I handle “just one small thing” requests?

Acknowledge and assess: “I can look into that. If it takes under 30 minutes, I’ll include it as a courtesy. If it’s more involved, I’ll let you know the cost before proceeding.” This sets a clear threshold.

Should I ever do free work beyond scope?

Only if it’s truly trivial (under 15 minutes) and you choose to. Never make it a habit. If you do free work, frame it as a one-time courtesy: “I’ll include this as a courtesy this time, but going forward, additional changes will be billed separately.” See Handle Scope Creep.