Why a Website Budget Beats a Website Quote
Most Hong Kong SME owners treat the website as a one-off purchase. They compare three quotes, pick one, pay, and then stop thinking about it. Eighteen months later the site is slow, the contact form is broken, and nobody remembers who set up the hosting.
The quote is the easy part. The harder question is what the site costs you every year after launch. This article is not about judging whether a quote is fair — it is about building a yearly budget line so the site never becomes an emergency expense.
Start With a Simple Inventory
Before you can budget, list what you already pay for. Open your bank statements and card statements for the last twelve months and look for anything with these names:
- Domain registrar (often HK$100–300 per year, easy to forget)
- Web hosting or cloud server
- SSL certificate, if not bundled with hosting
- CMS or plugin licences (paid themes, form plugins, booking tools)
- Email service tied to the domain
- Backup or monitoring service
- Any agency retainer for support or updates
Write the annual total down. Many SMEs discover they are paying for two hosting accounts because a previous developer never cancelled one. That is money you can redirect into maintenance.
The Three Buckets
Group every line item into one of three buckets. This makes the budget readable and stops you from arguing about individual invoices.
| Bucket | What it covers | Behaviour |
|---|---|---|
| Keep-alive | Domain, hosting, SSL, email, backups | Fixed, predictable, renews automatically |
| Maintenance | CMS and plugin updates, security patching, small fixes | Recurring but variable |
| Change | New pages, redesign, integrations, content refresh | Lumpy, planned in advance |
Keep-alive costs are non-negotiable. Maintenance is where most SMEs under-budget. Change is where the big numbers live and where planning pays off.
Reserve a Maintenance Percentage
A common industry rule of thumb is to set aside roughly 10–20% of the original build cost per year for maintenance and small improvements. Treat it as a planning anchor, not a law. A brochure site with five pages needs far less than a site with a booking engine, a member login and a payment gateway.
Two factors push you toward the higher end:
- Plugins and integrations. Every third-party component is a thing that can break after an update.
- Customer data. If the site stores enquiries, bookings or account details, patching is not optional.
If you have no idea what your build originally cost, use last year's actual maintenance spend as the baseline and add a margin for the next twelve months.
Build a Security Line Item
Security is the item SMEs most often leave out, and the one that produces the largest surprise bills. Hong Kong has been running structured cyber defence exercises that simulate real attack scenarios against participating organisations, and the consistent lesson from those exercises is that unpatched, unmonitored systems are the ones that fall first.
Translate that into a budget line. Even a modest monthly amount for monitoring, backups and patch management is cheaper than a single incident response. If you are unsure what belongs in that line, the scope of support we provide is a useful reference point — see our pricing page for how support and maintenance are typically structured.
Plan the Change Budget on a Three-Year Cycle
Websites age. Design trends move, mobile behaviour changes, and search engines adjust what they reward. Rather than pretending a site lasts forever, plan for a meaningful refresh every three years.
- Year 1: Launch. Budget mostly keep-alive plus a small buffer for post-launch fixes.
- Year 2: Maintenance plus one or two content or conversion improvements based on what analytics show.
- Year 3: Start funding the refresh. Set aside a monthly amount from January so the spend is absorbed rather than shocking.
This cycle also gives you a natural moment to renegotiate hosting and support, because you will have three years of invoices to compare against.
Decide Who Does the Work
Every budget needs an owner. If nobody internally can update plugins, take backups and check that forms still submit, that work has to be paid for. The cheapest option is not always the agency — sometimes it is a part-time staff member with clear instructions and a checklist. What matters is that the responsibility is named, not assumed.
Write it into the budget document: who does updates, how often, and what happens if they are unavailable. If you would rather hand the whole thing over, talk to us about a support arrangement before the next renewal date, not after something breaks.
Review the Budget Twice a Year
A yearly budget that is never opened is just a document. Put two review dates in the calendar — one mid-year, one before renewal season — and check three things:
- Are any subscriptions no longer used?
- Has anything changed about how the site collects or stores customer data?
- Is the change fund on track for the refresh?
Cancelling one unused subscription per year often funds an entire security monitoring plan.
Summary
Budget your website like a running cost, not a purchase. Inventory what you already pay, split it into keep-alive, maintenance and change buckets, reserve roughly 10–20% of build cost per year for upkeep, add an explicit security line, and fund a refresh on a three-year cycle. Name an owner for the maintenance work and review the numbers twice a year. Do that, and the next invoice you receive will be a planned expense rather than a shock.