The Freelance Rate Increase Script: Turn Scope Creep Into a Justified Price Conversation
Why this prompt matters
Freelancers who let scope creep go unaddressed for over a year typically end up either quietly burning out on an unprofitable account or having an unprepared rate conversation that gets deflected with 'let's revisit next quarter.' A vague 'I think I need to charge more' pitch is easy to push back on; a scripted, evidence-based ask tied to specific absorbed work is what actually gets approved without turning into a drawn-out negotiation.
What we use it for
You've done freelance graphic design for a client for 14 months at $75/hour. What started as a 10-hour/month retainer for social graphics has quietly grown to include weekly newsletter design, video thumbnails, and same-day rush requests never in the original agreement. You have a call with the client next Tuesday and need to raise your rate to $95/hour without sounding like you're punishing them for trusting you with more work.
Prompt
Role: Act as a senior freelance business consultant who has helped hundreds of independent contractors negotiate rate increases with long-term clients without losing the relationship. Context: - My current rate: [YOUR CURRENT RATE, e.g., "$75/hour"] - My target rate: [YOUR TARGET RATE, e.g., "$95/hour" — if you don't have one yet, tell me and I'll help you think through a minimum acceptable number instead of guessing] - Original scope of work when we agreed on the current rate: [DESCRIBE THE ORIGINAL AGREEMENT] - How the work has actually grown since then, with specific examples: [LIST SPECIFIC EXTRA DELIVERABLES, REQUESTS, OR RESPONSIBILITIES YOU'VE ABSORBED WITHOUT CHARGING FOR THEM, AND ROUGHLY HOW LONG THIS HAS BEEN GOING ON] - How long I've worked with this client: [LENGTH OF RELATIONSHIP] - Anything about this client's situation or personality I should account for: [OPTIONAL — e.g., "tight budget this quarter" or "very data-driven, wants numbers not feelings"] Task: Write a rate increase conversation script for me to use with this client, built specifically from the scope-creep evidence I gave you above — not generic negotiation advice. Constraints: - Do not use generic language like "I feel my rates should reflect my value." Every argument must be tied to a specific, concrete example from the evidence I gave you. - Keep the tone collaborative, not adversarial — the goal is to keep this client, not threaten to leave. - If I didn't give you a target rate, do not invent one. Instead, note what I should think about when deciding my minimum acceptable number before the call. - Anticipate real objections a reasonable client would raise, not strawman ones. Output Format: 1. PRE-CALL MESSAGE (2-4 sentences to send before the conversation, sets up the discussion without stating numbers yet) 2. LIVE SCRIPT (opening line, evidence-based case built from my specific examples, responses to the 3 most likely objections) 3. FALLBACK OFFER (one paragraph — a concession I can offer if they push back hard) 4. PREP CHECKLIST (3 bullet points of things to confirm or decide before the call)
Result
1. PRE-CALL MESSAGE
"Hi Jordan, I'd like to grab 20 minutes this week to talk through our working arrangement — nothing urgent or concerning, just want to make sure our setup still reflects everything we're collaborating on these days. Does Tuesday or Wednesday afternoon work?"
2. LIVE SCRIPT
Opening line: "Thanks for making time. I wanted to talk through how the scope of what I'm doing for you has evolved since we set up the $75/hour rate 14 months ago, and figure out together how to make sure that's still working for both of us."
The case: "When we started, the agreement was 10 hours a month on social graphics. Over the last several months, that's grown to include the weekly newsletter design, thumbnail graphics for the video series, and same-day turnaround on rush requests — none of which were part of the original scope. I've been glad to take these on as they came up, but at this point they're a consistent part of the work rather than occasional extras, and I want our rate to reflect that."
Objection 1 — "Budget is tight right now": "I understand budget is a real constraint. One option: we could phase this in — a smaller increase now, with a review in a quarter once the newsletter and thumbnail work has had time to show its impact."
Objection 2 — "We didn't realize it had grown that much": "That's fair, it happened gradually. Happy to walk through specific months if it's useful — the newsletter work alone has been roughly 4-5 hours a week since March."
Objection 3 — "Can we just go back to the original scope instead?": "Totally an option if that works better for your team — I can scale back to the original social graphics scope at the current rate, or we adjust the rate to reflect everything we're doing now. Whichever fits your priorities better this quarter."
3. FALLBACK OFFER
If $95/hour meets real resistance, propose $85/hour now with a scheduled review in 90 days, or alternatively, keep the $75 base rate for the original social graphics scope and bill the newsletter and thumbnail work as a separate $500/month add-on line item — this reframes the ask from "raise my rate" to "let's properly scope what's already happening," which is often an easier conversation.
4. PREP CHECKLIST
- Decide your real minimum acceptable rate before the call, not during it
- Pull 2-3 specific dated examples of absorbed extra work (screenshots of requests, invoice history) in case they ask for detail
- Know which fallback you'd actually prefer — a phased increase or unbundled line-item billing — so you're not deciding on the spot
Most freelance rate increase conversations fail for the same reason: the ask is vague. "I think my rates should go up" gives a client nothing concrete to agree to, so it gets deflected with "let's revisit next quarter" or quietly ignored. The freelancers who actually get the increase are the ones who show up with a specific, evidence-based case — here is exactly what the scope looked like when we agreed on this rate, here is exactly how it has grown since, here is the number that reflects that growth.
This prompt is built around that distinction. Instead of asking the model to write a generic negotiation pitch, it requires the user to first lay out the concrete scope-creep evidence — the original agreement, the specific extra deliverables absorbed for free, how long it's been happening — and then builds the entire script from that evidence. The constraint against generic language like "I feel my rates should reflect my value" is deliberate: that phrasing is exactly what makes a client's guard go up, because it sounds like a feeling rather than a fact they can evaluate.
The three-part structure — a pre-call message, a live script with objection handling, and a fallback offer — mirrors how actual rate conversations unfold. Clients rarely accept the first number outright, and a freelancer who hasn't thought through a fallback (a smaller increase now with a review date, or unbundling new work into a separate line item) ends up negotiating against themselves in the moment. Building the fallback in advance, calmly, is the difference between a planned concession and a defensive retreat.