================================================================ BAD CLIENT RESPONSE SCRIPTS Word-for-Word Scripts for 4 Hard Freelance Conversations ================================================================ From SoloStack — solostack.madethis.app/resources/freelance-client-red-flags These scripts are designed to protect your time and professionalism without burning bridges or sounding defensive. Adapt to your voice. ================================================================ SCRIPT 1: "We Don't Have a Budget Yet" ================================================================ SITUATION: A prospect reaches out but refuses to name a budget number, even when asked directly. WHY IT'S A PROBLEM: "No budget" almost always means one of three things: (1) they haven't thought seriously about cost, (2) they have a number but are fishing to see if yours is lower, or (3) their number is far below your rates. None of these are good signs. --- PROBE FIRST (use if you want to salvage the conversation) --- "Happy to put together a proposal — I just need a rough budget range to make sure we're a fit before either of us invests time in a full proposal. Are we talking $1K–$3K, $3K–$10K, or something larger? Even a ballpark helps me scope the right solution." (Wait for their response. If they refuse to give ANY number, that tells you everything. Use the exit script below.) --- EXIT GRACEFULLY (use if they still won't name a number) --- "I appreciate you reaching out. Without even a rough budget range, I can't responsibly put together a proposal — I'd be guessing at scope and risk wasting both our time. If you get clarity on budget and it looks like it might be in the $[your range] range, I'd love to reconnect. Best of luck with the project." KEY POINTS: - Don't apologize for asking about budget — it's standard - Don't write a free proposal "just to see" - Clients who won't discuss budget before a proposal rarely approve one ================================================================ SCRIPT 2: "Can You Do This for Exposure?" ================================================================ SITUATION: A prospect (often a startup, influencer, or "exciting brand") offers exposure, equity, or barter instead of payment — or offers a laughably low number with "exposure" as the upside. WHY IT'S A PROBLEM: Exposure doesn't pay rent. The "exposure" offer almost always means they know they can't afford you and are trying to use flattery and future promise to get free work. --- DECLINE AND REDIRECT (professional, no apology needed) --- "Thanks so much for thinking of me — the project sounds interesting. I don't take on exposure-based work, but if you're able to put a cash budget together, I'd genuinely love to work on this. My starting rate for this type of project is $[your rate]. Let me know if that's in range and we can schedule a call." --- SHORT VERSION (if you want to be brief) --- "I only work for cash — no exposure-based projects. If you have a budget, I'd love to hear more. If not, I wish you the best with it." KEY POINTS: - You don't owe an explanation for your payment policy - "Interesting project" doesn't change the payment policy - Leaving the door open for cash work is professional; it's not caving ================================================================ SCRIPT 3: "Can We Do This Without a Contract?" ================================================================ SITUATION: A prospect says they want to work together but asks to skip the contract because they "trust you" or it feels too formal. WHY IT'S A PROBLEM: Contracts protect BOTH parties. A client who resists contracts is either: (1) planning to not pay, (2) planning to move the goalposts, or (3) simply inexperienced — in which case you're doing them a favor by insisting. --- INSIST WITHOUT LOSING THE CLIENT --- "I completely understand — it can feel overly formal when trust is already there. But the contract is actually how I protect YOU as much as me: it defines exactly what's included, so you're never surprised by extra charges, and it sets the timeline so we're both accountable. I use a simple 1-2 page agreement for all my projects. It takes 5 minutes to sign and prevents 99% of the misunderstandings that would otherwise eat into the project. I'll send it over today — let me know if you have any questions about any clause." --- IF THEY STILL PUSH BACK --- "I appreciate the trust — genuinely. But I don't work without a contract. It's a professional standard I hold for every engagement, not just this one. If that's a dealbreaker, I completely understand, but I'm not able to move forward without it." KEY POINTS: - Frame the contract as protecting THEM — it's true and disarms resistance - If they still say no after the reframe: walk away - "We trust each other" is fine — but trust doesn't replace clear agreements ================================================================ SCRIPT 4: "We Need Changes — But We Didn't Discuss This" ================================================================ SITUATION: You've delivered the agreed work and the client comes back with revision requests that go significantly beyond what was scoped. Classic scope creep. WHY IT'S A PROBLEM: Scope creep is unpaid work. Every hour you spend on out-of-scope revisions is an hour you're not billing. Left unaddressed, it becomes a pattern — and you'll resent the project (and eventually the client). --- RESPOND PROFESSIONALLY (address it immediately, in writing) --- "Thanks for the detailed feedback — I want to make sure we deliver exactly what you're looking for. Looking at the revision list, a few of these items fall outside the original scope we agreed on: [specifically name the items, e.g., 'redesigning the header section' and 'adding a new pricing table' weren't in the original brief]. I'm happy to incorporate the in-scope revisions right away. For the additional items, I can put together a quick change order — usually just a short email confirming the scope add and the additional fee. For these two items, that would be approximately $[amount]. Want me to send that change order over so we can get everything moved forward?" --- IF THEY PUSH BACK ON THE CHANGE ORDER --- "I understand it may feel surprising — my goal is always to over- deliver within the agreed scope. But taking on work outside the original agreement without adjusting the budget isn't something I'm able to do. I'm happy to prioritize these additions if we can confirm the change order. Otherwise, I can complete the originally agreed revisions and we can revisit the additional items in a future project." KEY POINTS: - Address scope creep the FIRST time it happens — not the third - Reference the original scope in writing (this is why written briefs matter) - Be warm but completely clear: the additional work costs additional money - "Change order" sounds professional and matter-of-fact — not combative ================================================================ BONUS: The "I Don't Think We're the Right Fit" Decline Email (Use when you've spotted too many red flags and want to exit cleanly) ================================================================ Subject: Re: [Project Name] Hi [Name], Thank you for considering me for this project — I can tell you've put real thought into what you're building. After reviewing the scope and our conversation, I don't think I'm the right fit for this one. [Optional: "My schedule is fuller than I expected" or "The project is outside my current focus area" — you don't owe a detailed explanation.] I wish you all the best with it. If anything changes on future projects, feel free to reach back out. [Your name] KEY POINTS: - Short, warm, no over-explaining - You don't owe a detailed reason — "not the right fit" is complete - Leave the door open only if you genuinely mean it ================================================================ Download more free freelance resources at: solostack.madethis.app/resources ================================================================