Website Maintenance Plans NZ: A Small Business Checklist

Website care and maintenance plans for NZ small businesses

A website quote is only part of the ownership cost. After launch, someone needs to keep the content current, handle software changes and check that visitors can still enquire or buy. A useful website maintenance plan makes those responsibilities clear.

This agency-authored guide from Auckland-based No Brainer Creative helps NZ small businesses compare care arrangements. It does not rank providers or promise a particular support response. Choose the scope around your website and the work your own team can handle.

Start with the jobs your website needs to do

List the routes that matter: a contact form, a booking calendar, an online purchase, a downloadable menu or a request for a quote. Then name the person responsible for checking each route and handling failures. An uptime alert can tell you a page is available; it does not prove an enquiry reached the right inbox.

For example, a workshop might need its service pages, phone link and booking route checked after relevant updates. A retailer may also need a controlled test of checkout, stock information and notifications. These are examples to scope with a provider, not a claim that every care plan includes them.

Compare the full ownership cost

Ask for recurring costs and one-off work separately. A lower monthly fee is not automatically better or worse: it may simply cover fewer jobs.

Hosting and domain renewal: who supplies them, who owns the accounts and when they renew.
Software and service licences: which renewals are included and which stop working when the care arrangement ends.
Routine maintenance: the update schedule, compatibility checks and documented exceptions.
Content and design changes: the included allowance, approval process, exclusions and extra-work rate.
Recovery and incidents: what is covered, what requires a separate quote and who coordinates other suppliers.
Handover: notice periods, exports, migration work and any exit charges.

Confirm the currency, GST treatment, billing period and cancellation terms in writing. For No Brainer’s current offers, see the website care section of our pricing page and confirm the scope for your site. This guide does not replace a written quote or change those offers.

Six things to ask before choosing a plan

1. What happens before and after an update?

Ask how changes are assessed, when a recent backup is taken and how important functions are checked afterwards. For WordPress sites, the official WordPress updating guide advises taking a backup before updating. Ask how the provider handles a licence issue or an incompatible extension rather than assuming every update can always be applied.

2. Can the backup restore the website you need?

WordPress recovery normally needs both website files and its database. The official WordPress backup guidance explains the distinction and bases frequency on how often the site changes. Ask what is covered, where copies are held, how long they are retained and when a restore was last tested. A screenshot showing that a backup job ran is different from a successful restore test.

3. What do the support targets actually mean?

Separate acknowledgement, diagnosis and resolution. Confirm covered hours, the time zone, severity levels, escalation contacts and any outside-hours arrangement. Do not assume weekend or public-holiday cover, or interpret a response target as a guaranteed repair deadline.

4. Which visitor journeys will be tested?

Agree an appropriate test method for forms, phone links, bookings and checkout. A button opening a form is one check; a message arriving or an authorised transaction completing is another. Testing should avoid creating unwanted customer messages, bookings or charges.

5. Who can approve content and additional work?

Define a small change, a new page and a redesign separately. Confirm whether unused time carries over and who approves extra fees. Keep a route for correcting an urgent phone number or opening-hours error without treating every request as a new build.

6. What evidence will you receive?

A useful report identifies the work completed, its date, the checks performed and anything still pending. It should distinguish an available backup from a tested restore, and a functioning form from verified delivery. Ask how you will be told about an unresolved dependency.

Choose by responsibility, not provider label

Approach	When it may fit	What to confirm
In-house care	Your team has the time and skills to own the checks.	Named cover, documented tasks and a recovery process.
Independent specialist	You need a defined set of technical or content tasks.	Availability, cover during absence, scope and handover.
Hosting or platform support	You need support for the infrastructure or subscription.	Exactly where platform responsibility ends and website work begins.
Agency care	You want agreed technical, design and content work coordinated.	Actual inclusions, approval limits, support terms and reporting.

Any of these arrangements can work when responsibilities match the need. A provider’s label alone does not establish its backup frequency, response speed or quality.

Maintain, repair or rebuild?

Maintenance keeps an existing setup usable; a repair addresses a specific fault; a rebuild changes the underlying site or its structure. Website age or platform name alone is not enough to choose between them. Identify the business requirement that the current setup cannot meet, then compare the cost and disruption of each option.

If a new build is justified, our Auckland web design service covers the planning conversation. Use the website project brief guide to record the required pages, integrations, ownership and launch responsibilities.

Questions about website maintenance

What should a website maintenance plan include?

Ask for an agreed software-update process, backups and recovery arrangements, checks of important visitor journeys, support hours and a change allowance if you need one. Hosting, licences, content work and incident recovery may be included or separately charged; confirm each item.

How much does website maintenance cost in NZ?

There is no single useful figure without a scope. Compare the fee with hosting, domain renewal, licences, content work, extra support and any migration or exit charges. Confirm the currency, GST treatment and billing period in the quote.

How often should my website be backed up?

Choose a schedule around how often important data changes and how much you can afford to lose between backups. An online store receiving orders needs a different recovery plan from an occasional brochure-site update. Confirm what is backed up, retention and a tested restore process.

Do hosted website platforms need a care plan?

Start by checking what your platform subscription already covers. You may still need someone to maintain content, integrations, permissions and enquiry routes. Avoid paying two providers for the same task, and do not assume a platform needs replacing simply because it is hosted.

Does an older website automatically need a rebuild?

No. Review the actual business requirements, usability, software support and defects first. A focused repair or content update may be enough. A rebuild should have a clear reason and an agreed migration plan.

Is a support response time the same as a repair deadline?

No. A response target usually describes when a request will be acknowledged or assessed. Resolution depends on the fault and the agreed support scope. Confirm working hours, public-holiday arrangements, escalation and what happens outside the covered period.

Can I change maintenance providers?

Check the ownership and transfer arrangements for the domain, website files, database, hosting, licences and connected services. Some subscriptions and licences may not transfer. Agree handover responsibilities, notice periods and export formats before changing providers.

Our fillable website handover record (PDF, 2 pages) provides a place to record responsibilities, renewals, recovery checks and unresolved items. Keep passwords and recovery codes out of this planning document.

A practical next step

Gather your current provider agreement, renewal dates and a short list of the website jobs that matter. Ask for a scope that identifies who does each job and how completion is checked. If you would like No Brainer to review the fit, tell us about your website; confirm any recommended work and support terms before proceeding.