My client changed the project scope but not the price - what I wish I'd known

How $6,000 of Work Became $6,000 of Free Work

Daniel is a freelance web developer based in Chicago. He agreed to build a marketing website for a health and wellness brand — five pages, a contact form, and basic SEO setup — for $6,000. The project scope was clear in the proposal. The contract, however, was a one-page document that described the deliverables briefly without defining what was and wasn't included.

By the time the project ended four months later, Daniel had built eight pages, integrated an e-commerce checkout, created a blog CMS, and implemented a newsletter sign-up system. None of that was in the original proposal. Every addition had come as a friendly request mid-project, and Daniel had said yes each time to maintain the relationship.

He invoiced $6,000 as originally agreed. He calculated afterward that he had delivered approximately $12,000 worth of work.

What Scope Creep Actually Is — and Why It's a Contract Problem

Scope creep refers to the gradual expansion of a project beyond its original agreed boundaries, usually without a corresponding adjustment in price or timeline. It is almost never malicious — clients genuinely often don't realize they're asking for more. The problem is structural: without a contract that clearly defines what is included and what triggers a change order, there is no mechanism to say 'that's additional work.'

From a contract law perspective, scope creep typically involves one of two issues. Either the original contract was insufficiently specific about deliverables, leaving room for dispute about what was agreed. Or the client is making requests that clearly fall outside the contract, but the freelancer has no formal process to document and price the addition.

Both are solvable with the right contract language — and both are recoverable, to a degree, even after the fact.

The Contract Clauses That Prevent Scope Creep

Detailed deliverables definition

The contract should specify exactly what is included — not in summary, but in detail. 'A five-page marketing website' is insufficient. The contract should list each page, define the functionality included, and explicitly state what is not included (e.g., 'e-commerce functionality is not included in this scope').

Change order clause

A change order clause states that any request that falls outside the defined deliverables will be treated as a separate engagement, subject to a written change order with its own pricing and timeline. Without this clause, a verbal agreement to 'just add one more thing' can be construed as a modification to the original contract — at the original price.

Revision limits

Unlimited revisions are one of the most common undocumented scope expansions. A contract should specify how many revision rounds are included and what constitutes a revision versus a new direction (which would trigger a change order).

Out-of-scope work documentation

Some contracts include a provision that any work performed outside the defined scope, if completed without a signed change order, is performed at the freelancer's discretion and does not constitute acceptance of additional scope. This is a backstop that protects the freelancer even when they do complete informal additions.

Dealing with a contract dispute right now? Unstuck (Unstuck ) reads your contract from your side — flags what's enforceable, what isn't, and gives you ready-to-send responses. No lawyer needed.

Can You Recover Compensation for Scope Creep After the Fact?

In some cases, yes. The legal theory is unjust enrichment: a client should not be allowed to retain the benefit of work they received without paying for it. If you can document that (a) you performed work clearly outside the original contract scope, (b) the client requested and received that work, and (c) you have a reasonable market rate for that work, you may have a claim for the additional value delivered.

Daniel uploaded his original contract, his proposal, and a detailed log of every additional feature request (which he had preserved in email) to Unstuck. The analysis confirmed that the e-commerce checkout, blog CMS, and newsletter integration were clearly outside the five-page website scope described in his contract. It generated a supplemental invoice with a covering letter citing the documented requests, the market rate for each addition, and the unjust enrichment principle — while framing it as an opportunity to resolve the discrepancy professionally rather than an accusation.

The client paid 60% of the additional invoice — $3,600 — acknowledging that the additional work had been requested and delivered.

The Conversation to Have Before Every Project

The most effective scope creep prevention happens before the contract is signed. Walk through the deliverables list with the client explicitly. Confirm verbally what is and isn't included. Then make sure the contract reflects that conversation precisely.

When a client makes an informal mid-project request, the right response is not 'yes' or 'no' — it's 'that sounds great, let me put together a change order for that.' This frames the additional work as professional and valued, not as resistance.

The Cost of Not Having This Conversation

Scope creep is estimated to affect the majority of freelance projects in some form. The cumulative financial impact across a freelance career — of informal additions accepted without pricing — is often substantial. The contract clauses that prevent it take minutes to add. The conversation that invokes them takes one sentence.

Dealing with a contract dispute right now? Unstuck (Unstuck ) reads your contract from your side — flags what's enforceable, what isn't, and gives you ready-to-send responses. No lawyer needed.