The exact words to charge for extra work — without sounding greedy or risking the relationship.
Chris Do / Brennan Dunn / Mike Monteiro / Jonathan Stark / Blair Enns
“Saying yes to scope creep doesn't protect the relationship. It poisons it.
— THE CENTRAL THESIS
You're not bad at boundaries. You're scared of losing the client. That's why you say yes to the “quick favor.” Why you absorb the third revision when only two were promised. Why you swallowed your last invoice argument.
The fear is real. The math behind it is wrong.
Every “yes” to free work doesn't protect the relationship. It poisons it. Most freelancers in the game long enough know this. Almost none internalize it.
This book is the curated playbook from five people who already figured it out.
Five careers, one shared conclusion: speaking up doesn't lose clients. Staying silent does.
This book takes their work and turns it into the words you use Monday morning.
Read in about three hours. Use the first script within five days.
You're losing five figures a year to scope creep. Spread across a hundred small “yes” moments, you don't see it.
This calculator shows you the number.
Most honest freelancers land between $15K and $80K. The industry average — across Freelancers Union, PMI, and freelance-platform surveys — is roughly $40,000 per year.
You're not “missing out” on this money. You earned it. You gave it away.
The bigger loss is what scope creep does to you. Resentment builds. You dread client emails. You overdeliver to compensate for unspoken anger. You burn out. Good clients get less of you because the difficult ones eat your day.
Scope creep doesn't just steal money. It steals the energy to find better work.
“You're not building goodwill. You're training them.
The reason you say yes to free work is to keep the client. It's also why you're losing them.
Every “yes” trains the client. They don't see the favor. They see work that got delivered. Their idea of what you cost — in money and effort — quietly drops. The next ask gets bigger.
You're not building goodwill. You're training them.
Chris Do, 30 years running 8-figure creative agencies, says it plainly: clients respect freelancers who push back. They lose respect for ones who cave. Pushback is a signal. Professionals charge for changes. Amateurs absorb them.
Mike Monteiro said it sharper. The client who tells you “we don't need a contract, you can trust us” is the client who will burn you. Always. Trust without structure isn't a relationship. It's a setup.
Jonathan Stark frames it as math. Every favor you absorb teaches the client your time is negotiable. They learn fast. Every future conversation starts from a worse place. You can't un-train them. You can only avoid training them.
A copywriter — call her M. — landed a $4,000 client. Two weeks in: “Just a quick LinkedIn post to go with the launch.” Fifteen minutes. M. did it free. Next week: “Could you also write a follow-up email?” Done free.
Two months later she was writing 25% of the campaign unpaid. When she finally pushed back, the client was offended. From his side, the requests felt like part of the deal. M. had never said otherwise.
He never hired her again.
The fear that drove you to absorb free work — the fear of losing the client — is the same fear that's losing the client. The fix isn't aggression. The fix is speaking up earlier, more clearly, with less apology.
There's a 30-second window where money and respect are won or lost. Most freelancers never see it.
Creep requests almost always start with one of four phrases. Learn them. They're the bell.
When you hear them, you have 30 seconds. Not to reply — to decide.
That's the meta-skill. Once you train it, the scripts become muscle memory.
The scripts in the next chapter only work if you use them. You only use them if you catch the moment.
Eight moments. Three variants each. Soft, standard, firm. Pick the register that matches the relationship, the pattern, and the stakes.
Copy any script. Replace the highlighted variables. Send.
Could you also quickly add a contact form to the homepage? Should only take a minute.
The ask is tiny. Refusing feels disproportionate. Charging feels petty. So you do it free. Multiply by every project. Now you see your number from Chapter 1.
Hey [Name],
Happy to add that. It falls outside what we scoped, so I'll send a short addendum — flat $[amount] to cover it. If that works, I'll get started today.
Let me know.
Hey [Name],
This sits outside our agreed scope. I can take it on for $[amount], delivered by [date]. If you'd rather skip it, no problem — let me know either way.
Hey [Name],
That's a new piece of work, not part of the current scope. I'm happy to scope it separately: $[amount], with its own timeline. Treating it as part of the existing project isn't something I'm able to do.
Let me know if you'd like a proposal.
While we're at it, let's also add a contact page and a newsletter signup. Shouldn't change much, right?
It changes a lot. This isn't a small ask — it's new scope dressed up as a side note. The fear here is different: not that they'll think you're petty, but that they'll think you're not committed. You're not rejecting the work. You're naming it.
Hey [Name],
Good idea — and it's outside what we scoped. I'd suggest treating it as a Phase 2 so it gets the time it deserves. Quick estimate: $[amount], +[X] days to timeline.
Want me to send a short scope doc?
Hey [Name],
That's a meaningful addition. To do it right, I'd need to add $[amount] and push delivery by [X] days. Happy to put it in a change order so we keep things clean.
Let me know if you'd like to proceed, push to a later phase, or skip.
Hey [Name],
Adding that mid-project changes the math. To do it without compromising the current scope, the new work needs its own line: $[amount], with its own delivery date. Otherwise we either descope something existing or push the timeline.
Which would you prefer?
This is the hardest moment emotionally. The relationship is established. You've been compliant. Changing course now feels like a bait-and-switch. It isn't. The relationship is already damaged. The client just doesn't know it yet.
Hey [Name],
Quick housekeeping note. Tracking time across our work, we're well over what was originally scoped. No worries on what's already happened — but going forward, I'll send a short change order for anything outside the original spec. Keeps things clear for both of us.
Sound good?
Hey [Name],
I want to be straightforward: we've drifted significantly from the original scope, and I can't keep absorbing additions without adjusting.
Going forward, anything outside the original spec gets a short change order. For the work currently underway, I'd like to either bill the overage ($[amount]) or pull back to original scope.
Either is fine — but the current arrangement isn't sustainable on my end.
Hey [Name],
I need to be direct. Over the past [period], scope has grown by roughly [X]%, all unpaid. That stops now.
Two options: (1) We restructure the engagement at a fair monthly rate ($[amount]) that reflects actual work. (2) We finish the original scope as defined; any future work is quoted separately.
I'm not asking for back-pay. I'm asking for clarity going forward.
Sorry for the late ask but could you do X by Monday morning? Really urgent.
Time pressure is designed to bypass judgment. “Really urgent” makes refusing feel like ego. Two things are true: most “urgent” requests aren't actually urgent — they're poorly planned. And emergency work without emergency pay trains the client to keep doing this.
Hey [Name],
I can make this work, but it'll need to be a rush — I'm booked through tonight, and tackling it over the weekend is a rush fee (+50%, so $[amount]).
Alternatively, I can hit it first thing Monday at standard rate. Which works better?
Hey [Name],
Got the request. Two options:
(1) Rush turnaround: delivered Monday AM, +50% on the line item ($[amount]).
(2) Standard turnaround: delivered by [date], no surcharge.
Let me know which fits. Either way, I'll need confirmation by [time] to make it happen.
Hey [Name],
Just seeing this. I don't take on urgent work outside business hours without a rush fee, and at this stage of the day I'd be unable to deliver by Monday without compromising quality.
Best option: I'll start Monday morning. If that timeline doesn't work, send the scope and I'll quote a true rush turnaround (delivery Wed, +75%).
This is great. Just one more small tweak — can we try option B for the hero color?Then another. Then three more.
Each tweak is small. Each one feels too tiny to charge for. But “one more” never ends — because there's no defined end. The whole reason you wrote “two rounds” was for this exact moment.
Hey [Name],
We're at the end of our two included revision rounds. Happy to do more — they fall under additional work at $[amount] per round. Want me to bundle the remaining tweaks into a third round?
Let me know.
Hey [Name],
This would put us into a third revision round (our SOW includes two). Additional rounds are $[amount] each, capped at three rounds of consolidated feedback.
If you'd like to proceed, I'll need confirmation before starting. Alternatively, we can call the current version final — your call.
Hey [Name],
We've completed the two revision rounds defined in our agreement. Any further changes would need to be quoted as a small change order — $[amount] flat, regardless of size, to cover the open project until close.
A defined end-point is the only way to actually finish a project. Want me to send the change order?
We loved your portfolio. Could we hop on a quick 30-min call to talk through our project and see if there's a fit?The call happens. They ask deep questions. You give real answers. They thank you and disappear.
It feels like building the relationship. It actually feels like work — because it is. You just gave your most valuable asset (strategic thinking) away for a vague maybe.
Hey [Name],
Happy to talk — here's how I usually run it. A 15-minute intro call to see if we're aligned (free, just to qualify). If we're a fit, we move into a paid discovery session ($[amount], 60 minutes) where I dig into the actual strategy.
Link to book the intro: [link]. Want me to send the discovery details too?
Hey [Name],
Thanks for reaching out. Quick context on how I work:
— Free 15-min intro call to confirm fit (no strategy, just qualifying).
— Paid discovery ($[amount]) for the strategy conversation — this is the work, not a sales call.
— Proposal follows discovery.
Want to book the intro? [link]
Hey [Name],
I don't do unpaid strategy calls — the conversation about what to do is the work itself, not a preamble to it. What I can offer:
(1) A paid discovery session ($[amount]) where we map your situation and I recommend an approach.
(2) A short written proposal based on a brief you send me first.
Which works for you?
discovery.Call it what it is:
the paid strategy session.Naming it correctly is half the boundary.
Hey — we noticed something on the homepage. Can you just change the headline? Should be quick.
It IS quick. And the project's done. So why not? Because every just one thing
after sign-off teaches the client that delivery doesn't mean delivery. You become their unpaid maintenance team.
Hey [Name],
The project's been formally closed, so this would fall under post-delivery work. For small tweaks like this one I have a flat $[amount] mini-engagement — quick turnaround, no SOW needed.
Want me to handle it?
Hey [Name],
The project closed on [date] with sign-off, so this sits outside the original engagement. I offer post-delivery support two ways:
(1) One-off changes — $[amount] minimum, billed in 30-min increments.
(2) Monthly retainer for ongoing tweaks — $[amount]/mo, covers up to [X] hours.
For this specific request, option 1 makes sense. Should I proceed?
Hey [Name],
The project was closed and signed off on [date]. Post-delivery changes need to be quoted as new work — even small ones. For this: $[amount], delivered within [X] business days.
This isn't a fee for the work itself — it's the cost of reopening a closed project, doing change-tracking, and re-archiving. If you'd prefer to bundle several changes into a single engagement, let me know.
Digital proximity creates pseudo-availability. They aren't trying to abuse you — they just see you online and ask. You answer because not answering feels rude. Slack creep is the most invisible form of scope creep.
Hey [Name] — quick note. Going to be more disciplined about Slack hours going forward: I'll be checking [9am-5pm, weekdays] only.
For anything urgent outside those hours, email me — those I monitor with notifications. Standard Slack messages I'll get to the next working day.
Thanks for understanding.
Hey [Name],
Wanted to put some structure around how we're communicating. Going forward:
— Slack: business hours only ([9am-5pm, weekdays]). Response within 24 hrs.
— Email: for anything that needs attention. Same response window.
— Phone/urgent: only for true emergencies, +50% on the line item.
This lets me give you actual focused work instead of scattered attention. Let me know if you'd like to adjust.
Hey [Name],
I need to make a change in how we communicate. Slack DMs outside business hours have crept into a significant unpaid time commitment, and the constant context-switching is hurting the work you're actually paying for.
Going forward: I'm moving from Slack to email-only for our engagement. I'll check email twice daily (10am, 4pm) with 24hr response SLA. For genuine emergencies, my phone number is [number] — emergency rate applies.
“A change order is a gift to the client.
Saying no is one option. Charging is the better one.
The change order is how “no” becomes “yes, and $X more in your bank account.”
Most freelancers treat change orders like confrontation. They aren't. A change order is a gift to the client. You're giving them three things they don't get when you absorb work silently: the right to know what's changing, the right to see what it costs, and the right to decide if it's worth it.
Alvalyn Lundgren — designer, 30 years independent — frames the change order as the single most professional document a freelancer can send. Not because it's intimidating. Because it's clear.
Chris Do: every change order is a small new contract. Many small contracts add up to more revenue than the original project.
The freelancer who sends a change order gets paid for the new work. The freelancer who doesn't, gets resentment and the same workload. Same client. Different freelancer. Different outcome.
Most scope creep happens because your SOW left room for it.
A bulletproof SOW doesn't prevent every creep request. It prevents most of them — and gives you a paper anchor when the rest come.
Tick each one you've added to your current SOW. Tick honestly.
Brennan Dunn estimates ~80% of scope creep happens because the SOW was too vague to anchor the conversation. Mike Monteiro's rule: if it's not in writing, it didn't happen.
The SOW prevents 80% of creep. The scripts handle the rest.
“Pricing decides how often creep arrives. Scripts decide what happens when it does.
Scripts handle creep when it arrives. Pricing decides how often it arrives at all.
Most freelancers think of pricing as a number. It isn't. It's a structure. The structure you pick decides whether creep is a constant battle or a rare exception.
Every favor logged. Every invoice scrutinized. Clients hate growing hourly bills. You hate under-reporting. Creep is the inevitable battlefield.
Major upgrade on hourly — if your SOW is bulletproof. Works for well-defined projects, breaks down on engagements with uncertain scope.
Client pays for the outcome, not the deliverable. Conversation stops being about hours. Creep dies, because the engagement is about results.
Jonathan Stark's entire book — Hourly Billing Is Nuts — is built around a single insight: hourly aligns no one. The client wants fewer hours. You want more. Scope creep is what happens when the two sides fight each other.
Value-based pricing kills creep almost completely. Once the client pays $30,000 for an outcome instead of $3,000 for a deliverable, they stop asking for one more thing
— because they're paying you to figure out what should be done.
Value-based pricing isn't a number. It's a question: what's it worth to you?
When you send a proposal, never send one price. Send three.
Three options does three things: it shifts the conversation from yes or no
to which one,
it anchors the client to the middle, and it gives them visible control over their budget — which radically reduces creep, because they've already chosen what level they wanted.
The minimum viable version. What they asked for.
Adds the obvious extras that should be there. The version you'd actually ship.
Strategy, ongoing support, or a layer 70% won't pay for — but the right 30% will.
Most clients pick B. The clients who pick A are price-sensitive (still profitable). The clients who pick C are your dream clients (very profitable).
The first number you say is the number they'll remember. If your standard project is $4,000, never put $4,000 first in any conversation. Start at $6,000 (the premium). Let them negotiate down
to the middle. That's not deception — that's pricing 101.
Blair Enns calls this using the higher number as a gift to the client.
You're not gouging. You're showing them what's possible. They'll choose what fits.
Most freelancers price for the perfect-client version of a project. That client doesn't exist. Brennan Dunn's rule: price for the worst version. Your hardest, most demanding, most creep-prone client. Then triple that price. Why triple?
— 1x for the actual work.
— 1x for the creep, revisions, and client management.
— 1x for the opportunity cost of not taking a better project.
If your number sounds expensive, congratulations — you're priced correctly for sustainable freelancing. The clients who balk weren't going to be profitable anyway.
Get the pricing right and the scripts become rare.
You can save the relationship. You just have to be willing to risk it.
Every freelancer has at least one client they need to reset. Maybe several. The relationship started reasonable, then drifted. You're now 30%, 50%, 100% over scope and you've stopped tracking because tracking only makes you angry.
The reset conversation is the single hardest moment in freelancing — and the highest-leverage one. Done well, it saves both the relationship and your business. Done badly, you lose a client you needed to lose anyway. Both are wins.
If two of these are true, you need a reset. If four are true, you needed one six months ago.
just to keep things smoothmore than once a week.
Do this in a real-time call — video or phone. Not email. Real-time lets you read the room and adjust.
Two specific things you appreciate. Not flattery — real specifics.
Not feelings — numbers. We've added X hours, that's Y% over.
Specific: bill overage, restructure to a retainer, or quote each new piece.
End with Which of those works for you?
Client owns the choice.
Within 24 hours of the call, send the agreement in writing. Verbal isn't agreement — the written follow-up is the real contract.
Hey [Name],
Thanks for the conversation today — wanted to put our agreement in writing so we're aligned:
— Going forward: [the new arrangement].
— Starting date: [date].
— For anything outside the original SOW between now and then: [agreed handling].
Reply with confirmed
and we're set.
Thanks for being open to the conversation.
They accept the reset. Most common. They thank you for the clarity — because most clients didn't realize the drift was happening. Relationship gets better immediately.
They negotiate. Good. They value the relationship enough to want it to work. Land in the middle. They feel agency; you get most of what you needed.
They leave. Rare but possible. They were never going to be a sustainable client. You just saved yourself another year of resentment.
The best reset is the one you don't have to do. Once a quarter, with every ongoing client, send a check-in note: what's working, what could improve, anything to adjust.
The clients who appreciate it become long-term partners. The clients who ignore it are already in creep.
“The client you fear losing is the client you most need to risk losing.
Late payment is creep on the back end. Your money is owed. Act like it.
Every freelancer eventually gets stiffed. The question isn't whether — it's whether you have the structure to make it rare and the spine to enforce it when it happens.
Filters clients without budget. Makes them feel committed. Caps your downside if they ghost. Eliminates 90% of payment problems on its own.
Most underused leverage in freelancing. They literally cannot use your work until they've paid in full. Forgotten
invoices arrive same-day when reminded.
Late fee on its own: ignored. The work-stop gives the fee teeth. Not aggression — hygiene.
When an invoice goes late despite your structure, run this sequence. Three emails. Specific timing. Specific tone shifts.
Hey [Name],
Quick reminder — invoice #[X] for $[amount] was due [date]. Probably caught up in the inbox. Could you confirm receipt and let me know expected payment date?
Hey [Name],
Following up on invoice #[X] — still showing unpaid. Per our agreement, late fees of 1.5%/month kicked in day 14 and work will pause on day 21 if unresolved. I'll need payment confirmation by [date] to keep the project moving.
Hey [Name],
As of today, project work is paused per the terms of our agreement. Invoice #[X] for $[amount] (plus accrued late fees of $[amount]) remains unpaid 21 days past due. Work resumes within 48 hours of full payment plus a $[amount] re-engagement fee.
If day 30 passes with no resolution, escalate. Three options, in order:
1. Direct phone call. 30% of won't pay
clients pay within 48 hours of a real conversation.
2. Collections agency for invoices over $1,000. 20-30% cut, less reputation risk than litigation.
3. Small claims court for invoices over $2,000. The threat alone often resolves it.
What you should rarely do: hire a lawyer to chase a $4,000 invoice. Treat unrecoverable bad debt as the cost of doing business — and make sure your structure keeps that cost rare.
Your money is owed. Acting like it is the most professional thing you can do.
“Five different freelancers. Five different creep patterns. One shared move.
Five composite case studies. Names changed, situations composited from common patterns. The fixes are real.
Each story below illustrates one of the eight moments in action — the freelancer's situation, what they tried, what worked, the lesson. Use them as pattern recognition.
Five different freelancers. Five different patterns. One shared move: they stopped absorbing and started naming.
Every expert behind this book has written more. The short list:
That's the book. The work is yours from here.
One script that landed. One client conversation that shifted. Reply with a story — it shapes the next edition.