Revenue Communication
·25 April·6 min readScope Creep Is a Communication Problem Before It’s a Financial One
Scope creep is rarely a client problem. It is usually a communication problem — one that begins the moment a business owner responds to an out-of-scope request with apologetic or uncertain language.
By Casey Bawden
Scope creep — the accumulation of unpaid work beyond the agreed project boundaries — is one of the most consistent financial problems for self-employed professionals and small business owners. It is usually described as a client behaviour problem. The client keeps asking for more. The client does not respect the scope. The client takes advantage.
Sometimes that description is accurate. But in many cases, scope creep begins with a communication response — specifically, with how the business owner responds the first time a client requests something outside the agreed scope.
When a client requests out-of-scope work, the business owner has a decision: hold the boundary and state it clearly, or absorb the additional work without charging. Most business owners choose a third option, which is to hold the boundary but communicate it so apologetically that the client does not register the boundary as firm.
‘I know this is a bit awkward, but I think that might technically be outside what we agreed — I’m not really sure if we can include it without some kind of extra charge.’
This response contains a boundary — the work is outside the agreed scope. But it also contains enough softening language that the client reads it as negotiable. The words ‘a bit awkward’, ‘I think’, ‘technically’, and ‘kind of’ all signal that the position is uncertain. The client hears: this boundary might not hold if I push.
On the next project, the client pushes. On the one after that, they push harder. The pattern of escalating scope requests is a direct response to the signal the business owner has been sending: this boundary is soft.
Why the language of scope responses is apologetic
Scope boundary conversations feel confrontational to most business owners. The client has made a request that seemed reasonable to them. Declining it feels like disappointing someone, or like being difficult.
This feeling produces apologetic language. The problem is that the language designed to reduce discomfort also signals to the client that the business owner expects the boundary to be inconvenient and uncomfortable for them both. A boundary that is communicated apologetically is not a firm boundary. It is an opening position.
The structural boundary response
A structural scope boundary response contains two elements: what is outside the current scope, and what the path forward is.
Instead of
I know this is a bit awkward, but I think that might technically be outside what we agreed — I’m not really sure if we can include it without some kind of extra charge.
Write
That falls outside the current scope. I can provide a quote for the additional work, or we can adjust the existing scope to accommodate it. Let me know which you’d prefer.
This response does not apologise for the scope. It does not add language that signals the boundary is uncertain or negotiable. It states the fact, offers two clear options, and closes with a question that requires the client to make a decision.
The client is not being treated harshly. They are being given accurate information about what was agreed and what the options are. The clarity is respectful — it saves both parties time that would otherwise be spent in a conversation designed to gradually erode the boundary.
The financial cost of soft scope language
The cumulative cost of absorbing uncompensated scope is significant. A business owner who absorbs four uncompensated hours per month across their client base is working at a lower effective rate than their quoted rate. Over a year, the gap between what they charged and what they delivered can represent a substantial revenue loss.
More significantly, the pattern compounds within individual client relationships. A client who has had scope requests absorbed in the past will continue to make them. Each absorbed request sets the expectation that the next one will also be accommodated. The business owner who eventually holds the boundary is experienced by that client as having changed the rules, not as having enforced them.
Holding the boundary clearly from the first request prevents the pattern from establishing. The communication is the intervention.
Subscribe
Field notes, in your inbox.
New analyses on structural language and professional authority — sent occasionally, never to your spam folder.
No spam · Unsubscribe anytime
Subscribers receive Seven Professional Emails, Rewritten — free.
Structural Revenue System™