What happens to the price when you change your mind mid-project

When "just one more page" turns into an invoice

You asked for one more page halfway through the build, and a few days later there's a bill for it you didn't expect. That's usually not a scam. It's a sign that nobody defined, before the project started, where a normal request stops and a scope change begins.

That gap between what you assumed and what actually happened is one of the more common complaints about website projects — not because builders are being dishonest, but because "fixed" or "included" quietly got attached to a scope in your head that was never written down anywhere.

A revision adjusts something already inside the agreed scope: a color, a headline, a layout tweak on a page that was always part of the plan. A scope change adds something that wasn't part of the plan at all — a new page, a new feature, an integration nobody discussed before the contract was signed.

The line between the two isn't always obvious in the moment it comes up. Swapping one photo for another is a revision. Adding a whole new section with its own photos, copy, and layout is a scope change, even when it feels like a small ask from where you're sitting.

What actually sets the price on a project also sets what a change to that project costs — the scope itself, not which billing model was chosen to bill it.

A request that feels tiny to ask for can still mean real, paid work on the other end, which is exactly why the definition needs to live in the contract instead of in anyone's gut feeling about how big the ask sounds. A designer who has priced this kind of addition before can usually give you a straight answer on the spot rather than a guess.

Revision rounds, and where a round stops being included

A fixed-scope agreement names a specific number of revision rounds inside the price — two rounds, three rounds, whatever the proposal states. Every round past that number is billable as extra work, even when the request feels like a small continuation of the same conversation you were already having.

A round doesn't reset just because you asked for something new inside it. If your agreement covers two rounds and you're deep into feedback on a third, that's the point where "included" quietly stops applying, whether or not anyone says so out loud at the time.

How much of your own time the feedback process actually takes shapes this more than people expect going in. A round that drags because feedback trickles in over several separate messages can burn through the included count faster than a round handled in one focused pass.

Ask, before the project starts, exactly how many rounds are included and what happens once you're past that number. That answer belongs in the same conversation as the price itself, not a surprise discovered midway through a fourth round of notes.

How change orders usually get documented

A change order is a written record of three things: what's being added, what it affects in the existing build, and what it adds to the price or the timeline. It doesn't need to be a formal legal document. It needs to exist in writing before the new work starts, not after it's already done.

A short example helps. Say you ask for a members-only login area that wasn't in the original plan. A documented change order describes what that area needs to do, how it affects the existing site structure, and what it adds to the price and timeline before a single line of code changes.

Without a written change order, you're relying on memory and goodwill to settle a disagreement weeks later, when neither side remembers the conversation the same way. With one, both sides signed off on the same understanding at the moment the request was made.

That single record is what turns "I thought that was included" into a settled question instead of an argument.

Ask what the change order process actually looks like before you need one. Some builders send a short written estimate for approval before touching anything; others fold small changes into the next invoice with a line-item note. Neither is wrong, but you want to know which one you're dealing with.

Small tweak or change order — how to tell

A useful test: does the request change something already built, or does it add something new? Tweaks adjust what exists. Change orders add what doesn't exist yet. If you're asking for a new capability, a new page, or a new integration, assume it counts as a change order and ask directly rather than guessing.

Some categories are almost always change orders regardless of how they're phrased: a new integration with an outside tool, a feature that touches how the site is structured, or content that needs to live somewhere the original site map didn't account for. When in doubt, ask before assuming it's covered.

Don't judge it by how much effort the request feels like from your side. A request that sounds small to you can mean real rework on a structure that was built around a different layout. The honest move is to ask how a specific request will be treated before assuming it's free.

Get the pricing method settled before you need it

The best time to ask how change orders get priced is before the project starts, not in the middle of one. Get a straight answer: is it billed at an hourly rate, a flat fee per addition, or folded into a revised version of the fixed bid you originally agreed to?

If the answer is hourly, ask for a rough sense of how long the specific kind of addition usually takes, even if it's not exact. If it's a flat fee, ask what determines that fee for something you haven't specified yet. Either answer gives you something to hold the eventual number up against.

That question, asked early, tells you a lot about how the rest of the relationship will run. A builder who answers clearly, with a specific method, is easier to plan around. One who waves the question off is handing you an open-ended risk you haven't agreed to yet.

Write the answer down somewhere you'll actually look at it again. A verbal answer during a sales call is easy to forget three months into the build.

Keep your own paper trail

Don't rely on the builder to document every request on your behalf. Keep your own record — an email, a message thread, a shared doc, whatever you'll actually maintain — of what you asked for and when you asked for it. If a change order shows up that doesn't match what you remember requesting, you'll have something concrete to check it against.

This habit protects you in the other direction too. If something you assumed was already included in the quote turns out not to be, your own notes are the fastest way to sort out whether that's a genuine misunderstanding or a legitimate addition.

The same discipline applies to how many rounds of feedback were part of the original agreement. Write down what was promised when you agree to it, not later, while trying to reconstruct it from memory in the middle of a dispute.

A paper trail doesn't assume bad faith on anyone's part. It just means a disagreement, if one happens, gets settled by looking something up instead of by whoever argues harder.

More from the blog

All posts