Scope Creep: How to Price Change Requests Without Losing the Client

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.

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.

Tip: Absorbing one tiny change as goodwill is fine. Say so explicitly ("no charge for this one") so it doesn't become the expectation.