You asked for a five-page website. The quote says five pages, a contact form and two rounds of revisions. Six weeks later the invoice is 40% higher, because "five pages" turned out to mean five templates, the contact form needed a CRM integration, and every email you sent counted as a revision round. This is the most common way a Hong Kong SME website budget goes off the rails, and it is almost always fixable before you sign.
Start with a page inventory, not a page count
"Five pages" is not a scope. It is a number that two people can interpret in completely different ways. Before you ask for a quote, write down every page you expect to exist on launch day, and mark what kind of page each one is.
- Static pages: Home, About, Contact. One layout each, written once, edited rarely.
- Template pages: Services, Products, Blog posts. One design, many entries. The design cost is shared, but the content cost is not.
- Functional pages: Booking, quote request, member login. These carry logic and integrations, and they are where quotes usually break.
Put this list in the quote as an appendix. If the developer writes "10 pages" and you have listed 10, you both know what is in and what is out. If they write "up to 10 pages" and you have listed 14, you have just found the first line item that will come back as a change order.
Count content, not just screens
A page that needs 600 words of copy, three product photos and a downloadable PDF is a different job from a page that needs a headline and a phone number. Ask the developer to state, per page, who supplies the words and images. If the answer is "you do", that is fine, but it needs to be in the quote so nobody assumes a copywriter is included.
Write features as behaviours, not labels
"Contact form" is a label. "A form with name, email and message that sends to info@ and shows a thank-you page" is a behaviour. The gap between those two descriptions is where most disputes start, because a form that also needs to create a lead in your CRM, notify a WhatsApp group and block spam is three extra pieces of work.
For each feature, write one sentence in this shape: when [someone does X], the site should [do Y], and if [Z happens], it should [do W]. For example: when a visitor submits the quote form, the site should email the sales inbox and store the entry in the admin panel; if the email fails, the visitor should still see a confirmation and the entry should remain saved. That single sentence tells you whether the quote has priced the integration, the storage and the error handling, or just the form itself.
Separate must-have from phase-two
List every feature you want, then draw a line. Above the line: what the site cannot launch without. Below the line: what would be nice in six months. Ask for the phase-two items to be priced separately, even if you do not buy them now. You get a real number for later, and you find out early whether the developer has actually thought about the work. If you want help turning this list into a brief a developer can price, our team can walk through it with you via the contact page.
Define what counts as a revision round
"Two rounds of revisions" sounds generous until you discover that a round means one consolidated email, and that a new page request counts as a new round. The fix is to define three things in the quote:
- What a round is: one batch of written feedback, sent within a stated number of working days of the review link going live.
- What a round covers: changes to content within the agreed layout, not new layouts, new pages or new features.
- What happens after the rounds run out: the hourly rate for further changes, stated in the quote.
Also agree what "done" looks like at each stage. A design sign-off, a content sign-off and a pre-launch sign-off are three different gates, and each one should be listed. Without them, feedback arrives after the build, when every change is expensive.
Put the change process in writing
Even a well-scoped project will change. The question is whether the change is priced before or after the work. Ask for a one-line process: any request outside the appendix gets a written estimate and your approval before work starts. That single sentence protects both sides, and it makes the difference between a fixed quote and an open tab.
A short checklist before you sign
- Page inventory attached, with each page marked static, template or functional.
- Each feature described as a behaviour, with integrations named.
- Number of revision rounds stated, plus the definition of a round.
- Hourly rate for out-of-scope work written in the quote.
- Sign-off gates listed with dates.
- Who supplies copy and images, per page.
None of this requires technical knowledge. It requires you to write down what you expect before anyone starts building, and to ask the developer to confirm it in the same document. If you are comparing two quotes and only one of them has a scope appendix, you are not comparing prices. You are comparing one fixed number with one unknown. For a broader view of how quotes are structured, see our pricing page, and use the checklist above as the lens.