Most Hong Kong SME owners sign a website quote the way they sign a lease: glance at the total, check the deposit, sign. The deposit is usually the only number that gets real attention, because it is the only number that leaves the bank account on day one. Everything after that is assumed to be someone else's problem until the invoice arrives.
That assumption is where cash-flow trouble starts. A website build is a long project with many handoffs, and the payment schedule is the only lever you hold over how the risk is shared. Get the milestones wrong and you can end up having paid most of the fee before a single page is live.
Why the deposit is not the risky part
A deposit of 30 to 50 percent is normal and reasonable. It covers the supplier's initial work and signals commitment. The risk sits in what comes after: the middle payments. If a quote asks for 40 percent on "design approval" and 30 percent on "development start", you have handed over 70 percent of the money before anything has been tested on a real phone, on a real connection, by a real customer.
Ask a simple question of any schedule: at the moment I make each payment, what can I actually see and use? If the honest answer is "a PDF mock-up" or "a promise", the milestone is too early.
Milestones that map to things you can check
Good milestones are tied to verifiable output, not to phases of the supplier's internal process. A workable structure for a typical SME site looks like this:
- Kick-off (20–30 percent): paid on signing, after the scope document and page list are agreed in writing.
- Design sign-off (20 percent): paid when you approve final designs for every template, not just the homepage.
- Staging build (25 percent): paid when a working site exists on a staging URL that you can click through on your own phone, with forms sending test emails to your inbox.
- Launch (25 percent): paid after the site is live on your domain, redirects work, and you have admin access in your own name.
Note what is missing: there is no large payment for "development". Development is the longest and least visible phase, and paying heavily for it puts you in the weakest position. If the supplier disappears mid-build, you want the unpaid balance to be large enough to matter to them.
Hold back a retention amount
On projects above a few tens of thousands of dollars, consider holding 10 percent for 30 days after launch. This is standard in construction and it works here too: it covers the broken contact form, the missing redirect, the mobile menu that does not close. Without it, every post-launch fix competes with the supplier's next paying client.
The cash-flow risk nobody prices in
The obvious risk is paying too much too early. The less obvious one is the delay cost. A website that was meant to launch before a trade show or a seasonal peak, and slips by six weeks, has a cost that never appears on any invoice. Your deposit is gone, your launch window is gone, and you are still paying for the old site's hosting.
Two clauses reduce this exposure. First, put dates in the schedule and tie each payment to the supplier hitting that date, not just to the deliverable existing. Second, agree in writing what happens if the delay is on your side, for example waiting on product photos or copy. A fair contract pauses the clock rather than penalising either party, but it must be written down before the argument.
If a supplier resists putting dates and deliverable definitions in the payment schedule, that resistance is itself information about how the project will run.
Protecting yourself when the project stalls
Before the first payment, confirm four things in writing:
- Who owns the code, the design files and the domain, and at what point ownership transfers to you.
- That the domain and hosting accounts are registered in your company's name, with you holding the login.
- That staging access is provided from the mid-point, so you can see progress without asking.
- What happens to work completed if either side ends the project early, and how the unpaid balance is calculated.
That last point matters more than it sounds. If you have paid 70 percent and the relationship breaks down, you want a documented answer to "what do I actually own right now". A staged handover, with files transferred at each milestone, makes the answer obvious.
If you are still shaping the budget around these payments, it helps to see how the total is built before you negotiate the schedule. Our transparent pricing breakdown sets out what each phase of a build typically covers, which makes it easier to judge whether a milestone is priced sensibly. And if you would rather talk through a specific quote before signing, get in touch and we will read the payment terms with you.
Summary
The deposit is rarely the problem. The danger is a schedule that front-loads payments against invisible work, leaving you with little leverage if the build stalls. Tie each payment to something you can click, test or log into; keep the largest balance until launch; hold back a small retention for post-launch fixes; and put dates, ownership and early-exit terms in writing before money moves. A well-structured schedule does not just protect your cash, it gives the supplier a clear reason to keep the project moving.