How fixed-bid pricing actually works for a website project

The number that "can never change" — until it does

You signed a fixed-bid proposal thinking the number was locked no matter what happened next, and then a mid-project request came back with an extra charge attached. That's not the builder moving the goalposts. A fixed bid only locks the price to a specific, defined scope — not to whatever you end up wanting by the time the project is finished.

A fixed bid means one number for one defined piece of work. As long as the work stays inside that definition, the price doesn't move. The moment the work grows past it, the fixed part of "fixed bid" stops applying to the new piece.

Say the original scope covered a five-page site with a contact form. Partway through, you decide you also want an online booking calendar. That's a reasonable thing to want. It's also outside what the fixed number was calculated against, so it gets priced as its own addition rather than absorbed silently into the original number.

The scope document is the real price tag

The number in a fixed-bid proposal is only part of the agreement. The scope document underneath it is what that number is actually priced against. That document is supposed to spell out exactly what pages, features, and revisions are included. The dollar figure is just what that specific list costs.

A vague scope document is a warning sign regardless of how confident the number sounds. "Custom website design" as a line item tells you nothing about what's actually included. A specific scope — page count, named features, number of revision rounds, what's excluded — is what actually protects both sides later.

A strong scope document names the actual pages by title, lists specific features rather than vague categories, states how many rounds of revisions are included, and spells out what's explicitly excluded. If a proposal can't answer a plain yes-or-no question about whether something is included by pointing at a specific line, the scope isn't tight enough to hold a fixed number to.

What happens when you want something outside the scope

Wanting something that wasn't in the original scope isn't unusual by itself. It happens on most real projects. What matters is that it triggers a defined process — usually a change order — rather than a silent argument about whether it was supposed to be included.

Ask, before you sign, exactly what that process looks like. A written estimate for the addition, sent before the work starts, is a good sign. Work that just shows up on the next invoice with no advance notice is not.

This is also where a fixed bid can go wrong for the builder, not just for you. A scope that was vague enough to let extra work slip in unpriced hurts whoever absorbed it, and that pressure tends to show up later as rushed work or corners cut elsewhere on the project.

A good process leaves a paper trail on both sides: a request in writing, an estimate for the addition, and your approval before the extra work begins. That trail is what keeps a disagreement about scope from turning into a guessing match later.

Who a fixed bid actually benefits

A fixed bid suits a project you can already describe in real detail — you know the pages, the features, and roughly what the content will be. Certainty about the number is worth the most when the scope itself isn't likely to shift much.

It benefits less when you're still figuring out what the site needs to do. Locking a number to a fuzzy scope just moves the fuzziness into a fight over what counts as in scope later, instead of avoiding it.

Compare that to a project where you're still deciding whether you even want a blog section or a members area. Locking a fixed number to a scope that's still moving means somebody has to guess, and guesses tend to get padded to cover the guesser's own risk.

That's often where a fixed bid ends up costing more than it should — not because the model itself is unfair, but because it got applied before the project was ready for it. Wait until the pages and features are settled, then ask for the fixed number, rather than the other way around.

Signs a fixed bid is too vague to hold anyone to

A one-line scope next to a specific dollar figure is the biggest red flag. So is a proposal with no revision count, no named deliverables, and no list of exclusions. The number looks precise. The thing it's attached to isn't.

Before signing, ask to see the actual page list, the specific features named individually, and the number of revision rounds spelled out as a number rather than a word like "reasonable." If those answers require a follow-up conversation to pin down, get them pinned down in writing before the number becomes final.

Comparing that proposal against others is hard when the scope behind the number is this thin, because you can't tell what you'd actually be paying for versus what a more detailed proposal already spells out. Ask for the detail before you compare, not after you've signed.

What actually sets a project's price is the scope. A fixed bid without a real scope document is just a guess wearing a specific number.

One more habit worth building: keep a copy of the signed scope document somewhere you can find it fast, not buried in an old email thread. If a question about what's included ever comes up months into the project, you want to be able to check the actual language in minutes, not go digging.

More from the blog

All posts