The Scope Creep Script: What to Say When a Client Asks for 'One More Thing'

A client asking for "just one more thing" isn't the problem — not having a ready answer is. Below are three short scripts for that moment, plus how to pick the right one.

Quick answer

When a client asks for something outside the agreed scope, you have three reusable moves: quote a price before you start, point back to the specific line in the contract, or offer a trade — this new thing in exchange for something already on the list. Pick based on the client and the ask, not on how you're feeling in the moment.

This matters because scope creep — uncontrolled growth in a project's scope after the work has started — is closer to the default than the exception. A 2026 industry survey found that 67% of freelancers do unpaid work as a direct result of scope creep, and 72% of freelance projects experience some degree of it. The mechanism is simple: no single ask feels big enough to justify pushback, so they pile up — and a chunk of the project ends up unpaid. A tighter statement of work cuts down how often you need any of these scripts. But even a well-scoped project gets a "quick thing" request eventually, so keep the line ready anyway.

Step-by-step

The pricing script — quote it before you do it

The line: "That's outside what we scoped — happy to add it. Here's what it adds to the timeline and the invoice, let me know if you want to go ahead."

Say the cost or time impact out loud, or in writing, before you touch the work — not after. That single ordering change turns an invisible favor into a choice the client actually makes. No awkward moment three weeks later when the invoice is bigger than expected. Keeping a short, pre-priced list of common add-ons — Bonsai's guide to avoiding scope creep recommends building this straight into the contract — means you're quoting from memory instead of improvising a number on the spot.

The contract-reference script — point back to the agreement

The line: "That's not part of what we scoped in the [statement of work] — want me to add it as a separate item, or should we handle it next round?"

Naming the actual document, calmly and without apologizing, does most of the work here. It reframes the conversation from "no" to "here's what we agreed to," which is a lot easier for both sides. This only works if the original scope was specific enough to point to — a vague one-line description in an email doesn't hold up the way a client onboarding process that captures deliverables up front does.

The trade-off script — something in, something out

The line: "I can fit that in, but it'll mean pushing back [X] or dropping [Y] from this round — which do you want to keep?"

This works better than a flat price quote when the client is more sensitive to the calendar than the invoice. It also puts the trade-off decision where it belongs — with the person asking for the change — instead of leaving you to silently absorb the extra hours into an already-full week.

Common problems and fixes

The client pushes back on the quote. Hold the number you already gave. Re-negotiating live, on the spot, undoes the whole point of quoting it in writing first — repeat the figure, don't shrink it.

You've already said yes to a few small things for free. Don't try to retroactively bill for past favors; that reads as bait-and-switch. Reset going forward instead: the next ask gets one of the three scripts above, cleanly, with no reference to what slid before.

It's a long-term or high-value client. Absorbing a genuinely small ask for free can be a deliberate choice, not a default — the difference is that it's a choice. Cap it (say, once a quarter) and treat it as an exception you're aware of, not a habit you slid into. HBR's framing is useful here: scope control works better as a documented, repeatable process — shared with anyone else on the project — than as a fresh argument you have to win alone every time. If retainer clients are a recurring source of "one more thing" requests, pricing the retainer with built-in slack absorbs some of these asks before they ever need a script.

Frequently Asked Questions

What do I actually say when a client asks for extra work outside the contract?

Name the ask, point to the agreement, and quote a price or timeline impact before agreeing to anything — for example: "That's outside what we scoped — happy to add it, here's what it adds to the timeline and invoice." The goal is a factual, reusable sentence, not a fresh negotiation every time.

Is it rude to charge for scope creep?

No — leaving it unpriced is what actually strains the relationship, since it either costs you real income or forces the extra work into hours you never budgeted. Naming a price upfront is a normal part of running a freelance business, not a confrontation.

Should I ever do small extras for free?

Occasionally, and on purpose. For a long-term client or a genuinely five-minute tweak, absorbing it can be a deliberate relationship investment. The issue isn't doing free work sometimes — it's doing it by default because there wasn't a script ready.

How do I stop scope creep before it starts?

Write a specific, itemized scope into the contract or statement of work, so a request either clearly matches it or clearly doesn't. A vague original scope is what forces the in-the-moment negotiation these scripts exist to skip.

Doing this with Pomlo

Every one of these scripts needs a real number behind it, and that number comes from an accurate time log, not a guess. Pomlo's projects and clients view keeps hours organized by exactly which statement of work they belong to, so when a request falls outside the line item, you can see that at a glance instead of arguing from memory. Built-in invoicing turns "here's what it adds to the cost" from a vague warning into an actual line item you can send in one tap — and reports show a client where their hours already went before they ask for more. One-tap start/stop means the extra 20 minutes on a "quick" ask gets logged, not estimated after the fact.

Pomlo is available on iOS and Android, and in the browser.