Fixed scope, explained: how to buy a website without surprises
What a good scope lists, how revision rounds and changes should work, and why paying in stages protects both sides.
Most website projects that go wrong don't fail on design or code. They fail on a misunderstanding: you thought something was included, the person building it didn't. A fixed scope is how you avoid that.
What a scope should say
A scope is a short written list of what you're getting. Before you agree to anything, check that it covers:
- What's being built. The pages, and anything that works behind them, like an enquiry form or an automatic reply.
- What isn't included. Copywriting, photography and logo design are common gaps.
- How many revision rounds you get, and what counts as a round.
- The timeline, and what it depends on (usually your content and feedback arriving on time).
- The price and the payment stages.
- Who owns what at the end: the domain, the code and the accounts.
If any of these are missing, ask. A good builder will be glad you did.
Revision rounds
A round is one set of changes, sent together, to one version of the design. "Two rounds" means you can review, ask for changes, review again and ask for changes once more.
The trick is to collect all your feedback before you send it. Ten changes in one message are one round; ten changes in ten messages can quietly turn into ten.
When you want something new
Halfway through, you'll think of something else. That's normal. The fair way to handle it is a change: it's described, priced and agreed in writing before anyone starts on it. That way the original price stays the original price, and the new piece has its own.
Be wary of "we'll sort it out at the end". That's how a fixed price stops being fixed.
Why pay in stages
Paying everything up front leaves you with all the risk. Paying everything at the end leaves the builder with all of it. Stages split it fairly: you pay for one part, it's done and approved, then the next part starts.
A common pattern is a payment to start, one when the design is approved, and the last before launch. Each stage starting only once its payment clears keeps everyone honest, and keeps the work moving.
Make sure you own it
When the last payment is made, the domain, the code and every account should be in your name. If you ever want to move to someone else, you should be able to, without asking permission.
A one-line test
Before you sign, ask yourself: if the person building this disappeared tomorrow, would I know exactly what I'd paid for, and could I take it elsewhere? If the answer is yes, your scope is doing its job.
