DIFFICULT CLIENT CONVERSATION SCRIPTS
How to Handle 4 Hard Conversations Professionally
=========================================================
Free template from SoloStack (https://solostack.madethis.app)
Full library of freelance business templates: $19/mo membership


─────────────────────────────────────────────────────────────
HOW TO USE THESE SCRIPTS
─────────────────────────────────────────────────────────────
These scripts work for email, Slack, or phone. Read them before
your conversation so you know what you want to say — then put
it in your own words. The goal isn't to read a script verbatim;
it's to feel prepared so you don't go silent or cave under
pressure. Each script includes what NOT to do as well.


═════════════════════════════════════════════════════════════
SCRIPT 1: "THAT'S OUT OF SCOPE"
How to Push Back Professionally on Scope Creep
═════════════════════════════════════════════════════════════

WHEN TO USE THIS:
A client asks for something that wasn't in the original agreement
— more pages, more features, extra rounds of revisions, a task
in a completely different category.

THE TRAP TO AVOID:
Don't say yes and secretly resent them. Don't say no and sound
defensive. Use the "Yes, and here's what that looks like" frame.

─────────────────────────────────────────────────────────────
EMAIL VERSION:

Subject: Re: [New Request]

Hi [Client Name],

Thanks for sending that over — [brief description of request]
sounds like a great addition.

I want to flag that this is outside the scope of our original
agreement, which covered [brief description of original scope].

I'm absolutely happy to include it! Here's what that looks like:

• Additional work: [describe what it involves]
• Additional fee: [$X] or [X hours at $Y/hour]
• Impact on timeline: [none / adds X days]

If you'd like to move forward, I'll put together a quick change
order. Your signature plus a 50% deposit and we'll get it on
the schedule.

Let me know how you'd like to proceed!

[Your Name]

─────────────────────────────────────────────────────────────
VERBAL / CALL VERSION:

"Hey — I saw your message about [new request]. Love the idea,
and I can definitely do that. I just want to make sure we're
on the same page: that's outside what we agreed on originally.
My original quote covered [X], so [new request] would be an
add-on. I can send you a quick change order for [$ amount].
Does that work?"

─────────────────────────────────────────────────────────────
WHAT NOT TO SAY:
• "I can just throw that in." (devalues your work)
• "That's not what we agreed to." (sounds adversarial)
• "I guess I can do it this time." (sets a bad precedent)


═════════════════════════════════════════════════════════════
SCRIPT 2: "I NEED YOU TO PAY BEFORE I CONTINUE"
How to Stop Work for Non-Payment
═════════════════════════════════════════════════════════════

WHEN TO USE THIS:
An invoice is overdue and you don't want to keep working without
getting paid. Or a client missed a milestone payment.

THE TRAP TO AVOID:
Keep working while sending polite reminders that get ignored.
Silence from a client on payment is a red flag — don't let it
slide past 2 follow-ups without pausing work.

─────────────────────────────────────────────────────────────
EMAIL VERSION (First pause):

Subject: [Project Name] — Payment Needed to Continue

Hi [Client Name],

I wanted to follow up on Invoice #[X] for $[amount], which was
due on [date] and remains unpaid.

I've loved working on this project and want to keep momentum
going. To do that, I'll need to receive payment before I
continue with the next phase.

Once payment is confirmed, I'll get straight back to work and
we can keep to our original timeline.

Payment link: [link]
Due: As soon as possible to avoid further delays.

If there's an issue with the invoice or the payment method,
just reply here and we'll sort it out.

Thank you,
[Your Name]

─────────────────────────────────────────────────────────────
VERBAL / CALL VERSION:

"Hey [Name], I wanted to check in about the invoice I sent on
[date]. I haven't received payment yet, and I need to pause work
until it's cleared. I don't want this to affect our timeline,
so if we can get that resolved today or tomorrow, I can jump
right back in. Is there anything on your end causing a delay?"

─────────────────────────────────────────────────────────────
WHAT NOT TO SAY:
• "No worries, take your time." (it IS a problem)
• "I know things are busy..." (don't excuse it for them)
• "I'll keep working and you can pay when you can." (don't)


═════════════════════════════════════════════════════════════
SCRIPT 3: "I CAN'T MEET THIS DEADLINE"
How to Communicate a Delay Before It Becomes a Crisis
═════════════════════════════════════════════════════════════

WHEN TO USE THIS:
You realize you won't hit a deadline — whether because you
underestimated the work, something came up, or the project grew.
The rule: tell the client as soon as you know. Every day you
wait makes the conversation harder.

THE TRAP TO AVOID:
Going silent and hoping you can make up the time. You can't.
Silence makes it worse. A client who knows early can adjust.
A client who finds out the day of will remember it forever.

─────────────────────────────────────────────────────────────
EMAIL VERSION:

Subject: [Project Name] — Update on Our Timeline

Hi [Client Name],

I need to give you a heads-up: I'm not going to hit our deadline
of [date] for [deliverable].

Here's what happened: [one honest sentence — no over-explaining].

My revised timeline:
• [Deliverable]: [new date]
• Final delivery: [new date]

I'm sorry for the disruption to your plans. I should have
flagged this sooner. Here's what I'm doing to make sure we
land this cleanly: [one sentence on your plan].

If this creates a problem on your end, please tell me — I'd
rather know now so we can figure out a solution together.

[Your Name]

─────────────────────────────────────────────────────────────
VERBAL / CALL VERSION:

"I need to be straight with you about something. I'm not going
to make [date] for [deliverable]. [One-sentence reason.] I
wanted to tell you as soon as I knew rather than wait until the
deadline and surprise you. My revised date is [date]. I know
that may affect your plans — what's the impact on your end and
how can I help minimize it?"

─────────────────────────────────────────────────────────────
WHAT NOT TO SAY:
• "I'm almost done — just a little more time." (vague)
• "It's your fault for changing the scope." (blame never helps)
• [Saying nothing and hoping you can make it up — don't]


═════════════════════════════════════════════════════════════
SCRIPT 4: "I NEED TO END THIS PROJECT"
How to Exit a Project Professionally
═════════════════════════════════════════════════════════════

WHEN TO USE THIS:
• The project has become untenable (constant scope changes,
  non-payment, disrespectful behavior, impossible expectations)
• The client relationship isn't working
• Your circumstances have changed and you can't continue

THE TRAP TO AVOID:
Ghosting. Ending without notice. Or staying in a toxic project
because you feel guilty. A clean, professional exit is always
better for both parties.

─────────────────────────────────────────────────────────────
EMAIL VERSION:

Subject: [Project Name] — Important Update

Hi [Client Name],

I've given this a lot of thought, and I've made the decision to
step back from this project.

[Choose the reason that fits — keep it brief and non-blaming:]

Option A (scope/fit): "The project has evolved beyond what I can
deliver to the standard you deserve, and I don't think I'm the
right fit for where it needs to go."

Option B (workload/capacity): "I've had a significant change in
my workload and I can't give this the attention it deserves."

Option C (non-payment/conduct — firmer): "Despite several
attempts to resolve the outstanding payment / communication
issues, we haven't been able to reach a workable arrangement."

Here's where we currently stand:
• Completed work: [list what's been done]
• I'll deliver all completed files by [date]
• Outstanding amount for completed work: [$X] [if applicable]

I'll send over everything that's been completed so you can
hand it off to another professional without losing the work.

I wish you all the best with the project.

[Your Name]

─────────────────────────────────────────────────────────────
WHAT NOT TO SAY:
• "You're impossible to work with." (even if true)
• "I should never have taken this project." (unhelpful)
• [Disappearing without notice — never do this]

─────────────────────────────────────────────────────────────
AFTER THE CONVERSATION:

1. Deliver everything that's been completed, organized clearly
2. Send any outstanding invoices for work already done
3. Don't badmouth the client publicly (even if warranted)
4. Document what happened for your own records
5. Review your contracts and onboarding process — what could
   have caught this earlier?

─────────────────────────────────────────────────────────────
Want all your freelance business templates in one place?
SoloStack membership: $19/mo | https://solostack.madethis.app
50+ templates: contracts, proposals, SOPs, invoices, and more.
─────────────────────────────────────────────────────────────