Scope creep rarely arrives as one big demand. It's an extra page here, one more round of revisions there, a feature that seemed obvious to the client and new to you. Each is reasonable on its own. Together they can quietly turn a well-priced project into one you'd never have accepted.
What absorbing it really costs
A fixed price implies an hourly rate: the price divided by the hours you estimated. Every unpaid hour of extra work lowers that rate. Take a $6,000 project estimated at 60 hours, $100 an hour, where the client asks for changes that will take 12 hours.
Rate implied by the quote
$6,000 ÷ 60 hequals$100.00
Hours to bill
12 h × (1 + 20%)equals14.4 h
Change price
14.4 h × $100.00equals$1,440.00
If you absorb it
$6,000 ÷ 74.4 hequals$80.65
If you absorb the work, you've done 74.4 hours, including the time spent discussing and managing the change, for $6,000. Your effective rate drops from $100 to about $80.65, a cut of more than 19%, and the client has no idea.
Why the overhead matters
A change takes more than its build time. There's the conversation, re-reading the brief, re-testing what it touches, and updating anything that depended on the old version. Adding around 20% to the raw estimate covers that. Here, 12 hours of work becomes 14.4 billable hours, priced at the project's own rate: $1,440.
Rush changes
If the client also wants the change without moving the deadline, you're re-planning other work to fit it in. A rush premium of 25% is common, which takes the same change to $1,800.
How to say it
Clients respond better to options than to a bill. Something like: "Happy to add that. It's about 14 hours including testing, so $1,440, and I can fit it in without moving the launch date. Or we can add it in a second phase after launch." That names the cost, shows it's reasonable, and gives them a choice.
- Put a change process in the contract before work starts: every change is estimated and agreed in writing first.
- Keep a running list of requests, even ones you choose to do for free, so the client sees the value they're getting.
- Price changes at the project's implied rate, so small changes and big ones are treated the same way.
Common mistakes
- Pricing the change at a lower "friendly" rate. It teaches the client that extra work is cheaper than the original project.
- Estimating only build time. Discussion, re-testing and updating related work often add a fifth or more.
- Agreeing verbally and invoicing later. Get a one-line written approval of the price before starting, even by email.
- Letting several small changes pile up unpriced. Five "quick" changes of two hours each is a 10-hour mini-project.
If a client pushes back on every change, that's useful information too. It may be worth moving them to hourly or retainer billing for the next phase, where changes are paid for as they happen.
How small changes add up, in numbers
Take a $6,000 project estimated at 60 hours, so $100 an hour. Using the Scope Creep Calculator with a 20% overhead for switching, re-testing and communication:
- 3 hours of changes: a fair fee is $360. Absorbed for free, your real rate falls to about $94.34 an hour.
- 12 hours of changes: a fair fee is $1,440. Absorbed, your rate falls to about $80.65, almost 20% less.
- 20 hours of changes: a fair fee is $2,400. Absorbed, your rate falls to about $71.43, and the project has grown by 40%.
Most projects don't get one big change. They get many small ones, each too minor to argue about, which together become the 20-hour case. Tracking every change, even the tiny ones, is what makes the total visible.
A simple change-request process
- Write the scope as a list of deliverables in the proposal, and state that anything else is quoted separately.
- When a request arrives, reply the same day with an estimate in hours and money, and the effect on the delivery date.
- Start work only after written approval, even a one-line email.
- Keep a running change log and include it with each invoice.
- For very small requests, bundle them: "I'll group these with the next set and quote them together."
When absorbing a change makes sense
Not every change needs a fee. Fixing something you got wrong is part of the original job. A genuinely tiny tweak for a long-standing client can be goodwill worth giving, as long as you say so: "Happy to include this one at no charge." Naming it as a favour keeps it from becoming an expectation, and makes the next paid change easier to raise.
Tip: Absorbing one tiny change as goodwill is fine. Say so explicitly ("no charge for this one") so it doesn't become the expectation.
Questions people ask
- How do I price a change request on a fixed-price project?
- Estimate the hours, add around 20% for discussion and testing, and multiply by the rate implied by your quote (price ÷ estimated hours). Add a rush premium if the deadline can't move.
- How much does scope creep cost freelancers?
- In the example here, absorbing 12 hours of changes on a 60-hour, $6,000 project cuts the effective rate from $100 to about $80.65 an hour, more than 19%.
- How do I prevent scope creep?
- Define what's included, including revision rounds, agree a change process in the contract, and estimate every change in writing before doing it.
- How much does scope creep reduce my hourly rate?
- On a $6,000, 60-hour project, absorbing 12 hours of changes with 20% overhead cuts your real rate from $100 to about $80.65 an hour.