====================================================== DIFFICULT CLIENT SCRIPTS & RESPONSES SoloStack — solostack.madethis.app Free resource. No signup required. ====================================================== 15 word-for-word scripts across 5 situations. Copy, paste, and adapt. Tone notes and de-escalation variations included. ------------------------------------------------------ SITUATION 1: SCOPE CREEP ------------------------------------------------------ SCRIPT 1A — Scope Creep: First Request (Neutral) Situation: Client asks for something small but outside original scope. Hi [Name], I'd love to add that — it sounds like a useful addition. Since it falls outside our original scope, here's what it would look like: • Additional work: [description] • Estimated time: [X hours] • Cost: $[amount] Happy to fold this into the current project or treat it as a separate engagement. Just let me know which you prefer and I'll get a change order sent over before we proceed. Best, [Your name] TONE: Collaborative and business-like. You're agreeing to the work — not to doing it for free. DE-ESCALATION: If they push back on the charge: "I completely understand — this feels small on its own. The change order is how I keep track of everything that's in scope so there are no surprises on either side at the end of the project." ------ SCRIPT 1B — Scope Creep: Repeated Requests (Firmer) Situation: Client has asked for out-of-scope additions multiple times. Hi [Name], Just flagging that this is now the [third] addition to our original scope. I want to make sure we're aligned before continuing. Here's a summary of where we stand: • Original scope: [brief description] • Additions to date: [list] • Proposed addition today: [description] I'm happy to continue with all of these — they're great ideas. Here's the updated project estimate including all changes: $[amount]. Want me to send a revised contract for the expanded scope? Best, [Your name] TONE: Firm but not accusatory. You're documenting what's happened, not assigning blame. DE-ESCALATION: If they're surprised: "I should have flagged each change as it came up — that's on me. Here's a full summary so we can both see where we are." ------ SCRIPT 1C — Scope Creep: Stopping Work Until Resolved Situation: Scope has expanded significantly and you need resolution before continuing. Hi [Name], Before I move to the next phase, I need us to get aligned on scope. The project has grown meaningfully since we started: • Original deliverables: [list] • Additional requests to date: [list] • Estimated additional time: [X hours] / $[amount] I've paused work on Phase [X] until we have a change order signed for the additions. This protects both of us — you know exactly what you're getting, and I know what I'm building. I can have a change order to you today. Does [time] work for a quick 5-minute call to confirm the details? [Your name] TONE: Direct and professional. Pausing work is a legitimate tool — you're not being difficult, you're being organized. DE-ESCALATION: If they're upset about the pause: "I understand this is frustrating. My goal is to deliver exactly what you need — and to do that, I need to know what 'everything' includes." ------------------------------------------------------ SITUATION 2: LATE PAYMENT ------------------------------------------------------ SCRIPT 2A — Late Payment: First Follow-Up (Friendly) Situation: Invoice is 3–7 days past due. Hi [Name], Just a quick note — invoice #[X] for $[amount] was due on [date]. I haven't seen it come through yet. If there's anything I can clarify or if this has already been sent, please disregard. Otherwise, here's the payment link: [link] Thanks, [Your name] TONE: Light and friendly. Assume good faith on the first follow-up — invoices get lost. DE-ESCALATION: If they're apologetic and pay immediately: send a brief thank-you email to keep the relationship positive. ------ SCRIPT 2B — Late Payment: Second Follow-Up (Firmer) Situation: Invoice is 14+ days past due with no response. Hi [Name], Following up again on invoice #[X] — it's now [X] days overdue. Total due: $[amount] Original due date: [date] Payment link: [link or bank details] Per our contract, work on any new requests is paused until this invoice is settled. Please let me know if there's an issue I can help resolve. Best, [Your name] TONE: Firm and factual. This is not a friendly reminder — it's a professional escalation. DE-ESCALATION: If they claim they're waiting on their own client: "I understand cash flow can be tight. I need payment within [X] business days to continue. Is there a partial payment possible?" ------ SCRIPT 2C — Late Payment: Final Notice Before Collections Situation: Invoice is 30+ days past due. Last contact before escalating. Hi [Name], This is my final follow-up on invoice #[X]. Amount: $[amount] + late fee of $[amount] (per our contract, [X]% per month from the original due date of [date]) Updated total: $[amount] If I don't receive payment by [specific date], I will be escalating this to [collections / small claims court / my attorney] as outlined in our contract. I'd much prefer to resolve this directly. Please reach out if you'd like to discuss. [Your name] TONE: Direct and professional. This is a legal notice, not a personal attack — keep the emotion out. DE-ESCALATION: Only if they respond with a genuine financial hardship: offer a payment plan in writing with specific dates. Get it in writing before agreeing to anything. ------------------------------------------------------ SITUATION 3: GHOSTING ------------------------------------------------------ SCRIPT 3A — Ghosting: First Follow-Up (3 days) Situation: Client hasn't responded to a deliverable submission or question. Hi [Name], Just following up on the [deliverable] I sent over on [date]. Wanted to make sure it came through okay. If you have questions or need anything clarified, I'm happy to set up a call. Otherwise, I'll hold for your feedback before moving to the next phase. Best, [Your name] TONE: Light and assumed-good-faith. They might just be busy. DE-ESCALATION: N/A — this is the de-escalation version. ------ SCRIPT 3B — Ghosting: Second Follow-Up (7+ days) Situation: 7+ days of silence. Timeline is at risk. Hi [Name], I haven't heard back in [X] days and want to make sure we keep your project on track. Current status: • Submitted: [deliverable] on [date] • Awaiting: [feedback/approval/payment] • Timeline impact: [X-day delay on current schedule] Per our contract, if I don't receive a response by [specific date], I'll treat the deliverable as approved and move to the next phase. If there's been a change in priorities or the project needs to be paused, just let me know and we can figure out the best path forward. [Your name] TONE: Factual and clear. You're not guilt-tripping — you're documenting and giving a specific deadline. DE-ESCALATION: If they come back apologizing: "No worries — let's pick up where we left off. The revised timeline is [date]." ------ SCRIPT 3C — Ghosting: Project Close-Out (30+ days, no response) Situation: Project has effectively stalled with no response for 30+ days. Hi [Name], It's been [X] weeks since we last connected. I've tried reaching you on [date], [date], and [date] without response. At this point, I'm treating the project as paused per the terms in our contract. Here's where things stand: • Completed deliverables: [list] • Remaining work: [list] • Outstanding balance: $[amount] (if applicable) If you'd like to resume the project, I'm happy to discuss a timeline — but please note my schedule has shifted and I may not be able to pick this up immediately. If I don't hear back by [date], I'll formally close the project on my end. [Your name] TONE: Professional and final. This email creates a paper trail for your records and formally documents the situation. DE-ESCALATION: If they suddenly reappear with an emergency: "I'm glad you're back. Here's what we need to do to get the project back on track: [contract amendment / revised timeline / restart fee]." ------------------------------------------------------ SITUATION 4: MICROMANAGEMENT ------------------------------------------------------ SCRIPT 4A — Micromanagement: Setting the Communication Standard Situation: Client is requesting daily updates or constant check-ins from the start. Hi [Name], I want to make sure we're set up for a smooth process — here's how I typically communicate during projects: • Weekly progress update every [day] — covering what was completed, what's next, and any decisions needed from you • Immediate contact if there's a blocker, question, or risk to the timeline • Structured feedback rounds at [milestones] — I'll send clear questions to keep feedback focused This approach keeps us both informed without creating interruptions that slow down the work. Does this work for you? [Your name] TONE: Proactive and professional. You're setting the standard before they set a different one. DE-ESCALATION: If they push for more frequent updates: "I understand wanting to stay in the loop. The weekly update format actually gives you more information than a quick check-in would. If something urgent comes up in between, I'll flag it immediately." ------ SCRIPT 4B — Micromanagement: Pushing Back on Process Override Situation: Client is telling you how to execute your work. Hi [Name], I appreciate the input — I want to make sure we get this right. My recommendation to [approach you suggested] is based on [specific reasoning]. I've used this approach on similar projects and here's what it produces: [outcome]. I'm happy to try your preferred approach — I just want to flag that it may affect [timeline / quality / cost] because [reason]. Would you like to proceed with your approach, or should we try mine first and evaluate? [Your name] TONE: Deferential but clear about your professional reasoning. You're not refusing — you're documenting the trade-off. DE-ESCALATION: If they insist on their approach: follow it, document that you flagged the concern, and send a written summary: "Per your direction, we'll proceed with [approach]." ------ SCRIPT 4C — Micromanagement: Resetting After It's Gotten Difficult Situation: The relationship has become strained because of excessive oversight. Hi [Name], I'd like to suggest we take a step back and realign on how we're working. I've noticed we've been going back and forth a lot on [process/decisions], and I want to make sure that's not getting in the way of the actual work. Here's what I'd suggest: for the remaining [X phases], I'll send structured check-ins at [specific points] and I'll flag anything that needs your input immediately. Between those points, I'll execute based on the brief we agreed to. This will help us move faster and reduce the back-and-forth. Does that work for you? [Your name] TONE: Direct but collaborative. You're proposing a better process, not assigning blame. DE-ESCALATION: If they feel criticized: "I'm not trying to push you out of the loop — I want to make sure you're getting the best possible result. That's easier when I can execute fully between our check-ins." ------------------------------------------------------ SITUATION 5: DECLINING OR ENDING AN ENGAGEMENT ------------------------------------------------------ SCRIPT 5A — Declining Before Starting Situation: After reviewing the project, you've decided not to take it. Hi [Name], Thank you for considering me for this — I can see you've put real thought into what you're building. After reviewing the project details and our conversation, I don't think I'm the right fit for this one. [Optional: For a project like this, you might have better results with someone who specializes in [X]. If you'd like, I'm happy to point you toward a few people.] I wish you all the best with it — if a future project is a better fit, please don't hesitate to reach out. [Your name] TONE: Short, warm, and final. You don't owe a detailed explanation. "Not the right fit" is a complete sentence. DE-ESCALATION: If they ask why: "Honestly, I think there are freelancers who will serve you better on this particular brief. I want you to get the best outcome." ------ SCRIPT 5B — Pausing or Ending Mid-Project (Standard) Situation: You need to end an engagement that isn't working, mid-project. Hi [Name], I've given this a lot of thought, and I don't think I'm able to continue with this project. Here's where things stand: • Completed work: [list of deliverables] • Outstanding deliverables: [list] • Balance for work completed: $[amount] I'll send over everything completed to date in the agreed formats. Per our contract's termination clause, [relevant clause]. I appreciate the opportunity and wish you well with the project. [Your name] TONE: Professional and clear. No apology tour, no lengthy explanation. DE-ESCALATION: If they're upset or want to continue: "I understand this is difficult. My decision is final, but I want to make sure the handoff is as smooth as possible for you." ------ SCRIPT 5C — Ending Due to Non-Payment or Abusive Behavior Situation: You're ending the engagement due to a serious contract breach. Hi [Name], Due to [non-payment / [specific behavior] as outlined in our contract], I am ending this engagement effective immediately. Per Section [X] of our contract: [Paste relevant clause] Here is the status of work completed and payment due: • Completed: [list] • Payment outstanding: $[amount] • Due date for outstanding payment: [date] I will not be completing any further work. All files and assets created to date remain my intellectual property until full payment is received. Please confirm receipt of this message. [Your name] TONE: Formal and factual. This is documentation, not a conversation. Keep emotion out entirely. DE-ESCALATION: N/A — this script is for situations past the de-escalation point. Send it, document it, and follow through. ------------------------------------------------------ GET THE FULL SYSTEM ------------------------------------------------------ These scripts are a free download from SoloStack. For contract templates with the clauses that back these scripts up: → solostack.madethis.app/products ====================================================== END OF DOCUMENT ======================================================