July 3, 2026
Should you charge clients for out-of-scope work?
Thom Van Dycke · Van Dycke Strategic Business Architecture
You should charge for out-of-scope work when it's genuinely outside what you originally agreed to do, because doing it for free doesn't read as generosity to the client. It reads as evidence that the work wasn't worth charging for in the first place. The fix is naming the work before you do it, not finding your nerve.
Why do skilled professionals flinch before billing for work they clearly did?
Picture the moment. The amendment is done, the revision is finished, the extra round of edits is filed. It took real time and real expertise. And there you are, hovering over "send," running the math on whether to bill for it or just fold it in "as a courtesy," because billing for it feels like admitting you're the kind of person who nickel-and-dimes a client you actually like.
That flinch shows up constantly in professional services. Accountants wrestle with it on amended returns. Consultants wrestle with it on the follow-up call that ran forty minutes over. Designers wrestle with it on the third round of revisions that were never in the original scope. It's the same disease wearing different clothes: a professional who did clearly billable work, and can't make themselves say so.
It's tempting to call this a confidence problem. It isn't. Confidence is something you either have or build slowly over years. Positioning is something you can fix this week.
Picture the agency owner who quoted a project, delivered it, and then got a "quick favor" request for a fourth round of revisions nobody scoped. Or the coach whose client texts at 9pm with a question that turns into a thirty-minute call. Different industries, same flinch. Nobody trained any of them to say the number out loud when the ask came in, so nobody does, and the free work quietly becomes the standard.
What's actually happening when you decide not to bill for extra work?
You're teaching the client something, whether you mean to or not. Every time work goes out the door unbilled, you've quietly told the client that this kind of work is not worth paying for. It's just part of the relationship now, absorbed, expected. You didn't mean to communicate that. You communicated it anyway, because clients learn what things cost from what they're actually charged, not from what you privately believe your time is worth.
This is where the research lines up with what anyone doing this work already suspects: pricing hesitation is common, and it's expensive. One 2026 survey of small business owners and sole traders found more than 80% underprice their products or services, largely out of fear of losing the client or looking greedy rather than any real read on what the market would bear (Bottom Line Capital, "Pricing Strategy for Small Business"). The same body of research on price increases tends to find something calmer than the fear predicts: most service businesses lose fewer than 5% of clients after a reasonable increase, and the revenue from the clients who stay outweighs the ones who leave.
So the fear and the actual risk are two different sizes. The fear is enormous. The risk is usually small. What's driving the gap isn't the client's tolerance. It's whether the value was ever made visible enough to defend.
Undercharging doesn't read to a client as generosity, and charging doesn't read as greed. What actually shifts a client's perception is whether they were shown what they were getting, once, plainly, at the moment it happened.
In Van Dycke terms, this is Sales-framework work, not a character flaw: the specific, learnable skill of stating a price out loud, clearly, at the moment value gets created.
What does "name the work" actually mean in practice?
It means the invoice line item exists before the work does, not after. Not as an ambush. As information. "This falls outside the original scope. This is what it involves and what it costs" is a sentence you say once, calmly, at the moment the extra work is requested, not something you back into after the fact hoping nobody notices.
Contrast the two versions of the same moment. Version one: the client asks for the amendment, you do it, and either it shows up unexplained on the next invoice or it quietly disappears into "the relationship." Version two: the client asks, you say "happy to. That's outside what we scoped, and this is what it runs," and they decide with full information. Only one of those versions treats the client like an adult who can make a decision. The other one makes the decision for them, and then resents them for a choice they never got to weigh in on.
Naming the work before you do it
The next time you're asked for something outside the original scope, before you touch the work itself, say two sentences out loud or in writing, to the client, not just in your own head:
- Name it: "That's outside what we originally scoped."
- Price it: state plainly what that involves and what it runs.
Then let them decide. Most clients will say yes, because they asked for the work and they know it's real. The ones who balk are telling you something useful about the relationship, not about your nerve.
If saying it live still feels too exposed at first, build it into your intake or engagement letter as a standing clause: "Work outside the agreed scope will be quoted separately before it begins." That way the positioning is structural, not something you have to relitigate with your stomach every single time.
What changed when I stopped absorbing scope creep for free
I had to learn this the slow way, in my own business, not somebody else's. For years, if a client asked for something extra, a call that ran long, a question that turned into unscoped strategy work, I just took it on. It felt generous. It wasn't. It just meant new work landed on my desk at the same price as the old work, indefinitely.
What actually changed wasn't finding my nerve. It was learning to trade. When something new comes in now, either the retainer goes up to cover it, or something already on the plate that isn't earning its place comes off to make room. Add the new thing without subtracting or charging for it, and you've quietly redefined what the original price buys, forever. Trade for it instead, and the client sees exactly what they're getting and what it costs, every time, and so do I.
Sources
Frequently asked
Isn't it risky to start charging for work I used to give away for free?
It's less risky than it feels. Research on price increases consistently finds that most service businesses lose a small share of clients after a reasonable adjustment, and the revenue from the clients who stay more than makes up for it. The bigger risk is training every client to expect free work indefinitely.
What if the client gets upset when I mention a cost for extra work?
That reaction usually tells you the scope conversation happened too late, not that you were wrong to have it. Naming the work and the cost before you start it, rather than after, removes most of the surprise that causes the upset in the first place.
How do I know if something is really "out of scope" or just part of the job?
Go back to what was actually agreed to at the start of the engagement, in writing if you have it. If the request wasn't in that original agreement, it's additional work, full stop, regardless of how small it feels in the moment.
Does this apply to trades and other non-professional-services businesses too?
Yes. A contractor doing extra work beyond the original quote, a coach adding sessions beyond the package, an agency doing revisions past the agreed round: same pattern, same fix. Name the work, price the work, let the client decide.
Ready to look at the architecture honestly?
Book the conversation. We'll tell you what we see, including where your pricing is quietly teaching clients the wrong lesson. See how the Sales framework fits alongside the other three before your next scope conversation.
Ready for some serious action?
It starts with a quick 20-minute call to come up with a plan.
